I personally would prefer the GNU organization. 

But John Fitch is the sole administrator of the SourceForge site, so he
presumably has the most authority on stuff like this. 

As a first step, I suggest we take a poll of active Csound developers (but
who are they? You, me, John Fitch, Richard Dobson, John Ramsdell at least
in CVS... Matt Ingalls, Gabriel Maldonado outside CVS... the Cecelia
people? maybe more?). If most want a reorganization, we can talk to John
Fitch about it.

Original Message:
-----------------
From: stevenyi stevenyi@csounds.com
Date: Tue, 18 Nov 2003 09:01:22 -0800
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3386] Re: Road to Reentrancy


Well, the documentation in csound.h is pretty thorough IMO, and it's
fairly easy to read with doxygen generated documentation.  

However, a developer doc for architecture, design philosophy, and a TODO
list would be very nice to have.  

One thing I would like to bring up again would be moving all source code
into a src folder within the main CVS, so that we can add a doc folder
and keep TODO, LICENSE, etc. in the top level (I believe this is
standard GNU convention for project organization).  I can go ahead and
do this change but it would mean everyone doing pretty much a fresh
checkout to start again with the new locations of files.

steven



On Tue, 2003-11-18 at 08:10, Richard Dobson wrote:
> I think what we need now, especially now that Csound is on CVS, is 
> formal documentation of csound.h and the API in general (even if still 
> subject to change), so that not only those privy to an archive of this 
> list, but those who may discover Csound CVS tomorrow, have 
> self-contained information. Annotating each function is not enough - we 
> need a synopsis of the architecture, design philosopy and a "TODO" list 
> too. I have done a quick search for "csound.h" in my stock of posts, and 
> find plenty of snippets about this and that (discussions more than 
> documentation), so I am in much the same situation as John, and I think 
> other people may be too. It would be impossible for me to assemble 
> complete and accurate formal documentation on this just from the bits 
> and bobs in various posts to the list, any more than I could reconstruct 
> the VST SDK from posts to the vst dev list.
> 
> This documentation would then itself go into  CVS so that it is 
> automatically there with all the other files.
> 
> Someone will write a book about all this one day...
> :-)
> 
> 
> Richard Dobson
> 


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .