Closed Bug 1353528 Opened 7 years ago Closed 7 years ago

Setup new component called "blogs" under webops product

Categories

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

Product:
bugzilla.mozilla.org
Component:
Administration
Version:
Production
Type:
task

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: rwatson, Assigned: dylan)

References

Details

Hello bugzilla admins!

We have a bunch of people working on blogs and webops wants a new component to help triage that work. Our current components aren't fitting this work well and we have a new use case for this to enable us to work cross teams.


Can we get the "blogs" component setup under webops product.
* Anyone can file and request. 
* Setup default webops assignee 
* QA contact smani@mozilla.com 

Thanks.
Need a component description, please.
Flags: needinfo?(rwatson)
"Requests, support and issues related to blog.mozilla.org or any other Mozilla Blog" 

Thanks!
Flags: needinfo?(rwatson)
Assignee: nobody → ehumphries
Priority: -- → P1
Thank you for your patience. 

There are blog.mozilla.com/theden, and blog.mozilla.org under the websites product. Should the bugs in these be moved into the new blogs component?

Also, is smani@mozilla.com the triage contact?
Flags: needinfo?(rwatson)
No problem.

Yes. I think that's reasonable since webops owns and manages almost everything to do with blogs these days.

And yes, smani is also correct.
Thank you very much.
Flags: needinfo?(rwatson)
Great, I'll do that. What email lists should we notify about the change so that we can minimize surprise?
Perhaps wordpress-owners@mozilla.com This is the mailing list we submit to when we make blog changes.
Otherwise I'll inform the webops and craig.
* Created the component with the assigments for QA and triage
* Moved open bugs in 
  Websites::blog.mozilla.org/theden
  Websites::blog.mozilla.org
  to 
  Websites::blogs
* Disabled filing bugs in the old components
* Opening tickets to move old components and their closed bugs to graveyard
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Hm, Hi Emma. I just had a chance to look at this (I've been out). I must have miss-read your comment as the request was actually to create one called blogs:webops not blog:websites

The reason is, webops is the team that manages the blogs and has a good overview of that component. 

Can we get this moved?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
moving requires shell access, and I can take care of it.
Assignee: ehumphries → dylan
This should be Other:: Infrastructure and Operations :: webops : blogs

This component has been created.

Move the bugs in Other:: Websites: blogs to the new component.
In the future, it's better to just move components rather than move bugs between components.
Any update on moving this to webops? I want to make sure we aren't missing anything.
Any update here?
Flags: needinfo?(ehumphries)
We have one person available to do this and they are getting to admin tasks as they can.
Flags: needinfo?(ehumphries)
Seems reasonable. It went from an assigned to unassigned state so I wanted to make sure it was one someones radar.
Assignee: nobody → dylan
Flags: needinfo?(dylan)
Websites :: blogs is no more, and the bugs are in I & O :: WebOps: Blogs now
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.