MDN/Development/Meetings: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
<!--
== Guidelines ==
Template:
We schedule MDN development meetings by these guidelines:


== [Date] ==
* We like days without meetings
Purpose: [By default: Planning and Retrospective]
* We like short meetings
* We like meeting times that work for as many time-zones as possible
* We like clear agendas
* We like meetings that make our work clear for an entire week


* [Resulting plans]
MDN development staff work in time-zones from CEST to PT, so [http://www.timeanddate.com/worldclock/meetingtime.html?iso=20150105&p1=48&p2=179&p3=64&p4=224&p5=136 4pm UTC is our "magic-hour"] for meetings to include all staffers.
* [Process improvements]
 
* [Meeting video]
== 2014 ==
* [Meeting notes]
 
-->
In 2014, we reset our meetings according to the above Guidelines. So, we settled on the following weekly schedule:
 
* Mondays
** 16:00 UTC - Pull Request Triage
** 16:30 UTC - New Bug Triage
* Tuesdays
** 16:00 UTC - Project Meetings
* Wednesdays
** None
* Thursdays
** None
* Fridays
** 16:00 UTC - Weekly Retro
== 2013 ==
== 2013 ==



Revision as of 00:58, 13 June 2014

Guidelines

We schedule MDN development meetings by these guidelines:

  • We like days without meetings
  • We like short meetings
  • We like meeting times that work for as many time-zones as possible
  • We like clear agendas
  • We like meetings that make our work clear for an entire week

MDN development staff work in time-zones from CEST to PT, so 4pm UTC is our "magic-hour" for meetings to include all staffers.

2014

In 2014, we reset our meetings according to the above Guidelines. So, we settled on the following weekly schedule:

  • Mondays
    • 16:00 UTC - Pull Request Triage
    • 16:30 UTC - New Bug Triage
  • Tuesdays
    • 16:00 UTC - Project Meetings
  • Wednesdays
    • None
  • Thursdays
    • None
  • Fridays
    • 16:00 UTC - Weekly Retro

2013

2012

Before September 2012

Before September 2012, we recorded our meetings and development progress on page called Milestones.