co authors are not able to Abandon specs
Bug #1394336 reported by
David Chadwick
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Core Infrastructure |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
When writing keystone API specs, it is possible that several people may collaborate on it. One of the authors then submits the spec, and the rest are named as co-authors in the Commit message. However, only the submitting author sees the Abandon option. The co-authors do not have this permission. In many cases this is not be a problem, but if the submitting author moves to another job, leaving the other authors to continue the work, if for any reason they wish to abandon the work some time later, they are no longer able to do so.
Could it be possible to give co-authors the abandon permission as well as the submitting author?
Revision history for this message
| Jeremy Stanley (fungi) wrote | #1 |
| tags: | added: gerrit |
| Changed in openstack-ci: | |
| status: | New → Won't Fix |
To post a comment you must log in.
This is a limitation of Gerrit, specifically that it does not actually know anything about co-authors of a change (it's just arbitrary text in a commit message from the software's perspecitve). We somewhat mitigate this problem for the "abandon" feature by also granting abandon and restore privileges on projects to core reviewers of those projects, so as a workaround you can ask anyone who has the ability to +2/-2 and approve a change to abandon or restore it for you.
Implementing any features around co-authorship would have to happen upstream in the Gerrit project, so I'm marking this won't fix from the project infrastructure perspective.