> Ovidiu Predescu wrote: > > EUR CVS repository. Some developers might already have their own CVS > > repositories, perhaps at SF, but others may choose to have it > hosted here. > > I don't think the actual localtion of the CVS is particularly important > as long as there is a central place to find out about the projects. +1 most of this (mail lists et al.) can be organized at various places the real difference would be in some kind of cocoon in ASP setup where the different projects can be ran in their own cocoon environment: showcase running apps before people get it from scratchpad of examples would be the differentiator (and the hardest work: different cocoon versions possibly different tomcat combinations...)
that and the central website that talks about them. > However, a single domain name for the projects presents a feeling of > coherence to the community as a whole. > > > EUR mailing lists and Web archives for them. Perhaps a better > approach is to > > have common mailing lists for all the applications (separated > for users and > > developer), so we can maintain a closer community. Should we > reuse instead > > Apache's mailing lists? > > The more we can stay within the Apache domain the better. The Apache > name carries a good deal of respect in Industry. > > > EUR Web site presence. I think we need to have a combination of > static pages > > with dynamic ones, to show off examples and so on. > > It certainly needs to be Cocoon hosted! > > > For the Web site, I think > > we need to maintain a common look and feel, just like Mozilla > has for their > > applications. > > Absolutely. Forrest is moving along quite nicely. I am using it across a > couple of sites at the moment. It is still early in development and not > really ready for the "big time" but I'm sure the project would benifit > from more deveopers contributing ;-) > > > How do people publish their content? > > Forrest is getting closer to making the automatic updating of content > from CVS repositories. > forrestbot is running since euh.. week or 2 it's probably not the last incarnation of the thing, so there could be changes in the future, but it's running very stable over at our server to produce http://outerthought.net/forrest (actually also runs for http://outerthought.net with different content and skin) > > Do they have access to a > > staging area to test their site, and then publish it? > > I would say that the "staging" area is the developers own > responsability. Once it is in CVS it is considered publishable. Would > this mean maintaining a permanent branch for development work, keeping > the main branch for approved bug fixes only? Or possibly the other way > around, that is have a "release" branch for Forrest to publish from and > leave HEAD as the development code? > > > It would be great if > > we can get some thoughts on what we need here. > > I think the whole question of how and when things are published need to > be handled by Forrest. Perhaps people more active than I can comment on > how this would work. > see http://outerthought.net/forrest/forrest-contract.html I can easily give a hand on setting up the forrestbot conf for different projects > > The last bullet seems to be the biggest item. It would be great > if we can > > come up with some more requirements on what it takes to have > Web presence > > for these applications, and then sketch out an implementation > in Cocoon for > > it. > > I would like to know how many people actually have applications that can > be put into this environment. I for one am making noise about this but > don;t __have__ anything to put in there yet. I intend to have something > but that is __very__ different as you all know ;-) So lets also start a > list of the real, working (even if only alpha) apps we have: > > * BringMeThis - > http://www.superlinksoftware.com/cocoon/samples/bringmethis/ - Andrew C. > Oliver > > Ross > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
