Restrict changes to blueprints to a specific team
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Blueprints on Launchpad are quite nice idea, but in the current iteration they are mostly unusable for upstreams - if upstream chooses to use Launchpad's blueprint system, it ends up being an idea dump for the users, which might sound nice, but defeats the original purpose of blueprints to discuss the technical details of a feature that's planned for a milestone?
It'd be great if maintainers of a particular project could make the blueprint system read-only to public (perhaps even completely invisble) and being able to pick a team that has write permission.
If this is too much to ask, there could be at least a text area in the configuration (similar to bug configuration's "Helpful guidelines for reporting a bug:") where the maintainer could state the intended purpose of blueprints within the project.
| tags: | added: blueprints |
| summary: |
- Allow better configuration of blueprints + Restrict changes to blueprints to a specific team |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: feature |
| Seif Lotfy (seif) wrote | #1 |
I fully agree with the concept. Blueprints should be a discussion area for the people chosen by the maintainers to participate in a technical discussion or implementation of an idea.