Documentation by itself is of no interest, i.e. if a developer wrote a document, but no end user has access to it/knows where to find it, then for end users the document effectively does not exist.
What I know from my past experience is that a proper procedure should be established. That is, if developers agree to write documentation, they should also agree on a way of publishing it on the web site, and in such a manner the web site will be maintained. -----Original Message----- From: Lee Revell <[EMAIL PROTECTED]> To: Sergei Steshenko <[EMAIL PROTECTED]> Date: Fri, 13 Jan 2006 23:12:35 -0500 Subject: Re: Re[2]: [Alsa-user] Alsa problems > > On Sat, 2006-01-14 at 07:06 +0300, Sergei Steshenko wrote: > > The logical idea is that the one who wrote a piece of code also > > maintains documentation for it. > > The documentation for the code is already maintained. Maintaining the > web site is a different issue. > > Lee > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
