Following recent emails on list about documentation and learning &quot;Linux Audio Programming&quot;, I&#39;ve been thinking about an effort to help people get started with Linux Audio Coding.<br><br>I think some &quot;beginner&quot; coding documentation on Linux Audio would be a great asset to the community, and I&#39;m willing to contribute to such an effort. As Robin Gareus mentioned in another thread, a &quot;FLOSS&quot; manual is probably the best way to go for a community effort on documenting.<br>

<br>I&#39;ve been doing some &quot;tutorial&quot; style  programming articles on my blog <a href="http://harryhaaren.blogspot.com" target="_blank">harryhaaren.blogspot.com</a> and I&#39;d have no problem sharing the examples there (some basic GTK stuff, some small JACK apps, combining the GUI / JACK stuff ). Problem is that I was learning as I was going along, and there are some *fundamental* issues with some of the tutorials (especially with regards to thread safe code &amp; more advanced programming concepts)<br>

<br>Personally I&#39;d be even more enthusiastic about such an effort if some of the veteran Linux audio guys were to get on board and ensure the content is of a high quality. (As I&#39;m a self though programmer, there are some big gaps in my knowledge, and I&#39;d not like to provide bad sample code, or share bad concepts.)<br>

<br>Of course some issues will arise in choosing how to document Linux Audio, and some typical &quot;flame&quot; topics like GUI toolkits, libraries etc will arise. I have no idea how we can best avoid that issue, except by following the &quot;if you think it should be thought that way write the tutorial&quot;...  the downside of this is that if one tutorial uses toolkit &lt;X&gt; and the next toolkit &lt;Y&gt;, the average beginning coder is going to get lost in implementation details and that defeats the purpose of documentation :D<br>

<br>-Harry<br>