On Apr 30, 2012, at 05:23 PM, Jeremy Baron wrote:
On Sat, Apr 28, 2012 at 21:50, Barry Warsaw <barry@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