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.
As an example, by default, when you file a request for support of an event to Developer Engagement, those requests now generate two bugs. One for tracking and another for discussion (which is done in private and flagged company-confidential.) I could give plenty of other examples but because this is a public mailing list it would reach into areas I am not allowed to discuss on a public mailing list. That said, I think our use as a project and as an organization of company-confidential is overzealous and often times does not promote the transparency or working in the open that our manifesto envisions. So I am suggesting we discuss this here and on Moz Governance some. One idea that was suggested to me by Gerv was the idea of having a mozillian-confidential flag that employees and NDA contributors are added to and that we move towards defaulting to this more often. In the cases of things that truly need to be company-confidential then those could still be marked but unless a strong justification could be given for flagging company-confidential then bugs that would ordinarily be made company-confidential would be mozillian-confidential. Thoughts? _______________________________________________ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
