[Pkg-mailman-hackers] Bug#799281: ITP: mailman3-core -- Mailing list management system

[Pierre-Elliott Bécue]

Dear Thomas,

First, thanks for your answers and interest in my work! :)

Le jeudi 03 décembre 2015 à 16:04:50+0100, Thomas Goirand a écrit :
> On 11/30/2015 04:54 PM, Pierre-Elliott Bécue wrote:
> > Le jeudi 17 septembre 2015 à 16:19:09+0200, Pierre-Elliott Bécue a écrit :
> >> Package: wnpp
> >> Severity: wishlist
> >> Owner: "Pierre-Elliott Bécue" <becue at crans.org>
> >>
> >> * Package name    : mailman3-core
> >>   Version         : 3.0.0
> >>   Upstream Author : Barry Warsaw, Mark Sapiro, Aurélien Bompard, Florian Fuchs, Terri Oda, Stephen J. Turnbull, Abhilash Raj
> >> * URL             : http://list.org/
> >> * License         : GPLv3
> >>   Programming Lang: Python3
> >>   Description     : Mailing list management system
> >>
> >> GNU Mailman3 is a package providing mailing list management system.
> >> This would be the bare core of Mailman3, without client package,
> >> HyperKitty or Postorius, that would be packaged in different sources
> >> packages.
> >>
> >> There is currenctly mailman2 in Debian archive, and I was considering
> >> involve myself in packaging mailman3, Mailman developers seems to think
> >> that it is a pretty good idea, but they suggested me to wait 'till 3.1.0
> >> is out.
> >>
> >> I'm currently looking for a sponsor as I'm not a Debian Developer, nor
> >> used to build brand new packages. Since 3.1 is not released yet, I've
> >> some time to learn but I'll be happy to work with people already used to
> >> packaging.
> >>
> >> This bug report is CC-ed to Debian mailman team, as I do intend to
> >> collaborate with them, I hope I'll be helpful.
> >>
> >> This bug report will come with the others for the others components of
> >> Mailman3 suite. I hope this is the good way of doing ITP
> > 
> > Dear debian developers, dear mailman maintainers,
> > 
> > I started in september to package mailman3 core archive into debian. With
> > Barry Warsaw help and a lot of reading, I've so far managed to get to this :
> > https://github.com/P-EB/mailman3-core
> > 
> > Before requesting for sponsorship, I'd like to request some new eyes and
> > opinions on my work, as I'm totally new to packaging, and as I'm not sure at
> > all that I fullfilled all policy constraints. (and also because I don't want
> > to package mailman without having discussed with mailman maintainers!)
> > 
> > I've sent a mail to mailman developers, but I was also suggested to send a
> > mail here.
> > 
> > Any review would be appreciated, and thanks for the time anybody will give
> > to my work!
> > 
> > Cheers!
> 
> Hi,
> 
> A few remarks, quickly browsing to the github repo without deep checks,
> rebuilding and trying the actual package... I hope this still helps.
> 
> * Your changelog has 3 entries, though the package wasn't uploaded to
> Debian. Please remove the top 2 entries, and replace "sid" by "unstable.

Of course I will, for now it was a proof of concept, so I do dirty
changelogs updates and commits, my aim is to squash all these before
requesting for sponsorship. So, ack.

Ack for unstable, but, why that instead of sid?

> * Either write meaningful content, or remove debian/README.source

I'll probaby remove it.

> * There's no useful information in README.rst that isn't in the long
> description. Please remove it from debian/docs

I thought I had to keep it for lintian to be happpy.

> * Upstream provides a crontab entry, why not packaging one (not
> necessarily the one from upstream)?

Oh yeah, I definitely should. Will have a look on it, thanks!

> * It's looking like your postinst does nothing, am I missing something?

It is supposed to call systemctl enable mailman3.service at last. Still
thinking about how to do proper things.

> * Please review your long description, and incorporate what's in
> README.rst. The current long desc is quite bad.

Any suggestion is welcome, I'll try to do that. :)

> * It doesn't look like your package is producing an init script. Please
> provide a sysv-rc script. Instead of manually installing the systemd
> .service file, I'd recommend just moving debian/contrib/*.service to
> debian/.

Oh, that works automagically when mailman3.service is in debian? Didn't knew
that! I'm working on a sysv service file, will definitely add it.

> * IMO, you should be providing a mailman3-doc package using sphinx-build.

make html makes external imports from jquery and mathjax, that would break
policy regarding privacy. So I'm tied to make latex doc, except if there is
a proper way to remove these external imports.

Thanks for your time.

-- 
PEB