Quality/Bug Access Restrictions

Latest revision as of 11:11, 12 April 2011

Incentive

In many open-source projects (such as MeeGo) some bug reports are not accessible to the public. Without guidelines this can create mistrust (see e.g. bug 9943) and theories damaging the reputation of the project.

Restriction Categories

The listed categories are guidelines for QA and developers when a report could be made less accessible by setting the "Internal" or "Security" flag. It is mandatory to mention the category in a comment when restricting access to a bug report.

Access to a bug report, to specific comments, or to specific attachments can be restricted in case they contain:

• Copyrighted information
• Non-public hardware information of MeeGo stakeholders
• Spam advertisements for websites or non-MeeGo products
• Insults towards other users
• On specific request of the author: Content that makes the author appear in a bad light (e.g. accidentially posted file content) or content that reveals critical private data (e.g. private WPA key)
• Security defects are private until a resolution is available: See Security Bug Policy.
• IT infrastructure bug reports are private as sensitive data related to access, servers, etc cannot be exposed.