[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Two projects sharing one repos (was Re: svn commit: r11950 - trunk/doc/translations/spanish/book)

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-11-20 20:54:29 CET

On Nov 20, 2004, at 12:52 PM, Grzegorz Adam Hankiewicz wrote:
> Commit access to the Spanish translation is based on capability of
> speaking Spanish and accepting the project's rules. Commit access
> to the full tree doesn't go through this validation. Unless proven
> otherwise I don't consider any full commiter capable of modifying
> the translation.
> Surely this is obvious?

It is obvious. It's also obvious that every full committer isn't
capable of committing to every single part of the repository.

For example, I would never commit to the swig bindings, because I don't
know squat about them. But if I *did* think I was making a correct
change to the swig bindings, I would expect people to give me the
benefit of the doubt and review my publically change. If the change
were bad, I would expect people to object and discuss publically.

The problem here is that there's a communication gap. It looks like we
have two completely independent projects going on:

   * the projects have different rules, policies, and entry criteria
   * the projects' participants don't overlap at all
   * the projects have separate email lists
   * neither group is reading the other's list.

In every sense, these are separate projects -- they just happen to be
sharing a repository. Because there's no other point of communication,
it's understandable that the Subversion developers freak out when they
see a revert happen out of the blue! It's also understandable that the
leader(s) of the Spanish project are surprised when an unknown "full
committer" commits to the Spanish translation. One group thinks that
area of the repository is a private to a small set of people; the
other group thinks the entire repository is available to all full

I'm not sure what we should do about this. It seems like the Spanish
translation project is already 90% independent of the Subversion
project... maybe it it makes sense to give it a separate repository and
tigris page, doing the last 10%? If we don't do that, another
alternative is to read each other's lists. But that might be odd --
I'm pretty sure the Spanish translators aren't interested in API and C
spec discussions, nor are the svn devs interested in discussing the
proper Spanish terms for computer jargon.

Is there any other way to close the communication gap?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 20 20:55:49 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.