MDN/Development: Difference between revisions

From MozillaWiki
< MDN
Jump to navigation Jump to search
(Update for MDN Durable Team)
 
(25 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.  
= The Team =
* [[Engagement/MDN_Durable_Team|Our team]]
* 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] or follow the [https://mozilla.github.io/meao/ MozMEAO blog]


=Development Process=
=Development Process=
In March of 2013, the MDN development team switched from using Agile to a continuous deployment process using Kanban.  
== Current ==
* [https://wiki.mozilla.org/MDN/Development/drivers Work Prioritization process] - MDN-drivers
The MDN development team moved to Mozilla Marketing in 2016. For the current process, see the [[Engagement/MDN_Durable_Team|MDN Durable Team]] page.
* Overview of the MDN Kanban-based development [[/Process|process]]
* [[/Plans|Archive]] of Agile development sprints


==Following development in real time==
== 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].


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:
Most items on the board were either bugs that need to be addressed, or enhancements that came from the [[MDN/Development#Roadmap|roadmap]].


https://developer-dev.allizom.org/
(2013) [[/Process|process]] Overview of the MDN Kanbanery-based development


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


http://mzl.la/mdn_whats_deployed
==Following development in real time==


Commits also often include numbers of bugs that you can visit to see relevant discussions.
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=
=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]]
 
=Roadmap/Status=
*[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]
 
 
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.
 
=Projects=
==Current Projects==
====[[/Redesign|MDN Redesign]]====
*Large project aimed at rebranding & redesigning MDN to better serve developers as users and contributors.
 
====Localization dashboard====
*The [[MDN/Development/Localization dashboard|localization dashboard]] will make it easier for our localization teams to do their work.
 
==Proposed Projects==
 
====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
 
====[[/GitHub_Integration|GitHub Integration]]====
*Proposal for what GitHub integration might look like.
 
====Git backend for wiki====
*Proposal for [[MDN/Development/GitBackend|migrating to Git as the data backend for the wiki]], proposed by [[User:LesOrchard|lorchard]]
 
====Page building blocks====
*Proposed [[MDN/Development/BuildingBlocks|building blocks]] for the page templates and building blocks project requirement.
 
====Improving compatibility tables====
*Proposal to improve MDN's [[MDN/Development/CompatibilityTables|compatibility tables]], proposed by [[User:Jeremie|Jeremie]] and David Buchner
 
====Accessibility Review====
* will kickoff in 2014
 
====Mobile/Tablet & Offline Experience for MDN====
* will kickoff in 2014
 
==Completed Projects==
 
====Google Summer of Code====
*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.


=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}}
== 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"