Closed Bug 630989 Opened 15 years ago Closed 14 years ago

[One Mozilla] Update Bugzilla to new workflow for Firefox product site under .org

Categories

(www.mozilla.org :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: davidwboswell, Assigned: lforrest)

References

Details

Opening bug to track any changes needed in bugzilla components as part of the upcoming merging of www.mozilla.com and www.mozilla.org.
Assignee: nobody → mozillamarcia.knous
Component: www.mozilla.com → Bugzilla: Keywords & Components
Product: Websites → mozilla.org
QA Contact: www-mozilla-com → timeless
Target Milestone: 1.5 → ---
Version: unspecified → other
Moving back to original component -- there is no action to take here yet. We need to sort out what needs there are, if any, relating to merging the sites.
Assignee: mozillamarcia.knous → nobody
Component: Bugzilla: Keywords & Components → www.mozilla.com
Product: mozilla.org → Websites
QA Contact: timeless → www-mozilla-com
Target Milestone: --- → 1.5
Target Milestone: 1.5 → 1.6
Target Milestone: 1.6 → 2.0
Target Milestone: 2.0 → 2.1
Target Milestone: 2.1 → 2.2
Target Milestone: 2.2 → 2.3
Target Milestone: 2.3 → Future
Laura, Closing for simplicity, tracking bug 610724 for following along. Best, CB
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
Reopening for GPHemsley, assigning to GPHemsley.
Assignee: nobody → gphemsley
No longer blocks: 610724
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Note that this bug is about management of bugs after the merge. If there's no www.mozilla.com site, does it make sense to still have a www.mozilla.com component? Do we want bugs about Thunderbird pages, Firefox pages and other content on www.mozilla.org all to be handled in the same www.mozilla.org component?
There's nothing I can do about this bug. Not sure why it was assigned to me. This bug is intended to track the merging of the www.mozilla.com and www.mozilla.org components on BMO. It really should live in bugzilla.mozilla.org > Administration.
Assignee: gphemsley → nobody
Status: REOPENED → NEW
OS: Mac OS X → All
Hardware: x86 → All
Target Milestone: Future → ---
Version: other → unspecified
We should get Laura's input here. It's probably fine to continue using "mozilla.com" for a little while but it'd be nice to eventually move everything to "mozilla.org".
Status: NEW → RESOLVED
Closed: 14 years ago14 years ago
OS: All → Mac OS X
Hardware: All → x86
Resolution: --- → FIXED
Target Milestone: --- → Future
Version: unspecified → Firefox 4
(In reply to James Long (:jlongster) from comment #6) > We should get Laura's input here. It's probably fine to continue using > "mozilla.com" for a little while but it'd be nice to eventually move > everything to "mozilla.org". Before we merge anything in bugzilla, I'd like to let things settle with the new site for a bit so we can determine exactly how big the new mozilla.org actually is. My guess is that we'll need to slice the bugzilla components more thinly than just one big one for mozilla.org. (So, basically what James said, with the added note that it may not be as simple as just one mozilla.org component.)
I didn't mean to close this before, my page had a bunch of fields wrongly set, sorry.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to John Slater from comment #7) > Before we merge anything in bugzilla, I'd like to let things settle with the > new site for a bit so we can determine exactly how big the new mozilla.org > actually is. That makes sense. I had just set this up a while ago as a tracking bug so we'd have a place to discuss at some point. Feel free to close this one and open a new bug or do whatever makes sense to sort this issue out.
(In reply to John Slater from comment #7) > (In reply to James Long (:jlongster) from comment #6) > > We should get Laura's input here. It's probably fine to continue using > > "mozilla.com" for a little while but it'd be nice to eventually move > > everything to "mozilla.org". > > Before we merge anything in bugzilla, I'd like to let things settle with the > new site for a bit so we can determine exactly how big the new mozilla.org > actually is. My guess is that we'll need to slice the bugzilla components > more thinly than just one big one for mozilla.org. > > (So, basically what James said, with the added note that it may not be as > simple as just one mozilla.org component.) I agree. I think Mozilla.org will be better off as a Product, given that we have many different sections with many different owners: cbrodigan for Firefox, sancus for Thunderbird, dboswell for community-oriented stuff... I'm sure the list is much longer. And there's also the issue of L10n, which is being covered in bug 556236. Since the merge of Mozilla Messaging, I've been getting l10n-related e-mail that I might not necessarily want as a follower of the www.mozilla.org component, simply because everything is filed in the same place. That is just going to get worse as time goes on and things get merged in, I think.
Status: REOPENED → NEW
OS: Mac OS X → All
Hardware: x86 → All
Target Milestone: Future → ---
Version: Firefox 4 → unspecified
Laura, Renamed this bug and assigning to you. How would you like to approach our Bugzilla workflow for mozilla.org/firefox (formerly .com) in the coming weeks? Best, CB
Assignee: nobody → lforrest
Status: NEW → ASSIGNED
OS: All → Mac OS X
Hardware: All → x86
Summary: Change bugzilla components as needed to track merged www.mozilla.com and www.mozilla.org site bugs → [One Mozilla] Update Bugzilla to new workflow for Firefox product site under .org
Target Milestone: --- → Future
Laura, pinging you on this one. Any thoughts before the merge takes place?
Target Milestone: Future → 3.8
I agree with Comment 10. Make Mozilla.org the product, and then have different components within that. But I'm no Bugzilla pro...
I think there's some value in staying in the Websites product since that's a natural place for people to look when filing bugs or looking for bugs to fix. Another possible suggestion -- stay in the Websites product but have the following components: * www.mozilla.org * www.mozilla.org/firefox * www.mozilla.org/thunderbird
(In reply to David Boswell from comment #14) > Another possible suggestion -- stay in the Websites product but have the > following components: > > * www.mozilla.org > * www.mozilla.org/firefox > * www.mozilla.org/thunderbird Very strong +1 for this - I think it's very important to maintain separate components for the different areas of the site. Otherwise things will get messy.
(In reply to John Slater from comment #15) > (In reply to David Boswell from comment #14) > > Another possible suggestion -- stay in the Websites product but have the > > following components: > > > > * www.mozilla.org > > * www.mozilla.org/firefox > > * www.mozilla.org/thunderbird > > Very strong +1 for this - I think it's very important to maintain separate > components for the different areas of the site. Otherwise things will get > messy. +1 for mozilla.org/firefox I also think this will be super useful in keeping things clear for community members. OK to do this Laura!
Target Milestone: 3.8 → 3.7
Looks like a dupe of bug 681762 now.
Closing as resolved, file under www.mozilla.org/firefox for future.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
verified fixed component is now www.mozilla.org/firefox
Status: RESOLVED → VERIFIED
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.