Re: [aur-general] Discussion period - Moving [community] to use same system as main repos
On Sat, Jan 10, 2009 at 03:33:38AM +1000, Allan McRae wrote:
Hi all,
To get this moving along, I would like to start the official discussion period. Standard rules, 5 days discussion, 7 days voting, 75% quorum. If discussion raises some points which really need to be addressed before a vote then it can be delayed.
Abhishek has mad a good summary with some additions by Loui at http://wiki.archlinux.org/index.php/Community_move_to_devtools .
I am very much in favour of this move as it will allow use to use [testing] for community packages, which remove the current problems we have during big rebuilds. It also means that any other changes made to the repos (e.g. arch=any packages, delta support to name my favourites) only needs to be made in one place. I also like the idea of the AUR being just unsupported packages and (despite not actually contributing code to the AUR) I have the feeling that this separation would make AUR development cleaner.
Loosing the ability for users to leave comments about a package on the AUR is not a big deal for me as I think most of these should probably go to the bug tracker where they will not get lost. The concern about autonomy of the TUs is difficult for me to judge being a dev too, but given ~1/3 TUs are devs...
Well, what we lose or gain depends on how the change is implemented. We could still track votes via AUR until a better system is implemented. We just need to be able to get a checkout of everything in community and modify tupkgupdate.
Loui Chang wrote:
On Sat, Jan 10, 2009 at 03:33:38AM +1000, Allan McRae wrote:
Hi all,
To get this moving along, I would like to start the official discussion period. Standard rules, 5 days discussion, 7 days voting, 75% quorum. If discussion raises some points which really need to be addressed before a vote then it can be delayed.
Abhishek has mad a good summary with some additions by Loui at http://wiki.archlinux.org/index.php/Community_move_to_devtools .
I am very much in favour of this move as it will allow use to use [testing] for community packages, which remove the current problems we have during big rebuilds. It also means that any other changes made to the repos (e.g. arch=any packages, delta support to name my favourites) only needs to be made in one place. I also like the idea of the AUR being just unsupported packages and (despite not actually contributing code to the AUR) I have the feeling that this separation would make AUR development cleaner.
Loosing the ability for users to leave comments about a package on the AUR is not a big deal for me as I think most of these should probably go to the bug tracker where they will not get lost. The concern about autonomy of the TUs is difficult for me to judge being a dev too, but given ~1/3 TUs are devs...
Well, what we lose or gain depends on how the change is implemented. We could still track votes via AUR until a better system is implemented. We just need to be able to get a checkout of everything in community and modify tupkgupdate.
Just throwing this out there.... do we need votes once a package is in [community]?
2009/1/9 Allan McRae
Just throwing this out there.... do we need votes once a package is in [community]? One a packages is in [community] pkgstats is enough. My point.
-- Andrea `BaSh` Scarpino Arch Linux Trusted User
participants (3)
-
Allan McRae
-
Andrea Scarpino
-
Loui Chang