MDN/Development: Difference between revisions

From MozillaWiki
< MDN
Jump to navigation Jump to search
(Update for MDN Durable Team)
 
(41 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


==Platform==
=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.


*[https://github.com/mozilla/kuma Kuma on github]
== Old Processes ==
* [https://developer.mozilla.org/Project:en/Getting_started_with_Kuma Getting started with Kuma]
(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.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==
Most items on the board were either bugs that need to be addressed, or enhancements that came from the [[MDN/Development#Roadmap|roadmap]].
*[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]


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


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].
(2011-2013)[[/Plans|Archive]] of Agile development sprints


All of these resources provide essentially the same information, just in slightly different formats.
==Following development in real time==


==Current Projects==
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.
===[[/Redesign|MDN Redesign]]===
Large project aimed at rebranding & redesigning MDN to better serve developers as users and contributors.


===Google Summer of Code===
=Platform=
The Mozilla Developer Network team will be hosting a Google Summer of Code this summer. The project will center around building a Localization Dashboard to track localization status and help localizers find articles that need to be updated.


For more information, please see our [[/Google_Summer_of_Code_2013|Google Summer of Code 2013]] page.
* [https://github.com/mozilla/kuma Kuma on github]
* [https://github.com/mozilla/kumascript KumaScript on github]


===[[/GitHub_Integration|GitHub Integration]]===
=Subpages=
Proposal for what GitHub integration might look like.
This is a list of all subpages of this page. Most are out-of-date.
 
{{Subpagelist}}
 
==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]]
 
== 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.allizom.org/index.php?title=MDN/Development&oldid=1162641"