canmove, Confirmed users
842
edits
MDN/Development/drivers: Difference between revisions
Jump to navigation
Jump to search
→The Process
| Line 9: | Line 9: | ||
Drivers subscribe to the MDN-drivers 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 prioritize accordingly. | Drivers subscribe to the MDN-drivers 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 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. | 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 or developer/contributor experience - the point of having drivers is to add intelligence to a more automated process. | ||
As card "slots" become available (when cards are released into production) Luke Crouch (manager of the MDN dev team) will ask on the mailing list which of the bugs from the backlog should go on top for pulling into the kanban board. Discussion will follow, and the input will drive what to add to the workload by adding it into the board's "Selected" column. | As card "slots" become available (when cards are released into production) Luke Crouch (manager of the MDN dev team) will ask on the mailing list which of the bugs from the backlog should go on top for pulling into the kanban board. Discussion will follow, and the input will drive what to add to the workload by adding it into the board's "Selected" column. | ||
==Links and Information== | ==Links and Information== | ||