Websites/Mozilla.org/Archive/Contribute/Coding: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
Resources for helping new contributors hack on Mozilla
'''See [[Mentors]] for how to help contributors directly.'''


==Find something for a contributor to work on==
= Helping improve the process for engaging new developer contributors =


*[https://bugzil.la/sw:%5Bmentor%3D&resolution=--- List of mentored bugs]
*Discuss contributor engagement on [irc://irc.mozilla.org/#mozillians #mozillians] and [https://lists.mozilla.org/listinfo/mozillians mozillians@lists.mozilla.org]
*Fix a [https://bugzil.la/sw:contrib-engagement contrib-engagement bug]
*File a [contrib-engagement] bug to make entry to mozilla easy for new contributors (any bug with ''[contrib-engagement]'' in the whiteboard).


*[https://bugzil.la/kw:student-project&resolution=--- List of student-projects]
== Figure out these queries ==


*[https://bugzil.la/sw:%5Bgood%20first%20bugs%5D&resolution=--- List of good first bugs]
*TODO: list of blank r?
*TODO: list of blank f?
*TODO: uncommitted r+ed patches
*TODO: list of 1st patches
*Search the list of reviews which were denied. Ask the contributor if they need any help. Offer to help them over IRC and email.


== Interesting links ==


==Don't lose new contributors' stuff==
*http://eaves.ca/2010/07/20/some-thoughts-on-improving-bugzilla/
 
*http://www.joshmatthews.net/blog/2010/03/getting-involve-with-mozilla/
*TODO: list of blank r?
*http://vocamus.net/dave/?p=1286
*TODO: list of blank f?
*https://wiki.mozilla.org/Education/Learning
*TODO: uncommitted r+ed patches
*http://www.codesimplicity.com/post/open-source-community-simplified/
*TODO: list of 1st patches
* Search the list of reviews which were denied. Ask the contributor if they need any help. Offer to help them over IRC and email.
 
==Help newcomers==
 
*Volunteer to be a [[Mentors | bug mentor]]: add [mentor=your_bugzilla_id] to a bug whiteboard
*Visit [irc://irc.mozilla.org/#introduction #introduction] on IRC and answer questions.
*Triage [https://bugzil.la/sw:%5Bgood%20first%20bugs%5D&resolution=--- good first bugs] and convert them to [[Mentors | mentored bugs]]
 
==Help at a high-level==
*Discuss contributor engagement on [irc://irc.mozilla.org/#mozillians #mozillians] and [https://lists.mozilla.org/listinfo/mozillians mozillians@lists.mozilla.org]
*Fix a [https://bugzil.la/sw:contrib-engagement contrib-engagement bug]
*File a [contrib-engagement] bug to make entry to mozilla easy for new contributors (any bug with ''[contrib-engagement]'' in the whiteboard).


== Meetings, etc ==


==Interesting links==
*[[Mozilla.org/Contribute/AllHandsCodingSession|All-Hands Coding Contributor Engagement Session]]
 
*http://eaves.ca/2010/07/20/some-thoughts-on-improving-bugzilla/
*http://www.joshmatthews.net/blog/2010/03/getting-involve-with-mozilla/
*http://vocamus.net/dave/?p=1286
*https://wiki.mozilla.org/Education/Learning
*http://www.codesimplicity.com/post/open-source-community-simplified/
 
==Meetings, etc==
*[[Mozilla.org/Contribute/AllHandsCodingSession | All-Hands Coding Contributor Engagement Session]]

Revision as of 15:58, 18 April 2011

See Mentors for how to help contributors directly.

Helping improve the process for engaging new developer contributors

Figure out these queries

  • TODO: list of blank r?
  • TODO: list of blank f?
  • TODO: uncommitted r+ed patches
  • TODO: list of 1st patches
  • Search the list of reviews which were denied. Ask the contributor if they need any help. Offer to help them over IRC and email.

Interesting links

Meetings, etc