umbrella

In my experience[1] the best way to get contributors is exactly the opposite, you have to leave the easy and cool parts for new people and do all the grunt work by yourself. Making a new feature is something fun that other contributors can try to do and learn a lot, while optimizing your website is something that mostly only saves you money (as contributors could do that virtually anywhere else and learn the same). See an example of what I mean: [2] [1] http://github.com/franciscop/ [2] https://github.com/umbrellajs/umbrella/issues?utf8=%E2%9C%93...

What I do is keep bundling things together in a dev branch for a while and wait until I have to introduce a breaking change to release it all as a major version. Of course only with smaller projects where a new feature might be 3-4h of work, I cannot think Node.js waiting to introduce new features just for doing a marketing stunt. Example: https://github.com/umbrellajs/umbrella/milestone/8?closed=1

I discovered another way of getting contributors with Umbrella JS [1] (500+ stars), using up-for-grabs [2][3]. In total I'd say it's similar or even a bit more of effort per issue, however many people contribute and sometimes they step up and continue with more things. Not sure how useful it is for projects that are more monolithic though, I was lucky with this one as Umbrella JS has many small modular parts. [1] http://umbrellajs.com/ [2] http://up-for-grabs.net/ [3] https://github.com/umbrellajs/umbrella/issues?q=is%3Aissue+l...

An anecdote [1] about "No is temporary, Yes is forever": 4 months ago: However, please read the notes in Roadmap and new features before continuing with this work, as I'm not yet sure whether or not they are within the scope of Umbrella [...] 4 months ago: I don't think it's a good idea to change it, so only Strings will be available for after, before, etc. 3 months ago: I opened it to implement what was suggested here. 3 months ago: Okay, it was added. [1] https://github.com/umbrellajs/umbrella/issues/20

I'm going to propose one of my own[1], since I can do few projects without time limit (for fun) so I did my best to properly program, test and document it. I overcommented on the past but I'm trying to correct it now. Also, all of the new contributors follow the same style so things stay consistent. As an example, let's try to understand the function `.addClass`: - Just to use it you can see the documentation on the website[2], which is the first contact normally. - Then when you try to find the relevant files. They are in github's `src/plugins/addclass`, a name that is common and intuitive [3]. - Not only that, but you also got the documentation in that folder in github thanks to the name `readme.md`. - When opening it [4], the first thing that you note is that the function has a tiny footprint; 8 lines. A brief explanation of what it do

Yes they do with phantomJS [1] for example (see badge working example [2]) [1] http://phantomjs.org/ [2] github.com/umbrellajs/umbrella

Browser compatibility [1], array handling instead of just single elements, chainability and flexibility come high up in my list. These are important mainly when there are several elements and not just one. [1] https://github.com/umbrellajs/umbrella/blob/master/src/plugi...

GitHub actually shows a README file for each directory (if one exists), so the recommendation was to change /src/plugins/x/documentation.md to /src/plugins/x/README.md so that you could see the documentation on this page: https://github.com/umbrellajs/umbrella/tree/master/src/plugi...