Confirm
214
edits
Changes
no edit summary
=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 and meetups that bring developers together and share knowledge about open Web technologies. By support, the Dev Rel group includes financial sponsorship, help with securing Mozilla speakers, and Mozilla branded promotional items at the event.
=DevRel Event Participation Policy=
Diversity and inclusion are important for Mozilla, and are core to our community participation guidelines [https://www.mozilla.org/en-US/about/governance/policies/participation/] and the Mozilla Manifesto [https://www.mozilla.org/en-US/about/manifesto/].
We seek to foster diversity and inclusion in the technology industry because it is the right thing to do. If that isn’t a strong enough argument, then having diverse teams has proven again and again to create better products, foster a better work environment and to improve organization and team performance.
For more details, see appendix below.
== What kind of support does Mozilla provide for events? ==
If Mozilla sponsors your event, please be aware that we will ask you for follow-up information after the event, such as number of attendees and social media reach. The purpose of this follow-up is to help us track the effectiveness of our sponsorships and make decisions for the future. You're probably collecting this information anyway.
=More Details to our DevRel Participation Policy=
Mozilla promotes inclusion by making our support for events contingent on the following:
Code of conduct: All events we host, participate in or sponsor must have a published code of conduct and a clear plan to enforce it.
Diversity: We will only speak at or sponsor an event where organizers have demonstrated a commitment to enhance the diversity of their speakers and attendees; specifically including those from underrepresented groups.
Panels: Mozilla will only participate in panel discussions of two or more people where there is at least one member of an underrepresented group (e.g. woman, person with disabilities, non-binary person, person of color) on the panel, not including the chair.
Accessibility: Events with over 25 attendees need to have venues that are accessible and have an assigned point of contact for issues of accessibility.
(Note: this includes events hosted or funded by staff, representatives, or ambassadors of Mozilla and our projects.)
Mozilla will decline to provide speakers or sponsorship to events that do not adhere to these standards, and reserves the right to withdraw speakers, funding or visible sponsorship (logos, booth, etc) from any event that demonstrates an unwillingness or inability to provide an inclusive and safe environment. This includes falsely claiming diverse attendees or speakers, continuing to allow inappropriate or harassing conduct and content, and not adequately responding to abuse or COC violations.
There may be cases when it will be a struggle for event organisers to meet the above rules, especially with smaller scale events or meetups. We are always willing to discuss these on a case by case basis and provide assistance and guidance on how to implement practices that will help your events meet these guidelines. However, we are unable, and frankly, unwilling, to bend the rules regardless of the event, organizer, or ongoing relationship with Mozilla and the tech community.
Events are a highly visible part of our industry. Events build community and grow expertise, and encouraging broad participation in tech events and communities depends on an inclusive and welcoming experience for all, no matter their gender, ethnicity, sexual orientation, religion, national origin, disability or any other factor. Speakers at events serve not only as representatives of their respective companies and technologies, but as role models and highly visible faces of the tech industry and beyond. It is therefore vital that speakers and the content they present represent the diverse range of people working in technology today and who will be working in technology tomorrow.
In addition to the rules above, we highly encourage the following practices:
Offer diversity scholarships (free or discounted tickets for underrepresented groups and where necessary, financial help towards travel or accommodation).
Staff training,
Live captioning, assistive listening devices, hearing or induction loops, Braille and tactile signage, and food options, with signage, available for participants with dietary restrictions/allergies.
Providing ability for remote attendance and engagement, such as live streaming or telepresence.
Development of events that cater to specific underrepresented groups as a way to foster inclusion and diversity in our industry.
Including questions about Code of Conduct in post-event surveys.
Inclusive language: We encourage, and will always use, inclusive language at events and in online communities surrounding events. This includes, but is not limited to, discouraging the use of gendered or ableist language and content.
REFERENCES AND RESOURCES
Good Code of Conduct examples:
Mozilla View Source conference Code of Conduct [https://viewsourceconf.org/london-2017/code-of-conduct/]
Rust code of Conduct [https://www.rust-lang.org/en-US/conduct.html]
O'Reilly Code of Conduct [https://www.oreilly.com/conferences/code-of-conduct.html]
JSConfUS COC [http://jsconf.com/codeofconduct.html]
Crowd-sourced conference code of conduct [http://confcodeofconduct.com/]
Code of Conduct Response:
PyCon Attendee Procedure for incident handling [https://us.pycon.org/2018/about/code-of-conduct/attendee-procedure/]
PyCon Staff Procedure for incident handling [https://us.pycon.org/2018/about/code-of-conduct/staff-procedure/]
Post-event COC survey questions used by Mozilla [https://github.com/mozilla/diversity/blob/master/data-metrics/surveys/en/cpg-follow-up.md]
Accessibility Standards:
Americans with Disabilities Act [https://adata.org/learn-about-ada]
Creating inclusive spaces at your event [http://wiscon.net/spaces/]
