[gentoo-dev] Packages up for grabs: net-mail/mailman and everything that belongs to it

[gentoo-dev] Packages up for grabs: net-mail/mailman and everything that belongs to it

[Hanno Böck]

Hi,

I'm no longer using mailman personally, thus I'm not interested in
maintaining it any more.

The mailman packages currently in portage are the mailman 3 split
packages, which involve multiple packages providing the functionality,
plus a large number of dependencies. (Unfortunately with the switch
from mailman 2 to 3 upstream decided not only to move from python 2 to
3, but also to make the whole thing far more complicated and involve
far more dependencies...)

If you're interested in maintaining this please add yourself to the
metadata.xml of these packages:

dev-python/django-allauth
dev-python/django-appconf
dev-python/django-compressor
dev-python/django-extensions
dev-python/django-gravatar2
dev-python/django-haystack
dev-python/django-picklefield
dev-python/django-q
dev-python/python3-openid
dev-python/rcssmin
dev-python/robot-detection
net-mail/django-mailman3
net-mail/hyperkitty
net-mail/mailmanclient
net-mail/mailman
net-mail/mailman-meta
net-mail/postorius

If noone steps up maintaining this I'n not entirely sure what to do
with it, maybe just remove everything? (Including the python
dependencies that aren't used by any other package I guess.)

-- 
Hanno Böck
https://hboeck.de/

Re: [gentoo-dev] Packages up for grabs: net-mail/mailman and everything that belongs to it

[Jaco Kroon]

Hi Hanno,

I've started looking at this mess.  And a mess it is.  To the point,
where for our somewhat "subset of what mailman provides" requirements
I'm contemplating rather cooking an in-house solution (have done similar
in the past, but none of these really provide everything we require),
but will get back to you.

In the current state mailman3 as it is in tree I don't think it's usable
in any sensible way (Unless I'm really missing something), so if I go
another route I recommend we last-rite it and move on.  If I do pick it
up on it, then the problem is solved either way.

Kind Regards,
Jaco

On 2021/12/21 13:23, Hanno Böck wrote:
> Hi,
>
> I'm no longer using mailman personally, thus I'm not interested in
> maintaining it any more.
>
> The mailman packages currently in portage are the mailman 3 split
> packages, which involve multiple packages providing the functionality,
> plus a large number of dependencies. (Unfortunately with the switch
> from mailman 2 to 3 upstream decided not only to move from python 2 to
> 3, but also to make the whole thing far more complicated and involve
> far more dependencies...)
>
> If you're interested in maintaining this please add yourself to the
> metadata.xml of these packages:
>
> dev-python/django-allauth
> dev-python/django-appconf
> dev-python/django-compressor
> dev-python/django-extensions
> dev-python/django-gravatar2
> dev-python/django-haystack
> dev-python/django-picklefield
> dev-python/django-q
> dev-python/python3-openid
> dev-python/rcssmin
> dev-python/robot-detection
> net-mail/django-mailman3
> net-mail/hyperkitty
> net-mail/mailmanclient
> net-mail/mailman
> net-mail/mailman-meta
> net-mail/postorius
>
> If noone steps up maintaining this I'n not entirely sure what to do
> with it, maybe just remove everything? (Including the python
> dependencies that aren't used by any other package I guess.)
>

Re: [gentoo-dev] Packages up for grabs: net-mail/mailman and everything that belongs to it

[Jaco Kroon]

Hi Hanno,

We've decided to for the time being shelf Mailman completely.  We're
just about done (should go live with test clients this afternoon)
implementing an alternative that we've built in-house to more accurately
accommodate for our use-case in any case.

I would recommend proceeding to last-rite Mailman and related packages.

Kind Regards,
Jaco

On 2021/12/25 00:30, Jaco Kroon wrote:
> Hi Hanno,
>
> I've started looking at this mess.  And a mess it is.  To the point,
> where for our somewhat "subset of what mailman provides" requirements
> I'm contemplating rather cooking an in-house solution (have done similar
> in the past, but none of these really provide everything we require),
> but will get back to you.
>
> In the current state mailman3 as it is in tree I don't think it's usable
> in any sensible way (Unless I'm really missing something), so if I go
> another route I recommend we last-rite it and move on.  If I do pick it
> up on it, then the problem is solved either way.
>
> Kind Regards,
> Jaco
>
> On 2021/12/21 13:23, Hanno Böck wrote:
>> Hi,
>>
>> I'm no longer using mailman personally, thus I'm not interested in
>> maintaining it any more.
>>
>> The mailman packages currently in portage are the mailman 3 split
>> packages, which involve multiple packages providing the functionality,
>> plus a large number of dependencies. (Unfortunately with the switch
>> from mailman 2 to 3 upstream decided not only to move from python 2 to
>> 3, but also to make the whole thing far more complicated and involve
>> far more dependencies...)
>>
>> If you're interested in maintaining this please add yourself to the
>> metadata.xml of these packages:
>>
>> dev-python/django-allauth
>> dev-python/django-appconf
>> dev-python/django-compressor
>> dev-python/django-extensions
>> dev-python/django-gravatar2
>> dev-python/django-haystack
>> dev-python/django-picklefield
>> dev-python/django-q
>> dev-python/python3-openid
>> dev-python/rcssmin
>> dev-python/robot-detection
>> net-mail/django-mailman3
>> net-mail/hyperkitty
>> net-mail/mailmanclient
>> net-mail/mailman
>> net-mail/mailman-meta
>> net-mail/postorius
>>
>> If noone steps up maintaining this I'n not entirely sure what to do
>> with it, maybe just remove everything? (Including the python
>> dependencies that aren't used by any other package I guess.)
>>