Mailman 3 December 2012 - Mailman-Developers

Mailman will be sprinting at PyCon US 2013 -- Join us!
by Terri Oda 16 Dec '12

16 Dec '12

For anyone who was wondering, yes, Mailman is planning to be sprinting at PyCon US 2013. I know Barry, Florian, Mark and I say we're going, and I'm sure more people will speak up as they figure out their schedules. PyCon US 2013 is March 13-21 in Santa Clara https://us.pycon.org/2013/ I know it's a ways off, but I'm mentioning it down because the applications for financial aid close on Dec 31st and I want any of you who could use some to get your applications in ASAP. You can register for Pycon and apply for financial aid here: https://us.pycon.org/2013/registration/ Note that if you just want to come to the sprint, that's free and you can just show up. (This is what I did last year, but I hear pycon is awesome and you should all want to register for the conference!) Hope to see some of you in March! Terri

1 0

Reminder: Mailman/Postorius/Hyperkitty hackathon
by Florian Fuchs 15 Dec '12

15 Dec '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, this is just a quick reminder that we're having another virtual hackathon tomorrow! Personally, I'll probably start hanging around on #mailman on freenode around 13:00-ish (UTC). Hope to see you tomorrow! Florian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQy2oxAAoJEAszfsgOAINuJ2IH/RaY9wrVzVUPDqNkCLi36NoE PPmmOadmmu1jrz37bok6t1HKy50mr3OBx1ZhYiwYGIHvXejjfLBFty7buEPE/lMu XNe9+/maT9LU9zBV2iKKBuJQdzDls8C1cOSR71uxaqo/vJNORYZLAH6C7gH6usby DzIZ87zjfQWtJje1yg+1djf/CsSD4rLT65941S5ehIiQoWqitQOS5BAQLDQlAdo8 KR8hvX92QtSyva0Fffa/3etK2JudYic0f8volPbbAdND4/g0ZDzpeWlGESO5vFu1 u01i2h/jaKHmoELsvKSkKv4ckyZPEMNeZc04cagpbvhRY+1TQBRXJ0EPYLr0Wps= =YYG1 -----END PGP SIGNATURE-----

3 2

Re: [Mailman-Developers] Wiki woes
by Paul Boddie 14 Dec '12

14 Dec '12

I wrote: > On Thursday 13 December 2012 18:59:40 Mark Sapiro wrote: > > I haven't looked at much, but the biggest problem I see is for example > > <http://mmwiki.boddie.org.uk/DOC/Frequently%20Asked%20Questions?action=re > >ca ll&rev=5> versus > > <http://wiki.list.org/display/DOC/Frequently+Asked+Questions>. The issue > > is the FAQ in particular relies on the listing of child > > pages to make a hierarchical TOC, and the converted pages have lost > > the child pages listing. > > Yes, the child pages are recorded, but they need to appear below their > parents in the page hierarchy. Actually, looking at this again, it isn't really possible to nicely represent child pages as subpages in Moin in general, and I did actually write a note in my converter that child/parent/ancestor relationships should not affect the way pages are organised, but this information will need to be captured somehow. One alternative is to just read the child page references and then generate a list at the end of each page's content. This might not be wonderful for capturing the relationships, but there are ways of at least searching Moin for pages that link to others, so there will be possibilities to retain the navigational information to an extent. I could imagine using page metadata to record such information and to provide extensions that can understand it, possibly even extending the search mechanism, but this would obviously involve some extra effort. Paul

1 0

Mailman3 and LDAP
by Christian Dröge 12 Dec '12

12 Dec '12

Hi, I have a question regarding mailman3 and ldap. Is there some kind of ldap support in mailman3? I heard that it should support it somehow but I did not find any references to ldap in the code, so I guess this feature is currently not available. I know, that mailman3 is currently in development, but I am interested, if this will be a supported configuration in the future. Thank you. Christian

2 1

Wiki woes
by Terri Oda 12 Dec '12

12 Dec '12

I think in the latest wiki update I seem to have lost the ability to turn off rich text editing, and as a result it's nigh impossible for me to cut and paste some types of content from one page to another. Also, some pages are now missing content (specifically, anything marked as a code snippet) if they're viewed without JavaScript. I know we've been under some pressure from the FSF to switch to a more free wiki, and they'd offered to find us some help in doing the migration. Does anyone know the status of that? Because if we're using the wiki as our primary place for docs, not being able to see pages properly without JavaScript is potentially a really big problem for us. And personally, not being able to cut and paste from one page to another makes it awfully hard for me to wiki garden so that things are easy to find and in the right place. Terri

4 6

Re: [Mailman-Developers] Using bracketed prefixes in subject as filters
by Terri Oda 11 Dec '12

11 Dec '12

On 11/23/2012 01:55 PM, Gordon P. Hemsley wrote: > I filed a request for enhancement about using bracketed prefixes in > subjects as filters: > > https://bugs.launchpad.net/mailman/+bug/1082495 > > Barry mentioned that I should raise the issue with regard to the dlist > discussion, I presume because my proposal overlaps and/or conflicts > with it. > > However, the only things I know about what a "dlist" even is has been > garnered from skimming the four messages on the topic in the archive, > and it's not clear to me they my idea is necessarily compatible with > dlists. (They seem to be exclusive proposals that may handle the same > usecase.) I already responded in the launchpad bug, but actually, I think they're pretty similar, only dlists only uses the listname+topic email format to designate sublists/topics, and the current scope of what we're doing doesn't look at archives, just about delivery of mail to users who may have chosen only some topics they want from a given list. I think it'd be easier to add the prefix and archive capabilities once we have dlists working with Mailman 3. We already have the dlist code for Mailman 2.1 (and I believe that's all available on launchpad somewhere; ping me if you can't find a link and want one), and we *did* have a Google Summer of Code project aimed at porting this code to Mailman 3. Unfortunately the student was unable to complete the project (for personal rather than technical reasons which it would be impolite to share), so two of us from Systers are working on the port. The architecture looks compatible and we've got our best guess on the necessary data structures/database tables now. We're hoping to have it done in January and are actively working on it, so maybe it'd be best to wait 'till that port is done and then look at what will be needed to extend it? Terri

1 0

Re: [Mailman-Developers] New to mailman
by Barry Warsaw 10 Dec '12

10 Dec '12

On Dec 09, 2012, at 10:32 PM, Sandesh Agrawal wrote: >I am particularly interested in this bug/wishlist : >#1082495 Support bracketed prefixes in subject as >filters<https://bugs.launchpad.net/mailman/+bug/1082495> >https://bugs.launchpad.net/mailman/+bug/1082495?comments=all > >But not sure where to start from or which part of code to see... > >Also can you suggest me some easier bugs to start with. It will almost definitely be better to start with some easy bugs, which you can find as Mark indicated. While MM3 is still lacking better "big picture" documentation, I would recommend reading some of the docs at http://packages.python.org/mailman/ Something like bug 1082495 will probably touch several parts of the system, so you'll want to familiarize yourself with the concept of queue runners, rule processing, pipeline handling, etc. You might also be interested in this talk I gave at Pycon 2012. http://pyvideo.org/video/688/mailman-3 and at this chapter in AOSA v2: http://www.aosabook.org/en/mailman.html Hope that's a good start! -Barry

3 2

Re: [Mailman-Developers] New to mailman
by Sandesh Agrawal 10 Dec '12

10 Dec '12

Thanks barry, i got my answer. I will go through the resources you mentioned.

1 0

New to mailman
by Stephen J. Turnbull 10 Dec '12

10 Dec '12

Sandesh Agrawal writes: > But i have no idea about how to proceed , can somebody help me please. Well, first you need to tell us where you're stuck! The basic procedure is 1. Get a Launchpad account (sooner or later). 2. Check out the most recent commit to the sources you're interested in (Mailman 2 or Mailman 3, or both). 3. Find a bug. 4. Fix the bug. 5. Create a branch in your own workspace, and commit the bugfix to it. 6. Push the branch to your launchpad account. 7. Link your branch to the relevant issue. 8. (optional) Make a merge request on Launchpad. 9. (more optional) Announce the fix here. Quite likely you already know some or all of the above, but at least that will provide a framework to help us navigate to your stuckness. Thanks for your interest, and good hunting! Steve

4 5

Re: [Mailman-Developers] New to mailman
by Mark Sapiro 09 Dec '12

09 Dec '12

Sandesh Agrawal wrote: > >Also can you suggest me some easier bugs to start with. Look at bugs tagged 'easy' <https://bugs.launchpad.net/mailman/+bugs?field.tag=easy>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0