Hi,
I think it would be good a good new year's start to have a section describing the projects hosted on pure-data.sf.net's CVS-repository.
It would be great, if those who have stuff inside the repository could mail me a (short) description of what's inside their directories, who wrote it and so on.
I could write it myself (and I warn you, I would do it!), but it's less work for me, if you write it. ^_^
So please mail me your descriptions, I'll add them when they come in AsSoonAsPossible(tm).
Thank you and
ciao
Hi,
I already started the external description page from READMEs and source files in CVS. I think, tomorrow I'll leech and loot pure-data.org, too.
See http://pure-data.sf.net/subprojects.html
ciao
On Fri, 27 Dec 2002, Frank Barknecht wrote:
Hi,
I think it would be good a good new year's start to have a section describing the projects hosted on pure-data.sf.net's CVS-repository.
It would be great, if those who have stuff inside the repository could mail me a (short) description of what's inside their directories, who wrote it and so on.
I could write it myself (and I warn you, I would do it!), but it's less work for me, if you write it. ^_^
So please mail me your descriptions, I'll add them when they come in AsSoonAsPossible(tm).
Hi Frank,
Thanks a lot for stepping forward on this. I am really sorry that I wasn't around to back you up, X-mas is time without internet (well, lets say mailing lists) for me.
I think that this page is a very good idea, although it should be generated automatically, otherwise it will be very hard to maintain and constantly out of date.
For this to work out, we should agree on a convention for written documentation for externals.
Something like the reference patches that are already in place.
If we need to move the pure-data.sf.net site for that, this is not a problem at all. We can just redirect. Of course I think that the best thing would be to combine our efforts and integrate this into pure-data.org, or pddb, ...
Comments ?
Greetings,
Guenter
Hi, guenter geiger hat gesagt: // guenter geiger wrote:
Thanks a lot for stepping forward on this. I am really sorry that I wasn't around to back you up, X-mas is time without internet (well, lets say mailing lists) for me.
No problem. I did have the time then. A happy new year, btw ;)
I think that this page is a very good idea, although it should be generated automatically, otherwise it will be very hard to maintain and constantly out of date.
For this to work out, we should agree on a convention for written documentation for externals.
Maybe a simple convention for the name of a project descripton would be sufficient for now. Something like SFDESCRIPTION or such, that every developer can put in his directories, that should be included as text for the projects page. I would write a script that runs over the cvs-tree, finds all SFDESCRIPTION's and builds the html.
Another possibility would be to make the project page editable, see for example this quick copy'n'paste wiki page:
http://footils.org/cgi-bin/cms/pydiddy/wiki/PureDataExternalRepository
Something like the reference patches that are already in place.
If we need to move the pure-data.sf.net site for that, this is not a problem at all. We can just redirect. Of course I think that the best thing would be to combine our efforts and integrate this into pure-data.org, or pddb, ...
The sourceforge page should only list the externals/abstraction etc that are in the CVS, IMO. One could extract the descriptions from pddb, but currently no info is stored there about which externals are in the CVS. But this could be added, I think.
Other than that, I think, to have a central, developer editable place as the canonical source for projects desciptions would be great. pddp comes closest, atm...
ciao
Frank Barknecht said this at Tue, 7 Jan 2003 18:27:29 +0100:
Maybe a simple convention for the name of a project descripton would be sufficient for now. Something like SFDESCRIPTION or such, that every developer can put in his directories, that should be included as text for the projects page. I would write a script that runs over the cvs-tree, finds all SFDESCRIPTION's and builds the html.
Would people consider a similar convention for packaging up externals? It would be nice to be pointed to the: - external - library - doc - expected doc search path (c.f. Gem) - abstractions ...in a consistent manner. As it is, installation seems just too inconsistent, even by hand.
adam
-
Adam Lindsay -
Frank Barknecht -
guenter geiger