From barry at python.org  Thu May  3 00:45:55 2012
From: barry at python.org (Barry Warsaw)
Date: Wed, 2 May 2012 18:45:55 -0400
Subject: [Mailman-i18n] Looking for the coordinator of zh_cn mailmani18n.
In-Reply-To: <CAE-2OCZYHaxnMJL3=rowH=L5x5D6o83kfjevWxL6nBV7Gopq2w@mail.gmail.com>
References: <CAHcXnBEb5Q7myTHhdktqYHoxuA0uwZfzq+RyvCf=yhEDbxB8Ew@mail.gmail.com>
	<20120428215027.2ba454db@resist.wooz.org>
	<CAE-2OCZYHaxnMJL3=rowH=L5x5D6o83kfjevWxL6nBV7Gopq2w@mail.gmail.com>
Message-ID: <20120502184555.5cc39fdb@resist.wooz.org>

On Apr 30, 2012, at 05:23 PM, Jeremy Baron wrote:

>On Sat, Apr 28, 2012 at 21:50, Barry Warsaw <barry at python.org> wrote:
>>  - translatewiki.net.  Pros: open source (I think),
>
>GPLv2 or later. But a lot of what you get by using TWN is not in the software
>itself, but in the community and staff that exists on the site. If you run
>your own copy you won't necessarily get the same kind of community and staff
>to go with it.

We definitely don't want to run our own service IMO.  However, the code that
the service we use does need to be free software or at least open source.

>>   had some discussion with their developers back in January.  Cons: is wiki
>>   a good fit for translating Mailman?
>
>Why not? ;)

Honestly, since I don't do translations I don't know either, that's why I'm
looking for input. :)

Ideally, the system would be as inviting, open, and easy to use as possible
for translators, but also not be painful for the developers who need to upload
pot files and templates, and download .po files and translated templates on
our own schedule.

One nice thing about transifex IIUC, is that it has an API that we could hook
up to our release scripts.  So we can upload and download from the command
line, which would be fantastic.  I've never tried it though.

>You should talk to some of the existing users of TWN directly to see about
>their experience with it and get some of the existing mailman translators to
>try it out with any project that already uses TWN. (just register and do some
>translations for an hour)

I'd love to get some feedback from folks on this list.  Any translators here
have an opinion?

>>   May have some problems ensuring FSF requirements for
>>   contributions.
>
>I discussed this with the FSF again on Tuesday (6 days ago). There's been
>some progress off and on with getting the FSF to approve the use of TWN. Was
>stalled recently because there were other things distracting them but now
>they're working on it again. I should have another update from them within ~8
>days from now.

Cool!
-Barry

From mark at msapiro.net  Wed May 16 07:57:54 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 15 May 2012 22:57:54 -0700
Subject: [Mailman-i18n] Mailman 2.1.15rc1 released
Message-ID: <4FB341E2.8040808@msapiro.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I am happy to announce the first release candidate for Mailman 2.1.15.

Python 2.4 is the minimum supported, but Python 2.6 is recommended.
This release should work with Python 2.7, but has not been tested with
that version.

This release includes minor security enhancements, new features and
bug fixes. See the Changelog at
<https://launchpad.net/mailman/2.1/2.1.15rc1> for more details.

Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, please see:

http://www.list.org
http://www.gnu.org/software/mailman

Mailman 2.1.15rc1 can be downloaded from

https://launchpad.net/mailman/2.1/
http://ftp.gnu.org/gnu/mailman/

It is anticipated that the 2.1.15 final release will be on or about
June 13. Bugs found between now and then will be fixed if possible,
but I hope that most if not all changes between now and June 13 will
be i18n updates. Please send any updates to the templates and/or
message catalogs in the 2.1.15rc1 release directly to me no later than
June 11.

- -- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFPs0HiVVuXXpU7hpMRAhEfAKDHkpFORnL9a6ka3RRn4WP8m7EsHgCcCKFi
C17WrK2wc2irrXn9Gp2ju8I=
=5wvM
-----END PGP SIGNATURE-----

From mark at msapiro.net  Fri May 18 22:25:02 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 18 May 2012 13:25:02 -0700
Subject: [Mailman-i18n] Mailman 2.1.15rc1 released
In-Reply-To: <4FB341E2.8040808@msapiro.net>
References: <4FB341E2.8040808@msapiro.net>
Message-ID: <4FB6B01E.3070306@msapiro.net>

There was an issue in the tarballs I released for Mailman 2.1.15rc1.

They didn't include the updated version information so they installed as
version 2.1.14. This should not cause problems other than the version
displaying incorrectly. If the tarball was installed as an upgrade over
a 2.1.14 installation, the update script would not run to update list
attributes, but the lists would be updated when they are later
instantiated so this shouldn't be a problem.

The release tarballs at

https://launchpad.net/mailman/2.1/
http://ftp.gnu.org/gnu/mailman/
https://sourceforge.net/projects/mailman/

have all been replaced with the correct one. There is still an issue
with the bzr branch on Launchpad in that the 2.1.15rc1 tag is on
revision 1354 instead of 1355, but that will be fixed soon.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan