Grunt needs your help!

[cowboy]

We're looking for some help maintaining Grunt. Are you interested?

There are a number of specific things the project needs, such as:

• General grunt and grunt-cli maintenance
• Grunt contrib plugin maintenance
• Website / docs maintenance
• Issue triage
• New features (version 1.0? 2.0? The future!)

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!

[arthurakay]

I'd be willing to help in just about any way.

[morkro]

I am interested 👍
I would like to help out with website/ docs maintenance, and plugin maintenance. But basically everything sounds interesting.

[dsalvagni]

👍 I'm interested!

[tomapp]

I'm in! 👍

[pbrdmn]

I can help with website / docs.

[geoffdavis92]

I'd be interested in website/docs maintenance.

[rpdiss]

I can help too 👍

[kaapa-s]

I'm in, I'll do some node.js 👍

[mariuszbeltowski]

I am interested!

[verpixelt]

Count me in for the website (docs).

[lelui12cr]

I can help with website (docs)

[scurker]

I've been looking for ways I can get more involved in open source projects, so I'm definitely interested! I think I'd be willing to help out wherever I could.

[danieltott]

I am also interested!

[dperrymorrow]

would be willing to help with anything, but website / docs I may be of most use.

[jshemas]

I'm very interested and would like to help!

[jshrssll]

Can definitely help with the website & docs

[kaiquewdev]

Count me in!

[mitchellsimoens]

Interested in helping with anything

[cyprianos]

I can help with grunt and grunt plugin maintenance.

[claudiamatosa]

I'd be willing to help. Particularly interested in new feature development, but would be happy to help in any of the other areas!

[callumsong]

Not sure if I'm capable but would love to help in anyway I can!

[matricore]

im here. pick me.

[educostachaves]

I wish!

[dancasttro]

I can help with website / docs too.

[svenkeeter]

sure... will help anyway i can

[padsbanger]

I can help with site and docs. Count me in !

[Server4001]

Willing to help with grunt, grunt-cli, contrib, site and docs!

[mattkime]

i'd love to pitch in where i can.

this isn't the typical way of an open source project getting contributors but i kinda like it!

[sashashakun]

Ready to help anyway I can! May be docs or website maintenance

[danparm]

Still a Node and Grunt grasshopper. However I'm using Grunt more heavily at the company I work for and working it into our everyday development. Definitely interested in helping.

[wayspurrchen]

Also happy to pitch in a little here and there. I'm particularly fond of documentation but I can do maintenance work as well.

[ghost]

Yep, sign me up. Can help with Grunt maintenance

[christopher-akins]

I'm definitely interested!

[duereg]

👍

[doron2402]

👍

[vladikoff]

What does 👍 mean in this case? are you happy to help with everything? some of it?

[karuto]

Count me in 👍

[hyeomans]

👍

[JulienItard]

I could help with french translation

[kimwooglae]

I'm interested

[kasiriveni]

Definetely I'm in.

[ivanzhaowy]

I'm interested in impelementations of new features. I used grunt everywhere in my projects during every work, and I do have some feature requests about this great tool.

[fscherwi]

I'm interested to and will help where i can! 👍

[ehhc]

I would be interested in helping as well. I would like to help in general grunt or grunt-cli maintenance but I haven't done a lot with node.js so I might not be that helpful...

[johnnonolan]

docs/some coding we use grunt a lot so it would be good to give back.

[Mark-Towndrow]

I'm interested

[Ykid]

program in nodejs for around 4 months full time. would like to help. could do some maintenance jobs.

[battaile]

I'd like to help, Issue triage and handling minor issues initially.

[ntrphanikumar]

I would like to contribute too

[JulioMontas]

Hey I can help with the Website (Design) / docs maintenance and any design promotion to help GruntJS to keep growing for new users.

[hitenv]

Happy to help where I can

[abhi05b]

Willing to contribute... :)

[mflores88]

I would love to contribute with docs and website :)

[LuisRBarreras]

I'm interested

[jrcryer]

👍

[dmethvin]

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:

• Triage the open issues. If the issue is unclear or the OP doesn't reply to questions, assume it's dead/stale. If an issue is really important, people will come back and make their case.
• Triage the open pull requests. Some of them are years old and most likely can't be merged. Let's get that cleared up and find out what is really usable.
• Once we've assessed where we are, take unassigned issues and start creating pull requests.

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!

[vladikoff]

For those who want to contribute with code / review / testing, here are two pull requests:

• "Add support for Gruntfile.babel.js" - Add support for Gruntfile.babel.js #1368 Could you review this PR or test this with your babel project?
• "Update findup-sync to 0.3.0 and lodash to 3.10.1" - https://github.com/gruntjs/grunt/pull/1406/files Same thing, could you pull in that particular version and see if it breaks anything. Large projects that use Grunt would be helpful for testing.

Feel free to comment in those issues. Let me know in those issues if you have any questions.