canmove, Confirmed users
1,953
edits
MDN/Development/drivers: Difference between revisions
Jump to navigation
Jump to search
mdn-drivers is being deprecated
(mdn-drivers is being deprecated) |
|||
| Line 7: | Line 7: | ||
==The Process== | ==The Process== | ||
Drivers subscribe to the MDN | Drivers subscribe to the [https://lists.mozilla.org/listinfo/mdn MDN] mailing list, where most of the discussions will happen, and also participate in a monthly meeting. The expectation is that drivers will propose and champion features (via bugs in Bugzilla & discussion in the mailing list) relevant to their areas of interest, but also evaluate all bugs & proposed features and their impact on developers and contributors and prioritize accordingly. | ||
MDN development uses a continuous deployment process, where we create "cards" of work that are passed into the dev team via a [http://en.wikipedia.org/wiki/Kanban Kanban] board. Cards are created from the MDN backlog, which is a list of bugs in Bugzilla that are ordered primarily based on votes, duplicate counts, and priority. For most bugs, the best way to influence MDN product development is to [https://bugzilla.mozilla.org/page.cgi?id=voting.html vote] on the bugs in Bugzilla and participate in the prioritization of top vote-getting bugs. Drivers also can, and should, champion low-vote bugs that are essential to their products, the developer/contributor experience, and performance/security - the point of having drivers is to add intelligence to the process beyond just votes on bugs. | MDN development uses a continuous deployment process, where we create "cards" of work that are passed into the dev team via a [http://en.wikipedia.org/wiki/Kanban Kanban] board. Cards are created from the MDN backlog, which is a list of bugs in Bugzilla that are ordered primarily based on votes, duplicate counts, and priority. For most bugs, the best way to influence MDN product development is to [https://bugzilla.mozilla.org/page.cgi?id=voting.html vote] on the bugs in Bugzilla and participate in the prioritization of top vote-getting bugs. Drivers also can, and should, champion low-vote bugs that are essential to their products, the developer/contributor experience, and performance/security - the point of having drivers is to add intelligence to the process beyond just votes on bugs. | ||
| Line 15: | Line 15: | ||
==Links and Information== | ==Links and Information== | ||
*To post to the list, send your message to: Mdn | *To post to the list, send your message to: Mdn@lists.mozilla.org | ||
* [https://groups.google.com/forum/#!forum/mozilla.mdn | * [https://groups.google.com/forum/#!forum/mozilla.mdn Archive of discussions] | ||
*[https://lists.mozilla.org/listinfo/mdn | ** [https://groups.google.com/forum/#!forum/mozilla.mdn-drivers Historical archive] of (deprecated) mdn-drivers list | ||
* [https://lists.mozilla.org/listinfo/mdn Subscribe to mdn@] | |||
* [http://mzl.la/mdn_backlog MDN Backlog] (sorting by votes is helpful) | * [http://mzl.la/mdn_backlog MDN Backlog] (sorting by votes is helpful) | ||
* [https://mdn.kanbanery.com/projects/32137/board/?key=0383ba5f05e165e0eb19d8476654fe9775ce2ca7 Kanban board] | * [https://mdn.kanbanery.com/projects/32137/board/?key=0383ba5f05e165e0eb19d8476654fe9775ce2ca7 Kanban board] | ||