Engagement/Developer Engagement/Event request guidelines: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 1: Line 1:
=Developer Event Request Guidelines=
=Developer Event Request Guidelines=
Mozilla Developer Relations community seeks to help developers use open Web technologies. One way that we do this is by sponsoring and helping to find speakers for technical conferences, hackathons, and meetups that bring developers together and share knowledge about open Web technologies.
Mozilla Developer Relations community seeks to help developers use open Web technologies. One way that we do this is by supporting technical conferences, hackathons, and meetups that bring developers together and share knowledge about open Web technologies.


If you are looking for support from Mozilla for a developer-oriented events, please submit a request using our [https://bugzilla.mozilla.org/form.dev-engagement-event Developer Event Request Form]. Requests are reviewed approximately weekly. Please allow at least 4 weeks lead time before your event (preferably more), to allow for consideration of your request and working out of logistical details. If you have a question about events that is not covered by the request form, please email [mailto:dev-events@mozilla.com dev-events (at) mozilla (dot) com].
If you are looking for support from Mozilla for your developer-oriented event, please submit a request using our '''[https://bugzilla.mozilla.org/form.dev-engagement-event Developer Event Request Form]'''. Requests are reviewed approximately weekly. Please allow at least 6 weeks lead time before your event (preferably more), to allow for consideration of your request and working out of logistical details. If you have a question about events that is not covered by the request form, please email [mailto:dev-events@mozilla.com dev-events (at) mozilla (dot) com].


In making decisions about sponsorships and speaking opportunities, Developer Relations considers the following factors (among others):
In making decisions about sponsorships and speaking opportunities, Developer Relations considers the following factors (among others):

Revision as of 01:56, 6 May 2014

Developer Event Request Guidelines

Mozilla Developer Relations community seeks to help developers use open Web technologies. One way that we do this is by supporting technical conferences, hackathons, and meetups that bring developers together and share knowledge about open Web technologies.

If you are looking for support from Mozilla for your developer-oriented event, please submit a request using our Developer Event Request Form. Requests are reviewed approximately weekly. Please allow at least 6 weeks lead time before your event (preferably more), to allow for consideration of your request and working out of logistical details. If you have a question about events that is not covered by the request form, please email dev-events (at) mozilla (dot) com.

In making decisions about sponsorships and speaking opportunities, Developer Relations considers the following factors (among others):

Relevance to Mozilla goals
It helps if you can show a relationship between your event and achieving Developer Relations 2014 goals.
Mozilla participation
Money alone doesn't represent Mozilla very well, so we only sponsor events where members of the Mozilla community (volunteers or staff) are participating. They could be attending, speaking, or organizing.
No pay-to-speak
While having a Mozillian speak at your event helps increase the likelihood of getting sponsorship, at the same time, we don't pay for sponsored speaking slots. We prefer that Mozilla speakers be invited or accepted on their own merits.
Code of conduct
In keeping with Mozilla's culture of inclusiveness, we strongly encourage event organizers seeking sponsorship or speaker to create, publish, and enforce a code of conduct for their event participants. The bigger your event, the stricter we will be about this requirement. However, small events can also benefit from explicit guidelines for respectful behavior. You can find examples and guidance for writing a code of conduct on the Geek feminism wiki.