Blueprint Registration should have been able to set ACLs
Bug #1234738 reported by
Howard Chan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
In the Ubuntu project page on Launchpad (https:/
The blueprint feature has been spammed the past year as a way to request features, whilst feature requests should be done via reporting bugs in Launchpad.
I think it would be a great idea if we can set ACLs for registering blueprints, so the feature doesn't get spammed too much. For Ubuntu, it might either be ~ubuntu-members or other teams.
Revision history for this message
| Colin Watson (cjwatson) wrote | #1 |
| tags: | added: chr lp-blueprints |
| Changed in launchpad: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| importance: | Low → High |
To post a comment you must log in.
Blueprints have been spammed for something like the last seven or eight years, sadly, not just the past year. It's a very long time since looking through the blueprint list was a remotely helpful indicator of developer activity; and most of the blueprints filed by casual users never get any attention, since they have been misled into thinking that filing a blueprint is a useful way to make a feature request, rather than a mechanism for developers to plan, coordinate, and record non-trivial feature development work.
I think it'd be reasonable to use the members slot for this. Really, blueprints are a tool for developer coordination, but it's quite common for them to be registered by people in management positions and I think the developer slots would be a bit too restrictive in practice. The bar for membership should be low enough that anyone who's really involved shouldn't have a problem, while it would steer casual users to more constructive avenues for feature requests.