Mailman 3 April 2015 - Mailman-Developers

Approach for making Editable fields in user profile
by Ankush Sharma April 13, 2015

April 13, 2015

Hello everyone, I need to discuss in context with the feature request https://bugs.launchpad.net/postorius/+bug/1432383. The point is to make the fields like irc handle, first-name, last-name etc. editable in the user profile. User registration is currently done using *django-browserid *with the default *User Model. *There are no schema rules for these *extra *fields in the *auth_user *table of the underlying Postorius database due to the use of the default *User Model*. I am thinking of using a CustomBackend class overriding the BrowserIdBackend class for adding customisation *[1]*. Also, I think it would be required to have a *new *User model for these extra fields which can be used by django-browserid for the initial user registration. Initially, these *extra *fields can be set to *empty*. Later on, with the help of an update view users can be asked to update their profiles when they login. This would require the use of database migrations. Other option is to use to create an extra table for these fields and for it the default *User model *would be suffice. In this case, an extra form would do the job. I want to ask whether my approach is correct ? Or it would be more meaningful to take input for these fields during the first time when the user registers by using Persona ? ( I guess it would require some ugly tweaks ) Waiting for your opinion on it ! Thanks, Ankush Sharma IIT-BHU, Varanasi India *github.com/black-perl <http://github.com/black-perl>* [1] : http://django-browserid.readthedocs.org/en/latest/user/customization.html#a…

1 0

Currently on HN front page
by Andrew Stuart April 7, 2015

April 7, 2015

https://news.ycombinator.com/item?id=9336291

1 0

prepping TODO list for PyCon sprints next week
by Sumana Harihareswara April 7, 2015

April 7, 2015

The PyCon sprints are Monday, April 13th 2015 -- Thursday, April 16th 2015 in Montréal and are free to attend. http://wiki.list.org/DEV/PyCon%202015%20Sprint Please add yourself to that page if you're coming (if you're not going to be there all 4 days, it would be cool if you could say that so people know when they can find you). The main thing people seem to want to do: release the 3.0 version of the suite. The blockers to release: http://wiki.list.org/DEV/Mailman%203.0 Please do go ahead and update that page and/or the relevant bugs if they're already fixed. best, Sumana -- Sumana Harihareswara http://brainwane.net

1 0

How to validate mailing list-id?
by Andrew Stuart April 3, 2015

April 3, 2015

I’ve read RFC2919 https://www.ietf.org/rfc/rfc2919.txt which says: "The list header fields are subject to the encoding and character restrictions for mail headers as described in [RFC822]." RFC822 http://www.w3.org/Protocols/rfc822/ says: "The field-body may be composed of any ASCII characters, except CR or LF. (While CR and/or LF may be present in the actual text, they are removed by the action of unfolding the field.)" Am I correct in understanding then that a mailing list-id may be composed of any ASCII characters? Thus this is a valid mailing list-id: ///*/etc/pw.txt Is this function an accurate validator for a mailing list-id? def is_valid_list_id(list_id): try: list_id.decode('ASCII') except UnicodeDecodeError: return False else: return True

2 1

LWN article about the upcoming Mailman suite's 3.0 release
by Sumana Harihareswara April 1, 2015

April 1, 2015

I wrote this article for LWN about what's new in the upcoming release and implications for the larger open source ecosystem: http://lwn.net/SubscriberLink/638090/0229275ea355532b/ I took screenshots of HyperKitty and Postorius, in case you want to see! The comments have some interesting thoughts as well. Thanks to the Mailman development team for answering my questions via IRC and email as I was writing this! -- Sumana Harihareswara http://brainwane.net

1 0