Engagement/Developer Engagement/DeveloperEventsProcess

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

Intake & Review

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 with a representative from Developer Engagement to review the requests.
3. If the event is approved, it will go into one of two tracks:
   • A track for events managed by Developer Engagement - these are larger events that require a speaker from the Technology Evangelism group, or other special handling. They are expected to be fewer in number, and management these type of events is not further discussed in this process.
   • A track to be managed and executed by a community representative.
4. If the event is declined, a member of the community council will send a e-mail to inform the requester of the decision, explaining the reason(s) and possibly suggesting opportunities for future Mozilla participation.

Execution

1. Once an event has been approved by the council, the council will name a qualified community representative to manage Mozilla's participation.
2. The rep will handle the sponsorship logistics, including contract execution and payment, and supplying logos, company descriptions and swag. An event resource library will be available to provide commonly-requested items.
3. The rep will attend the event and write a summary report of the experience, including a recommendation about future participation.

Migration from Old Process

1. The old process relies on event requests being sent to the dev-events alias for consideration. That e-mail alias will be modified to send an automated response pointing the requester to the new web form.