- Stephen J. Turnbull (turnbull.stephen.fw@u.tsukuba.ac.jp) [210525 09:28]:
It's possible that we could make this easier to configure with some changes to core. However, if this is as close to what you need as I think it is, I would advise against vendoring Mailman, and instead writing some scripts to help manage mass subscription, or create the member adapter.
I agree, any changes to existing code in core should be mergeable.
I however think about replacing the hard dependency on allauth by an interface (which would mean minimal changes to the existing code, but would allow to plug in another class than allauth if helpful).
But that's another topic than the one I asked at the beginning of this mail :)
That's helpful to know. This sounds very similar to the Systers approach, where the Mailman core User database is the authoritative membership database for the organization.
Re Systers, I found https://bazaar.launchpad.net/~systers/systers/stable/files
This is however mm2 based. Is this what everybody hinted at, or is there also a mm3 clone I failed to find yet?
Andi