[aur-general] Questions about some of my packages being adopted in [community]

[Konstantin Gizdov]

Hi all,

I'm writing to hopefully get some clarity on some packages that I
maintained in AUR (python-awkward-array, unuran), but have been overtaken
now in [community]. Also one other package that I have not maintained
'libafterimage', but dear to me.

Firstly, thanks to Felix Yan for picking them up and sorry if the following
questions have been asked before and obvious to everyone.

This is what I know:

1. Nothing in the core repos depends on them and they are libraries. I've
not seen requests to add them before.
2. 'libafterimage' includes a bug that has been reported to AUR, but has
not been fixed. I've had to include a patch in my local chain.
3. The packages do not provide the same functionality as before, but
conflict with the AUR ones.
4. I wasn't told anything - my AUR package was deleted with a 'thanks for
maintaining it' message.
5. I've reported a few bugs FS#6024{6,7,8}, but have been denied resolution.

The reason I'm asking is because over the years I've added and been
maintaining some professional software and these packages are part of that
chain. Colleagues in the field have become accustomed to me for packaging
with care and updating with new features. But now, obviously that is
changing and people are going to flock if something doesn't work as
expected. So this is sort of me getting ahead of the wind and basically
asking the question:

 - Why?
 - How many & which will be put into [community]?
 - How can I effectively communicate the nuts & bolts to the new
maintenaners so to say, to make sure users still get what's expected?
 - Is there anything I can do if new packages do not meet what the original
intention was - apart from making a conflicting AUR package?

Thanks in advance.

--
Regards,
Konstantin