Re: [Mailman-Developers] Internationalization
I was away at the Python conference all last week, so it's nice to see there are only about 113 Mailman messages to catch up on :-). I will say that I thought Ken's talk went well, and we certainly had a lot of interest from Pythoneers about Mailman. We had a lot of interesting off-line discussions about where Mailman is and where it could go.
The following are my thoughts on what we need to do in the short term. I would like to have a stable 1.0 release by the time of the Usenix LISA 98 conference, where we have another paper and where John will (hopefully) be giving a talk. This isn't very far away so I feel we need to be *really* conservative in what we try to do before then.
I agree with John that internationalizing Mailman should be a top priority, but I don't really think we can make much headway in the next 3 weeks or so. In my experience CVS branches suck so I try to avoid them, but if other core developers have more confidence in them, I'll go along for the ride.
I think we should shoot for NO new features, but just banging the hell out of the current source tree, expecting to have all the current bugs shaken out in time for LISA. Once 1.0 is released, then we can talk about an architecture for supporting all the contributed translations. It's great to see there's a lot of enthusiasm for supporting languages other than English.
-Barry
On Mon, 16 Nov 1998, Barry A. Warsaw wrote:
The following are my thoughts on what we need to do in the short term. I would like to have a stable 1.0 release by the time of the Usenix LISA 98 conference, where we have another paper and where John will (hopefully) be giving a talk. This isn't very far away so I feel we need to be *really* conservative in what we try to do before then.
Is this means MailMan got codeFreezeEvent()? ;) Iam sorry but now Iam hurry in writing the C++ code for my diploma work...
I think we should shoot for NO new features, but just banging the hell out of the current source tree, expecting to have all the current bugs shaken out in time for LISA. Once 1.0 is released, then we can talk about an architecture for supporting all the contributed translations. It's great to see there's a lot of enthusiasm for supporting languages other than English.
Well, I have a *lot* of stupid users who cannot get their password just because they don't understand MailMan's *Hungarian* error messages.
By the way I like to see the code to be combed out, because I would like to hear some aims (for example global user data, archive functions via email, administration commands such as admin subscribe etc) what you want to do or not to do. After 1st December ;-)
Linux Supporting Center -- Red Hat Qmail packages -- http://lsc.kva.hu PGP 0x1DE3631D / A8 B4 92 EE 1F 55 27 C8 86 64 9C 42 41 A4 BD B8
"BN" == Balazs Nagy <julian7@kva.hu> writes:
BN> Is this means MailMan got codeFreezeEvent()?I hope so, but I'm not sure if the other core maintainers agree with me :-)
BN> ;) Iam sorry but
BN> now Iam hurry in writing the C++ code for my diploma work...Good luck!
BN> Well, I have a *lot* of stupid users who cannot get their
BN> password just because they don't understand MailMan's
BN> *Hungarian* error messages.I understand (I think :-). Internationalization should be a priority for us after the 1.0 release.
BN> By the way I like to see the code to be combed out, because I
BN> would like to hear some aims (for example global user data,
BN> archive functions via email, administration commands such as
BN> admin subscribe etc) what you want to do or not to do. After
BN> 1st December ;-)Well, I know that Ken and I have a lot of thoughts on where to go after 1.0. I think we might be having a core confab this weekend, and I'm hoping we'll get a chance to sit in front of a whiteboard and thrash about our ideas, and hopefully agree on a direction. Stay tuned.
-Barry
participants (2)
-
Balazs Nagy -
Barry A. Warsaw