Hi all, I've been (co-)maintaining the bluez package, which contains the linux bluetooth stack, for openSUSE since about 15 years, but now I realize that it deserves a maintainer that does actually use the stuff. I now noticed, after Dominique hinted me at severe issues with a seemingly trivial update in https://build.opensuse.org/request/show/902427#comment-1482547, that I am actually not using any bluetooth hardware since almost two years. This makes me not that well suited as the maintainer of the bluez package IMVHO. Advertising blurb follows ;-) Package maintainance is usually low-effort: you watch out for new releases, update the tarball, check if patches are still needed and do still apply and you are done. Upstream code quality is very good, regressions like the current one are really the exception and the upstream community is helpful (if you know how to write a good bugreport and provide the necessary information ;-). But it certainly would be good if someone who is actually using the software would take a look at the stuff. As an extra bonus, there is also Al Cho who from SUSE side co-maintains the package and does stuff like security fixes etc, so you are not alone if you dare to take on this challenge :-) I'm not going away and I will keep updating the package in my current modus operandi, which means "do the version updates, keep it building and submit it to Factory" if nobody steps up and takes over, but I certainly won't be able to process most of the bug reports (I actually have not been really looking at bug reports for almost a year) and the package will only be maintained in a "it builds, let's ship it!" sense. If you want to take over, I'll of course also try to help in the future if questions about "WTF do we carry this patch?" or "what has he been thinking when doing this crazy thing in the spec file?" arise. Best regards, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman