Community Platforms/2012Q2: Difference between revisions

(→‎Support Engineering: updating status)
 
(3 intermediate revisions by 2 users not shown)
Line 13: Line 13:


=== Support Engineering ===
=== Support Engineering ===
* Turn off Sphinx completely
* {{ok|Turn off Sphinx completely (e.g. remove the code, shut off the server, turn off the lights, fill the facility with concrete, bury it deep in the earth's core, ...)}}
* /questions performance: halve the mean and upper_90 times?
** {{ok|Get rid of fixtures.}}
* Continuously Deploy... oops we did this ahead of time in Q1!
* Get <code>upper_90</code> for all views (GET) to < 800ms.
* Something something API
* {{ok|Document entry points for contributors.}}
* Find a way to expose/credit code contributors. (humans.txt?)


=== MDN Engineering ===
=== MDN Engineering ===

Latest revision as of 21:57, 16 May 2012

DRAFT
The content of this page is a work in progress intended for review.

Please help improve the draft!

Ask questions or make suggestions in the discussion
or add your suggestions directly to this page.


Community Platforms goals for 2012 Q2.

Community Platforms

These are meta goals that I'd like to turn into something actionable.

  • Increase collaboration between CP teams. (Combined on/off site?)
  • Push toward platformitization.
  • Look for opportunities to interconnect platforms.
    • PuSH b/w Mozillians.org and MDN developer profiles, esp. w/ aim towards open badges

Support Engineering

  • [ON TRACK] Turn off Sphinx completely (e.g. remove the code, shut off the server, turn off the lights, fill the facility with concrete, bury it deep in the earth's core, ...)
    • [ON TRACK] Get rid of fixtures.
  • Get upper_90 for all views (GET) to < 800ms.
  • [ON TRACK] Document entry points for contributors.
  • Find a way to expose/credit code contributors. (humans.txt?)

MDN Engineering

  • Turn MindTouch server completely off
  • Velocity?
    • 15/week?
    • <10% "dropped/bumped" points

Community Tools Engineering