You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No commits have been pushed or pull requests merged in nearly a year and nobody seems to be checking active pull requests, so has this repository and published package been abandoned by all current maintainers? This is especially of concern due to #136 being a soon-to-be critical blocker for any further use of the package in new ember projects.
If this is the case, an organization called adopted-ember-addons can handle giving access to new maintainers and it can also do future npm publishing.
There is also a dispute process to obtain publishing rights from abandoned npm packages, as well.
The text was updated successfully, but these errors were encountered:
I haven't been using this add-on at work or personally since May 2018. I'd be happy to re-allocate some time to maintaining/updating the package, but I've never had npm publish permissions. The last npm publish was April 2017. Even if we do the work of updating things to work with the latest versions of ember (Octane), I'm not sure it'd be possible to get it published without going through the dispute process with NPM. Even back a couple years ago when I was more active on this project I had trouble getting assistance from @asennikov to publish on npm.
No commits have been pushed or pull requests merged in nearly a year and nobody seems to be checking active pull requests, so has this repository and published package been abandoned by all current maintainers? This is especially of concern due to #136 being a soon-to-be critical blocker for any further use of the package in new ember projects.
If this is the case, an organization called adopted-ember-addons can handle giving access to new maintainers and it can also do future npm publishing.
There is also a dispute process to obtain publishing rights from abandoned npm packages, as well.
The text was updated successfully, but these errors were encountered: