Maintenance is frozen #177
Open
Comments
Thanks for letting people know! I've watched so many repos where support quietly disappears leaving open source contributors wondering what is going on. I would consider taking over maintainership, though it would obviously be up to Kent as to whether he would trust me with that role. I've helped out here occasionally, though most of my work thus far has been on iter-tools (283 commits) and macrome. |
I was thinking of all people you would be the most likely to hand over ownership to. I think it would probably be ok. The event-stream incident just has me a little paranoid Just ping me when there's a PR needing my attention, but really I think we're mostly done anyway so |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
kentcdodds commentedMay 13, 2021
I'm no longer watching this repo. This babel plugin is pretty much done and I'm no longer using it much. If you really need something changed, then I suggest you fork it.
Unfortunately, this plugin is so widely used that it would be irresponsible for me to hand over publish rights to someone I don't know and trust. So I'm basically freezing development unless someone who fits that description wants to take it over.
I might be willing to accept a PR to keep this project up-to-date for compatibility reasons with babel. But in general, there's no more maintenance that will happen on this package. Thanks for understanding.
The text was updated successfully, but these errors were encountered: