Bug#550817: ITP: gitolite -- standalone, souped-up version of gitosis
Package: wnpp Severity: wishlist Owner: Gerfried Fuchs rho...@debian.at * Package name: gitolite Version : 0.5 Upstream Author : Sitaram Chamarty sitar...@gmail.com * URL : http://github.com/sitaramc/gitolite * License : GPLv2 Programming Lang: Perl Description : standalone, souped-up version of gitosis Gitolite is a rewrite of gitosis, with a completely different config file that allows (at last!) access control down to the branch level, including specifying who can and cannot rewind a given branch. Thanks. :) Rhonda -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550817: ITP: gitolite -- standalone, souped-up version of gitosis
Hi, On Tue, Oct 13, 2009 at 10:15:24AM +0200, Gerfried Fuchs wrote: * Package name: gitolite […] Description : standalone, souped-up version of gitosis Gitolite is a rewrite of gitosis, with a completely different config file that allows (at last!) access control down to the branch level, including specifying who can and cannot rewind a given branch. I suppose, this is not the final version of the description. Anyway, I think it does not make much sense to base most of the description on a reference to gitosis but, rather, it should specify what *gitolite* actually is. In other words: This description would be suitable for people switching from gitosis to gitolite but it does not include much useful information for new users. Cheers, Sebastian -- Sebastian tokkee Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/ Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin signature.asc Description: Digital signature
Bug#550817: ITP: gitolite -- standalone, souped-up version of gitosis
On Tue, Oct 13, 2009 at 10:15:24AM +0200, Gerfried Fuchs wrote:
Description : standalone, souped-up version of gitosis
Gitolite is a rewrite of gitosis, with a completely different config
file that allows (at last!) access control down to the branch level,
including specifying who can and cannot rewind a given branch.
/me playing devil's attorney role
What if one has no idea of what gitosis is? For such a person, the
above description will be close to meaningless. I suggest expanding in a
couple of words what gitosis is, turning the reference to it as
something like similar to gitosis.
Thanks for your packaging work!
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
Bug#550817: ITP: gitolite -- standalone, souped-up version of gitosis
Hi! * Sebastian Harl s...@tokkee.org [2009-10-13 10:46:02 CEST]: On Tue, Oct 13, 2009 at 10:15:24AM +0200, Gerfried Fuchs wrote: * Package name: gitolite […] Description : standalone, souped-up version of gitosis Gitolite is a rewrite of gitosis, with a completely different config file that allows (at last!) access control down to the branch level, including specifying who can and cannot rewind a given branch. I suppose, this is not the final version of the description. Of course it isn't; it's just the short blurb that can be seen on the upstream website about it. Having a full fledged description at ITP stage means that one already started at working on the package - and given that an ITP is meant to be there so that we don't duplicate work and /personally/ the package description is something that I rather *not* think as first of when starting to work on a package sending out the ITP with something final package description is backwards, counter-productive and anachronistic to me. :) Anyway, I think it does not make much sense to base most of the description on a reference to gitosis but, rather, it should specify what *gitolite* actually is. 'sactly, and I'm absolutely with you on that, agree to it and am thankful for you to mention it (just in case it wouldn't have crossed my mind) but see above for why it was done like that. :) So long, and thanks. :) Rhonda -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550817: ITP: gitolite -- standalone, souped-up version of gitosis
on 13/10/09 14:33 Stefano Zacchiroli wrote: On Tue, Oct 13, 2009 at 10:15:24AM +0200, Gerfried Fuchs wrote: Description : standalone, souped-up version of gitosis Gitolite is a rewrite of gitosis, with a completely different config file that allows (at last!) access control down to the branch level, including specifying who can and cannot rewind a given branch. /me playing devil's attorney role What if one has no idea of what gitosis is? For such a person, the above description will be close to meaningless. I suggest expanding in a couple of words what gitosis is, turning the reference to it as something like similar to gitosis. Gitosis (and therefore Gitolite) is an ssh-based gatekeeper for a server that hosts many git repos, and that needs access control of some sort. Without gitosis/gitolite, each developer needing to push to one of the repositories hosted will need a (Unix) userid and password on that server; gitosis/gitolite let you do that just using ssh public keys tied to a single, common, user that hosts all the repositories. Gitolite goes further than gitosis. Its primary target is corporate environments where the ability to restrict who can push to what branch is also important. Over the past few weeks it has grown a bit beyond that primary reason, and acquired several other neat features described in the main README. Thanks for your packaging work! Cheers. -- Sitaram Chamarty -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
