Hi, PulseAudio is a widely used sound server. According to popcon it is present on ~60% of Debian installations [1]. Most of the time it just works and no one notices its existence [2]. Less often it has issues and this is how the amount of bugs outgrew the small team of PulseAudio maintainers (which basically had only one active member for years). :-( If you care about the sound system on Debian either because you have issues with it to solve or because you would like to keep it working for others as well, please consider helping the maintenance team a bit by moving bugs forward or even joining the team. Thanks, Balint [1] http://qa.debian.org/popcon.php?package=pulseaudio [2] http://packages.qa.debian.org/p/pulseaudio.html
Hi, I've just subscribed to the list in response to this bug. I'd like to help as my time permits. Please add me to the team in alioth, my username is fsateler. I've glanced at the bug list and it looks to me that many bugs have not had any activity (maintainer or otherwise) in over 2 years. I think bugs that are too old should be closed (with a ping first, maybe) so that the bug list becomes useful again. As time permits I will try to fix other bugs.
Added you. Go for it :) Thanks!
Thanks! There are some bugs that are actualy feature requests. How should we deal with those? Given the undermanned state of the team, I'm tempted to close them with a suggestion to file it upstream, but that is not very friendly. Perhaps I can forward the bug first and then close it. I don't think keeping bugs we won't be acting upon open is a good use of the BTS. What do you think?
Hello, I thought I had already replied to this bug - I apologize if I emailed someone directly on accident. II use pulseaudio and infact use the bluetooth module all the time. I'm interested to help out and gain a foot-hold into Debian development - I'm a c++ developer of over 10 years (I'll admit I'm replying as I'm heading to the source to see if its even my language) - but can generally write anything. Ah, as its C I shouldn't have any problem. Are you still seeking help? I have registered on Alioth previou/sly and will request to join the team If you need the help, and add me: Where should I begin (aside from reading all documentation in the vcs as well as upstream)? Best, *Richard B. Winters*
reading at the bug page and see if there is any bug you would be able to help. I think there are a couple of new ones I haven't had the time to reply yet, so if you could start there it would be great! You need to subscribe to the team as well. Also, you should probably check out the latest 6.0 release already on git (I haven't been able to upload yet), and test it. Saludos Felipe Sateler PS: these RFH bugs don't reach the maintainers by default :(. Good thing you applied on alioth otherwise we would have missed this!
Hello I could help with this. Is this RFH still topical? - Tommi Höynälänmaa
Hello It turned out that pulseaudio is to be replaced by pipewire in the future. Hence I withdraw from this project. - Tommi Höynälänmaa
Hello, I would like to help as my time permit too for this project. I use debian since multiple year, and this is my first first time I want participate into the tracking part of a package. I am not interested about pipewire and I want continu to use pulseaudio. :) Please add me to the team. my username is borrougagnou.
Hi, I’d like to help with Debian’s PulseAudio packaging on an ongoing basis, potentially as a co-maintainer if that would be useful to the team. I work professionally with audio systems and have been getting more involved in Debian packaging. As a first concrete contribution, I tested the proposed JACK2 Build-Depends change in Bug #1143540 against the current PulseAudio Salsa packaging. I switched the build dependency from libjack-dev to libjack-jackd2-dev, verified dpkg-checkbuilddeps, and completed a full binary package build successfully on Debian 13 amd64 with JACK 1.9.22 detected and pulseaudio-module-jack produced. I’m happy to keep helping with bug triage, reproducing and testing fixes, preparing packaging changes/MRs, and audio-integration issues around JACK/ALSA/PipeWire. I can start with small, reviewable tasks and build trust from there. If the RFH is still current, I’d appreciate guidance on the most useful next package-maintenance work to pick up. Thanks, Thomas Stephens GitHub: https://github.com/tmsteph