Community Platforms/2012Q1: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 1: | Line 1: | ||
== Community Platforms == | == Community Platforms == | ||
Line 16: | Line 12: | ||
=== MDN Engineering === | === MDN Engineering === | ||
{{draft}} | |||
* Transition to standard staging environments | * Transition to standard staging environments | ||
Line 21: | Line 19: | ||
=== Community Tools === | === Community Tools === | ||
{{draft}} | |||
* Transition Input ownership. | * Transition Input ownership. |
Revision as of 19:36, 4 January 2012
Community Platforms
Support Engineering
See also the Support team's goals.
- [ON TRACK] 100% of search traffic on ElasticSearch.
- Get push-button deploy (chief) for production (depends on IT).
- [ON TRACK] Transition to new planning strategy (become an agile, full-on poker-using team).
- Support BrowserID—Experimental, put BrowserID on the normal login page.
- [ON TRACK] Get working vagrant/puppet merged into the main repo.
MDN Engineering
- Transition to standard staging environments
- Migrate off MindTouch.
Community Tools
- Transition Input ownership.
- Transition Mozillians ownership.
- Start (launch 1.0?) TaskBoard project.
- Create transition plan for Affiliates for Q2.