Bug 40602

Summary: Network tunnel documentation is lacking somewhat
Product: PulseAudio Reporter: Thijs van Dijk <freedesktop>
Component: miscAssignee: pulseaudio-bugs
Status: RESOLVED MOVED QA Contact: pulseaudio-bugs
Severity: normal    
Priority: medium CC: colin, lennart
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Thijs van Dijk 2011-09-03 07:49:31 UTC
The documentation at 
http://pulseaudio.org/wiki/NetworkSetup#Usingatunnel
could do with a clarity/completeness update.

Specifically, it should contain at least a basic manual on setting up a tunnelled connection for those uninitialised in the internals of PulseAudio.
Comment 1 Colin Guthrie 2011-09-04 01:24:13 UTC
It's a wiki, please feel free to add content to it. We're aware that all the pages on the wiki could do with updates, and it's an ongoing effort to fill it in (motivating developers to fill this in is tricky, but we'll likely do a "sprint" or similar to try and move documentation over the the freedesktop.org wiki.

I'm going to close this bug, as it's just a general suggestion that we fully acknowledge but I do not think would be helped via a bug to track any progress. If you can help out in improving the pages, it would be most welcome.
Comment 2 Thijs van Dijk 2011-09-04 01:46:14 UTC
Yes, I'm aware that it's a wiki. As soon as I find out how to set up a tunnelled connection, I'll be happy to contribute as much as I can.

My point, however, was that this information is difficult if not impossible to find, and it should at the very least be mentioned in some level of detail on the project website.

Filing a bug seemed like a structured way of asking someone who *does* have this information available (i.e. not me) of elaborating the wiki slightly. 
Then again, I may be hugely wrong.
Comment 3 Colin Guthrie 2011-09-04 01:59:51 UTC
Well I won't close this bug again (it seems rude to do so) but trust me when I say this will not change my priorities simply by having this here. Improving the docs has been on my todo list for a loooong time and it is gradually getting towards the top of the list. But I guarantee, that keeping a bug open will only clutter the real, critical code bugs and generally make my bug management harder and more complex.


But if you can, please come on IRC, ask us ad-hoc questions and learn how things work, then write some kick ass docs. You would be doing us a massive service if you did that :)
Comment 4 GitLab Migration User 2018-07-30 10:09:44 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/248.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.