On Sep 11, 2015, at 12:49 AM, Pierre-Elliott Bécue wrote:
>As a Debian fanboy and also a mailman addict, I'd like to try packaging it
>in Debian.
Excellent! Do check wnpp to make sure there's not already an ITP for Mailman
3. Note too that there is already a Mailman 2 package, so you might want
On Sep 11, 2015, at 11:26 AM, Stephen J. Turnbull wrote:
>Mailman3 (or mailman-suite) would be a trivial package that depends on
>all of the above.
Yep, though I'd go with something like mailman3-suite. Or you can reserve the
'mailman3' source package name for the umbrella package that depends o
OK, I have something that follows these requirements (except the
site-defaults + site-config thing, currently site-wide checks take
precedence).
If you want to look at it :
https://gitlab.com/abompard/mailman/commits/import-header-matches
If you have some time Barry, I'd like your review on some t
On Sep 11, 2015, at 04:25 PM, Aurelien Bompard wrote:
>If you want to look at it :
>https://gitlab.com/abompard/mailman/commits/import-header-matches
I took a brief look, and I think you're heading in the right direction. I'll
do a more details review once the mp is up[*].
>In the code and in t
> You're right that model classes should never be imported outside mailman/model
> although there are a few violations of this rule. It's less hard-and-fast for
> tests since sometimes that's just the most convenient way to handle it.
> [...]
Great explanation, thanks.
I'll send a merge request r
