Closed Bug 783300 Opened 12 years ago Closed 12 years ago

Create New Product For Mozilla.org Website called "www.mozilla.org" & Move Existing Bugs

Categories

(bugzilla.mozilla.org :: Administration, task)

Product:
bugzilla.mozilla.org
Component:
Administration
Version:
Production
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: bensternthal, Assigned: glob)

References

(
URL
)

Details

Note: The below request has been reviewed by Byron. We would like this live on Tuesday August 21. 

Please confirm if this date is OK or if you would like a different date. 

This request can also be found at the etherpad linked to from this bug (easier to read).


= Summary =
Mozilla.org  is now large enough that we would benefit from having it as a product  with components, rather than a single component under Websites. 

= Changes To Existing Component =
Product (Websites) -> Component (www.mozilla.org)
All bugs under the current component should be moved to the new product under the category "general". It is assumed that no bug data other than the product and component will change.

= New Product =

    Product Name: Mozilla.org Website

    Classification: Other Products -> Other

    Description: For issues with content on www.mozilla.org http servers (but not the functioning of the servers). More Info     

    More Info Link -> https://wiki.mozilla.org/Websites/Mozilla.org

= New Components =
Analytics
Bugs and feature requests related to tracking & traffic information

Bedrock 
Bugs and feature requests related to the mozilla.org back end platform

General 
Miscellaneous requests that do not 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 
Bugs and feature requests related to the legacy codebase

Pages & Content 
For creating and updating pages and anything related to HTML/CSS/JS

Project Tracking 
Project tracking bugs.

= Versions =
Use same versioning as current mozilla.org component

= Target Milestones =
Use same target milestones as current mozilla.org component

= Flags = 
None
 
= Custom Fields =
 The name of the field:  Locale
 A longer description:  Denotes the locale affected by this bug or feature
 The type: Multiple Selection Box
 The initial set of values: See Locale List Here 
 http://l10n.mozilla-community.org/~pascalc/langchecker/outputlocales.php
 The  product(s) it should show up in: For now just this product but seems  like it might be applicable to a lot of people at mozilla
 Whether it can be set on bug creation: Yes
> We would like this live on Tuesday August 21. 
> Please confirm if this date is OK or if you would like a different date. 

code pushes happen weekly on thursdays, so the earliest we can achieve this will be end of next week.
Not a problem, Thursday, August 23rd works from our end. If this works for you as well we should be good-to-go.
(In reply to Ben (:bensternthal) from comment #2)
> Not a problem, Thursday, August 23rd works from our end. If this works for
> you as well we should be good-to-go.

We currently already have a 'mozilla.org' product for IT related requests. I think we should do more here to differentiate the two 'Mozilla.org Website' might be too similar and confuse people. That's just my opinion and ignore if I am worrying for no reason. 

Maybe we should talk to others to rename 'mozilla.org' to 'Mozilla' or 'Mozilla Infrastructure' which would help alleviate any confusion.

dkl
(In reply to David Lawrence [:dkl] from comment #3)
> (In reply to Ben (:bensternthal) from comment #2)
> > Not a problem, Thursday, August 23rd works from our end. If this works for
> > you as well we should be good-to-go.
> 
> We currently already have a 'mozilla.org' product for IT related requests. I
> think we should do more here to differentiate the two 'Mozilla.org Website'
> might be too similar and confuse people. That's just my opinion and ignore
> if I am worrying for no reason. 

We should just use "www.mozilla.org". All the other website products use the full URL. There's no reason why this should be different.
(In reply to Reed Loden [:reed] from comment #4)
> We should just use "www.mozilla.org". All the other website products use the
> full URL. There's no reason why this should be different.

s/URL/FQDN/
i agree that "www.mozilla.org" is preferable to "Mozilla.org Website", and as reed said, it's in line with current naming practices.

i don't think that renaming the current "mozilla.org" product would work, as i have concerns about the amount of breakage this would cause with saved searches and external tools.
Summary: Create New Product For Mozilla.org Website & Move Existing Bugs → Create New Product For Mozilla.org Website called "www.mozilla.org" & Move Existing Bugs
I am OK with using the www.mozilla.org as the name, my main concern was confusion with the existing mozilla.org product. 

I do agree with you that the existing mozilla product is not a great name and would support that one being renamed if possible but understand if it is not.

As always thanks for the help.
"locale" custom field created, values populated.  we don't need to use custom code to make this visible on a per-product basis.

i'll start creating the product now.
Assignee: nobody → glob
the product has been created (currently closed for bug entry).

code changes committed:

Committing to: bzr+ssh://bjones%40mozilla.com@bzr.mozilla.org/bmo/4.0/
modified extensions/BMO/lib/Data.pm
Committed revision 8277.
               
Committing to: bzr+ssh://bjones%40mozilla.com@bzr.mozilla.org/bmo/4.2/
modified extensions/BMO/lib/Data.pm
Committed revision 8308.

immediately after this code has been pushed, IT will have to run:

./contrib/reorg-tools/syncmsandversions.pl Websites www.mozilla.org
./contrib/reorg-tools/movebugs.pl Websites www.mozilla.org www.mozilla.org General

(we should ask them to do so on this weeks code push bug).

then we can allow bugs to be created in the new product, and update the description for the mozilla.org product.
Depends on: 784927
done.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Is it expected that a change like that would remove my Component Watching? If yes, then it would be nice to give a heads-up to any person watching the component.
(In reply to Anthony Ricaud (:rik) from comment #11)
> Is it expected that a change like that would remove my Component Watching?
> If yes, then it would be nice to give a heads-up to any person watching the
> component.

ah, yes, sorry about that.  people watching the old component aren't migrated to the new component.

unfortunately the old component has been deleted, so i can't provide a report of people impacted by this.  ben -- be sure to mention this in your announcement.

i'll look at what changes we can make code-wise to ensure this doesn't happen again.
(In reply to Byron Jones ‹:glob› from comment #12)
> i'll look at what changes we can make code-wise to ensure this doesn't
> happen again.

filed bug 785083
Poking around everything looks good.

Thanks for the advice and for completing this on time.
Status: RESOLVED → VERIFIED
Spoke to soon...

The more info link has extra quotes in it https://wiki.mozilla.org/Websites/Mozilla.org%22%22

Should just be

https://wiki.mozilla.org/Websites/Mozilla.org
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
oops, fixed.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Looks good. Thanks again.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.