On Sat, 9 Mar 2002, Martijn Sipkema wrote: > > .... So, i think there's a time to code THEN there a time > > to build docs (the doxygen sections in code are oftenly updated). > > > > This is why i think there is a non-sense in this *advandage* > > of OSS here. > > I don't agree. Good documentation is essential and I see the lack > of it as a serious problem for ALSA. > > > Why waiting, help them, if you have time, if you want help the > > world. I'm pretty sure if you try another time, you will get feedback > > from Alsa devels and Alsa client devels to write a nice Alsa > > Programmer's > > Guide, since alsa09 is largely used in native mode. > > It's not that easy to write documentation without documentation. > This would be best done by the people who wrote the API I > think. It would take some time, but then again it is a matter of > where the priorities are. I think documentation is very important, > and in the long run would gain other developers' contribution > and make life easier for the ALSA core developer team.
I don't know, if you are noticed, that some documentation already exist at http://www.alsa-project.org/alsa-doc/alsa-lib . It is build from sources via doxygen. I think that PCM API descriptions has good backgrounds with a few examples. The problem is, that I'm not English native writer and always busy with other maintaince things, so definitely, I can't create perfect English documentation. I tried several times to ask for help on alsa-devel, but - as you can see - I got only rare critics. It would be really helpful from developers to give some feedback and/or rephase my texts. Jaroslav ----- Jaroslav Kysela <[EMAIL PROTECTED]> Linux Kernel Sound Maintainer ALSA Project http://www.alsa-project.org SuSE Linux http://www.suse.com _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
