MDN/Development/drivers

MDN Drivers

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

Essentially, drivers subscribe to the MDN-drivers mailing list and particpate in a monthly meeting propose or vote on features or fixes you want on the site. Everything from wiki pages, Demo Studio/Dev Derby, Hacks blog to DevHub/Apps content and any new sections we add to the site moving forward. We will also help guide the redesign/rebranding efforts on MDN, Devhub, Demo Studio & Hacks. We'll add any additional stakeholders as needed.

The process: MDN development uses a continuious deployment process, and we create "cards" of work that are passed into the dev team via a kanban board. Drivers will help choose features the team should work on (essentially a product backlog if you are familiar with Agile). As card "slots" become available Luke or I will ask on the mailing list which of the features from the backlog should go on top for pulling into the kanban board. This is a new process for us, so we'll refine as we go along; the important thing is to get a wider group of developer-facing roles helping is decide on the direction of development work.