cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <rgard...@wkwyw.net>
Subject Re: Cocoon apps Web site hosting
Date Mon, 12 Aug 2002 08:05:07 GMT
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. 
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.

> 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.

> 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: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message