Websites/Mozilla.org/Archive/Contribute/AllHandsCodingSession

Details

• Wed, April 6, 2:00 PM PDT
• Very Good Very Mighty (3rd floor, near JS pit)
• Conference call details to be finalized
• join irc.mozilla.org #mozillians for back channel

Suggested Reading

Summary of last week's discussions on dev-planning

Experience reports

• https://live.gnome.org/GnomeLove
• https://wiki.mozilla.org/Firefox/Projects/TabCandy/Work
• http://www.joshmatthews.net/blog/2010/03/getting-involve-with-mozilla
• https://wiki.mozilla.org/JavaScript:New_to_SpiderMonkey
• https://groups.google.com/group/mozilla.dev.planning/msg/ea66ebfa2061d888
• https://groups.google.com/group/mozilla.dev.planning/msg/d0bbd32c1139af92
• https://groups.google.com/group/mozilla.dev.planning/msg/f49f0a96e6ab86dd

Agenda

Discussing engaging with new contributors, specifically related to coding and the Mozilla tree.

Contributor engagement funnel

• good first bugs
• mentor assignment
• landing page

experience reports

• seamonkey?
• l10n?
• tabcandy?
• ckaiser?
• sfink?
• jdm?
• paul biggar
• others?

Mentoring

• how-to documentation
• experience reports
• volunteers + volunteer page

Documentation

• beginner documentation
• getting started with the tree
• formats (MDN?)
• tools listings + guides

metrics

• r?
• [commit-needed]
• contributors needing responses
• Metrics/dmose have a metrics dashboard

Pain points

• make -f client.mk build
• mozconfig
• enable-application
• directory name
• unassigned r?
• turning point of finding the right committer
  • document this
• fear of claiming bugs
  • bug squatting
• tryerver access
• outside "regular work hours"
• bugzilla
• following progress/workflows

• removing bottlenecks
  • tryserver
  • reviewers
  • approvals
  • [checkin-needed]
  • contributor agreement

• -u flag (!!!)

volunteers!

• (any tasks not have a volunteer?)

collaboration

• mailing list/irc
• future meetings
• bugzilla category/tracking bugs