|
|
| (14 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| = Mozilla.com/org Web Team =
| |
|
| |
|
| This is a page to document web team projects and processes.
| |
|
| |
| ==== Who We Are & What We Do ====
| |
|
| |
| We're a cross-functional group of people working to make Mozilla.org (currently still at Mozilla.com) amazing.
| |
|
| |
| The current core team includes:
| |
|
| |
| *James Long, Lead Web Developer on Mozilla.org/firefox
| |
| *Steven Garrity, WebDev
| |
| *Anthony Ricaurd, WebDev
| |
| *Laura Forrest, Marketing Manager & Moz.org/fx Team Lead<br>
| |
| *Chrissie Brodigan, User Experience Lead
| |
| *John Slater, Creative Director
| |
| *Raymond Entornam, QA
| |
|
| |
| We work with a team of product marketing managers (PMMs) responsible for overseeing product information relating to our core product lines. They are our brand stewards!
| |
|
| |
| The current team includes:
| |
|
| |
| *Laura Mesa, FX desktop
| |
| *Grace Jimenez, Rapid Release, Sync
| |
| *Jaclyn Fu, FX mobile
| |
| *Gregory Jost, FX Europe
| |
| *Dan Horner, Apps & Add-ons<br>
| |
|
| |
|
| |
|
| |
| ==== Release Cycles ====
| |
|
| |
| We have weekly release cycles launching each Tuesday. Code freeze is each Monday. This allows us to release a handful of website improvements to the world on a weekly basis. To see our release cycle see the [https://wiki.mozilla.org/Webdev:Releases WebDev Release Calendar] for our release dates and milestone numbers. <br>
| |
|
| |
| '''Details:'''
| |
|
| |
| 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 query 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.org/firefox 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.
| |
|
| |
| If you're thinking of kicking off a larger project on the site then schedule a meeting with Laura and Chrissie to get started. Here's a [https://wiki.mozilla.org/Engagement/Websites/Firefox/Webteam/Content in-depth overview] of how to launch an entire marketing campaign on Mozilla.org.
| |
|
| |
| 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!
| |
|
| |
| ===== I'm Launching X. Where Can it Go On Our Site? =====
| |
|
| |
| For all matters relating to content strategy and management talk to Laura Forrest
| |
|
| |
| ===== 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 built, and then go live within a scheduled milestone. QA takes about 1 day. If your page contains any sort of functionality, add more time to that estimate. <br>
| |
|
| |
| <br>
| |
|
| |
| == Related Links ==
| |
|
| |
| [https://wiki.mozilla.org/Engagement/Websites/Firefox/Webteam/Content Launching an Engagement campaign on Mozilla.org/firefox] (A How-to for PMMs and other Engagement folks)
| |