launchpad help|
Size: 2122
Comment: typos and a bit of rewording
|
← Revision 13 as of 2018-05-29 15:31:33 ⇥
Size: 1961
Comment: explain previous commercial subscription scheme
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Any open source project may choose to purchase a commercial subscription to enable additional privacy features. Proprietary projects require a commercial subscription. Details about commercial subscriptions are found on the project's "Sharing" page. | Projects with prior approval from Canonical can use additional privacy features. Proprietary projects may only use Launchpad with such approval. Details are found on the project's "Sharing" page. |
| Line 3: | Line 3: |
| Projects with a commercial subscription can configure the bug and branch sharing policies: | Projects with commercial support can configure the bug and branch sharing policies: |
| Line 13: | Line 13: |
| As the maintainer of a project with a commercial subscription, you can create: | As the maintainer of a project with commercial support, you can create: |
| Line 18: | Line 18: |
| You can [[http://shop.canonical.com/product_info.php?products_id=230 | purchase a commercial subscription at the Canonical store]] for US$250/year/project + applicable V.A.T. If you select 'Other/Proprietary' as the project license, the project overview page also shows the directions to purchase a commercial use subscription | Canonical [[https://answers.launchpad.net/launchpad/+faq/208|formerly sold commercial subscriptions]] which allowed the use of commercial-only features. This scheme is no longer in operation, although use of commercial-only features may still be granted on a case-by-case basis. |
| Line 20: | Line 20: |
| [[https://launchpad.net/+tour/join-launchpad#commercial|Read more about a commercial subscription to Launchpad]] | [[https://launchpad.net/+tour/join-launchpad#commercial|Read more]] |
Projects with prior approval from Canonical can use additional privacy features. Proprietary projects may only use Launchpad with such approval. Details are found on the project's "Sharing" page.
Projects with commercial support can configure the bug and branch sharing policies:
Public
Branches or bugs are public unless they contain sensitive information.Public, can be proprietary
New branches or bugs are public, but can be made proprietary later.Proprietary, can be public
New branches or bugs are proprietary, but can be made public later. Only people who can see the project's proprietary information can create new branches or bugs.Proprietary
Branches or bugs are always proprietary. Only people who can see the project's proprietary information can create new branches.
We recommend that projects share all information types with their developer teams. Sharing with your organisation team will also ensure your co-workers are informed and can do their job. Avoid sharing with users because they leave projects and organisations; if a user needs access to confidential information either add the user a team that is already shared with or subscribe the user to just the bugs and branches then need to work with.
As the maintainer of a project with commercial support, you can create:
Private teams
Visible to team members onlyPrivate mailing lists
Visible to team members onlyPrivate package archives
Visible to team members and to users you offer a package subscription too
Canonical formerly sold commercial subscriptions which allowed the use of commercial-only features. This scheme is no longer in operation, although use of commercial-only features may still be granted on a case-by-case basis.
