You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Karl Fogel <kf...@red-bean.com> on 2009/03/18 15:55:12 UTC

Re: Translation stuff to do before a release

Greg Stein <gs...@gmail.com> writes:
> On Wed, Mar 18, 2009 at 15:54, Arfrever Frehtes Taifersar Arahesis
> <Ar...@gmail.com> wrote:
>> Please don't change pl.po in the future.
>
> Anybody in this project is allowed to change pl.po. That is not
> "yours" to solely maintain.
>
> If Jens made a mistake on pl.po, then you can provide a review of his
> change. Or you can fix it. But you're never allowed to tell somebody
> they cannot work on something in Subversion (assuming it is within
> their commit area, according to COMMITTERS).

+1

It's okay to suggest to a committer that they need more experience
before they make changes to something within their commit area.  That's
usually enough to solve the problem; if it's not enough, and someone
continue to make bad commits, then the solution is to have a discussion
here (or on the private committers list, if necessary).  But no one
person can unilaterally tell another to stop committing somewhere in
contradiction to COMMITTERS.

Remember: it's under version control; mistakes can always be reverted.

-K, who hasn't hardly committed in ages, and expects to exercise careful
   judgement when he does

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1349173