Engagement/Developer Engagement/DeveloperEventsProcess: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "= '''Developer Events Process''' = The Developer Engagement group continually receives requests for Mozilla to participate and/or sponsor events and conferences of interest to d...")
 
Line 7: Line 7:


* Events Mozilla participates in must promote open web technologies or other elements of the Mozilla Mission
* Events Mozilla participates in must promote open web technologies or other elements of the Mozilla Mission
* At least one Mozilla employee or community member must attend any event that Mozilla sponsors; stated differently, someone in the Mozilla community must be passionate enough about the event that he or she will attend
* At least one Mozilla employee or community member must attend any event that Mozilla sponsors; stated differently, a Mozilla employee or community member must be passionate enough about the event that he or she will attend
* The Mozilla community, and in particular, the Mozilla community council is best
* The Mozilla community, and in particular, the Mozilla Community Council will play a key role in decision making and implementation


== Process Steps ==


During Phase 1, only employees and close partners are eligible to receive phones. We are not yet able to give phones to non-employee contributors.
# Requests for event participation are made through a form that captures key details about the event and the level of participation and sponsorship sought from Mozilla. Completion of the form will automatically populate a Google Doc spreadsheet that serves as a master list of all event requests.
 
# The Mozilla Community Council will meet periodically to review the requests, along with a representative from Developer Engagement.
=== [[B2G Test Drivers]] (blue-green stickers) ===
 
To qualify for a phone under the B2G Test Drivers program, you must:
 
* be a Mozilla employee
* be based in the SF, Mt. View or Toronto offices
* agree to test the phone daily, send feedback, file bugs, participate on the mailinglist, etc.
* not to re-flash the phone with another build of B2G
 
Visit the [[B2G Test Drivers]] page for more information on how to sign-up.
 
=== FirefoxOS Test Drivers (orange stickers) ===
 
To qualify for a phone under the FirefoxOS Test Drivers program, you must:
 
* be a Mozilla employee
* be able to build B2G and flash it to the device
* have a key role in the launch of FirefoxOS
 
To request a phone, file a request in [https://mozilla.service-now.com/ Service Now].
 
== Phase 2 (Nov-Dec 2012) ==
 
Phase 2 includes deploying Unagi devices to the following groups:
 
* second wave of internal "dogfooders"
* non-employee contributors
 
The details for this phase are still being determined. This page will be updated as soon as there is more information.
 
== Phase 3 (Jan 2013) ==
 
Sometime in January 2013 we will have another set of phones, some available to handout, and some available for purchase. More details coming soon. If you need an allotment of these phones, contact [[User:Ckoehler | Christie Koehler]].
 
== Background Info ==
 
=== '''Audiences'''  ===
 
We need to get phones to the following audiences that are a part of the Firefox OS (B2G) launch ecosystem:
 
*Core development team needs phones to develop and test Firefox OS (B2G).
*[[B2G_Test_Drivers]] (internal, only MV/SF/TO Spaces)
*Evangelists/Marketing
**In order to get web developers creating apps for the phone, we need to be able to demo and show off the phone at hackfests and outreach events.
**Developer engagement team and key ReMo reps and Speaker Evangelists are the initial teams who will be equipped with demo/testing devices.<br>
*Reps/Localizers
**B2G will come out localized and it's important to make sure localizers have an opportunity to test their work on an actual device.
*Web developers.
**While not every web developer will need a phone to test their apps, some will need it for testing for specific performance and user experience reasons (games in particular).
**External volunteers and partners
 
==='''Deployment Targets'''===
* [[B2G Test Drivers]]
**Paid staff (starting with MV/SF/TO, for IT support as well as privacy concerns)
**Feedback, crashes, and phone updates will be tracked (with their knowledge) so that we can have 2-way conversations. Each B2G Test Driver device will have a unique ID set on the device and a short-form feedback application in the default Gaia apps that enable easy tracking.<br>
*Developer Outreach
**We will give developers many opportunities to interact with hardware at events organized or sponsored by Mozilla
**A comprehensive developer program for hardware is in the works
*Contributor Outreach
**We will engage with the Mozilla contributor base through ReMo and other related programs. We will also be giving contributors opportunities to interact with hardware at events like MozCamps
 
=== '''Request Process''' ===
*Any Mozilla paid staff can be added to our '''waitlist for devices''' by filing a Hardware Request though the ServiceNow Service Catalog (https://mozilla.service-now.com/navpage.do) and, for now, select the "Unagi phone". Your request will be routed to the B2G Hardware team for processing. Request a phone only if you are willing to use the phone as your personal cellphone and report bugs & provide feedback about the phone regularly during this pre-release period.
*We are working on a program for external contributors to request early hardware in conjunction with the [https://wiki.mozilla.org/ReMo ReMo] program.
 
=== '''Developer Channels'''  ===
 
We distribute the Firefox phone through the following channels to reach target developer audience:&nbsp;
 
==== Hack days and Conferences ====
 
*Developers can hack on phones during hack days and strategic developer events.
*Developers who create quality apps that qualify for the B2G marketplace get to borrow or keep the phone.
*Mozilla Developer Engagement follows up with qualifying developers to help them get to finished app for marketplace.  
 
==== Launch Relationships ====
 
*Mozilla Developer Engagement partners with select app developers who want to make apps on Firefox OS
*Work with these developers to port their apps to Firefox OS

Revision as of 20:03, 5 November 2012

Developer Events Process

The Developer Engagement group continually receives requests for Mozilla to participate and/or sponsor events and conferences of interest to developers working with open web technologies. This wiki page describes a process for deciding when Mozilla should participate in a particular event, how the event should be staffed and how the logistic and financial requirements of participation should be satisfied.

Guiding Principles

These are the principles that inform the process and the resulting decisions about event participation:

  • Events Mozilla participates in must promote open web technologies or other elements of the Mozilla Mission
  • At least one Mozilla employee or community member must attend any event that Mozilla sponsors; stated differently, a Mozilla employee or community member must be passionate enough about the event that he or she will attend
  • The Mozilla community, and in particular, the Mozilla Community Council will play a key role in decision making and implementation

Process Steps

  1. Requests for event participation are made through a form that captures key details about the event and the level of participation and sponsorship sought from Mozilla. Completion of the form will automatically populate a Google Doc spreadsheet that serves as a master list of all event requests.
  2. The Mozilla Community Council will meet periodically to review the requests, along with a representative from Developer Engagement.
Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Engagement/Developer_Engagement/DeveloperEventsProcess&oldid=485068"