Mailman 3 October 2016 - Mailman-Developers

Setting up installation to test own changes
by Ana Cutillas Oct. 24, 2016

Oct. 24, 2016

Hello, we at Systers had a student over summer work on some features and we would like to put those in a server and do some testing. I was thinking of using the mailman bundler and then changing the source files (she only did changes to postorius). Would that work? Or should we do it differently? Thanks! Ana

1 0

REST returns 405 to PATCH in development environment.
by Mark Sapiro Oct. 19, 2016

Oct. 19, 2016

I'm sure there's something wrong with what I'm doing, but I have the following issue. I am developing/testing a change to Postorius to support alias_domain as implemented by <https://gitlab.com/mailman/mailman/merge_requests/202> and <https://gitlab.com/mailman/mailmanclient/merge_requests/18>. I made some changes to postorius/forms.py postorius/templates/postorius/domain/index.html postorius/views/domain.py to support displaying and setting alias domain. I have a development environment with Python 2 and Python 3 virtualenvs with all the pieces installed via 'python setup.py develop' in the appropriate venv. I am running Mailman core via '.tox/py35/bin/mailman start' with (I think) an appropriate mailman.cfg and running Postorius in the Python 2 venv via 'example_project/manage.py runserver' and connecting to Postorius via http://localhost:8000. It all seems to work except editing. I can create a domain with or without an alias_domain, see it all listed and delete the domain, but any attempts at editing the domain fail with the core REST server returning 405 to the PATCH request. Even if I stash my changes and revert to the branch head, edits fail in the same way. Does anyone know what I'm missing/doing wrong? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 3

GNU Mailman Architectural Patterns & Quality Attributes for Research
by Michael Skeen Oct. 15, 2016

Oct. 15, 2016

Hello GNU Mailman Community, I am part of an undergraduate research group focusing on software architecture patterns and quality attributes at Utah Valley University. We recently analyzed the work published on GNU Mailman in the Architecture of Open Source Applications <http://aosabook.org/en/index.html> (AOSA) and referenced it in a paper we presented at the 13th Working IEEE/IFIP Conference on Software Architecture (WICSA), as attached. As a part of our continuing research we wish to validate our architectural analysis for GNU Mailman with the current developers. We would like to know if we are missing any patterns or quality attributes that may have been included in GNU Mailman, or if there are any we listed that aren’t used. Any additional comment on these topics you might have would also, of course, be welcome. We believe we found the following software architectural patterns in this application: * Pattern Name | Is This Found in the Architecture? (yes / no / don't know) | Comments (optional)* Client Server Layers Master and Commander Pipes and Filters Shared Repository Simple Repository Other? We also identified the following quality attributes: * Attribute Name | Is This Found in the Architecture? | Comments (optional)* Scalability Extensibility Performance Portability Reliability Other? For your convenience, we have a complete list below of the patterns and quality attributes we referred to when conducting our research. To clarify, we are specifically studying architectural patterns, rather than design patterns such as the GoF patterns. Architectural Patterns Considered Quality Attributes Considered Active Repository Scalability Batch Usability Blackboard Extensibility Broker Performance Client Server Portability Event System Flexibility Explicit Invocation Reliability Implicit Invocation Maintainability Indirection Layer Security Interceptor Testability Interpreter Capacity Layers Cost Master and Commander Legality Microkernel Modularity Model View Controller Robustness Peer to Peer Pipes and Filters Plugin Presentation Abstraction Control Publish Subscribe Reflection Rule-Based System Shared Repository Simple Repository State Based Virtual Machine Please respond by October 25th, if possible. Thank you for considering our request, and for your continued work on GNU Mailman. Sincerely, Michael Skeen, with Erich Gubler, Danielle Skinner, Brandon Leishman, Neil Harrison, Ph.D. (advisor) Reference: Neil B. Harrison, Erich Gubler, Danielle Skinner, "Software Architecture Pattern Morphology in Open-Source Systems",WICSA, 2016, 2016 13th Working IEEE/IFIP Conference on Software Architecture (WICSA), 2016 13th Working IEEE/IFIP Conference on Software Architecture (WICSA) 2016, pp. 91-98, doi:10.1109/WICSA.2016.8

1 0

Re: [Mailman-Developers] can't login with Google/Yahoo (last mailman-bundler)
by Mark Sapiro Oct. 10, 2016

Oct. 10, 2016

On 10/10/2016 09:13 PM, Leon wrote: > Latest mailman-bundle, Hyperkitty==1.0.3, python-social-auth==0.2.21. > > Added 'backends.yourmembership.YourMembershipAuth' in > AUTHENTICATION_BACKENDS > > Got exception like this: > TypeError at /login/yourmembership/ > auth() got an unexpected keyword argument 'SSL' This is a known issue. In mailman-web/urls.py remove ", {"SSL": True}" from the lines url(r'', include('social.apps.django_app.urls', namespace='social'), {"SSL": True}), url(r'', include('django_browserid.urls'), {"SSL": True}), However, you should be aware that python-social-auth and Persona are all going away in favor of Django Allauth. Mailman-bundler is currently behind what's in development. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: [Mailman-Developers] can't login with Google/Yahoo (last mailman-bundler)
by Leon Oct. 10, 2016

Oct. 10, 2016

Latest mailman-bundle, Hyperkitty==1.0.3, python-social-auth==0.2.21. Added 'backends.yourmembership.YourMembershipAuth' in AUTHENTICATION_BACKENDS Got exception like this: TypeError at /login/yourmembership/ auth() got an unexpected keyword argument 'SSL' Request Method: GET Request URL: http://list.conferency.com/login/yourmembership/?next=/ archives/ Django Version: 1.8.15 Exception Type: TypeError Exception Value: auth() got an unexpected keyword argument 'SSL' Exception Location: /opt/mailman/mailman-bundler/ eggs/python_social_auth-0.2.21-py2.7.egg/social/apps/django_app/utils.py in wrapper, line 51 Python Executable: /opt/mailman/venv/bin/python Python Version: 2.7.6 Seems like this exception is caused by Hyperkitty. -- Best wishes, Libin Feng

1 0

wiki sidebar: time to add Mailman 3?
by Jim Tittsler Oct. 6, 2016

Oct. 6, 2016

While I still use Mailman 2 everywhere, there do seem to be a growing number of Mailman 3 users. Is it time to update the wiki sidebar to reflect this, perhaps by inserting Mailman 2 and Mailman 3 headings? Even better, has someone already thought through this and imagined a good menu/link list? I could change the "theme" to make this happen. -- Jim Tittsler https://OnJapan.net/ GPG: 0x01159DB6 Python Starship http://Starship.Python.net/crew/jwt/ Mailman IRC irc://irc.freenode.net/#mailman (jimt)

1 0