Hi All,
Michael. Does it have to be hosted on your server? A lot of projects use Github/Gitorious/Bitbucket as their official repository. They provide the infrastructure for access. For example, on Gitorious you define teams, and when a project is owned by a team, team members can push to the repository.
Just to add my 2 pence to the discussion. GitHub, Gitorious etc. would be ideal and I am sure most of us use them in some capacity if it was not for one caveat.
Most of the major code hosting platforms have been rather copyright takedown heavy of late, especially for a number of kernel projects for matters as simple as headers from 'public' SDK's and whatnot. Some of them are no doubt legitimate but it is unfortunate that all of the hosting platforms have been very quick to pull projects and very slow to reinstate (the recent Qualcomm silliness springs to mind with many other examples).
Considering you lose not just GIT but tracker items and such if the project is pulled/suspended it represents a bit of a risk to the project.
With that in mind it sort of ruled out the 1st choice of GitHub (we use it a lot for the OP stuff, both public and private) and left self-hosting as an option (with mirrors to whatever service took peoples fancy, so could still mirror GIT's to GitHub etc.).
I have used Allura a little in the past and it does the job, Gitorious' self-hosted platform would also be ok but both of them really like a dedicated box/VM to run on so that is something we may wish to consider.
At least if we host all the project parts on a server owned by the project it is harder to cause any heavy handed damage and we have a closer tie between the open aspects and commercial aspects of the project.
Regards,
John