1003386 - Create new "Mozilla Foundation Operations" product

Status: RESOLVED FIXED

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

Description

[Angela Plohman]

The name of the product: Mozilla Foundation Operations

The classification (group) you would like the product in: Other

A longer description, usually including a web link for more info on the product: Bugs for the Mozilla Foundation Operations team

The initial list of components, with their info (see below): General
    
The initial list of versions, with their info (see below): None

The initial list of target milestones, with their info (see below): None

The security group(s) bugs should be classified under when a user checks the security flag (if you don't know, we can help figure this out for you): we need a security group for MoFo Operations bugs.

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

If you want review requests to require a reviewer (optional, false by default): N/A

The list of suggested reviewers for the review flag (optional, empty by default): N/A 


///

General component

The name of the component: General

The product it should go in: Mozilla Foundation Operations

A longer description: Bugs for the Mozilla Foundation Operations team

Default assignee: '[e-mail]'

Same as above for QA contact.

Email addresses for whoever should be CC-ed to every bug in the component: N/A

Any flags (bug and/or attachment) that will need to be visible for bugs against the new component: the Default needinfo and review flags

The list of suggested reviewers for the review flag (optional, uses the product's review suggestions by default): None.


///

Security Group

Name for the new group: Mozilla Foundation Operations

Which products need to have the new group enabled: Mozilla Foundation Operations
 
Whether a specific account or mailing list should be automatically cc'ed when a bug is placed in the new group (optional): None

List of users to be placed in the new team group initially: 
[e-mail]
[e-mail]

Who should be the admin for the new group (bless rights) that will be able place others in the team group (optional):
[e-mail]

Comment 1

[Dylan Hardison [:dylan] (he/him)]

Would it be better to make a "Mozilla Foundation" product and have "Mozilla Foundation Operations" be a Component of that product?

Comment 2

[Adam Lofting (:adamlofting)]

Just chatting about this one now (Angela, Jbuck and I), we've concluded that Mozilla Foundation Operations:

* Needs security groups
* Needs the sub-component level of organization 

So is best as a product on it's own.

Comment 3

[Angela Plohman]

One additional note, Mozilla Foundation Operations should only allow bugs to be filed by employees (MoCo or MoFo).

Comment 4

[:glob ✱]

(In reply to Angela Plohman from comment #3)
> One additional note, Mozilla Foundation Operations should only allow bugs to
> be filed by employees (MoCo or MoFo).

that's a very unusual request, and would require development effort to achieve.
can you explain the use-case/reasoning for that?

Comment 5

[Adam Lofting (:adamlofting)]

+Jbuck, as I think you know where this came from.

Comment 6

[:glob ✱]

creating a product for a single component is unusual and wasteful (products are not without overheads).
there's a similar request from adam in bug 1005158 asking for a 'mozilla foundation metrics' product.


angela and adam: i think we can serve you, your users, and bugzilla better by creating a single 'mozilla foundation' product, with 'operations' and 'metrics' as components.  do you have any objections to this?

Comment 7

[Jon Buckley [:jbuck]]

Angela's out sick this week, so attempting to put words in her mouth...

I think Angela's concern was that pretty much every bug that will be filed for MoFo Operations is something that should only be seen by the Ops group. It'd be things like employee contracts, expenses, hr matters, etc.

So, what's the best way to accomplish "A bug gets filed, and by default it is only seen by MoFo Operations?"

Comment 8

[David Lawrence [:dkl]]

(In reply to Jon Buckley [:jbuck] from comment #7)
> Angela's out sick this week, so attempting to put words in her mouth...
> 
> I think Angela's concern was that pretty much every bug that will be filed
> for MoFo Operations is something that should only be seen by the Ops group.
> It'd be things like employee contracts, expenses, hr matters, etc.
> 
> So, what's the best way to accomplish "A bug gets filed, and by default it
> is only seen by MoFo Operations?"

The issue is that if you want different mandatory permissions per component, we have to do different products. Unless we hack in some code in the BMO extension to add the group manually based on the component after the bug is submitted. Not liking that as much. The other thing is that we can set a specific group to be on by default for people in the group when filing the bug so that they would need
to manually uncheck it before submitting. For someone not in the group, they would not see the checkbox at all and the bug would be public. But as I said before, if you want the bug to be private by default even for those not in the operations group, then we will need to do the hack or make two products.

dkl

Comment 9

[:glob ✱]

(In reply to Jon Buckley [:jbuck] from comment #7)
> I think Angela's concern was that pretty much every bug that will be filed
> for MoFo Operations is something that should only be seen by the Ops group.
> It'd be things like employee contracts, expenses, hr matters, etc.

thanks for the clarification.

that's a reasonable reason to require a standalone product, and is much more preferable to bmo specific hacks.

let's proceed with creating this product.

Comment 10

[Angela Plohman]

Thanks for moving ahead with this and apologies for my silence - I have been out sick. If you need any further information about our needs for this product, please let me know. Thanks!

Comment 11

[Angela Plohman]

Hi - I just wanted to check in to see if there are any blockers to moving ahead with this as agreed above? Don't hesitate to let me know if you need any info from me to proceed. Thanks!

Comment 12

[Dylan Hardison [:dylan] (he/him)]

Attachment: bug-1003386.patch

For your review.

Comment 13

[Dylan Hardison [:dylan] (he/him)]

(it's not just a one line change to a file, honest. There are many gears turning behind the scenes. :-)

Comment 14

[:glob ✱]

Comment on attachment 8426064 [details] [diff] [review]
bug-1003386.patch

Review of attachment 8426064 [details] [diff] [review]:
-----------------------------------------------------------------

::: extensions/BMO/lib/Data.pm
@@ +198,4 @@
>      "Websites"                     => 'websites-security',
>      "Webtools"                     => 'webtools-security',
>      "www.mozilla.org"              => 'websites-security',
> +    "Mozilla Foundation Operations" => 'mofo-operations',

please call the group "mozilla-foundation-operations" to match our existing groups.

Comment 15

[Dylan Hardison [:dylan] (he/him)]

Attachment: bug-1003386-v2.patch

Renamed groups, revised patch

Comment 16

[Dylan Hardison [:dylan] (he/him)]

Comment on attachment 8426375 [details] [diff] [review]
bug-1003386-v2.patch

face. palm. facepalm.

Comment 17

[Dylan Hardison [:dylan] (he/him)]

Attachment: bug-1003386-v2.1.patch

Comment 18

[:glob ✱]

Comment on attachment 8426378 [details] [diff] [review]
bug-1003386-v2.1.patch

Review of attachment 8426378 [details] [diff] [review]:
-----------------------------------------------------------------

r=glob

Comment 19

[Dylan Hardison [:dylan] (he/him)]

To [e-mail]:webtools/bmo/bugzilla.git
   4b9eebb..398daee  master -> master

Will resolve when code is deployed and product is enabled.

Comment 20

[Dylan Hardison [:dylan] (he/him)]

The product has been created & is open for bugs.

Comment 21

[Angela Plohman]

This is awesome, thank you so much for your work and help with this!