MDN/Development/drivers: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 3: Line 3:
MDN Drivers are group of stakeholders (product owners, community members and the like) that help drive the direction of MDN and the development work we do on the platform (django pages, the wiki and beyond).  
MDN Drivers are group of stakeholders (product owners, community members and the like) that help drive the direction of MDN and the development work we do on the platform (django pages, the wiki and beyond).  


Essentially, drivers will subscribe to the MDN-drivers mailing list and participate in a monthly meeting  to prioritize features or fixes on the site. Prioritization encompasses development work on everything from the wiki pages/platform (aka Kuma), Demo Studio/Dev Derby, Hacks blog to DevHub/Apps content and any new sections we add to the site moving forward. Drivers will also help guide the redesign/rebranding efforts on MDN, Devhub, Demo Studio & Hacks. We'll add any additional stakeholders as needed, and all Mozillains are invited to join the list and participate.  
Essentially, drivers will subscribe to the MDN-drivers mailing list and participate in a monthly meeting  to prioritize features or fixes on the site. Prioritization encompasses development work on everything from the wiki pages/platform (aka Kuma), Demo Studio/Dev Derby, Hacks blog to DevHub/Apps content and any new sections we add to the site moving forward. Drivers will also help guide the redesign/rebranding efforts on MDN, Devhub, Demo Studio & Hacks. We'll add any additional stakeholders as needed, and all Mozillians are invited to join the list and participate.  


==The Process==
==The Process==

Revision as of 18:37, 10 July 2013

MDN Drivers

MDN Drivers are group of stakeholders (product owners, community members and the like) that help drive the direction of MDN and the development work we do on the platform (django pages, the wiki and beyond).

Essentially, drivers will subscribe to the MDN-drivers mailing list and participate in a monthly meeting to prioritize features or fixes on the site. Prioritization encompasses development work on everything from the wiki pages/platform (aka Kuma), Demo Studio/Dev Derby, Hacks blog to DevHub/Apps content and any new sections we add to the site moving forward. Drivers will also help guide the redesign/rebranding efforts on MDN, Devhub, Demo Studio & Hacks. We'll add any additional stakeholders as needed, and all Mozillians are invited to join the list and participate.

The Process

MDN development uses a continuous deployment process, where we create "cards" of work that are passed into the dev team via a Kanban board.

Drivers will help choose features the MDN engineering team should work on from the MDN backlog (a selected list of bugs in Bugzilla), as well as make suggestions for new bugs/features. As card "slots" become available Luke Crouch (manager of the MDN dev team) will ask on the mailing list which of the features from the backlog should go on top for pulling into the kanban board. Discussion will follow, and we will chose what to add to the workload.

I'll send email reminders to this list before the MDN engineering team pulls new work from our MDN backlog into our Kanban board. When a slot opens up in our board, Ali, I, or an MDN dev will pull a bug from the backlog - primarily based on votes, duplicate counts, and priority - into the board's "Selected" column.

So, the best way to influence MDN product development is to vote on bugs in the MDN backlog and participate in the prioritization of top voted bugs.

In addition, our Kanban board reports an average "Lead Time" [3] - i.e., how long it takes for a card to move from "Selected" to "Released". So we can also prioritize bugs anticipating their delivery dates.

Links and Information