[aur-general] Changing AUR development infrastructure.
Recently I've had the idea that I should move the 'main' AUR git repo, which I have been the caretaker of to the community server where all other community and AUR development is done. This would also mean we would have to run a git daemon, and should also install a web interface like cgit to browse the repo. I'm hearing that there is some opposition to this. I'd like to start a discussion to hear the reasons behind that. Here are the reasons I have for moving the repo: * The Trusted Users will have more control over the AUR development since it will be on their own server. * We can use the new infrastructure to host other TU and community projects. * We don't need to create superfluous shell accounts on gerolde to for push access to those repos. Those accounts already exist on sigurd. The AUR and community development infrastructure used to all be hosted on the main Arch Linux server, but we moved the community portion when a new server was donated by sevenl.net. I think it makes a whole lot of sense to also move the rest. Cheers!
I know I'm an outsider (no TU, only did a bit of AUR developement before), so I just have a question: On 17 January 2011 09:19, Loui Chang <louipc.ist@gmail.com> wrote:
Here are the reasons I have for moving the repo: * We don't need to create superfluous shell accounts on gerolde to for push access to those repos. Those accounts already exist on sigurd.
If the issue is having to create extra shell accounts, could it be eliminated using gitolite/gitosis? That would allow more fine-grained control over the permissions of the different projects (which would definitely come up if there are more projects hosted on the same server). E.g. push privileges could be granted to people without TU status when needed, or TUs can be kept off projects they are not taking part in. Just a thought. Cheers, Greg
On Mon 17 Jan 2011 09:40 +0800, Gergely Imreh wrote:
I know I'm an outsider (no TU, only did a bit of AUR developement before), so I just have a question:
On 17 January 2011 09:19, Loui Chang <louipc.ist@gmail.com> wrote:
Here are the reasons I have for moving the repo: * We don't need to create superfluous shell accounts on gerolde to for push access to those repos. Those accounts already exist on sigurd.
If the issue is having to create extra shell accounts, could it be eliminated using gitolite/gitosis? That would allow more fine-grained control over the permissions of the different projects (which would definitely come up if there are more projects hosted on the same server). E.g. push privileges could be granted to people without TU status when needed, or TUs can be kept off projects they are not taking part in.
Yes, that is possible, but that still leave much control over the repo on a foreign server. gitolite/gitosis might be something that we could look at implementing even on the community server for people without shell accounts who we want to give access. Actually not all TUs are able to push to the repo. Only those that have been given admin access. There has even been a non-dev, non-TU that was granted devel/admin access because of proven merit. Currently, any admin/dev of the AUR will need special access to the git repo on gerolde, and to the AUR hosted on sigurd. Since it's not very likely that we would move the hosting back to gerolde it makes a lot of sense to me to move the devel infrastructure to sigurd. So admins of the AUR will only need an account on one server. Admin access includes mysql, web server, and the filesystem, so it definitely requires a shell account.
On Monday 17 January 2011 01:19:22 Loui Chang wrote:
Recently I've had the idea that I should move the 'main' AUR git repo, which I have been the caretaker of to the community server where all other community and AUR development is done. This would also mean we would have to run a git daemon, and should also install a web interface like cgit to browse the repo. I'm hearing that there is some opposition to this. I'd like to start a discussion to hear the reasons behind that.
Here are the reasons I have for moving the repo: * The Trusted Users will have more control over the AUR development since it will be on their own server. * We can use the new infrastructure to host other TU and community projects. * We don't need to create superfluous shell accounts on gerolde to for push access to those repos. Those accounts already exist on sigurd.
Seems sensible to me. Point 2 might be a bonus, if we make it easy for TUs to set up new projects, then we might see more being hosted here. Make it a bit of a hub, so to speak. Pete.
Am 17.01.2011 02:19, schrieb Loui Chang:
Recently I've had the idea that I should move the 'main' AUR git repo, which I have been the caretaker of to the community server where all other community and AUR development is done. This would also mean we would have to run a git daemon, and should also install a web interface like cgit to browse the repo. I'm hearing that there is some opposition to this. I'd like to start a discussion to hear the reasons behind that.
I'd like to point out that we have all the infrastructure on gerolde so that all repos are available for cloning and cgit-browsing in a central place. I don't see the point of duplicating that and scattering our infrastructure further. Currently, all Arch-related projects are hosted in a central place and I'd like to keep it that way.
Here are the reasons I have for moving the repo: * The Trusted Users will have more control over the AUR development since it will be on their own server. * We can use the new infrastructure to host other TU and community projects. * We don't need to create superfluous shell accounts on gerolde to for push access to those repos. Those accounts already exist on sigurd.
If you really think it is necessary, we could always put the main repo to sigurd and have a mechanism set up to sync it to gerolde (either pull with a cronjob, or push from sigurd to gerolde in post-update). As a side note, not more than one or maybe two people should have direct push access to a git repository. If anyone else wants to contribute, they should send pull requests - the maintainer of the main repository should be active enough to pull and merge them quickly though.
Am 17.01.2011 02:19, schrieb Loui Chang:
Recently I've had the idea that I should move the 'main' AUR git repo, which I have been the caretaker of to the community server where all other community and AUR development is done. This would also mean we would have to run a git daemon, and should also install a web interface like cgit to browse the repo. I'm hearing that there is some opposition to this. I'd like to start a discussion to hear the reasons behind that.
I'd like to point out that we have all the infrastructure on gerolde so that all repos are available for cloning and cgit-browsing in a central place. I don't see the point of duplicating that and scattering our infrastructure further.
Currently, all Arch-related projects are hosted in a central place and I'd like to keep it that way. That would also be easier for maintenance, so i vote for staying with
On Mon, 2011-01-17 at 12:57 +0100, Thomas Bächler wrote: the same system. "If it works, don't brake it"
Here are the reasons I have for moving the repo: * The Trusted Users will have more control over the AUR development since it will be on their own server. * We can use the new infrastructure to host other TU and community projects. * We don't need to create superfluous shell accounts on gerolde to for push access to those repos. Those accounts already exist on sigurd.
If you really think it is necessary, we could always put the main repo to sigurd and have a mechanism set up to sync it to gerolde (either pull with a cronjob, or push from sigurd to gerolde in post-update).
As a side note, not more than one or maybe two people should have direct push access to a git repository. If anyone else wants to contribute, they should send pull requests - the maintainer of the main repository should be active enough to pull and merge them quickly though.
-- Jelle van der Waa
participants (5)
-
Gergely Imreh
-
Jelle van der Waa
-
Loui Chang
-
Peter Lewis
-
Thomas Bächler