Why would we do it via flatpak when we have a native, source repository, and can more easily guarantee that it is using our optimized libraries, interpreters (in the case of python), etc.?

Like if you don't want to maintain it, that's fine. We can RFC it for a new maintainer, but it being distributed via flatpak is hardly a reason for it to not be included.

Thanks for the quick reply. The main reason is that I have switched to another distribution as daily driver, meaning that I am not available anymore to maintain the package actively (now it is at 0.2.2). If someone else could maintain the package (or at least update it to 0.2.6 / c20c51951749aa991c72a2937621b07b7a460f48, which uses the Meson build system - since I believe this release will stay the latest for quite a while) then I would be even happier

Needless to say, I am certainly available for questions regarding any packaging issues - although I believe the new Meson build is even more straightforward (and gnome-ish) than the old setup.py one