Who would like to Fork this and continue the dev from there?

[GeorgeWL]

The Maintainer hasn't updated in two years. I'd be fine with forking it if could get some other maintainers to join.

@wcandillon @framerate @pcgeekbrain

[framerate]

I think everyone has moved on to linter/linter-eslint packages :/

[Joezo]

I've actually moved to using the linter and linter-plugin packages too. If someone does want to work on this though i'm happy to accept PRs and give active maintainers the privileges they'd need.

[GeorgeWL]

I have just realised that I moved to using that too, was there any features this provided that linter doesn't?

Otherwise it might even make sense to remove this from the APM completely as a defunct project, then we'll stop getting random pings about bugs that haven't been fixed for two years after someone downloads it.

[Joezo]

I think most people think they're using this when in fact they're using linter. This project offers nothing on top of linter but does offer a lot less... I keep meaning to see if there is an apm deprecate.

[GeorgeWL]

one I've seen used often is to change the name to title [DEPRECATED]

and the description to something like

This project is now defunct on Atom version X.x.x and higher as all the features and more are covered by [other Project link](example.com)

Also there's folks working on defining a apm deprecate but it doesn't exist yet https://github.com/atom/apm/issues/351

If you would rather have the package not published at all though, they have already got a apm unpublish command.

I just remembered why I was orginally using this package though, University PCs are incredibly locked down on what apps and they don't allow app updates, I couldn't have eslint, but this one worked on the version the University PCs had.

[GeorgeWL]

oh and unpublish also let's you unpublish specific versions

[andre-morassut]

+1 for updating the title as GeorgeWL suggested. Could save time for people.