FS#17911 - aur packages should have the ability to support multiple maintainers
Attached to Project:
AUR web interface
Opened by Anish Bhatt (anish) - Wednesday, 20 January 2010, 02:23 GMT
Last edited by Lukas Fleischer (lfleischer) - Tuesday, 09 June 2015, 06:56 GMT
Opened by Anish Bhatt (anish) - Wednesday, 20 January 2010, 02:23 GMT
Last edited by Lukas Fleischer (lfleischer) - Tuesday, 09 June 2015, 06:56 GMT
|
Details
many packages have multiple people maintain them and do bug
fixing, however updates are allowed only to packaged
maintainers, and there can be only one maintainer per
package. this can result in bug fixes being available, but
packages not being updated because the aur maintainer is
missing, or duplicate packages because the one and only
maintainer has abandoned his/her aur package.
solution : support multiple maintainers for one package, or add hierarchy such that maintainer can give others permission to update. |
This task depends upon
Closed by Lukas Fleischer (lfleischer)
Tuesday, 09 June 2015, 06:56 GMT
Reason for closing: Implemented
Additional comments about closing: Implemented in 4.0.0-rc1.
Tuesday, 09 June 2015, 06:56 GMT
Reason for closing: Implemented
Additional comments about closing: Implemented in 4.0.0-rc1.
For important/useful/popular PKGBUILDs one can set up an svn or git repo to allow those interested in that particular package to contribute.
I'm not against a permission-based implementation, actually. Just that I don't think it'll be trivial to implement :)
User clicks "adopt package". If no maintainer, user is set as maintainer. If there is an existing maintainer, he is asked to share ownership. If he accepts, then the user is added as a maintainer. They'd all have equal rights, and a disown would remove the user from the list.
Now, if only any of us knew how to actually code for this :P
And yes. At least patch and diff support would be cool.
Every package can have directory ./patches/ in it and users will be able to upload unlimited amount of patches (or even PKGBUILDS which will be processed using diff after upload) to it. There will be nice colorfull diffview and maintainer will be able to accept or reject the diff with single click. There can even be accept/reject links in notification mail, so we will be able to accept/reject the patch from mail using one single click on link.
Then of course the other possibility would be for the 'main' maintainer himself to send requests to other people. If that could be combined with
FS#34692in inactive cases, that'd be.. well awesome.And for the fact that somebody might destroy other one's package there should be some sort of backup logic. It's not enough to just revert to what the package used to be after the main maintainer's last commit, since that might have been a _long_ time ago.
But why not allow pull requests, or something like that ?