From MozillaWiki
Jump to: navigation, search


Vivien Nicolas, John Hammink and Alfredos-Panagiotis Damkalis (Fredy)

B2G Contribute Group

Welcome to the B2G Contribute group!

If you are looking to get involved with Boot2Gecko, this is the right place.

We invite you to read this wiki to give you an overview about how we work and the team that you would be best in.

Please, choose a team, subscribe to its mailing list and send to it an e-mail presenting yourself and saying what you would like to do.

If you are not sure about those steps, don't worry! Add your name on I want to contribute section and we will contact you. Also, you can contact Vivian [vnicolas AT mozilla DOT com], John [jhammink AT mozilla DOT com] or Fredy [fredy AT freemail DOT gr] for more information.

Note: For coding volunteer needs, we're working with the Coding Stewards to piggyback on the work they're doing.

Action Plan


  • Have a wide team composed by paid staff and volunteers
  • Move forward the B2G project, increase its reach and make easier its acceptance in the market
  • Have at least three volunteers working on each team
  • Have a project driven by the community
  • Make easier to everyone to be part of the project
  • Align with Grow Mozilla and Stewards efforts


Online Channels

Offline Channels



  • Development: This team is composed by contributors who help coding B2G, Gaia and web apps. Those who help contributing with apps, look at their own market (their country/region) and create apps to make easier the transition from any platform to B2G.
  • QA: This team ensures the quality of the product for the final-users. It is composed by core contributors whose goal is to make B2G excel on quality.
  • SUMO: This team gives support to end-users of B2G. Its goal is to answer questions of users and help them to keep using it and solve their problems.
  • Design and UX: This team is composed by designers and UX developers. These contributors will support the development team to have well-designed apps and make of gaia a great option to choose because of its simplicity and ease of use.
  • Evangelism: Team of contributors who knows how to do public speaking and who are watching their markets for user needs and special partnerships. Its incredible important to have people doing evangelism about new technologies to increase the number of developers to provide to users the apps they are needing. They also will watch their country/region to find new partnerships that will make easier the adoption of B2G.
  • L10N: This team will give support to the development team to make the apps easy to use in different countries giving to users the capability to choose apps and at least have one on their own locale.

I want to contribute

If you already chosen a team where you would like to contribute, please subscribe to its mailing list, send an e-mail presenting yourself and wait for more instructions.

If you don't know how to start to contribute, please edit (you need to create a wiki user) this part of the wiki and add your name and e-mail address.

  • Name - E-mail - Interest - [contacted by = to be completed by a contributor]
  • Srikanta -
  • Joshua Smith - - UX on Flatfish

Potential Contributors

Active Contributors

Core Contributors

Background Information

Identify Community

Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?


Suggestion: Use the contributor directory to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the Mozillians dashboard will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.

Define Contribution Opportunities

Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?


Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.

Map Contribution Paths

Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?


Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.

Establish Goals and Metrics

Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?


Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.