Re: Permitting more than one account per translation
On Sat, Jan 08, 2000 at 10:14:29PM +0300, Michael Sobolev wrote:
> On Sat, Jan 08, 2000 at 02:06:14PM -0500, James A. Treacy wrote:
> > > What is the objection to many accounts per translation team?
> > Simply that we don't want to spend our time doing admin work.
> I see.
>
> > With 2-3 accounts per translation we should be able to keep the translations
> > on a good footing while keeping the admin down to a minimum.
> Yes, but this does not solve the problem I mentioned: the need to trace the
> changes for all people who made the translation. If not all team members are
> team coordinators :), how one would trace what is changed by whom? If all
> changes are sent to one of the coordinators, this makes the life of the latter
> more difficult than if it were in case all trustworthy translators put changes
> directly into the cvs tree...
>
You can also look at it the other way around: if lots of people can make
changes to the translation, it is harder for the translation coordinator
to keep track of what is going on.
Our original stance was to only allow one account per translation. I feel
allowing 2-3 per translation is a good compromise. Translation coordinators
are still free to set up a secondary CVS server and give out as many
accounts as they wish.
The real problem here is CVS. It isn't very flexible about granting separate
permissions for different parts of the same repository. I'd love to be able
make it so translations could only modify their portion of the repository
and let the coordinators give out as many accounts as they wish for their
area.
--
James (Jay) Treacy
treacy@debian.org
Reply to: