Package: wnpp Severity: normal X-Debbugs-Cc: debian-devel@lists.debian.org, debian-devel@lists.debian.org, debian-python@lists.debian.org, pkg-mailman-hackers@alioth-lists.debian.net Control: affects -1 src:mailman3 Control: affects -1 src:mailmanclient Control: affects -1 src:postorius Control: affects -1 src:hyperkitty Control: affects -1 src:django-mailman3 Control: affects -1 src:mailman-hyperkitty Control: affects -1 src:mailman-suite Hey mailman(3) friends, The Debian Mailman Team needs some help. We (Jonas and Pierre-Elliott) packaged mailman3 components and dependencies and maintain the packages since a few years. Unfortunately, lately, considering the increasing requirements to maintain the packages in good shape, particularly because of their dependencies, we are finding ourselves lacking of the appropriate time to do it in a timely manner, which makes handling bugreports et al harder than what we would like. Also, while we both still run Mailman3 instances, a broaded contributor environment would be better. The mailman3 packages consist of the following: * mailman3: the "delivery engine", a daemon written in python3, along with some MTA (mail transport agent) integration. * mailmanclient: the official Python3 bindings for Mailman3's REST API * postorius, hyperkitty: webinterface/web archive, django components. * django-mailman3: the common component for both Postorius and HyperKitty * mailman3-web: wsgi daemon for the django web application with quite some configuration magic and webserver (apache, nginx) integration. * various dependencies: mostly python3 libraries or django components So we're looking for you if you: * happen to run mailman3 instances and have some spare cycles * want to give your share to keep mailman3 packages in Debian * are keen to get your hands dirty in python packages which touch a lot of different packaging aspects We're looking forward to you as a new Mailman3 Team member. Kind regards Jonas & Pierre-Elliott
Hi, thank you for note and thanks a lot for bringing and maintaining mailman3 in Debian. do you mean 'NEW python packages' that needs to be uploaded & maintained in debian, or, 'new dependencies' that make testing/packaging mailman itself more timeconsuming? Regards, Daniel
Hi, thank you for note and thanks a lot for bringing and maintaining mailman3 in Debian. do you mean 'NEW python packages' that needs to be uploaded & maintained in debian, or, 'new dependencies' that make testing/packaging mailman itself more timeconsuming? Regards, Daniel
Hey Daniel, Daniel Baumann wrote: Maintaining mailman3 includes keeping its dependency packages in shape. We packaged a bunch of python modules and django packages in order to get mailman3 into Debian and all of them need to be forward-maintained. So at the moment there's no need to package new dependencies and get them through NEW, it's rather about new releases of the dependency packages - sometimes even enforced by bumped version dependencies of newer mailman3 releases. Cheers Jonas
Hey Daniel, Daniel Baumann wrote: Maintaining mailman3 includes keeping its dependency packages in shape. We packaged a bunch of python modules and django packages in order to get mailman3 into Debian and all of them need to be forward-maintained. So at the moment there's no need to package new dependencies and get them through NEW, it's rather about new releases of the dependency packages - sometimes even enforced by bumped version dependencies of newer mailman3 releases. Cheers Jonas
Hey Daniel, Daniel Baumann wrote: Maintaining mailman3 includes keeping its dependency packages in shape. We packaged a bunch of python modules and django packages in order to get mailman3 into Debian and all of them need to be forward-maintained. So at the moment there's no need to package new dependencies and get them through NEW, it's rather about new releases of the dependency packages - sometimes even enforced by bumped version dependencies of newer mailman3 releases. Cheers Jonas
Hi Jonas, is there already a way to "easily" track them/have an overview of the amount of these "dependency" packages (e.g. how about subscribing them to the DDPO for pkg-mailman-hackers@l.a.d.o)? i'm glad that mailman is in debian and i'm happy to help with maintaining python packages. Regards, Daniel
Hi Jonas, is there already a way to "easily" track them/have an overview of the amount of these "dependency" packages (e.g. how about subscribing them to the DDPO for pkg-mailman-hackers@l.a.d.o)? i'm glad that mailman is in debian and i'm happy to help with maintaining python packages. Regards, Daniel
Hi, I co-maintain Wikimedia's Mailman3 install and have also done a bit of work upstream. Please let me know how I can help.
Hi, I'm co-maintaining the mailman3 install with Kunal in Wikimedia. I would be more than happy to help with future packaging too. Best
Hey Moritz, hey Amir and Kunal, Moritz Muehlenhoff wrote: That's great news, thanks for letting me/us know! I'll take the discussion to our mailinglist and the bugreport in order to bring all the respective parties together :) I co-maintain mailman3 together with Pierre-Elliott and he's actually more active than me recently. Pierre, do you have good first tasks in mind to get Amir and Kunal started with the mailman3 packages? Maybe a short introductionary chat session would be nice to introduce them to the packages? I'm looking forward to have you both in the Debian mailman team in future, Amir and Kunal :) Indeed I totally missed these responses as I forgot to subscribe to the bug report. Cheers jonas
Hi all, Jonas Meurer <jonas@freesources.org> wrote on 09/12/2021 at 22:09:05+0100: I guess Amia and Kunal could try to package the new upstream release of postorius? It should be pretty straightforward and I'm eager to give them some rights on the repos. Thanks both for your interest!