David Crossley wrote: > Ovidiu Predescu wrote: > > Ivelin Ivanov wrote: > > > > > How about a web ring? > > > > Yes, a Web ring is definitely a good idea. > > > > > I am about to host a coon apps site myself. > > > Since we all might be running on different versions and with different ideas > > > about our applications, maybe a loosely connected structure is better. > > > > > > Send me your URLs, I'll link from my web site. > > > You can link to mine too: > > > cocoonhive.org > > > > Actually we should have something better than this, so that everybody in the > > Web ring is able to see the participants without the link management hassle. > > We could just modify the existing xdocs/link/hosting.xml > We certainly do not want to manage two documents.
Sorry. On second thought, we actually do need two separate docs. "Cocoon Hosting" the existing one, is for organisations offering application infrastructure services to run your own Cocoon server. The Web Ring idea is specifically for fostering a Cocoon Apps developer community. Am i right? The "put an xml doc in CVS" idea is still relevant. --David > The problem with this solution is that Cocoon website is > still irregularly updated manually, until Forrest. > > > We can put the sites participating in the Web ring in an XML file on a > > central site. All the participants can then fetch this file every once in a > > while, and generate the HTML version of it. Very similar with the RSS stuff > > in Weblogs. > > Great idea. Is it sufficient to just get the file from CVSview? > GET > >http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-cocoon2/src/documentation/xdocs/link/hosting.xml?rev=HEAD&content-type=text/xml > There is probably a better solution down the track, with > Forrest generating it for them. > > Do we need a table in the hosting.xml that summarises them? > --David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
