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

Re: [BOOK] Translation to spanish

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2004-10-02 21:14:03 CEST

> > >Regardless of hosting issues, I'd still send periodic patches to
> > >include in http://svn.collab.net/repos/svn/trunk once somebody
> > >answers the first question I quoted. And I will still push you
> > >towards internationalising the page at http://svnbook.red-bean.com/.
> >
> > Could you be persuaded to reconsider, Grzegorz?
> > [...]
> > I think everyone would agree that translation should be a full
> > part of the project, not forced out to seek hosting elsewhere.
> My main reason for not wanting to use the main repository to host the
> work being translated is because of the rules outlined in HACKING.
> They are too strict for small and progressive translations. Ariel
> seems to prefer making changes in small batches.

Umm; I can't imagine which rules you are talking about here, so.. I'm
scanning HACKING now for any relevant sections.

Ok. I see these relevant sections in HACKING:

* Writing log messages
* Patch submission guidelines

To start with the latter, it will not be in your way, since you will
(presumably) be committing your changes. The former says you should
write a log message which describes what you changes, continuing to
state requirements to documenting code changes in the log. The
documenting-code-changes-in-the-log part does not apply to the book,
so that the only requirement here will be that you describe the nature
of the changes you applied. Maybe you interpreted HACKING differently?
If so, would using my interpretation be enough to have you use the
Subversion repository?

> The second reason would be the verbosity of the main development
> repository. For practical and psychological reasons I want all
> translators to read all the commits done to the project. The volume
> of svn@subversion.tigris.org is too much for this (which would
> increase by at least 60+ more small commits per month). I don't want
> translators to have to bother with such amount of email. I don't
> want to deal with it myself. My machine has a post-commit hook, and
> that's enough, so we don't need a separate mailing list for commits.

I chatted with some of the other devs in IRC and those who spoke on
the subject feel that your commit volume will not be a problem to the
rest of Subversion development. We welcome your commit volume as we
welcome your project.

> I don't see this as a departure from the main project. The
> communication mailing list would be kindly hosted by
> you. Periodically I would sync the translations of the
> finished documents in our local repositly as patches under your
> submission guidelines. As for the web part, I'll try now with
> svnbook.red-bean.com as you suggested.

We however feel that you can spend your time most effectively if you
can work with only one repository. With resyncing much more risks are
involved at keeping both translations up to date. Besides that, the
project must be more actively managed which takes time we'd like you
to be able to use to do your translation.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 2 21:14:28 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.