From jwt at onjapan.net  Thu Oct  6 21:43:03 2016
From: jwt at onjapan.net (Jim Tittsler)
Date: Fri, 7 Oct 2016 10:43:03 +0900
Subject: [Mailman-Developers] wiki sidebar: time to add Mailman 3?
Message-ID: <74a95a9a-69af-c8e6-aea7-d6be824623e2@onjapan.net>

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)

From best.sum at gmail.com  Tue Oct 11 00:13:24 2016
From: best.sum at gmail.com (Leon)
Date: Tue, 11 Oct 2016 00:13:24 -0400
Subject: [Mailman-Developers] can't login with Google/Yahoo (last
 mailman-bundler)
Message-ID: <CAPDq0P1TYv9V1d+=taaP4Hdy_EEE544rt0kyp754ZSNcGYMt5A@mail.gmail.com>

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

From mark at msapiro.net  Tue Oct 11 00:30:46 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 10 Oct 2016 21:30:46 -0700
Subject: [Mailman-Developers] can't login with Google/Yahoo (last
 mailman-bundler)
In-Reply-To: <CAPDq0P1TYv9V1d+=taaP4Hdy_EEE544rt0kyp754ZSNcGYMt5A@mail.gmail.com>
References: <CAPDq0P1TYv9V1d+=taaP4Hdy_EEE544rt0kyp754ZSNcGYMt5A@mail.gmail.com>
Message-ID: <3c893ea8-c2cd-027d-cb91-0641157f3a67@msapiro.net>

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 at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mmskeen at gmail.com  Sat Oct 15 16:42:47 2016
From: mmskeen at gmail.com (Michael Skeen)
Date: Sat, 15 Oct 2016 14:42:47 -0600
Subject: [Mailman-Developers] GNU Mailman Architectural Patterns & Quality
 Attributes for Research
Message-ID: <CAAqp00Rga36gARQU_0qfHKSWDjk+CVn7ABXBpOssgj39pyN1dw@mail.gmail.com>

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PID4110571 (Morphology).pdf
Type: application/pdf
Size: 231943 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20161015/556c3242/attachment-0001.pdf>

From mark at msapiro.net  Mon Oct 17 22:23:17 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 17 Oct 2016 19:23:17 -0700
Subject: [Mailman-Developers] REST returns 405 to PATCH in development
 environment.
Message-ID: <f9226d3d-6706-7f29-b936-8c8771ceb159@msapiro.net>

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 at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From barry at list.org  Tue Oct 18 11:02:49 2016
From: barry at list.org (Barry Warsaw)
Date: Tue, 18 Oct 2016 11:02:49 -0400
Subject: [Mailman-Developers] REST returns 405 to PATCH in development
 environment.
In-Reply-To: <f9226d3d-6706-7f29-b936-8c8771ceb159@msapiro.net>
References: <f9226d3d-6706-7f29-b936-8c8771ceb159@msapiro.net>
Message-ID: <20161018110249.19c6c6cd@subdivisions.wooz.org>

On Oct 17, 2016, at 07:23 PM, Mark Sapiro wrote:

>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.

Hi Mark.

The way Falcon works is that you need an on_<METHOD>() method for every HTTP
METHOD that a resource implements.  If you look at the ADomain class (or the
_DomainBase base class), it only implements an on_get() and an on_delete(),
but no on_put() or on_patch().  So when you try to invoke PUT or PATCH on a
domain resource, you get a 405, i.e. Method Not Allowed.

And afaict, your MR doesn't an on_patch().

It's a bit more work to implement PUT and PATCH, so not every resource
currently supports it.  There are several examples in the code though, and
often on_put() and on_patch() differ only in the set of required attributes.
By definition, PUT requires a complete resource and PATCH allows for partial
resources.  Take a look at ListArchivers in rest/lists.py for an example.

Cheers,
-Barry

From mark at msapiro.net  Wed Oct 19 01:11:08 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 18 Oct 2016 22:11:08 -0700
Subject: [Mailman-Developers] REST returns 405 to PATCH in development
 environment.
In-Reply-To: <20161018110249.19c6c6cd@subdivisions.wooz.org>
References: <f9226d3d-6706-7f29-b936-8c8771ceb159@msapiro.net>
 <20161018110249.19c6c6cd@subdivisions.wooz.org>
Message-ID: <2ac87d21-0606-9cfb-f517-ce10efc21a27@msapiro.net>

On 10/18/2016 08:02 AM, Barry Warsaw wrote:
> 
> The way Falcon works is that you need an on_<METHOD>() method for every HTTP
> METHOD that a resource implements.  If you look at the ADomain class (or the
> _DomainBase base class), it only implements an on_get() and an on_delete(),
> but no on_put() or on_patch().  So when you try to invoke PUT or PATCH on a
> domain resource, you get a 405, i.e. Method Not Allowed.
> 
> And afaict, your MR doesn't an on_patch().


Thanks Barry,

I get it and I will fix.

I also note that in my production installs (current branch heads)
Postorius can't edit a domain for the same reason. That's what threw me
off as I assumed editing a domain worked in general and just not in my
development environment.

I'll create an issue and a MR to fix it, but probably not until tomorrow
evening or Thurs.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From barry at list.org  Wed Oct 19 09:41:15 2016
From: barry at list.org (Barry Warsaw)
Date: Wed, 19 Oct 2016 09:41:15 -0400
Subject: [Mailman-Developers] REST returns 405 to PATCH in development
 environment.
In-Reply-To: <2ac87d21-0606-9cfb-f517-ce10efc21a27@msapiro.net>
References: <f9226d3d-6706-7f29-b936-8c8771ceb159@msapiro.net>
 <20161018110249.19c6c6cd@subdivisions.wooz.org>
 <2ac87d21-0606-9cfb-f517-ce10efc21a27@msapiro.net>
Message-ID: <20161019094115.63ceeee7@subdivisions.wooz.org>

On Oct 18, 2016, at 10:11 PM, Mark Sapiro wrote:

>I get it and I will fix.
>
>I also note that in my production installs (current branch heads)
>Postorius can't edit a domain for the same reason. That's what threw me
>off as I assumed editing a domain worked in general and just not in my
>development environment.
>
>I'll create an issue and a MR to fix it, but probably not until tomorrow
>evening or Thurs.

Cool, no worries.  My huge unsub-workflow branch is nearly ready to land,
which will remove the bottleneck on core.

One thing to keep in mind though is that not all attributes of the domain
resource are writable.  `description` should be of course, and if you look in
the model, domains also have an `owners` attribute that's not currently
included in the GET.  If it were, that should be writable too, as well as your
new `alias_domain` attribute.

But `mail_host` should be read-only.

Cheers,
-Barry

From anitacorr at gmail.com  Mon Oct 24 10:00:56 2016
From: anitacorr at gmail.com (Ana Cutillas)
Date: Mon, 24 Oct 2016 16:00:56 +0200
Subject: [Mailman-Developers] Setting up installation to test own changes
Message-ID: <CABDJ2UocX6+X5sy-L39_Pz5Bc1cCysOM=6W62cD+C_8rpu4JHw@mail.gmail.com>

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

From mark at msapiro.net  Mon Oct 24 12:49:48 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 24 Oct 2016 09:49:48 -0700
Subject: [Mailman-Developers] Setting up installation to test own changes
In-Reply-To: <CABDJ2UocX6+X5sy-L39_Pz5Bc1cCysOM=6W62cD+C_8rpu4JHw@mail.gmail.com>
References: <CABDJ2UocX6+X5sy-L39_Pz5Bc1cCysOM=6W62cD+C_8rpu4JHw@mail.gmail.com>
Message-ID: <a2c1e46b-c8f7-95fd-2e6a-25e1f593cb1b@msapiro.net>

On 10/24/2016 07:00 AM, Ana Cutillas wrote:
> 
> 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?


The recommended development setup is at
<https://wiki.list.org/DEV/SetupDevEnvironment>. Mailman bundler is not
recommended because it doesn't install the current development branches.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Mon Oct 24 18:17:30 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 24 Oct 2016 15:17:30 -0700
Subject: [Mailman-Developers] Issue recording VCR tapes in Postorius.
Message-ID: <f6dba8f6-8c14-9642-3fef-70f57aecfc8c@msapiro.net>

I have started a branch to expose the pending domain.alias_domains
attribute in Postorius.

I haven't yet done anything with tests, but I did the basic
modifications and created
<https://gitlab.com/mailman/postorius/merge_requests/186>. Of course,
this merge failed CI because "create_domain() got an unexpected keyword
argument 'alias_domain'".

So I need to record a new tape and modify the test. So my problem is I
can't record any tapes. My "tox -e record" attempts fail with tracebacks
like the attached.

It appears the virtualenv in .tox/record is a Python 3.5 virtualenv and
Python 3.5 doesn't have a urllib2 module.

Why is tox creating this as a Python 3 virtualenv? All the others it
creates for Postorius are Python 2.7. I've even tried "tox -e record
--force-dep 'python <=2.7'" but that doesn't help.

Does anyone know what I need?

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
-------------- next part --------------
Traceback (most recent call last):
  File "example_project/manage.py", line 27, in <module>
    execute_from_command_line(sys.argv)
  File "/var/MM/3.0/postorius/.tox/record/lib/python3.5/site-packages/django/core/management/__init__.py", line 367, in execute_from_command_line
    utility.execute()
  File "/var/MM/3.0/postorius/.tox/record/lib/python3.5/site-packages/django/core/management/__init__.py", line 341, in execute
    django.setup()
  File "/var/MM/3.0/postorius/.tox/record/lib/python3.5/site-packages/django/__init__.py", line 27, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/var/MM/3.0/postorius/.tox/record/lib/python3.5/site-packages/django/apps/registry.py", line 108, in populate
    app_config.import_models(all_models)
  File "/var/MM/3.0/postorius/.tox/record/lib/python3.5/site-packages/django/apps/config.py", line 199, in import_models
    self.models_module = import_module(models_module_name)
  File "/var/MM/3.0/postorius/.tox/record/lib/python3.5/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 986, in _gcd_import
  File "<frozen importlib._bootstrap>", line 969, in _find_and_load
  File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 673, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 665, in exec_module
  File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed
  File "/var/MM/3.0/postorius/src/postorius/models.py", line 30, in <module>
    from django_mailman3.lib.mailman import get_mailman_client
  File "/var/MM/3.0/postorius/.tox/record/lib/python3.5/site-packages/django_mailman3/lib/mailman.py", line 25, in <module>
    from urllib2 import HTTPError
ImportError: No module named 'urllib2'


From simon.hanna at serve-me.info  Mon Oct 24 18:33:41 2016
From: simon.hanna at serve-me.info (Simon Hanna)
Date: Tue, 25 Oct 2016 00:33:41 +0200
Subject: [Mailman-Developers] Issue recording VCR tapes in Postorius.
In-Reply-To: <f6dba8f6-8c14-9642-3fef-70f57aecfc8c@msapiro.net>
References: <f6dba8f6-8c14-9642-3fef-70f57aecfc8c@msapiro.net>
Message-ID: <98A83F75-FCA8-4891-8003-540ABAD1A516@serve-me.info>


>So I need to record a new tape and modify the test. So my problem is I
>can't record any tapes. My "tox -e record" attempts fail with
>tracebacks
>like the attached.
>
>It appears the virtualenv in .tox/record is a Python 3.5 virtualenv and
>Python 3.5 doesn't have a urllib2 module.
>
>Why is tox creating this as a Python 3 virtualenv? All the others it
>creates for Postorius are Python 2.7. I've even tried "tox -e record
>--force-dep 'python <=2.7'" but that doesn't help.
>
>Does anyone know what I need?

You have to prefix the environment with py27. So you would be running `tox -e py27-record`
Since no base Python version is defined in to, it probably uses the Python version that was used to install tox itself. 

You can have a look at the tox config. You could also specify the django version to be used by adding django110 to the command (the environment selectors are always separated using hyphens)


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

From mark at msapiro.net  Mon Oct 24 19:53:22 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 24 Oct 2016 16:53:22 -0700
Subject: [Mailman-Developers] Issue recording VCR tapes in Postorius.
In-Reply-To: <98A83F75-FCA8-4891-8003-540ABAD1A516@serve-me.info>
References: <f6dba8f6-8c14-9642-3fef-70f57aecfc8c@msapiro.net>
 <98A83F75-FCA8-4891-8003-540ABAD1A516@serve-me.info>
Message-ID: <b7cfe01b-e35a-e766-ee1b-3b1b168d5814@msapiro.net>

On 10/24/2016 03:33 PM, Simon Hanna wrote:
> 
> You have to prefix the environment with py27. So you would be running `tox -e py27-record`
> Since no base Python version is defined in to, it probably uses the Python version that was used to install tox itself. 


Thanks Simon. That helped a lot.

However, it turns out that my underlying issue was simpler than I
thought. The tests all run fine in my own development environment, but
they won't run in GitLab CI because the MR depends on
<https://gitlab.com/mailman/mailmanclient/merge_requests/18> which in
turn depends on <https://gitlab.com/mailman/mailman/merge_requests/202>,
neither of which is merged yet.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From turnbull.stephen.fw at u.tsukuba.ac.jp  Tue Oct 25 06:38:57 2016
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Tue, 25 Oct 2016 19:38:57 +0900
Subject: [Mailman-Developers] Setting up installation to test own changes
In-Reply-To: <a2c1e46b-c8f7-95fd-2e6a-25e1f593cb1b@msapiro.net>
References: <CABDJ2UocX6+X5sy-L39_Pz5Bc1cCysOM=6W62cD+C_8rpu4JHw@mail.gmail.com>
 <a2c1e46b-c8f7-95fd-2e6a-25e1f593cb1b@msapiro.net>
Message-ID: <22543.13889.280837.600124@turnbull.sk.tsukuba.ac.jp>

Mark Sapiro writes:

 > Mailman bundler is not recommended because it doesn't install the
 > current development branches.

Mailman 3.1 is "close" to release (how close is for Barry, Florian and
Aurelian to say, but the improvements over 3.0 in the dev branches are
substantial).  I strongly (as co-mentor :-) recommend using the dev
branches.

I'm not sure how far bundler has been updated, but the kind of issue
you are likely to run into is, for example,
       <https://gitlab.com/mailman/mailman-hyperkitty/issues/10>
This is a problem with the environment that tox sets up for standalone
testing, not with interoperability of current Mailman components with
each other.  However, as stated in
            <https://gitlab.com/mailman/mailman/issues/181>
this kind of thing is generally not going to get timely fixes in static
bundles.

Aside to devs: I think we should toxify the procedure at
<https://wiki.list.org/DEV/SetupDevEnvironment>, and allow
specification of a ref tuple for the mailman components.

Steve

From barry at list.org  Tue Oct 25 18:17:39 2016
From: barry at list.org (Barry Warsaw)
Date: Tue, 25 Oct 2016 18:17:39 -0400
Subject: [Mailman-Developers] Request to process merge requests faster
In-Reply-To: <3dddf311-a029-2b5f-3f6f-9498a2c37edf@serve-me.info>
References: <3dddf311-a029-2b5f-3f6f-9498a2c37edf@serve-me.info>
Message-ID: <20161025181739.6e998ddc@subdivisions.wooz.org>

On Sep 13, 2016, at 12:43 AM, Simon Hanna wrote:

>I know all core devs are volunteers, and no one is maintaing the Mailman
>projects full-time, but it's a little frustrating to have your merge request
>open for a couple of months without any/much reaction to it...

Simon, I personally apologies for the long delay in responding, and in any
delays in reviewing your work on core.  Like others, it was a stressful
(northern hemisphere) summer for me and after my travel I got quite
backlogged.  Work and family come first of course.

But I am actively working now to reduce the core backlog.  I am working
through merge requests now, but it's difficult to get through more than one in
a sitting.  I think there are some GitLab workflow issues that slow me down,
but also, most branches require fairly deep thinking, testing, and review.
Still, that doesn't help you when you're frustrated by the progress.

I hope you won't leave us in anger just yet though.  Patience does win
eventually, and we do value your contributions.

Thanks also to Terri and Steve for their thoughtful insights on this thread.

Cheers,
-Barry

From best.sum at gmail.com  Thu Oct 27 14:55:30 2016
From: best.sum at gmail.com (Leon)
Date: Thu, 27 Oct 2016 14:55:30 -0400
Subject: [Mailman-Developers] Hyperkitty 1.0.3 doesn't have
 add_user_to_mailman function
Message-ID: <CAPDq0P2DAHGbSEgqGcLELK_nQBZ1sb0_zT2nqYGfxeBV204j_w@mail.gmail.com>

Latest mailman-bundle, Hyperkitty==1.0.3, python-social-auth==0.2.21.

https://gitlab.com/mailman/mailman-bundler/blob/master/mailman_web/production.py#L243
https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/lib/mailman.py

Im trying to implement a custom authentication backend by following a
tutorial. In the tutorial, the
version of hyperkitty is actually 1.0.4, and the whole thing works well.
However, it didn't work on top of 1.0.3. I can find this function in
commit 1755122c
https://gitlab.com/mailman/hyperkitty/commit/1755122c708abc96933142ca77dd0ff72feef056




-- 
Best wishes,
Leon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot 2016-10-27 15.16.34.png
Type: image/png
Size: 523159 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20161027/01af0db4/attachment-0001.png>

From mark at msapiro.net  Thu Oct 27 15:22:58 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 27 Oct 2016 12:22:58 -0700
Subject: [Mailman-Developers] Hyperkitty 1.0.3 doesn't have
 add_user_to_mailman function
In-Reply-To: <CAPDq0P2DAHGbSEgqGcLELK_nQBZ1sb0_zT2nqYGfxeBV204j_w@mail.gmail.com>
References: <CAPDq0P2DAHGbSEgqGcLELK_nQBZ1sb0_zT2nqYGfxeBV204j_w@mail.gmail.com>
Message-ID: <516ef3b6-7801-4767-f8aa-c755cffc32ec@msapiro.net>

On 10/27/2016 11:55 AM, Leon wrote:
> Latest mailman-bundle, Hyperkitty==1.0.3, python-social-auth==0.2.21.
> 
> https://gitlab.com/mailman/mailman-bundler/blob/master/mailman_web/production.py#L243
> https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/lib/mailman.py
> 
> Im trying to implement a custom authentication backend by following a
> tutorial. In the tutorial, the
> version of hyperkitty is actually 1.0.4, and the whole thing works well.
> However, it didn't work on top of 1.0.3. I can find this function in
> commit 1755122c
> https://gitlab.com/mailman/hyperkitty/commit/1755122c708abc96933142ca77dd0ff72feef056


HyperKitty and Postorius have switched from using Persona and SocialAuth
to using Django Allauth. Mailman bundler is not yet compatible with
this. at a minimum you need to also install django-mailman3 and make
config changes. See <https://wiki.list.org/x/17891998> for potentially
helpful stuff.

Also note, rather than posting a png screenshot of an error screen, it's
much better to just copy/paste the text.

And when mentioning that you are following a tutorial, it would help us
if you provide a link to it so we can see what it says.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From best.sum at gmail.com  Sun Oct 30 18:30:59 2016
From: best.sum at gmail.com (Leon)
Date: Sun, 30 Oct 2016 18:30:59 -0400
Subject: [Mailman-Developers] Hyperkitty 1.0.3 doesn't have
 add_user_to_mailman function
In-Reply-To: <516ef3b6-7801-4767-f8aa-c755cffc32ec@msapiro.net>
References: <CAPDq0P2DAHGbSEgqGcLELK_nQBZ1sb0_zT2nqYGfxeBV204j_w@mail.gmail.com>
 <516ef3b6-7801-4767-f8aa-c755cffc32ec@msapiro.net>
Message-ID: <CAPDq0P2NcHnb6_35ZHVDYn5ni0HQddZ-+6ea=c1YL5o6f8GZ6Q@mail.gmail.com>

Thank you. I have followed the instruction(
https://wiki.list.org/DOC/Mailman%203%20installation%20experience)?.
 urls.py, production.py and settings_local.py have been changed. I got an
ImportError.

Traceback (most recent call last):

  File "/usr/lib/python2.7/wsgiref/handlers.py", line 85, in run

    self.result = application(self.environ, self.start_response)

  File
"/opt/mailman/mailman-bundler/eggs/Django-1.8.15-py2.7.egg/django/contrib/staticfiles/handlers.py",
line 63, in __call__

    return self.application(environ, start_response)

  File
"/opt/mailman/mailman-bundler/eggs/Django-1.8.15-py2.7.egg/django/core/handlers/wsgi.py",
line 170, in __call__

    self.load_middleware()

  File
"/opt/mailman/mailman-bundler/eggs/Django-1.8.15-py2.7.egg/django/core/handlers/base.py",
line 50, in load_middleware

    mw_class = import_string(middleware_path)

  File
"/opt/mailman/mailman-bundler/eggs/Django-1.8.15-py2.7.egg/django/utils/module_loading.py",
line 26, in import_string

    module = import_module(module_path)

  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module

    __import__(name)

ImportError: No module named middleware

From turnbull.stephen.fw at u.tsukuba.ac.jp  Mon Oct 31 00:02:26 2016
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Mon, 31 Oct 2016 13:02:26 +0900
Subject: [Mailman-Developers] GNU Mailman Architectural Patterns & Quality
 Attributes for Research
In-Reply-To: <CAAqp00Rga36gARQU_0qfHKSWDjk+CVn7ABXBpOssgj39pyN1dw@mail.gmail.com>
References: <CAAqp00Rga36gARQU_0qfHKSWDjk+CVn7ABXBpOssgj39pyN1dw@mail.gmail.com>
Message-ID: <22550.49746.363305.728288@turnbull.sk.tsukuba.ac.jp>

Hi Michael,

Did you ever get an answer to this request?  I broke a bunch of ribs
on the 14th and have been pretty useless for the last two weeks, but
now I have a chance to catch up on correspondence of less than "life
or death" importance.

Regards
Steve


Michael Skeen writes:
 > 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
 > 
 > ----------------------------------------------------------------------
 > PDF: external: PID4110571 (Morphology).pdf, PDF          [fetch]
 > 
 > ----------------------------------------------------------------------
 > _______________________________________________
 > Mailman-Developers mailing list
 > Mailman-Developers at python.org
 > https://mail.python.org/mailman/listinfo/mailman-developers
 > Mailman FAQ: http://wiki.list.org/x/AgA3
 > Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/
 > Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/turnbull.stephen.fw%40u.tsukuba.ac.jp
 > 
 > Security Policy: http://wiki.list.org/x/QIA9

From mark at msapiro.net  Mon Oct 31 00:53:57 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 30 Oct 2016 21:53:57 -0700
Subject: [Mailman-Developers] Hyperkitty 1.0.3 doesn't have
 add_user_to_mailman function
In-Reply-To: <CAPDq0P2NcHnb6_35ZHVDYn5ni0HQddZ-+6ea=c1YL5o6f8GZ6Q@mail.gmail.com>
References: <CAPDq0P2DAHGbSEgqGcLELK_nQBZ1sb0_zT2nqYGfxeBV204j_w@mail.gmail.com>
 <516ef3b6-7801-4767-f8aa-c755cffc32ec@msapiro.net>
 <CAPDq0P2NcHnb6_35ZHVDYn5ni0HQddZ-+6ea=c1YL5o6f8GZ6Q@mail.gmail.com>
Message-ID: <7054352e-9018-d98b-2bba-86b50e626460@msapiro.net>

On 10/30/2016 03:30 PM, Leon wrote:
> Thank you. I have followed the
> instruction(https://wiki.list.org/DOC/Mailman%203%20installation%20experience)
> ?.  urls.py, production.py and settings_local.py have been changed. I
> got an ImportError.


What did you do that produced this error? If it was in response to a
command, exactly what command?  And if you have installed in a
virtualenv, was the virtualenv active when you gave the command?


> Traceback (most recent call last):
> 
>   File "/usr/lib/python2.7/wsgiref/handlers.py", line 85, in run
> 
>     self.result = application(self.environ, self.start_response)
> 
>   File
> "/opt/mailman/mailman-bundler/eggs/Django-1.8.15-py2.7.egg/django/contrib/staticfiles/handlers.py",
> line 63, in __call__
> 
>     return self.application(environ, start_response)
> 
>   File
> "/opt/mailman/mailman-bundler/eggs/Django-1.8.15-py2.7.egg/django/core/handlers/wsgi.py",
> line 170, in __call__
> 
>     self.load_middleware()
> 
>   File
> "/opt/mailman/mailman-bundler/eggs/Django-1.8.15-py2.7.egg/django/core/handlers/base.py",
> line 50, in load_middleware
> 
>     mw_class = import_string(middleware_path)
> 
>   File
> "/opt/mailman/mailman-bundler/eggs/Django-1.8.15-py2.7.egg/django/utils/module_loading.py",
> line 26, in import_string
> 
>     module = import_module(module_path)
> 
>   File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
> 
>     __import__(name)
> 
> ImportError: No module named middleware
> 


-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20161030/a9674c58/attachment.sig>

From mmskeen at gmail.com  Mon Oct 31 18:46:26 2016
From: mmskeen at gmail.com (Michael Skeen)
Date: Mon, 31 Oct 2016 16:46:26 -0600
Subject: [Mailman-Developers] GNU Mailman Architectural Patterns &
 Quality Attributes for Research
In-Reply-To: <22550.49746.363305.728288@turnbull.sk.tsukuba.ac.jp>
References: <CAAqp00Rga36gARQU_0qfHKSWDjk+CVn7ABXBpOssgj39pyN1dw@mail.gmail.com>
 <22550.49746.363305.728288@turnbull.sk.tsukuba.ac.jp>
Message-ID: <CAAqp00Sv0Nqy+V24kKpYi+3CtXc=ZRKFWA_OZ8PUTZ3cWPTMcg@mail.gmail.com>

Stephen,

No, we have not had any reply regarding this request. I am sorry to hear
that you got injured...sounds terrible! If you have an opportunity to give
some response, it would be most appreciated.

Thank you, and hope you continue to heal quickly,
Michael

On Sun, Oct 30, 2016 at 10:02 PM, Stephen J. Turnbull <
turnbull.stephen.fw at u.tsukuba.ac.jp> wrote:

> Hi Michael,
>
> Did you ever get an answer to this request?  I broke a bunch of ribs
> on the 14th and have been pretty useless for the last two weeks, but
> now I have a chance to catch up on correspondence of less than "life
> or death" importance.
>
> Regards
> Steve
>
>
> Michael Skeen writes:
>  > 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
>  >
>  > ----------------------------------------------------------------------
>  > PDF: external: PID4110571 (Morphology).pdf, PDF          [fetch]
>  >
>  > ----------------------------------------------------------------------
>  > _______________________________________________
>  > Mailman-Developers mailing list
>  > Mailman-Developers at python.org
>  > https://mail.python.org/mailman/listinfo/mailman-developers
>  > Mailman FAQ: http://wiki.list.org/x/AgA3
>  > Searchable Archives: http://www.mail-archive.com/
> mailman-developers%40python.org/
>  > Unsubscribe: https://mail.python.org/mailman/options/mailman-
> developers/turnbull.stephen.fw%40u.tsukuba.ac.jp
>  >
>  > Security Policy: http://wiki.list.org/x/QIA9
>