Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Fwd: Moving Mozilla.org to Bugzilla Product
8 views
Skip to first unread message
Anthony Ricaud
Aug 10, 2012, 6:58:16 AM8/10/12
to dev-moz...@lists.mozilla.org, Benjamin Sternthal, Mike Alexis
Forwarding this to the m.d.mozilla-org newsgroup for wider distribution.
Begin forwarded message:
> From: Mike Alexis <mal...@mozilla.com>
> Subject: Moving Mozilla.org to Bugzilla Product
> Date: August 9, 2012 01:11:32 GMT+02:00
>
> Hi all,
> A few weeks ago Ben Sternthal and I solicited feedback on a plan to move Mozilla.org from a component to a product in Bugzilla. After iterating on that feedback and some technical discussion with the BMO team, we have a plan of action.
>
> In one week we’ll begin moving all open mozilla.org bugs into Product: Mozilla.org > Component > “General.” Once that is complete we and others in Web Prod will triage bugs into one of the following components:
>
> • Analytics: (for implementing tracking tags to collect traffic information)
> • Bedrock (for dev work related to the mozilla.org back end platform)
> • General (for miscellaneous work that doesn't fit in any other component)
> • Information Architecture & UX (work related to usability, accessibility, interaction design and organizing site information)
> • L10N (for localizing pages, content and media on mozilla.org)
> • Legacy PHP system (for dev work and changes to pages on our legacy codebase)
> • Pages & Content (for creating and updating pages and anything related to HTML/CSS/JS)
> • Project Tracking (main project "tracking bug" in which dependency bugs will be added)
>
> These changes are going to benefit us in a few key ways:
> • less reliance on whiteboard tags
> • faster dev cycles (get things done quicker)
> • happier developers
> • helps us be more Agile (w/ a capital A)
>
> Action Item for you, dear reader: please review and let us know if any of these changes break your current workflow. Anyone using the bugzilla api to pull in moz.org bugs will most likely need some minor fixes.
>
> -Mike
>
> --
> Web Program Manager, Mozilla
> https://mozillians.org/malexis
Begin forwarded message:
> From: Mike Alexis <mal...@mozilla.com>
> Subject: Moving Mozilla.org to Bugzilla Product
> Date: August 9, 2012 01:11:32 GMT+02:00
>
> Hi all,
> A few weeks ago Ben Sternthal and I solicited feedback on a plan to move Mozilla.org from a component to a product in Bugzilla. After iterating on that feedback and some technical discussion with the BMO team, we have a plan of action.
>
> In one week we’ll begin moving all open mozilla.org bugs into Product: Mozilla.org > Component > “General.” Once that is complete we and others in Web Prod will triage bugs into one of the following components:
>
> • Analytics: (for implementing tracking tags to collect traffic information)
> • Bedrock (for dev work related to the mozilla.org back end platform)
> • General (for miscellaneous work that doesn't fit in any other component)
> • Information Architecture & UX (work related to usability, accessibility, interaction design and organizing site information)
> • L10N (for localizing pages, content and media on mozilla.org)
> • Legacy PHP system (for dev work and changes to pages on our legacy codebase)
> • Pages & Content (for creating and updating pages and anything related to HTML/CSS/JS)
> • Project Tracking (main project "tracking bug" in which dependency bugs will be added)
>
> These changes are going to benefit us in a few key ways:
> • less reliance on whiteboard tags
> • faster dev cycles (get things done quicker)
> • happier developers
> • helps us be more Agile (w/ a capital A)
>
> Action Item for you, dear reader: please review and let us know if any of these changes break your current workflow. Anyone using the bugzilla api to pull in moz.org bugs will most likely need some minor fixes.
>
> -Mike
>
> --
> Web Program Manager, Mozilla
> https://mozillians.org/malexis
Anthony Ricaud
Aug 23, 2012, 6:24:38 AM8/23/12
to
0 new messages