885372 - Create new Product for MoFo Communications in Bugzilla

Status: RESOLVED FIXED

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

Description

[Matt Thompson (@OpenMatt :OpenMatt)]

* Product = Mozilla Foundation Communications
* Components = TBD
* Erica S: let's work out details here: 
https://etherpad.mozilla.org/MoFo-bugzilla

Comment 1

[David Humphrey (:humph)]

I assume you mean "create a new Product + Components in existing bugzilla?"  You almost certainly don't want to have to manage your own instance.

Comment 2

[Matt Thompson (@OpenMatt :OpenMatt)]

Yes, that. :)

Comment 3

[Matt Thompson (@OpenMatt :OpenMatt)]

* Scheduling a meeting on this so we can push ahead

Comment 4

[Matt Thompson (@OpenMatt :OpenMatt)]

* Let's forget the meeting and push ahead
* Components listed above. Can you push ahead with this?

Comment 5

[:glob ✱]

there's a lot more information that we'll need to create a product, please see the requirements on https://wiki.mozilla.org/BMO/Requesting_Changes#Products

Comment 6

[Erica Sackin]

Amazing! 

I've added two more components, if that's OK. 

    Message platform

    Launch

Is there any way to get those added as well? 

@matt are you handling the documentation for filing? Let's connect before you send anything around staff-wide -- I'd like to combine it w/ a few other comms teams updates.

Comment 7

[Matt Thompson (@OpenMatt :OpenMatt)]

* Any status updates on this one? Anything anyone needs Erica or I to additionally file or complete here?

* Product = "Mozilla Foundation Communications"
and Components required are here:
https://etherpad.mozilla.org/MoFo-bugzilla

Comment 8

[David Lawrence [:dkl]]

(In reply to Matt Thompson (@OpenMatt) from comment #7)
> * Any status updates on this one? Anything anyone needs Erica or I to
> additionally file or complete here?
> 
> * Product = "Mozilla Foundation Communications"
> and Components required are here:
> https://etherpad.mozilla.org/MoFo-bugzilla

Just a reminder that the etherpad is still lacking the additional information we will need to create the new product as outlined here https://wiki.mozilla.org/BMO/Requesting_Changes#Products

Thanks
dkl

Comment 9

[Matt Thompson (@OpenMatt :OpenMatt)]

Thanks David! Does this do it?




     The name of the product: Mozilla Foundation Communications

     The classification (group) you would like the product in: "Other." (assuming this refers to the categories listed here? https://bugzilla.mozilla.org/enter_bug.cgi )

     A longer description, usually including a web link for more info on the product: The Mozilla Foundation runs programs like Mozilla Webmaker, Open Badges, Open News and more. http://www.mozilla.org/foundation/

     The initial list of components, with their info:

    Launch

    Press

    Blog

    Graphic Design 

    Logo design & identity

    Social Media 

    Email outreach

    Web site 

    Message platform

    Documentation

    Press materials 

    Copy editing/ review

    
The initial list of versions, with their info: not applicable

   
The initial list of target milestones, with their info: not applicable

   
The security group(s) bugs should be classified under when a  user checks the security flag: let's follow the same protocol for this as the Webmaker product.

   
The number of votes needed to confirm a bug (UNCO --> NEW) (optional, disabled by default): not needed

Comment 10

[:glob ✱]

sorry, but we'll need more information for each of those components.
see https://wiki.mozilla.org/BMO/Requesting_Changes#Components
while we can guess most of those, you'll have to provide the component descriptions.

Comment 11

[Matt Thompson (@OpenMatt :OpenMatt)]

Ok thanks Byron. Here's the component descriptions:

    Launch -- for software releases, big announcements, launching new initiatives, etc.

    Press -- PR and outreach to journalists and newsmakers

    Blog -- posts to the Webmaker blog, Mozilla blog and others

    Graphic Design -- visual assets and design work

    Logo design & identity -- design work related specifically to logos, wordmarks and branding

    Social Media -- planning and programming for our social media channels 

    Email outreach -- email sends to our main mailing list 

    Web site -- web site content, planning and strategy for webmaker.org and other MoFo sites

    Message platform -- talking points and key messaging 

    Documentation -- HOW TOs and documentation for users 

    Copy editing / review -- for editing text and tightening copy

Comment 12

[Matt Thompson (@OpenMatt :OpenMatt)]

* does what I've listed above work? I'm on PTO as of Thurs, so just want to make sure I provide everything needed before then. Thanks!

Comment 13

[David Lawrence [:dkl]]

(In reply to Matt Thompson (@OpenMatt) from comment #12)
> * does what I've listed above work? I'm on PTO as of Thurs, so just want to
> make sure I provide everything needed before then. Thanks!

Pretty sure that gives us what we need to get started. We will try to knock this out asap.

dkl

Comment 14

[David Lawrence [:dkl]]

lizzard, can you take this one? I can do if not.

dkl

Comment 15

[Matt Thompson (@OpenMatt :OpenMatt)]

Thanks David! Much appreciated.

Comment 16

[Liz Henry (:lizzard) (relman/hg->git project)]

Matt: here you go:

https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Foundation%20Communications

Each component has a watch user, such as "[e-mail]". In a user's Bugzilla Preferences, under the Component watching tab, they can set their account to get bugmail whenever a change is made to a bug in that component. So, for each component, if you have particular people responsible for monitoring activity, you may want to walk them through setting up component watching and setting up bugmail filters in their email client. 

I set the group access controls to be the same as Webmaker, though I'm not sure that is necessary.

Comment 17

[Matt Thompson (@OpenMatt :OpenMatt)]

Thanks Liz! Great news.