Le 13/04/2015 06:46, Benjamin Kerensa a écrit :
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.
[...]
Thoughts?
Hi,
I have to deal regularly with bugs marked as employee confidential,
mostly marketing ones. Here is what I noted:
- some employees mark all of their bugs as employee confidential, I am
guessing that they are using one of these simplified forms that have
that option by default
- sometimes, bugs are marked as 'security confidential' when they should
be marked as 'employee confidential'
- The confidentiality of these bugs is related to a partnership and
usually an announcement on our web parts of something done with
partners, that can be for example a bug with screenshots where you can
see a Firefox OS partner logo. When the information becomes public, the
confidentiality flag is not removed while there is nothing secret anymore.
As I work with localizers who are volunteers, it can be annoying because
they can't see the content of the bug, yet they are supposed to
translate stuff that is described in the bug, which means that we have
to CC manually trusted localizers to the bug, which also means that it
is often the same localizers that have to work on this urgent stuff
(when it involves partners, it always comes late because of legal
reviews and there is always an additional dosis of stress involved ;) ).
The concept of a wider range of confidential bugs that would give access
to trusted mozillians is interesting, that's the kind of more granular
rights that you can see in CMS. It could also add another level of
complexity though.
What personnally I'd like to see happening is two things:
1/ A reason in the bug description why this bug was marked as
confidential ('Marking this bug as employee confidential because it
contains infrormation that we don't want to be public before date x" for
example).
2/ See all bugs marked as employee confidential get this flag removed
when the reason makes no sense anymore (new secret product launched in
market X, anouncement of a partnership now everywhere in the press...)
3/ On the simplified forms, have a separate field where the employee
explains why a bug is confidential and append this explanation to the
bug description in comment #0
Cheers
Pascal
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance
