-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this repo still maintained? #322
Comments
Right now no. I would be totally happy if others wanted to join as a contributor and/or maintainer. It would be great to get the help. For anyone interested feel to reach out to me either on twitter or via this issue.
Good idea (will happily merge a PR if you add that section!). I will also pin this issue so hopefully others can see it. |
@thoov I'd like to join as a contributor. Our team is using this awesome package and we'd like to continue using it. There are already some PR's we want to be merged |
@Atrue thank you! and I will set you up as a contributor |
@Atrue I added you to NPM so you should now be able to publish |
Dear @thoov ,
Thanks for providing this awesome package! I saw that despite its popularity there has not been much maintenance in recent months or years. I was wondering if it would be a good idea to reach out to the community, trying to get two or three people on board to take care of at least some basic maintenance, updating the npm package, checking MRs and so forth.
Repos that remain unmaintained can become a security risk without users and former maintainers noticing. That would be a shame to happen.
Looking forward what you and others think about that. Oppinions? I'm hoping that this will lead to some maintenance plan or similar. E.g. a simple tag in the
README.md
yelling "maintainers wanted" would be a good starting point.Best regards from Berlin
Marius
The text was updated successfully, but these errors were encountered: