Diff for "Bugs/PrivateBugs"

Not logged in - Log In / Register
Differences between revisions 5 and 6
⇤ ← Revision 5 as of 2011-03-23 22:59:18 →
Size: 2365
Editor: ppp121-44-132-166
Comment: note about apport private bugs
← Revision 6 as of 2012-09-06 17:45:41 → ⇥
Size: 0
Editor: pool-108-28-25-212
Comment: This draft was published a long time ago.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from PrivateBugs/Draft
~-[[FrontPage|Launchpad Help]] > [[Bugs]] > Private bugs -~

||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||

= Overview =

While most agree that "[[http://en.wikipedia.org/wiki/Linus%27s_law|given enough eyeballs, all bugs are shallow]]", some bug reports should only be seen by a restricted group of people.

Launchpad gives you two levels of privacy for bug reports: private bugs and security-related bugs.

== Private bugs ==

Anyone can mark an existing bug as private or, as a project owner, you can choose to have all bugs reported against your project marked private by default.

Once someome marks a bug report as private:

 * it no longer appears in search results or bug listings, unless you have permission to view the full report
 * indirect subscribers to the bug -- i.e. people who are subscribed to all bugs related to the project, package or distro -- become direct subscribers
 * the full report is visible only to the bug's direct subscribers and the relevant owners/drivers.

This means that, after the bug has been marked private, no new people can view or subscribe to it without an invitation from an existing direct subscriber but that anyone subscribed -- directly or indirectly -- before the bug was private will continue to have access.

=== Apport-filed bugs ===

When Ubuntu's crash-reporting tool {{{apport}}} files a bug for you, [[https://wiki.ubuntu.com/CrashReporting|it initially marks it as private]]. Later a developer will check there's no personal information in the report, and then make it public.

== Security-related bugs ==

Again, anyone can mark a bug report as a security vulnerability. Security-related bugs behave in a similar way to private bugs, except that:

 * Launchpad emails the project or distro's security contact with details of the bug report
 * indirect subscribers are not converted to direct subscribers, giving you greater control over who can view the report.

= Next step =

Let's look at how Launchpad handles [[Bugs/Expiry|bugs that have gone stale]].

||<tablestyle="width: 100%;">~-[[Bugs/YourProject|< Tracking your project's bugs in Launchpad]]-~||<style="text-align: right;">~-[[Bugs/Expiry|Bug expiry >]]-~||