Package: wnpp Severity: normal X-Debbugs-Cc: debian-de...@lists.debian.org, debian-de...@lists.debian.org, debian-pyt...@lists.debian.org, pkg-mailman-hack...@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
