Commercial subscriptions for Canonical projects need extending
Bug #1026612 reported by
Curtis Hovey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
Commercial admins inspect the commercial-support list and the review the list of all new projects because Canonical staff do not make a proper request to extend the trial subscription. It would be better if Launchpad could determine that the proprietary project is owned by canonical and automatically extended the commercial subscription.
The ideas that have considered are:
* The owner of the project is a team, and the team is ultimately owned by a user who is a member of Canonical.
* Do not extend subscriptions to projects owned by users because they can leave Canonical.
* The project is a member of a white-listed project group
* Project groups are hard to configure and cannot be set at the time of project registration
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
| description: | updated |
| tags: | removed: disclosure |
To post a comment you must log in.
Extending subscriptions for any participant of ~canonical is probably sensible, say a year at a time. That would handle current employees, teams of current employees etc., projects with stale owners may expire, but thats no worse than the current situation.