On 2004-09-26, Max Bowsher <email@example.com> wrote:
> If you would like a mailing list, to discuss the translation in
> spanish, then I see no problem with providing one.
> The current dev/users lists are moderated. If you want a list,
> should it be moderated or unmoderated, and if moderated, we will
> need a list of moderators.
Thank you very much.
My only experience with mailing list moderation has been through
the mailman interface provided by SourceForge services. The model I
have in mind is for subscribed users to be able to post freely. Non
subscribers don't need to subscribe in order to post, but their
messages will have to await moderation.
Moderation should be done at least by two people. I will ask Rubén
and Ariel if they want to moderate it too. I'll get back to you
with their answer if they don't to reply to this publicly.
> >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. Rubén and me go
with a minimum of one paragraph a day, which we find better to avoid
overloading ourselves and still be able to share those changes with
others interested in them. At the moment I see no advantage working
directly against http://svn.collab.net/repos/svn/trunk.
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 firstname.lastname@example.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 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.
PD: Please don't send me private copies of your public answers. TIA.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Sep 26 18:38:34 2004