## page was renamed from LEP/ManagingDisclosure
= Sharing =

Project and distribution owners can share and unshare restricted/private
data with users and teams.

Project and distribution owners need to see who restricted information
about their project is shared with.

[[PrivateProjectsAndDistributions]]


== Rationale ==

With the introduction of private projects and distributions, owner need a
way give share to hundreds of private project artefacts.

Stakeholders need to know who they are sharing with, and in a single action,
share more or unshare. This is valuable to public project with default private
bug and branches--once restricted data is shared with a company team, all
employees have access to company information.

e.g. Steve Magoun from OEM would like to be able to see exactly who has access
to every component in his project.


== Stakeholders ==

 * OEM (Joey Stanford, Steve Magoun, Cody A.W. Somerville)
 * Hardware enablement (Chris Van Hoof, Hugh Blemings)
 * ISD (Stuart Metcalfe)
 * Landscape (???)
 * UbuntuOne (John Lenton)

== User stories ==

<<Anchor(commercial-stories)>>
=== Commercial stories ===

'''As a ''' commercial project owner<<BR>> 
'''I want ''' to mark some data as proprietary that should not be shared with other projects<<BR>>
'''so that ''' information provided in confidence is not disclosed<<BR>>

'''As a ''' commercial project owner<<BR>> 
'''I want ''' share proprietary information with users and teams<<BR>>
'''so that ''' my organisation and contractors can collaborate<<BR>

<<Anchor(canonical-stories)>>
=== Canonical stories ===

'''As a ''' member of ~canonical<<BR>> 
'''I want ''' to share everything proprietary data in my project with ~canonical<<BR>>
'''so that ''' that members of my organisation are not blocked from collaborating<<BR>

'''As a ''' member of IS<<BR>> 
'''I want ''' to add a new employee to the ~canonical team<<BR>>
'''so that ''' that he has access to all information shared with ~canonical<<BR>

'''As a ''' member of IS<<BR>> 
'''I want ''' to run remove all things shared with a former Canonical member in Canonical projects<<BR>>
'''so that ''' that confidential data is not disclosed<<BR>


<<Anchor(oem-stories)>>
=== OEM stories ===

'''As a ''' maintainer of OEM projects (~pmteam)<<BR>> 
'''I want ''' to share everything with ~oem-dev (the driver)<<BR>>
'''so that ''' they I can delegate all development to them<<BR>>

'''As a ''' driver OEM projects (~pmteam)<<BR>> 
'''I want ''' to share some bugs and branches with a contractor<<BR>>
'''so that ''' he can fix the issues for us<<BR>>

'''As a ''' maintainer of OEM projects (~pmteam)<<BR>> 
'''I want ''' to see all users who have some things shared with them<<BR>>
'''so that ''' I can share nothing with them if they are not under contract<<BR>>


<<Anchor(ubuntu-stories)>>
=== Ubuntu stories ===

'''As a ''' the maintainer of Ubuntu<BR>> 
'''I want ''' to unshare user-data with maintainer and share user-data with the apport bot<<BR>>
'''so that ''' no human has access to personal user-data<<BR>

'''As a ''' the maintainer of Ubuntu<BR>> 
'''I want ''' to unshare security with maintainer and share user-data ~ubuntu-security<<BR>>
'''so that ''' only trusted experts see security issues<<BR>>


== Constraints and Requirements ==

=== Must ===

 1. A lists of all the users with all or some things shared. <<BR>>
 The view must also show exactly ''how'' the user has access, for example: directly or via a team;
 as a (core?) contributor or as a user; by subscribing to some artefacts or through access to the whole project.


 1. A summary everything an user may know about the project.<<BR>>
 The view must also show how the user was shared: direct or via a team.

 1. A way to share everything with a user or team.<<BR>>
 When a owner shares with a team, the view must show who who is being
 shared with and how many members (person-picker).

 1. A way to unshare everything with a user or team. <<BR>>
 Revocation removed all subscriptions to individual artefacts be default.
 The owner many choose to keep some subscription so that partial access is
 allowed. If the user has access via a team, the view must explain how to
 remove either the user or the team to unshare.


=== Nice to have ===

 1. List the users who everything is shared via the owner or driver team. <<BR>>
 The owner may need to know about contributors as well as users. If the
 owner can unshare with an owner/driver, then the user must be removed
 from the team and assignments and subscriptions are removed too.

=== Must not ===

 1. Unsharing with a user or team must not allow the user to have some things shared.<<BR>>
 Revoking access to a user must remove the individual subscriptions that
 provide partial access.

 1. Sharing must not cede control of what is shared.<<BR>>
 Inclusive teams (open and delegated) may not be shared with.
 Inclusive teams allow anyone to choose to become a member, which undermines the
 owner's power to manage the information disclosure.


== Subfeatures ==

 1. Replace bug and branch privacy mechanism with a common way classify the data
    * private and security/branch visibility do not interact with each other
    or meet the needs of sharing all of a kind of restricted data.
    * Use Public, Unembargoed Security, Embargoed Security, User data
    to describe the existing kinds of privacy
 1. Introduce the Proprietary kind of privacy that is not multi-tenant.
 1. Introduce a choice picker that support descriptions with the terms.


== Workflows ==

 1. Viewing a list of users that the project is shared with
 and a summary for a single user when some things are shared.

 1. Share a kind of information with a user or team

 1. Failing to share with a team that is inclusive.

 1. Unsharing with a user with all things shared.

 1. Unsharing with a user with something things shared.

 1. Unsharing with a team with something things shared.


== Success ==

=== How will we know when we are done? ===

 1. An owner can see all users that restricted information is shared with.

 1. The owner can see is the information was shared to the user, via team, or via a bug or branch.

 1. The owner can see a summary of the artefacts that were shared.

 1. The owner can unshare a user and see what the user was unsubscribed from
 everything.


=== How will we measure how well we have done? ===

 1. All canonical projects with proprietary data are shared with ~canonical.
 1. Ubuntu only shares User Data with ~apport and Embargoed Security with ~ubuntu-security
 1. OEM projects share all kinds of data with drivers


== Thoughts? ==

=== jml ===

 1. Owner, drivers, security contacts and bug supervisors are assumed to have full access.
 1. We should get a team within Canonical to beta test