bug rejected by unqualified individuals
Bug #73967 reported by
Forest Bond
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
I'm not sure if this is a security breach or not. The individuals that rejected my bug have no visible qualifications for doing so. Please see:
https:/
If these individuals are, in fact, qualified, shouldn't there be some indicator to other users of what their qualifications are? I would expect that they would be maintainers of the package, or members of a group that is considered authoritative on Launchpad. There should be some visual indicator of their veto powers.
Thanks,
Forest
Revision history for this message
| Diogo Matsubara (matsubara) wrote | #1 |
Revision history for this message
| Forest Bond (forest-bond) wrote | #2 |
| Changed in malone: | |
| status: | Unconfirmed → Rejected |
To post a comment you must log in.
Hello Forest,
this is not a security vulnerability and shouldn't be a private bug.
There is some discussion about who should have permission to change the bug status.
See Bug workflow spec <https:/
From my experience on Launchpad, I don't see many people abusing the permission model we have currently. The same applies for the Ubuntu project (I asked Simon Law, Ubuntu's QA Manager).
I'd also suggest that if you don't agree with the way your bug was triaged you can change back the status to Unconfirmed leaving a comment with your rationale or even better you could bring up the issue in the #ubuntu-bugs IRC channel.
Thanks for your report.