MDN/Development: Difference between revisions

From MozillaWiki
< MDN
Jump to navigation Jump to search
(Update for MDN Durable Team)
 
(34 intermediate revisions by 8 users not shown)
Line 1: Line 1:
The MDN site is under active development and is constantly evolving. In addition to the paid engineering, writing and product teams, the MDN community contributes feature requests, helps prioritize work and contributes code to the platform.  
The MDN site is under active development and is constantly evolving. In addition to the paid engineering, writing and product teams, the MDN community contributes feature requests, helps prioritize work and contributes code to the platform.  


==Development Process==
= The Team =
In March of 2013, the MDN development team switched from using Agile to a continuous deployment process using Kanban.  
* [[Engagement/MDN_Durable_Team|Our team]]
* [https://wiki.mozilla.org/MDN/Development/drivers Work Prioritization process] - MDN-drivers
* You can find us in the <tt>#mdndev</tt> channel on <tt>irc.mozilla.org</tt>
* Overview of the MDN Kanban-based development [[/Process|process]]
* For regular updates about development status, please join [https://lists.mozilla.org/options/dev-mdn our mailing list] or follow the [https://mozilla.github.io/meao/ MozMEAO blog]
* [[/Plans|Archive]] of Agile development sprints


==Following development in real time==
=Development Process=
== Current ==
The MDN development team moved to Mozilla Marketing in 2016.  For the current process, see the [[Engagement/MDN_Durable_Team|MDN Durable Team]] page.


If you want to stay in the loop on a bug or a set of bugs, be sure to add yourself to the "cc" list. Designers and developers update bugs with discussions and decisions as they go. A github robot will automatically comment on bugs when corresponding code is merged into the master line of development. Those commits are automatically pushed to the dev server every 5 minutes:
== Old Processes ==
(2014-2016) The MDN development team adopted Trello for its Continuous Development process. The process revolved around [[/Meetings|2 weekly meetings]] - Planning & Review - where the team went through [https://trello.com/b/p56Gwq46/mdndev-rocks the weekly planning board].


https://developer-dev.allizom.org/
Most items on the board were either bugs that need to be addressed, or enhancements that came from the [[MDN/Development#Roadmap|roadmap]].


The dev team pushes commits to stage and production servers when the code is ready. You can see which commits are on the stage & production servers here:
(2013) [[/Process|process]] Overview of the MDN Kanbanery-based development


http://mzl.la/mdn_whats_deployed
(2011-2013)[[/Plans|Archive]] of Agile development sprints


Commits also often include numbers of bugs that you can visit to see relevant discussions.
==Following development in real time==
 
==Platform==
 
*[https://github.com/mozilla/kuma Kuma on github]
* [https://developer.mozilla.org/Project:en/Getting_started_with_Kuma Getting started with Kuma]
* [https://developer.mozilla.org/Project:en/Introduction_to_KumaScript Introduction to KumaScript]
* [[MDN/Development/Contribute/Development|Contributing to development]]
* [[MDN/Development/Contribute/Design|Contributing to design]]


==Roadmap/Status==
If you want to stay in the loop on a bug or a set of bugs, be sure to add yourself to the "cc" list. Designers and developers update bugs with discussions and decisions as they go. A github robot will automatically comment on bugs when corresponding code is merged into the master line of development. Those commits are frequently pushed to the staging  server, and then to production.
*[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AtB4DXCweXv2dHNqUXZTdFJmaXY1a1hwT2IyYTR4NUE#gid=0 MDN 2013 Roadmap]
* Notes from our January 2013 [https://etherpad.mozilla.org/MDN-Austin-2013 planning meeting in Austin]
* Notes from our August 2012 [https://etherpad.mozilla.org/MDN-Toronto-2012 planning meeting in Toronto]


=Platform=


For notifications about changes to the MDN, please subscribe to our [http://bit.ly/mdn-dev-rss-released feed of released changes]. For more technical information about a change, click through from that feed entry to the Bugzilla ticket the entry is associated with. You can also follow our [https://github.com/mozilla/kuma/commits/master.atom feed of all source code commits] or watch this page for an [https://developer.mozilla.org/en-US/docs/Project:Changelog overview of commits pushed to production].
* [https://github.com/mozilla/kuma Kuma on github]
* [https://github.com/mozilla/kumascript KumaScript on github]


All of these resources provide essentially the same information, just in slightly different formats.
=Subpages=
 
This is a list of all subpages of this page. Most are out-of-date.
==Current Projects==
===[[/Redesign|MDN Redesign]]===
Large project aimed at rebranding & redesigning MDN to better serve developers as users and contributors.
 
===[[/GitHub_Integration|GitHub Integration]]===
Proposal for what GitHub integration might look like.
 
==Proposed Projects==
=== Summit 2013 ===
====Badges====
Proposal for [https://wiki.mozilla.org/MDN/Development/Badges Badges] on MDN, being managed by Florian
====Metrics====
Proposal for [[MDN/Development/Metrics|Metrics]] on MDN, being managed by [[User:Groovecoder|groovecoder]]
====Product versioning====
Proposal to support [[MDN/Development/Product_Versioning|product versioning]], proposed by Will
====Git backend for wiki====
Proposal for [[MDN/Development/GitBackend|migrating to Git as the data backend for the wiki]], proposed by [[User:LesOrchard|lorchard]]
 
==Required subprojects==
===Page building blocks===
Proposed [[MDN/Development/BuildingBlocks|building blocks]] for the page templates and building blocks project requirement.
 
===Localization dashboard===
The [[MDN/Development/Localization dashboard|localization dashboard]] will make it easier for our localization teams to do their work.
 
==Subpages==
This is a list of all subpages of this page.
{{Subpagelist}}
{{Subpagelist}}
== Contact ==
* [[MDN/Development/Team|The team]]
* For regular updates about development status, please join [https://lists.mozilla.org/options/dev-mdn our mailing list].


__NOTOC__
__NOTOC__

Latest revision as of 18:43, 10 February 2017

The MDN site is under active development and is constantly evolving. In addition to the paid engineering, writing and product teams, the MDN community contributes feature requests, helps prioritize work and contributes code to the platform.

The Team

Development Process

Current

The MDN development team moved to Mozilla Marketing in 2016. For the current process, see the MDN Durable Team page.

Old Processes

(2014-2016) The MDN development team adopted Trello for its Continuous Development process. The process revolved around 2 weekly meetings - Planning & Review - where the team went through the weekly planning board.

Most items on the board were either bugs that need to be addressed, or enhancements that came from the roadmap.

(2013) process Overview of the MDN Kanbanery-based development

(2011-2013)Archive of Agile development sprints

Following development in real time

If you want to stay in the loop on a bug or a set of bugs, be sure to add yourself to the "cc" list. Designers and developers update bugs with discussions and decisions as they go. A github robot will automatically comment on bugs when corresponding code is merged into the master line of development. Those commits are frequently pushed to the staging server, and then to production.

Platform

Subpages

This is a list of all subpages of this page. Most are out-of-date.


Retrieved from "https://wiki.mozilla.org/index.php?title=MDN/Development&oldid=1162641"