On 2014-04-21, 7:27 PM, Benjamin Peterson wrote:
I'm rather out of the loop, so I can't mention anything specifically. However, if there are any small harmony features to be implemented, those can be a lot of fun for new contributors. (You can tell your friends "I implemented that" when they start using a cool new JS feature.) See the "harmony" meta-bug perhaps.
FWIW different people have different ideas of what a good first bug is. I would personally pick up a *small* task which you're sure that the contributor can accomplish in their sleep, and try to focus the first bug on getting them familiar with our process of building our code, writing patches against it, uploading them, getting reviews, and getting their change landed (while of course making the goals of the good first bug very clear.)
But of course it's OK to have both kinds of good first bugs. Cheers, Ehsan _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
