Confirmed users
583
edits
Groovecoder (talk | contribs) |
No edit summary |
||
| Line 9: | Line 9: | ||
== 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]. | 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]. | ||
Most items on the board are either bugs that need to be addressed, or enhancements that come from the [[#Roadmap|roadmap]. | |||
==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] | |||
== Old Processes == | == Old Processes == | ||
(2013) [[/Process|process]] Overview of the MDN Kanbanery-based development | (2013) [[/Process|process]] Overview of the MDN Kanbanery-based development | ||
| Line 33: | Line 47: | ||
* [[MDN/Development/Contribute/Development|Contributing to development]] | * [[MDN/Development/Contribute/Development|Contributing to development]] | ||
* [[MDN/Development/Contribute/Design|Contributing to design]] | * [[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]. | 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]. | ||