On 13/04/15 05:46, Benjamin Kerensa wrote:
> We are talking about radical participation this year as a organization
> priority but there are still a lot areas of the project and to Mozilla
> itself that are not visible to core contributors (I like to call it the
> Great Wall of Mozilla) even those who are under NDA. I was recently
> discussing how there is a prevalence to flag groups of bugs and types of
> bugs as company-confidential by default when they could be open to core
> contributors who are in the NDA Group.

To add some data to the discussion, here are some numbers for groups in
Bugzilla which aren't security groups (i.e. they don't conceal security
bugs). All counts are total bugs, other than where indicated.

Note that having a group in this list does not mean I think it should
necessarily have its access permissions broadened.

marketing-private: 381
metrics-private: 1,940
mozilla-confidential: 4049, of which 27 are open
mozilla-employee-confidential: 10,000+, of which 1,973 are open,
  10,000+ fixed
  (Bugzilla won't tell me how many; there's a 10,000 limit)
mozilla-engagement: 889
mozilla-foundation-confidential: 17
mozilla-messaging-confidential: 0
mozilla-reps: 7301
pr-private: 0
privacy: 0
www-mozilla-org-confidential: 11
community-it: 22
consulting: 0

mozilla-confidential for many years early in the project was a catch-all
group for things which needed to be hidden. For many years it was rarely
used, but in mid-2013 it started to receive large dumps of obsolete
bugs. It doesn't seem to be used much for live bugs, although the Data
Compliance group seem to be using it.

Automatic Memberships: mozilla-confidential automatically includes all
Corporation, Foundation and Messaging employees, assuming they are
members of the appropriate (non-bug) group.
mozilla-employee-confidential automatically includes all Corporation,
Foundation and Mozilla Japan employees.

Gerv
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance

Reply via email to