MDN/Development: Difference between revisions

From MozillaWiki
< MDN
Jump to navigation Jump to search
Line 42: Line 42:


All of these resources provide essentially the same information, just in slightly different formats.
All of these resources provide essentially the same information, just in slightly different formats.
=Projects=
==Current Projects==
====Badges====
*Proposal for [https://wiki.mozilla.org/MDN/Development/Badges Badges] on MDN, being driven by Janet, Florian, Christie & Robert
====Improving compatibility tables====
*Proposal to improve MDN's [[MDN/Development/CompatibilityTables|compatibility tables]], proposed by [[User:Jeremie|Jeremie]] and Daniel Buchner
====[[/GitHub_Integration|GitHub Integration]]====
*Proposal for what GitHub integration might look like.
==Proposed Projects==
====Personal Dashboard====
* Proposal to build a [[MDN/Development|Personal_dashboard|Personal dashboard]] on MDN; this is a customizable "home" page for users that provides key information about things they care about on MDN.
====Metrics====
*Proposal for [[MDN/Development/Metrics|Metrics]] on MDN, being managed by [[User:Groovecoder|groovecoder]]
====Blackhole Integration====
*Project to integrate [https://wiki.mozilla.org/MDN/Development/Blackhole MDN with Blackhole] (Mozillians) project
====Working Sample Code====
*Proposal for JSFiddle-like [https://wiki.mozilla.org/MDN/Development/Sample_Code sample code] on every page that you can download, tweak, run "out of the box"
====Social Features====
Implement [https://wiki.mozilla.org/MDN/Development/Social social features] on the site to promote collaboration and community
====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]]
====Page building blocks====
*Proposed [[MDN/Development/BuildingBlocks|building blocks]] for the page templates and building blocks project requirement.
====Accessibility Review====
* proposed by teoli
====Mobile/Tablet & Offline Experience for MDN====
* From community feedback during MDN redesign
====Mozilla Hacks Localization====
*Proposal for [[MDN/Development/HacksLocalization|Mozilla Hacks Localization]], being managed by [[User:Robnyman|Robert Nyman]]
====StackOverflow widgets====
*Proposal to add topical StackOverFlow widgets to MDN pages, proposed by by [[User:Robnyman|Robert Nyman] & Ali
====Filtering UI for MDN Seach / "Command & Query"====
*Proposal to finish and improve our in-progress work for implementing a [http://hollyhabstritt.com/blog/2013/11/5/command-query-a-better-filter-and-search-for-developers-on-mdn filter UI to the search field on MDN], proposed by Holly & Jannis
==Completed 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.
====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=

Revision as of 20:39, 5 June 2014

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

  • Our team
  • You can find us in the #mdndev channel on irc.mozilla.org
  • For regular updates about development status, please join our mailing list.

Development Process

In March of 2013, the MDN development team switched from using Agile to a continuous deployment process using Kanban.

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:

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

Roadmap/Status


For notifications about changes to the MDN, please subscribe to our 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 feed of all source code commits or watch this page for an overview of commits pushed to production.

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.