Engagement/Websites/Firefox/Webteam: Difference between revisions

Engagement/Websites/Firefox/Webteam (view source)

Revision as of 23:31, 14 July 2011

672 bytes added , 14 July 2011

m

no edit summary

Lforrest

Confirmed users

685

edits

@@ Line 3: / Line 3: @@
 This is a page to document web team projects and processes.
-==== Release Cycles ====
+==== Who We Are &amp; What We Do ====
-In Q1 we tried a bi-monthly release cycle to varying success. After meeting during our Q2 onsite we decided to experiment with a weekly release cycle in order to release changes faster instead of waiting 2 weeks for the next cycle. We also decided to change our process in a couple of other ways listed here.
+We're a cross-functional group of people working to make Mozilla.org (currently still at Mozilla.com) amazing.
-'''Q2 Experiment:'''
+The current core team consist of:
-*'Slush' (our keyword for code freeze) each Monday. Push content each Tuesday.
+*James Long
-*Set expectations with stakeholders that content will be live by X instead of live on x
+*Steven Garrity
-*Document pushes on a public calendar (https://wiki.mozilla.org/Webdev:Releases) include start/end dates and link to bug query
+*Anthony Ricaurd
-*Cancel Tuesday Triage. Keep Thursday status meeting
+*Laura Forrest
-*Use more tracking bugs
+*Chrissie Brodigan
-*Meet regarding how to track bugs in Bugzilla (QAWanted, process, etc.)
+*John Slater
-*Alternate between devs: keep plane flying vs. working on infrastructure improvements
+*Raymond Entornam
-''All in all - do double the releases with half the meetings. ''
+==== Release Cycles  ====
-'''Continue:'''
+During Q2 of 2011 we started having weekly release cycles instead of bi-monthly releases. This allows us to release a handful of website improvements to the world on a weekly basis. To see our release cycle see the WebDev Calendar for our release dates. <br>
-*Using milestones
+'''Details:'''
-*Using a release cycle of some sort
+&nbsp; We use milestones through the quarter. The first release of Q3 is 3.0, then next is 3.1, onwards on a weekly basis. To see which bugs are in each release follow the link within the WebDev Calender or conduct a queary in Bugzilla.
+<br>
+==== Working With Us ====
+Launching new site content? Submit your change via Bugzilla [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites here] under the www.mozilla.com Component. To make sure it gets triaged assign to Laura Forrest or Chrissie Brodigan. They will then field it to the necessary milestone based on current work happening on the site.&nbsp;
+If you're thinking of kicking off a larger project on the site then schedule a meeting with Laura and Chrissie to get started.
+Note: if you file a bug and it's assigned to no-one, and it has no milestone, nothing will get done. Oh noes! Avoid that!
+===== How Long Will It Take to Get My X Live? =====
+It depends! For the most part start with the assumption that any change will take at least 5 work developer work days before they are build, and then go live within a scheduled milestone.