Contributors needed for maintenance and development
holtkamp opened this issue · 10 comments
I noticed that this library does not receive the time and energy it deserves. This delays merging of Pull Requests and answering to issue reports;
@longbill is the original maintainer who granted me the privileges needed to maintain this library. Maybe it is good to start looking for more people who want to contribute so @longbill can contact them.
Anybody interested?
Coming over from #441 to chat about this.
I am interested in becoming a maintainer, as we use this library extensively and I think there's a really good base to build upon.
I am a bit cautious, however, since it seems that the project is not really maintained right now and I can't say I have that much free time. I would probably not be able to actively maintain it completely on my own. Do you plan to stay as a maintainer or are you looking for a replacement? Also, is @longbill active anymore?
I think there is plenty of room for improvement in this plugin, starting from file structure & plugin architecture, organizational details (readmes, publishing, versioning, etc) and npm publishing. After consolidating these I think we can start pruning PRs and issues, as there are many leftovers from what I see. The next step, before merging any valid PR or doing anything else on the codebase, in my opinion, would be to add unit and integration testing. I feel like this is vital for further updates.
Awesome stance @monovertex !
The reason I am a "maintainer" is because one of the projects I am working on uses this library and I found some bugs. But I am not a JavaScript developer and all the "new" possibilities like plugins, isolating the language files, or Gulp tasks are a real challenge for me, for which I do not have really time to dive into.
So I am not really maintaining it, just trying to keep it alive. Merge "obvious" PR's, respond to questions etc. Someone with a bit more knowledge who can help out once in a while is really appreciated!
@longbill seems to be monitoring the project, but not actively participating. @longbill what do you think? Can you add @monovertex as a maintainer?
If I organize a plan and guidelines for PRs / issues, would you at least be available for triage? Stuff like assigning labels, pointing out that PRs / issues don't meet requirements, closing old / irrelevant issues? It would be pretty much what the work you were doing so far, but I'd like to have a more organized approach, so that we can manage the big amount of issues.
#404 (comment) sure!
@holtkamp, please drop me a mail at cos.stamate@gmail.com, so that we can chat some more about what I mentioned, once I become a contributor and we can start filtering the PRs and the issues.
@monovertex I am sorry that I have not interests on front-end projects now. I am focusing on node.js now. Let me add you to the maintainer list. Thanks for your contribution!
@longbill, no worries. Thank you for the invite and thank you for the work on this plugin!
this library is dead? 💀
It is not dead, just not under active development. I am actively answering and triaging issues, but unfortunately I did not find the time I wanted for development. PRs are welcome!