When we first started the Moblin project, we hosted git source
repositories using traditional unix accounts where granting somebody
write access required a user account with the use of unix groups to
control who could write.

This was a pain from day one for a number of reasons, and if any of you
have tried managing a bunch of repos like this then you know what I'm
talking about.

On my first trip to meet the OpenedHand guys face-2-face, they turned me
on to a pretty cool project called gitosis which only requires one user,
and then uses ssh keys to manage who has access to what repos.  When
this is combined with a git-daemon providing read-only access via the
git:// protocol, and then something like cgit to provide a web interface
for browsing the source.... well, it works out to be a nice way of
managing a source repository sever.

For those that are curious, a great article about gitosis can be found
at:
http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way

We started using gitosis on git.moblin.org to host new projects, but
didn't really talk about it, didn't attempt to move all the existing
projects, and never had a proper web interface to expose the project
that lived in gitosis (as opposed to the old location on the server.)

Now that we have a bunch of new projects starting to land, I want to go
ahead and start with a fresh new machine configured in a sustainable way
using gitosis, git-daemon (for read-only access), and cgit.

If you currently have write access to a git tree on moblin (that is not
using gitosis), then please send me your public ssh key and the name of
the tree that you work on.  

I'll send another email right before doing switch.

    --rusty 

_______________________________________________
Moblin dev Mailing List
[email protected]

To manage or unsubscribe from this mailing list visit:
https://lists.moblin.org/mailman/listinfo/dev or your user account on 
http://moblin.org once logged in.

For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists

Reply via email to