>how about to add informational pages for each driver, and make links >from soundcard matrix? then a user can reach to the detailed info by >two clicks from the top page. > >a driver page will contain: [ ... ] >the pages should be controlled by cvs, so that both developers and web >admins can keep them up-to-date. >an advantage is that we can generated documents for >alsa-kernel/Documentation from these files. > >i'm not sure whether these docs to be auto-generated or should be >static files. also, we need to discuss which format is best - sgml, >docbook, html or else. > >we can start from converting existing docs (e.g. CMIPCI.txt) to >such pages. > > >any comments please?
we had quite a bit of discussion about this a month or two back. some people were in favor of something like a wiki, where people could add information in a dynamic, immediate way, and thus increasing the likelihood that we'd accumulate a bunch of useful information. others wanted something more like you're suggesting. i think that its important that there is a mechanism to make collecting information from users extremely easy, because otherwise there simply won't be very much in this pages. CVS doesn't meet this requirement since its intended to grant write access to a relatively small number of people (and certainly not just anybody who happens to have a useful piece of info about their audio interface). patrick even mocked up a sample page which i critiqued in a number of ways. whatever we do, we should move forward with this fairly quickly, because its one of the biggest weaknesses (after the complete lack of user-usable documentation for ~/.asoundrc) of ALSA at this time. --p _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
