Greetings!
Let's get right into it: LavaLauncher needs a new maintainer / new
main developer. I am abandoning the project.

Here is why. I believe that you can only be an effective developer if
you yourself use the project you are working on regularly. I have not
used LavaLauncher in over a year and won't have a use for it in the
forseeable future. As such, I am unqualified and unwilling to put in
the work needed to keep the project going.

LavaLauncher is functional in its current state. However, to add
certain additional features (which I think the project needs to remain
useful and interesting), some changes to the code base need to be made.
This was the very first Wayland client I ever wrote, in fact even the
very first graphical application. As such, I made a few abstractions
and decisions that turned out to be less than ideal; I programmed myself
into a corner. The codebase is totally salvageable. I already started
in the devel branch (which btw I also recommend for users), where I
estimate that I have already done somewhere between 20% and 40% of the
work needed.

Since this is a packaged application which has actual real-world users,
I won't be forwarding the BDFL role to any random person. To get my
official blessing, you need to have experience with the C language and
with maintaining medium-sized projects. Alternatively you can also
just fork the project, obviously. Either way, I am available for
questions regarding the codebase and Wayland even after someone else
has picked the project up.

Or maybe no one has interest in this project anyone, in which case I
recommend users switch to an alternative (Latte dock has Wayland
support AFAIK and is visually similar). Package maintainers should
remove the package as soon as it no longer works on recent compositors,
as I don't plan on fixing compatibility bugs, or any bugs at all.


Friendly greetings,
Leon Henrik Plickat