MDN/Development: Difference between revisions

From MozillaWiki
< MDN
Jump to navigation Jump to search
(Update for MDN Durable Team)
 
Line 2: Line 2:


= The Team =
= The Team =
* [[MDN/Development/Team|Our team]]
* [[Engagement/MDN_Durable_Team|Our team]]
* You can find us in the <tt>#mdndev</tt> channel on <tt>irc.mozilla.org</tt>
* You can find us in the <tt>#mdndev</tt> channel on <tt>irc.mozilla.org</tt>
* For regular updates about development status, please join [https://lists.mozilla.org/options/dev-mdn our mailing list].
* 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]


=Development Process=
=Development Process=
== Current ==
== Current ==
In 2014, the MDN development team adopted Trello for its Continuous Development process. The process revolves around [[/Meetings|2 weekly meetings]] - Planning & Review - where we go thru [https://trello.com/b/p56Gwq46/mdndev-rocks our weekly planning board].
The MDN development team moved to Mozilla Marketing in 2016. For the current process, see the [[Engagement/MDN_Durable_Team|MDN Durable Team]] page.


Most items on the board are either bugs that need to be addressed, or enhancements that come from the [[MDN/Development#Roadmap|roadmap]].
== 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].
==Roadmap==
The MDN engineering roadmap is significantly influenced by the [[Engagement/Developer_Engagement/Project_Roadmap|Developer Relations roadmap]], which is a product of a quarterly [[Engagement/Developer_Engagement/Process_Documents#Prioritization|prioritization process]].
 
Notes from major planning sessions:
 
* Notes and discussion for 2014 planning from our December 2013 Developer Engagement Leads off-site in Boulder are in the [https://lists.mozilla.org/listinfo/engagement-developers engagement-developers] archives: [https://groups.google.com/d/msg/mozilla.engagement.developers/8GHN55k9fNE/TwtDfhve7VYJ Day 1] and [https://groups.google.com/d/msg/mozilla.engagement.developers/_BbKquFh-CI/r_YH-OmUZqcJ Day 2]
* Notes from our January 2013 [https://etherpad.mozilla.org/MDN-Austin-2013 planning meeting in Austin]
* [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AtB4DXCweXv2dHNqUXZTdFJmaXY1a1hwT2IyYTR4NUE#gid=0 MDN 2013 Roadmap]
* Notes from our August 2012 [https://etherpad.mozilla.org/MDN-Toronto-2012 planning meeting in Toronto]


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


== Old Processes ==
(2013) [[/Process|process]] Overview of the MDN Kanbanery-based development
(2013) [[/Process|process]] Overview of the MDN Kanbanery-based development


Line 30: Line 21:
==Following development in real time==
==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 automatically pushed to the dev server every 5 minutes:
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://developer-dev.allizom.org/
 
The dev team pushes commits to stage and production servers when code is ready - often multiple times per day. You can see which commits are on the dev, stage, & production servers here:
 
http://mzl.la/deployed-mdn
 
Commits also often include numbers of bugs that you can visit to see relevant discussions.


=Platform=
=Platform=


*[https://github.com/mozilla/kuma Kuma on github]
* [https://github.com/mozilla/kuma Kuma on github]
* [https://developer.mozilla.org/Project:en/Getting_started_with_Kuma Getting started with Kuma]
* [https://github.com/mozilla/kumascript KumaScript on github]
* [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]]
 
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].
 
All of these resources provide essentially the same information, just in slightly different formats.


=Subpages=
=Subpages=
This is a list of all subpages of this page.
This is a list of all subpages of this page. Most are out-of-date.
{{Subpagelist}}
{{Subpagelist}}


__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.allizom.org/index.php?title=MDN/Development&oldid=1162641"