Mailman 3 May 2015 - Mailman-Developers

Moving to git and gitlab
by Barry Warsaw 12 May '15

12 May '15

With the release of Mailman 3.0, it's time to take a look at our project management, with an eye toward making it easier for core developers, easier for non-core contributors, and providing improved quality, all while staying true to the GNU project's principles. There's a lot to like about Bazaar, and it's served us well over the years, but it's also pretty clear that this round of version control systems has been won by git. We have converted the Core's vcs to git, and will soon convert Postorius and mailman.client. HyperKitty is already managed under git. There's a lot to like about Launchpad. It's free software, and it has some nice features, including one of my favorites: bug tasks, which allow us to report a bug affecting more than one project or series, and track each task as it's resolved. Launchpad has even announced git support: http://blog.launchpad.net/general/git-code-hosting-beta There are also reasons why we might want to move off of Launchpad. Most compelling is that Launchpad is difficult or impossible to use for code hosting by our Indian colleagues. We have therefore decided to move to Gitlab. The Core is now hosted here: https://gitlab.com/mailman/mailman Postorius and mailman.client will follow after Florian has had some time to work through the existing Launchpad merge proposals. HyperKitty may move at some point soon. We currently have no plans to move any hosting of Mailman 2.1. For now, its code will continue to live in Bazaar on Launchpad, its bugs will continue to be managed on Launchpad, as will merge proposals. Q: What about the existing lp:mailman Bazaar branch? A: Let's leave it there for now, effectively keeping it around read-only. Q: What about existing LP bugs for Mailman 3? A: Abhilash is working on transferring them to Gitlab. It won't be a perfect conversions since we can't match users on the two systems, but if/when we do transfer them, we'll keep a link to the LP bug report in the Gitlab issue. We will only be moving the bugs tagged 'mailman3' on LP. If you own a Mailman 3 bug on Launchpad, feel free to close it there and open a new one on Gitlab. In the meantime, or if the transfer doesn't work well enough, we'll just close bugs on LP as we fix them. Please report all new bugs on Gitlab. Q: What about existing LP merge proposals? A: These are much tougher to transfer. If you have an open merge proposal on LP, feel free to update it to the latest git head and submit a new merge request on Gitlab. If you do, please close your mp on LP. In the meantime, I'll work my way through the existing LP merge proposals, applying diffs by hand if necessary. Q: What about CI? A: This is definitely one of the exciting features of Gitlab we're eager to start using. Our plans are to requisition a VM from python.org and set up CI on it. I'd like for us to never commit directly to the official project branches. Q: Why Gitlab and not Github or Bitbucket? A: Gitlab has an edition that is free software. If for some reason we have to leave gitlab.com, we could potentially stand up our own Gitlab and have an easier time transferring our projects to it. Plus we have to be a *little* different don't we? :) Cheers, -Barry

2 1

python error when try to save a setting
by Thomas Stein 08 May '15

08 May '15

Hello. When i try to save a setting --schnipp-- Settings / Message Acceptance Default action to take when a member posts to the list ---> Accept --schnapp-- via pistorius i get: UnboundLocalError at /mailman3/lists/hoppla.domain/settings/message_acceptance local variable 'HTTPError' referenced before assignment Request Method: POST Request URL: http://127.0.0.1:8000/mailman3/lists/hoppla.domain/settings/message_accepta… Django Version: 1.7.8 Exception Type: UnboundLocalError Exception Value: local variable 'HTTPError' referenced before assignment Exception Location: /var/www/mailman/eggs/postorius-1.0.1-py2.7.egg/postorius/views/list.py in list_settings, line 787 Python Executable: /var/www/mailman/venv/bin/python2.7 Python Version: 2.7.9 Python Path: ['/var/www/mailman/eggs/Django-1.7.8-py2.7.egg', '/var/www/mailman/eggs/postorius-1.0.1-py2.7.egg', '/var/www/mailman/eggs/HyperKitty-1.0.0-py2.7.egg', '/var/www/mailman/eggs/Whoosh-2.7.0-py2.7.egg', '/var/www/mailman/eggs/mock-1.0.1-py2.7.egg', '/var/www/mailman/eggs/beautifulsoup4-4.3.2-py2.7.egg', '/var/www/mailman/eggs/djangorecipe-1.11-py2.7.egg', '/var/www/mailman/eggs/zc.recipe.egg-2.0.1-py2.7.egg', '/var/www/mailman/venv/lib/python2.7/site-packages', '/var/www/mailman/eggs/numpy-1.9.2-py2.7-linux-x86_64.egg', '/var/www/mailman/eggs/lockfile-0.10.2-py2.7.egg', '/var/www/mailman/eggs/django_extensions-1.5.2-py2.7.egg', '/var/www/mailman/eggs/django_haystack-2.3.1-py2.7.egg', '/var/www/mailman/eggs/enum34-1.0.4-py2.7.egg', '/var/www/mailman/eggs/networkx-1.9.1-py2.7.egg', '/var/www/mailman/eggs/python_dateutil-1.5-py2.7.egg', '/var/www/mailman/eggs/mailmanclient-1.0.0-py2.7.egg', '/var/www/mailman/eggs/django_browserid-1.0.0-py2.7.egg', '/var/www/mailman/eggs/django_compressor-1.5-py2.7.egg', '/var/www/mailman/eggs/django_paintstore-0.2-py2.7.egg', '/var/www/mailman/eggs/pytz-2015.2-py2.7.egg', '/var/www/mailman/eggs/robot_detection-0.3-py2.7.egg', '/var/www/mailman/eggs/cssmin-0.2.0-py2.7.egg', '/var/www/mailman/eggs/rjsmin-1.0.10-py2.7-linux-x86_64.egg', '/var/www/mailman/eggs/django_crispy_forms-1.4.0-py2.7.egg', '/var/www/mailman/eggs/djangorestframework-3.1.1-py2.7.egg', '/var/www/mailman/eggs/python_social_auth-0.2.7-py2.7.egg', '/var/www/mailman/eggs/django_gravatar2-1.3.0-py2.7.egg', '/var/www/mailman/eggs/six-1.9.0-py2.7.egg', '/var/www/mailman/eggs/decorator-3.4.2-py2.7.egg', '/var/www/mailman/eggs/httplib2-0.9.1-py2.7.egg', '/var/www/mailman/eggs/requests-2.6.2-py2.7.egg', '/var/www/mailman/eggs/django_appconf-1.0.1-py2.7.egg', '/var/www/mailman/eggs/PyJWT-1.1.0-py2.7.egg', '/var/www/mailman/eggs/requests_oauthlib-0.4.2-py2.7.egg', '/var/www/mailman/eggs/oauthlib-0.7.2-py2.7.egg', '/var/www/mailman/eggs/python_openid-2.2.5-py2.7.egg', '/var/www/mailman', '/var/www/mailman/bin', '/var/www/mailman/venv/lib64/python27.zip', '/var/www/mailman/venv/lib64/python2.7', '/var/www/mailman/venv/lib64/python2.7/plat-linux2', '/var/www/mailman/venv/lib64/python2.7/lib-tk', '/var/www/mailman/venv/lib64/python2.7/lib-old', '/var/www/mailman/venv/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7', '/usr/lib/python2.7/plat-linux2'] How can i repair this? Thanks and cheers t.

2 2

error when trying to register via hyperkitty
by Thomas Stein 06 May '15

06 May '15

Hello. When i try to signup via hyperkitty i get: KeyError at /archives/accounts/register/ 'email' Request Method: POST Request URL: http://127.0.0.1:8000/archives/accounts/register/?next=/archives/ Django Version: 1.7.8 Exception Type: KeyError Exception Value: 'email' Exception Location: /var/www/mailman/eggs/HyperKitty-1.0.0-py2.7.egg/hyperkitty/views/forms.py in clean_username, line 57 Python Executable: /var/www/mailman/venv/bin/python2.7 Python Version: 2.7.9 Python Path: ['/var/www/mailman/eggs/Django-1.7.8-py2.7.egg', '/var/www/mailman/eggs/postorius-1.0.1-py2.7.egg', '/var/www/mailman/eggs/HyperKitty-1.0.0-py2.7.egg', '/var/www/mailman/eggs/Whoosh-2.7.0-py2.7.egg', '/var/www/mailman/eggs/mock-1.0.1-py2.7.egg', '/var/www/mailman/eggs/beautifulsoup4-4.3.2-py2.7.egg', '/var/www/mailman/eggs/djangorecipe-1.11-py2.7.egg', '/var/www/mailman/eggs/zc.recipe.egg-2.0.1-py2.7.egg', '/var/www/mailman/venv/lib/python2.7/site-packages', '/var/www/mailman/eggs/numpy-1.9.2-py2.7-linux-x86_64.egg', '/var/www/mailman/eggs/lockfile-0.10.2-py2.7.egg', '/var/www/mailman/eggs/django_extensions-1.5.2-py2.7.egg', '/var/www/mailman/eggs/django_haystack-2.3.1-py2.7.egg', '/var/www/mailman/eggs/enum34-1.0.4-py2.7.egg', '/var/www/mailman/eggs/networkx-1.9.1-py2.7.egg', '/var/www/mailman/eggs/python_dateutil-1.5-py2.7.egg', '/var/www/mailman/eggs/mailmanclient-1.0.0-py2.7.egg', '/var/www/mailman/eggs/django_browserid-1.0.0-py2.7.egg', '/var/www/mailman/eggs/django_compressor-1.5-py2.7.egg', '/var/www/mailman/eggs/django_paintstore-0.2-py2.7.egg', '/var/www/mailman/eggs/pytz-2015.2-py2.7.egg', '/var/www/mailman/eggs/robot_detection-0.3-py2.7.egg', '/var/www/mailman/eggs/cssmin-0.2.0-py2.7.egg', '/var/www/mailman/eggs/rjsmin-1.0.10-py2.7-linux-x86_64.egg', '/var/www/mailman/eggs/django_crispy_forms-1.4.0-py2.7.egg', '/var/www/mailman/eggs/djangorestframework-3.1.1-py2.7.egg', '/var/www/mailman/eggs/python_social_auth-0.2.7-py2.7.egg', '/var/www/mailman/eggs/django_gravatar2-1.3.0-py2.7.egg', '/var/www/mailman/eggs/six-1.9.0-py2.7.egg', '/var/www/mailman/eggs/decorator-3.4.2-py2.7.egg', '/var/www/mailman/eggs/httplib2-0.9.1-py2.7.egg', '/var/www/mailman/eggs/requests-2.6.2-py2.7.egg', '/var/www/mailman/eggs/django_appconf-1.0.1-py2.7.egg', '/var/www/mailman/eggs/PyJWT-1.1.0-py2.7.egg', '/var/www/mailman/eggs/requests_oauthlib-0.4.2-py2.7.egg', '/var/www/mailman/eggs/oauthlib-0.7.2-py2.7.egg', '/var/www/mailman/eggs/python_openid-2.2.5-py2.7.egg', '/var/www/mailman', '/var/www/mailman/bin', '/var/www/mailman/venv/lib64/python27.zip', '/var/www/mailman/venv/lib64/python2.7', '/var/www/mailman/venv/lib64/python2.7/plat-linux2', '/var/www/mailman/venv/lib64/python2.7/lib-tk', '/var/www/mailman/venv/lib64/python2.7/lib-old', '/var/www/mailman/venv/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7', '/usr/lib/python2.7/plat-linux2'] I used no special characters for username and email. Any ideas? ciao t.

2 1

Please consider donating to the GNU Mailman project
by Barry Warsaw 05 May '15

05 May '15

I should have included this in our release announcement. I'd like to remind everyone that GNU Mailman has a directed donation fund set up at the Free Software Foundation. Please consider donating! http://wiki.list.org/x/4816967 This year, we used a portion of our fund to sponsor Abhilash coming to PyCon 2015. Abhilash has been a core developer since his participation in GSoC, and has proven himself to be indispensable across a wide range of the project. We were beyond happy to be able to meet him in person and work with him over the course of the sprints, and we reached the 3.0 release in large part because of his participation at the sprints. Your donations can help with future sprints, user testing, hosting, and more. We're a small team of volunteers and every dollar can help. A portion of your donation also goes to the Free Software Foundation, so you can help two great organizations with one donation. Cheers, -Barry

1 0

Re: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation
by Brian Carpenter 04 May '15

04 May '15

> -----Original Message----- > From: Mailman-Developers [mailto:mailman-developers- > bounces+brian=emwd.com(a)python.org] On Behalf Of Danil Smirnov > Sent: Wednesday, April 29, 2015 4:24 PM > To: Mailman Developers > Subject: Re: [Mailman-Developers] mailman 3.0 roadmap, feature-parity > with mailman 2.x and documentation > > 2015-04-29 18:03 GMT+03:00 Brian Carpenter <brian(a)emwd.com>: > > Just to be clear, this is a stable fully working version of Mailman 3.0? I > > tried setting up Mailman 3 on a CentOS server about 2 weeks ago and had a > > number of issues including listinfo pages not working (404 errors), no clear > > directions on setting up users, various bugs such as internal server errors. > > The server admin that I had hired informed me there was a number of > python > > related bugs and he felt Mailman 3 was not ready for production use. > > > > I am ready to give this another try but I want to make sure that this > > version will be a full working version of Mailman 3. > > I had similar experience a week ago (after PyCon sprint) and there > were couple bugs in the installation process on Centos 7 including > hard one with bad virtualenv version which is still not reflected in > the installation manual: > https://bugs.launchpad.net/mailman/+bug/1445764/comments/19 > > I suppose anyone who try to install Mailman on Centos 7 will face this bug. > > Danil The OS was CentOS 6.5 in my case. Is there a recommended server environment to run Mailman 3? Brian

4 5