Working with branches after 4.6

Stavros Giannouris stavrosg at
Fri Feb 20 20:46:36 CET 2009

On Thu, 19 Feb 2009 21:27:50 +0100
Jannis Pohlmann <jannis at> wrote:

> On Thu, 19 Feb 2009 10:48:37 -0800
> "Brian J. Tarricone" <bjt23 at> wrote:
> > Nick Schermer wrote:
> > > What are the permission problems/limitations?
> > 
> > Git doesn't do fine-grained inside-repo permissions by default.
> > We'd need to write (or find and modify) pre-commit hooks to (for
> > example) allow translator access to the po dirs but nothing else.
> > This isn't super hard, I don't think, but it's something we'd need
> > to do.  Bonus points if it can use our existing svnperms.conf file
> > for all the permissions regexes.  If not, someone needs to redo all
> > that stuff.
> Hm. It should not be too hard, I guess one of us can do that. But I'm
> wondering if that's necessary. Basically, we could just allow one
> *real* user group to access all the repositories, including a few
> translations coordinators. And they could pull from the repositories
> of the translators and then push their changes to the repository.
> That's the nice thing about distributed version control. 
> To make providing the translators' changes to the coordinators easier
> we could set up a separate repository web frontend, because clearly
> not everyone has the possibility to host his repository somewhere
> public.
> If that makes no sense I'd volunteer to look into the access
> management stuff.
> Cheers,
> Jannis

How about using transifex[1] for this, which is made to solve this
exact problem? It has a multi-VCS backend, statistics, and a nice web
interface to help people not familiar with this kind of stuff.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <>

More information about the Xfce4-dev mailing list