Clean up owner and registrant attributes
Bug #153333 reported by
David Allouche
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
As a rule, Launchpad content classes should have:
* A "registrant" attribute, immutable, that records the person who initially registered the object.
* An "owner" attribute, mutable, that is used for access control.
Many content classes in Launchpad do not have a registrant attribute, they should be fixed.
Some objects are not user-created and/or do not need ownership semantics. They should be reviewed by the DBA and granted exceptions.
See also bug 207532 bug 1581, bug 51804, bug 150962, bug 202135, and bug 360076.
| description: | updated |
| Changed in launchpad: | |
| status: | New → Confirmed |
| Changed in launchpad-registry: | |
| importance: | Undecided → Wishlist |
| status: | Confirmed → Triaged |
| description: | updated |
| description: | updated |
To post a comment you must log in.
Existing content classes and database classes needs to be audited for their use of the "registrant" and "owner" attributes.
* Where "owner" is used and "registrant" should be used, the attribute should be renamed.
* Where ownership semantics are wanted, but an immutable "registrant" attribute is used, a mutable "owner" attribute should be added, initially set to the registrant.
* Where no immutable attribute is present to record the person who registered the object, a "registrant" attribute should be added. A data migration strategy (picking a default value, or allowing NULL values) must be defined.