318561 - Create Websites product with components www.mozilla.org, mozilla.com, spreadfirefox.com, *.mozilla.org, other

Status: RESOLVED FIXED

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

Description

[Mike Beltzner [:beltzner, not reading bugmail]]

Suggest that we use ...

Description: For issues involving mozilla.com http servers and their content.
Default Assignee: [e-mail]
Default QA Contact: [e-mail]

pkim, you OK with that?

Comment 1

[Paul Kim]

> pkim, you OK with that?

What is the scope of this? Am I going to get all mozilla.com bugs addressed to [e-mail] emailed to me?

Comment 2

[:Gavin Sharp [email: [e-mail]]]

(In reply to comment #0)
> Default Assignee: [e-mail]

I think using a resolvable hostname is discouraged. Maybe [e-mail] ?

Comment 3

[Paul Kim]

(In reply to comment #0)

Beltzner - per our discussion this morning, please add me and [e-mail] as QA contacts for mozilla.com.

Also - can sysadmins add pkim and cbeard as module owners for mozilla.com.

Comment 4

[timeless]

*** Bug 318368 has been marked as a duplicate of this bug. ***

Comment 5

[timeless]

um. let's start with the basics. we've been using watchable addresses fairly consistently for components (it happens that [e-mail] has it reversed, but people haven't really complained). partly this avoids people getting unwanted bugmail and partly it avoids people complaining that bugs they thought were private were being mailed to people who they felt were stalking them.

i'm going to suggest [e-mail] as the qa contact.

as for getting ownership of the module, classically dbaron was among the people to make such changes, sysadmins stayed out of the politics.

once mike settles on a watchable qa contact, justdave can create the account and i'll gladly setup the component.

Comment 6

[Mike Beltzner [:beltzner, not reading bugmail]]

OK, so ..:

product   : mozilla.org
component : [e-mail]
assignee  : [e-mail]
qa contact: mozilla.com@bugs

justdave, can you set up the mozilla.com@bugs address for people to start watching and let us know when that's ready?

timeless, when that's ready, can you create the component under mozilla.org?

Comment 7

[Dave Miller [:justdave]]

OK, we now have a large number of websites that could really use a bug system for managing content requests.  In addition to www.m.o and www.m.c, there's also spreadfirefox.com, devmo, addons, and a smattering of other little subsites.

Maybe we need a Websites product, with components for each of the sites?

Comment 8

[Mike Beltzner [:beltzner, not reading bugmail]]

I'd support that. And we could also rename the components to more sensible:

 mozilla.com
 mozilla.org
 spreadfirefox.com
 addons
 etc

with default QA contacts being

 [e-mail]
 [e-mail]
 [e-mail]

which more or less follows the firefox convention of [e-mail]

(yes I know, I just changed the QA contact again, but if we're changing everything than predictability is goood!)

Comment 9

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Comment 8 makes sense to me.

Comment 10

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

(In reply to comment #0)
> Description: For issues involving mozilla.com http servers and their content.

I think this should be more like:

For issues with content on mozilla.com http servers (but not the functioning of the servers).

and the others should probably be similar.

Comment 11

[:Gavin Sharp [email: [e-mail]]]

*** Bug 313708 has been marked as a duplicate of this bug. ***

Comment 12

[timeless]

ok, this is going to be a multistep process.

for this bug, we're going to:
1. create the Websites product (i will do this)
Description: For issues with content of Websites managed by Mozilla Corporation.
(if people have complaints about wording, I ask that they file new bugs, this bug is unfortunately complicated enough as it involves two people doing work, and will only barely scratch the surface of the changes required).

For the time being, Websites will not appear on the main enter bug page, if at some point it's decided that we need it to, a new bug can be filed and people can discuss that there.

2. move the [e-mail] component to it (justdave will do this)
***** Other things that will move from mozilla.org at a later date: Mozilla Store, developer.mozilla.org, Talkback Server & Webtool, and Server Operations.
3. create a few placeholder accounts and rename a few (justdave will do this)
4. rename Websites:[e-mail] to Websites:www.mozilla.org (i will do this)
5. create a few more components in Websites (all assi's will be [e-mail]) (justdave will create/rename the accounts, I will create/update the components):

Name: Other
QA: [e-mail]
Description: Content of any websites managed by Mozilla Corporation but not covered by other components in bugzilla.mozilla.org

* the reason for the slightly different wording in this component is that temporarily some websites have components in other products, I expect that this will mostly change, although it may always be this way as bugzilla.org kinda falls into this category and lives in the Bugzilla product.
** If people have a better way of phrasing Mozilla Corporation, I am open to ideas, however getting these changes done soon is more important and I don't think it's likely that there's a better way to phrase it, libpr0n.com for instance is not a Mozilla Corporation property and therefore is intentionally excluded from this component.

Name: *.mozilla.org
QA: [e-mail]
Description: Websites in the mozilla.org domain that are not covered by other components in this product. (e.g. bittorrent.mozilla.org and planet.mozilla.org)

*** I'm using -'s instead of .'s specifically because other isn't other.mozilla.org, and other-mozilla.org seems really really strange.

Name: mozilla.com
QA: [e-mail]
Description: For issues with content on mozilla.com http servers (but not the functioning of the servers).

**** 'functioning' seems wrong, i'm open to suggestions in a later bug.

Name: spreadfirefox.com
QA: [e-mail]
Description: For issues with content on spreadfirefox.com http servers (but not the functioning of the servers).

Name: www.mozilla.org
QA: [e-mail]
Description: {current description from mozilla.org:[e-mail], as this will be the moved component. listed here because justdave will be renaming the email address of the component and I will be changing the assignee to nobody and removing the current qa contact.}

Comment 13

[Dave Miller [:justdave]]

Server Ops isn't moving.

Also note, the error handling pages on mozilla.org and mozilla.com will need to be updated to point at the new product/component combination for the "file a bug" link.

And it'll break a bunch of people's stored queries.  But such is life.

Comment 14

[Dave Miller [:justdave]]

Are the current component owners of the sites that have existing components on board with this and aware it's happening?  (Marcia in the case of the store component, I haven't looked around to see who the others are)

Comment 15

[Paul Kim]

On board, and aware WRT mozilla.com.

Comment 16

[Marcia Knous [:marcia]]

What about the default assignee? When I poked around, looks like most of the components are well owned. I think we should keep that behavior - I don't care so much about the QA contact, but I think the default assignee should remain the same where that makes sense.

(In reply to comment #14)
> Are the current component owners of the sites that have existing components on
> board with this and aware it's happening?  (Marcia in the case of the store
> component, I haven't looked around to see who the others are)
> 

Comment 17

[timeless]

ok, we did 1, 3, 4, and 5.

justdave still needs to move www.mozilla.org, fixup the links to it, change the product lists, and eventually fix the error pages.

eventually i'll go through and fix any components that incorrectly reference other components in the wrong place (there are 5-10)

wrt assignee, if you guys have an assignee you like to keep, we're not going to stomp on it. if you're ok w/ us putting in place consistent generics to match the other components, that's good.

note that i'm gone as of 5pm PST today until Feb 1, so I won't be the person doing this work. Also the component move piece is taking justdave a bit longer because he's reinventing the script to do it. 

thanks to everyone for their cooperation and patience. i hope everything is for the best.

Comment 18

[Mike Beltzner [:beltzner, not reading bugmail]]

Since the new product is active but unreachable from the enter_bug page, I filed bug 324498 to get it added there. Thanks for the work to date timeless/justdave.

Comment 19

[Reed Loden [:reed]]

What about mozilla.org :: Mozilla Store and mozilla.org :: developer.mozilla.org? Can they be moved to the Websites product as store.mozilla.org and developer.mozilla.org, respectively?

Also, when will www.mozilla.org be moving to Websites?

Comment 20

[Dave Miller [:justdave]]

yes, and as soon as I write the script to do it.  With my current priorities we're probably looking at next week sometime.

Comment 21

[Mike Beltzner [:beltzner, not reading bugmail]]

(In reply to comment #20)
> yes, and as soon as I write the script to do it.  With my current priorities
> we're probably looking at next week sometime.

Do I have to bribe you with booze for this script? ;)

Comment 22

[Gervase Markham [:gerv]]

Is there anything left to do here? mozilla.org/developer.mozilla.org has turned into the Mozilla Developer Center top-level product.

www.mozilla.org moves to websites in the new reorg:
http://www.gerv.net/temp/bmo-reorg.html

Would you like Mozilla Store moved as well (as store.mozilla.org)?

Gerv

Comment 23

[Reed Loden [:reed]]

(In reply to comment #22)
> www.mozilla.org moves to websites in the new reorg:
> http://www.gerv.net/temp/bmo-reorg.html

Finally.

> Would you like Mozilla Store moved as well (as store.mozilla.org)?

I would, yes.

Comment 24

[Dave Miller [:justdave]]

(In reply to comment #19)
> Also, when will www.mozilla.org be moving to Websites?

About a half hour ago. :)