Diff for "CommercialHosting"

Not logged in - Log In / Register
Differences between revisions 4 and 13 (spanning 9 versions)
⇤ ← Revision 4 as of 2012-03-13 20:22:44 →
Size: 1020
Editor: pool-74-96-179-82
Comment:
← Revision 13 as of 2018-05-29 15:31:33 → ⇥
Size: 1961
Editor: cjwatson
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 user subscription to enable additional privacy features. Proprietary projects require a commercial use subscription. 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:
Project's with a commercial-use subscription may have private-by-default bugs, and you may also request the setup of private code hosting. As the maintainer of a project with a commercial-use subscription, you may create private teams with private mailing lists and package archives. Any project may have a commercial-use subscription to enable commercial-features. Projects with commercial support can configure the bug and branch sharing policies:
 * Public <<BR>> Branches or bugs are public unless they contain sensitive information.
 * Public, can be proprietary <<BR>> New branches or bugs are public, but can be made proprietary later.
 * Proprietary, can be public <<BR>> 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 <<BR>> Branches or bugs are always proprietary. Only people who can see the project's proprietary information can create new branches.
Line 5: Line 9:
You can [[http://shop.canonical.com/product_info.php?products_id=230 | purchase a commercial subscription at the Canonical store]] Commercial subscriptions cost 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 {{attachment:sharing.png}}
Line 7: Line 11:
[[https://launchpad.net/+tour/join-launchpad#commercial|Read more about a commercial subscription to Launchpad]] 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 <<BR>> Visible to team members only
 * Private mailing lists <<BR>> Visible to team members only
 * Private package archives <<BR>> Visible to team members and to users you offer a package subscription too

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.

[[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.

sharing.png

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 only

  • Private mailing lists
    Visible to team members only

  • Private 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.

Read more

CommercialHosting (last edited 2018-05-29 15:31:33 by cjwatson)