Grunt needs your help! #1403
We're looking for some help maintaining Grunt. Are you interested?
There are a number of specific things the project needs, such as:
If you're interested, please reply in this thread. Let us know how you're interested in helping, and we'll figure out where to go from there. Thanks!
UPDATED: Please read the post at the bottom. Contributions and new helpers welcome!
The text was updated successfully, but these errors were encountered:
Wow, thank you everyone! I'm closing this thread to new comments, but if you are interested and haven't commented please read on, it's never too late to contribute.
If you haven't done so already, please read the contributing page. Most of the information there is relatively up to date and certainly enough to get things started. In particular, the #grunt-dev channel on IRC is a good place for real-time discussion and the contributing page can help you get started if you've never used IRC.
Now that Grunt is part of the jQuery Foundation we'll be switching to the jQuery Foundation CLA so please sign there if you haven't yet. Soon we'll have a bot that checks pull requests to ensure that the contributor has signed the CLA. A typical interaction with the bot looks like this if you haven't yet signed. Be sure that the email and name use use on your git commits matches the one you use to sign the CLA.
So what about working on the project? For now I would anticipate a 0.4.6 that is a very conservative set of bug fixes and minor enhancements. Stuff is already tagged for that release but it seems like a lot, so if there is any doubt or a lack of someone to do the work it might be better to push it off until later.
For the longer term it seems safer to come out with Grunt 1.0.0 and start actually using Semver because anything but trivial changes will probably break a lot of existing Grunt setups. A good example is this ticket about a message. Grunt is used widely enough that even its messages can't be changed! At least with a major Semver bump people can be a little more prepared.
So, eager volunteers, here is what I recommend as a starting point:
When doing this work, it's best to spend some time looking at an issue and understanding where it was left off. Instead of just bumping a PR with a comment like "Does anyone know where this stands?" you could say, "I tried merging the PR with the current master and it's really out of date, lots of merge conflicts. Should we close this?"
Once it's clear who the active volunteers are over the next couple of weeks, we'll be trying to organize a more permanent team of people who can form the ongoing Grunt team. For the folks who volunteered to do docs and web sites, I think that work will lag the actual code work by a bit. Once we have the code under control there will definitely be a need to update things. Stay tuned!
For those who want to contribute with code / review / testing, here are two pull requests:
Feel free to comment in those issues. Let me know in those issues if you have any questions.