Re: Moving Mozilla.org to Bugzilla Product

[Reed Loden]

Where is the bug tracking this work? There are a few issues with the
proposal (such as the product "Mozilla.org" already being taken for
other things).

~reed

On Fri, 10 Aug 2012 12:58:16 +0200
Anthony Ricaud <ant...@ricaud.me> wrote:

> 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
> _______________________________________________
> dev-mozilla-org mailing list
> dev-moz...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-mozilla-org

[Benjamin Sternthal]

Reed:

Thanks for providing feedback. We were waiting 1 week to file the bug to give folks a chance to get back to us with comments. The new product will be "Mozilla.org Website" not mozilla.org which you correctly point out is already in use. You can see the text of the bug we will be filing in this etherpad:

https://romana.etherpad.mozilla.org/L10N-Bedrock-Bugzilla-Moz-org-website-request

Best,
Ben

[Gervase Markham]

On 15/08/12 16:29, Benjamin Sternthal wrote:
> Thanks for providing feedback. We were waiting 1 week to file the bug
> to give folks a chance to get back to us with comments. The new
> product will be "Mozilla.org Website" not mozilla.org which you
> correctly point out is already in use.

This needs a lower-case M; both domain names and the name of our
organization use lowercase.

However, an alternative, more consistent and IMO better option for the
Product name is "www.mozilla.org"; there are several other websites
which have products with a name of that form - addons.mozilla.org,
support.mozilla.org, quality.mozilla.org...).

Gerv