Mailman 3 April 2006 - Mailman-i18n

Vietnamize mailman
by ho anh April 18, 2006

April 18, 2006

I want to translate Mailman into Vietnamese. It means that the language use in Mailman program include of Vietnamese. Please tell me how to Vietnamize Mailman ! Thank a lot --------------------------------- Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min.

2 1

New Mailman wiki, Subversion (and other stuff)
by Barry Warsaw April 15, 2006

April 15, 2006

For a while now, I've been trying to implement several project management improvements for Mailman, so that future development can be opened up to more people. As Tokio's and Mark's work has shown, there are very talented programmers out there that can contribute great stuff to Mailman if given a chance. Folks like Brad, JC, and Terri have also contributed greatly in ways other than with code, and I'd like to make it easier for others like them to help out. With 2.1 in maintenance mode, planning for 2.2 gearing up, and my desire to once again jump start 3.0 work, we need all the help we can get. While I'm still working on some things, there have been some good developments that I wanted to let you know about. First, Atlassian has offered free licenses and hosting for their excellent products Jira (issue tracker) and Confluence (wiki). I've used both for several years now and I think they are top-notch applications; Jira is definitely one of the best issue trackers I've used. The wiki is now live, although not a lot of content has been moved there. Please see <http://wiki.list.org>. You can browse the wiki anonymously, but you must sign up to make any additions or changes. I would eventually like to move things like the Mailman FAQ, list of Mailman users, online documentation (where it doesn't overlap with the latex docs), and all community contributed content from the main web site to the wiki. If you've been looking for a way to contribute to Mailman that doesn't involve coding, here's your chance! While Jira is live, there's nothing yet there. I've done only the minimal configuration for the issue tracker, but have not yet even set up any projects. Still, you can go to <http://bugs.list.org> to sign up or get a feel for the basics. Right now, I'm working on a conversion script that will take the SourceForge tracker data and massage it into a form that Jira can import. My plan is to move all issue tracking to Jira from SF's trackers. One option to getting there faster is to just start Jira from scratch -- i.e. not import the SF issues. We could say that all 2.2 and 3.0 bugs and patches must go to Jira, but that 2.1 bugs would stay on SF. Then, when 2.1 is retired, we'd retire the SF tracker (that may not be for a long time though, given how pervasive 2.1 is). I'm interested in getting opinions about whether we should migrate all issues to Jira now, split the issues as described above, or take some other approach. Now that Mailman 2.1.8 is out, I've gone ahead and converted the SF CVS repository to Subversion. You can checkout the entire tree via <https://svn.sourceforge.net/svnroot/mailman> but understand that that will checkout /everything/ (trunk, tags, branches, etc). If you just want Mailman 2.1, you can check out <https://svn.sourceforge.net/svnroot/mailman/branches/Release_2_1-maint>, or if you just want the trunk (2.2) you can check out <https://svn.sourceforge.net/svnroot/mailman/trunk>. You should no longer be able to check anything into the CVS repository. Not everyone who had write permission to CVS has been given Subversion write access. If you still need write access to Subversion and don't have it, please let me know. Now that the conversion is complete, I plan on doing some repo house cleaning, such as moving the website stuff out of the main directory. After that, we can decide to leave the Subversion repository on SourceForge, or move it to Atlassian's hosting. The latter gives us the ability to control write permissions per directory and a hook to Fisheye for repo browsing through the web. Even if we want to move, we don't need to do that right away, as an svn dump/restore should do the trick. Now that these changes have been made, I think it's time to start planning for Mailman 2.2. To that end, I would like most development artifacts to be recorded in the wiki, although discussion should still happen on mailman-developers (there's a 'Development' space and a link for 2.2 under that). I also plan on getting our data imported into Rosetta so we can coordinate i18n there; it's mostly my fault I've dropped the ball on this one. Longer term, as we begin to restart Mailman 3 development, all those decisions will go in the wiki too. I have some other thoughts about Mailman 3 that I'd like to get feedback on, but as this message is getting fairly long anyway, I'll defer that for the time being. So in summary, please check out the wiki. Let me know what you think about importing the SF issues into Jira. And check out the Subversion repository. -Barry

1 0

RELEASED: Mailman 2.1.8
by Tokio Kikuchi April 15, 2006

April 15, 2006

On behalf of the development team, I'm pleased to announce the release of GNU Mailman 2.1.8. In this release, we have fixed a cross-site scripting security bug in the previous release (CVE-2006-1712), integrated a new version of email library (email-2.5.7), and added bounce processing supports for number of sites and MUAs. It is highly recommended that all sites using 2.1.7 and before should update to this release. Mailman is free software for managing email mailing lists and e-newsletters. For more information, see: http://mailman.sourceforge.net/ For links to download the Mailman 2.1.8 source tarball, see: http://sourceforge.net/project/showfiles.php?group_id=103 (Note that uploading to the mirror sites may be delayed.) -- Tokio Kikuchi

1 0

How to tell if HTML templates have changed?
by Clytie Siddall April 14, 2006

April 14, 2006

Hello all :) Now I've translated all the html templates, I need to be able to monitor them for changes. Where the PO format is designed to tell us which original strings are untranslated or only partially translated, HTML format is not. I'll ask the Omega-T developer about this: it's a HTML translation tool. Meanwhile: could you please tell us if you have changed the HTML templates? Otherwise, we'll have to diff the lot everytime Mailman is updated. If you have any better ideas on how to track changes in the HTML templates, please say! :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN

1 0

Released: Mailman 2.1.8 release candidate
by Tokio Kikuchi April 7, 2006

April 7, 2006

Hi all, Mailman 2.1.8rc1 was released for the final test of 2.1.8. Important: This is not only a release candidate but also include a fix for a cross-site scripting bug found in 2.1.7. All sites running previous versions are adviced to upgrade to 2.1.8(rc1). I am going to release the final by the next weekend if nothing serious happens. Please download it from Sourceforge file area: http://sourceforge.net/project/showfiles.php?group_id=103 Cheers, Tokio --------------------------------------------------- Here is a history of user visible changes to Mailman. 2.1.8rc1 (07-Apr-2006) Security - A cross-site scripting hole in the private archive script of 2.1.7 has been closed. Thanks to Moritz Naumann for its discovery. Bug fixes and other patches - Bouncers support added: 'unknown user', Microsoft SMTPSVC, Prodigy.net and several others. - Updated email library to 2.5.7 which will encode payload into qp/base64 upon setting. This enabled backing out the scrubber related patches including 'X-Mailman-Scrubbed' header in 2.1.7. - Fix SpamDetect.py potential hold/reject loop problem. - A warning message from email package to the stderr can cause error in Logging because stderr may be detached from the process during the qrunner run. We chose not to output errors to stderr but to the logs/error if the process is running under mailmanctl subprocess. - DKIM header cleansing was separated from Cleanse.py and added to -owner messages too. - Fixes: Lose Topics when go directly to topics URL (1194419). UnicodeError running bin/arch (1395683). edithtml.py missing import (1400128). Bad escape in cleanarch. Wrong timezone in list archive index pages (1433673). bin/arch fails with TypeError (1430236). Subscription fails with some Language combinations (1435722). Postfix delayed notification not recognized (863989). 2.1.7 (VERP) mistakes delay notice for bounce (1421285). show_qfiles: 'str' object has no attribute 'as_string' (1444447). Utils.get_domain() wrong if VIRTUAL_HOST_OVERVIEW off (1275856). Miscellaneous - Brad Knowles' mailman daily status report script updated to 0.0.16. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/

1 0

Mailman Arabic translation is ready
by Munzir Taha April 4, 2006

April 4, 2006

Hi, It's my pleasure to contribute an Arabic translation of mailman. I will polish it more and complete the missing strings in the near future. Please commit it and let me know the procedure of updating/merging the template files when changes occur. Hope there is a way other than doing a manual compare. The add_language line should read: add_language('ar', _('Arabic'), 'utf-8') Keep up the good work. The attachment is sent privately to Barry. -- Munzir Taha Telecommunications and Electronics Engineer Maintainer of Fedora Arabic Translation Project https://listman.redhat.com/mailman/listinfo/fedora-trans-ar Maintainer of the OpenBugs project page at http://www.arabic-fedora.org/munzir/OpenBugs.html Master CIW Designer, ICDL, MOUS, Linux+, LPI 101 Riyadh, SA

4 7

ways to prioritize what to translate?
by Bruno Haible April 3, 2006

April 3, 2006

Hello, On the translation-i18n mailing list some translators said that they were not willing to translate the entire mailman POT file because it was so big, and many messages appeared to be in a context never seen by a mailing list subscriber. Would it be possible for the mailman project to prioritize the messages according to the target user role? I was told that mailman has three types of users: admins, editors, subscribers. They see different output from mailman. I would estimate that the localization of the parts that reaches subscribers is higher priority than the rest. (Because when you have 5 people or more starting a mailing list, you can expect to find one of them who understands English; this person then can become the list administrator.) For the translators, it is acceptable to have 3 POT files instead of a single POT file; it is also acceptable to keep everything in a single POT file which has extracted tags (#. syntax) that indicate the target user (e.g. "#. to subscribers") or prioritization (e.g. "#. +", "#. ++", "#. +++"). If distinct user roles are handled by distinct source files, you can simply pass different file lists in 3 different xgettext invocations. If not, you can use different translation functions instead of _(); xgettext 0.15 will have an option to create specific extracted tags in #. syntax depending on the translation function that is used. Bruno

1 0