launchpad-dev team mailing list archive

[Curtis Hovey <curtis.hovey@xxxxxxxxxxxxx>]

A Brief Primer on Launchpad Privacy (issue 1)
=============================================

This document explains the goals of Launchpad Private structures and the
user experience working with them.

There is a lot to discuss, and many topics will not hold your attention.
This discussion is broken into several emails, sent on different days. I
hope this will help us to semi-independent discussions in a
comprehensible format.

Goals
-----

Canonical and its partners often need to work in secret so that competitors
do not learn about intentions or products until they are ready to be public.

Launchpad will have a single set of rules for managing privacy consistently
across several axes: general traversal, access to a specific artefact, distribution
source package admin, public-private relationships.

In summary:

    Launchpad will provide a way to state a project is private and everything
    that belongs to the project is inherently private as well. This will be
    true for any primary structure that users use to manage their work in
    Launchpad.

    Owners can add users and restricted teams to their private projects.

    Owners of a private structures, such as a project, can see a list of all
    users and teams that have full access to the project or partial access via
    an item like a bug report.

    Owners can see a summary of what an individual user can know about the
    project

    Pages will clearly state that the user is seeing private information.

-- 
__Curtis C. Hovey_________
http://launchpad.net/

Attachment: signature.asc
Description: This is a digitally signed message part