Re: Status and future of libembperl-perl

[intrigeri <intrigeri@debian.org>]

Hi Axel, hi team,

Axel Beckert (2020-08-24):
> I won't discuss this part again.

> Niko Tyni wrote:
>> At that time Axel (explicitly cc'd just in case) was strongly against
>> removal.
>> 
>> Axel, is this still the case?

Thank you, Niko, for pointing this out. At the time I started this
thread, I was not aware of the conversation that had happened on
#899021.

> Yes, and — as I wrote to intrigeri as reply to the bug report — up to
> the extent to maintain it outside the team. I'm quite sick of this
> discussion.

I understand that me starting this thread put you in the unpleasant
situation when you faced essentially the same set of arguments as you
had, in a previous discussion that had already been unpleasant for
you. I'm sorry I've hurt your feelings. And I'm sorry it took me so
long to write this message.

I can live with keeping libembperl-perl team-maintained:

 - I've not put any work into this package myself so far beside trying
   to triage #871729, and it's unlikely that I ever do, so the impact
   on me is limited to remembering I should ignore libembperl-perl,
   when I look for potentially problematic team-maintained packages.
   I'll try my best.

 - Looking at this topic in terms of taking care of each other and of
   the group, at this point it is more important to me that we heal
   the bad feelings I've triggered, than to avoid some recurring
   team-maintenance work.

As a final note, making this conversation taboo forever would not seem
smart to me: a conclusion that's OK today may not be good enough in
2025, as the situation evolves with time. If one of us feels the need
to resume this conversation at some point, I hope they'll manage to
take all the relevant factors into account right from the beginning,
which I've sadly not been able to do.

Cheers!