Engagement/Developer Engagement/Process Documents
Prioritization
To propose a feature or project, complete the (prototype) intake form.
Overview
Developer Relations includes a wide variety of activities and efforts designed to develop and maintain connections between Mozilla and a global community of web developers. There are numerous stakeholders in the effort and many great ideas to choose from. This process describes how we select what to work on next.
What kind of projects?
This process is intended to work for large projects. How large? Large enough that undertaking them might put at risk something else we have deliberately chosen to do in a quarter. This process will generally not apply to things that take less than a week of effort to complete.
This process is intended to work for any large effort that Developer Relations might undertake. It is not only for engineering projects, but it is likely to address those first since there is so much demand for engineering effort.
Improving the process
This process includes regular reviews to ensure it continues to be effective. Feedback is welcome: email engagement-developers@lists.mozilla.org or join one of our regular meetings.
Timeline
Prioritization of large projects happens on a quarterly cycle. Proposals are welcome any time in the form of a bug filed with the 'productwanted' keyword. Reprioritization midway through a cycle is unusual, but not impossible.
At any time
- Anyone can submit a new project proposal for review.
- Product leads may meet to adjust current priorities immediately in response to new information or conditions.
In the last month of a quarter
- The product manager will convene Product Leads to review 'productwanted' bugs
- That team will triage bugs in one of four ways:
- By asking for clarification or more information
- By removing the 'productwanted' keyword and adding the bug to the product roadmap
- By removing the 'productwanted' keyword and commenting on why the bug won't be added to the product roadmap
- By resolving the bug WONTFIX
Throughout the quarter
- Product Leads will work with their teams to deliver projects and features
- Product Leads and the product manager will work to articulate upcoming projects and features so they are ready for implementation
Stakeholders
This process depends on a handful of Product Leads and on a larger list of representatives from various stakeholder groups.
Product Leads:
- Luke Crouch (MDN Engineering)
- Ali Spivak (MDN Content and Community)
Stakeholders:
- MDN Engineering
- MDN Content
- Mozilla Developer Evangelism
- MDN Community
- Developer Tools
- Apps Ecosystem
- Web Compatibility
- Addons
- Product Marketing
Product Manager: Justin Crawford