I also support Steven's effort to unite everyone that was planning to run a
Cocoon application server.
I think that the cocoondev best practices and documentation should be
consulted for the upcoming cocoon.apache.org contracts.
It also makes most sense for the cocoondev.org people to move over to the
PMC.
Very importantly, we have to formalize the clear separation of the open
source project from any commercial interests.
I am sure Stefano, Carsten, Steven, Vadim and probably other people have
thought a lot about this and can write up a draft which we can start
discussing.
It is vital to keep Cocoon clean from influence of private interests not
driven by the project's success itself.
At the same time allowing individuals to take full material advantage of
their expert knowledge.
Ivelin
----- Original Message -----
From: "Steven Noels" <stevenn@outerthought.org>
To: <cocoon-dev@xml.apache.org>
Cc: <supporters@lists.cocoondev.org>
Sent: Wednesday, October 30, 2002 11:04 AM
Subject: Re: [important proposal] Cocoon as official Apache project
> Stefano Mazzocchi wrote:
>
> > 3) what does it mean for Cocoon?
> >
> > Being a project allows us to host several different incubation-stage
> > efforts underneath. Cocoblog, wyona, forrest, cocoon-related IDE
> > plugins could be possible additions. Of course, with the idea of
> > promoting them as top-level projects when they are successful from a
> > community perspective.
> >
> > Also, it means that we could have our own machine running the entire
> > cocoon.apache.org web site (that means: finally having Cocoon
> > serving its own pages!)
> >
> > Last but not least, it will give much more visibility to Cocoon since
> > it will be visible directly from www.apache.org
>
> Seems you hit the sweet spot pretty hard :-|
>
> OK. I won't be doing this all by myself. But I don't want to see
> something we have been preparing for such a long time willingly ignored
> by this proposal.
>
> So I would like to make a sub-proposal attached to this vote:
>
> The dream of cocoon.apache.org having its own hardware resources can be
> realized by working further on the foundations of http://cocoondev.org/.
> I'm ready to see the proposed cocoondev.org board being subsumed by the
> Cocoon PMC for that matter. Also, what we have set up as guidelines
> should be scrutinized and fleshed out further to bring in line with the
> new PMC's ideas. The main benefit of cocoondev.org is that it has been
> set up with sufficient compartimentization in mind, both on a security
> and classloading level. So all these cocoon-based apps can be developed
> and showcased independently from each other. And that the machine is
> there and available, of course.
>
> I'm all +1 for cocoon.apache.org being a top-level project, of course. I
> sent you a mail suggesting to move forward with this 5 days ago.
>
> But I would be very sad to see what we have been doing for cocoondev.org
> going lost in the turmoil. Especially on my 32nd birthday :-|
>
> All: if you were not aware of http://cocoondev.org/, please take a look.
> If you are interested and want to discuss further , please subscribe
> yourself using supporters-subscribe@lists.cocoondev.org
>
> But hopefully, this list might soon become something like
> infrastructure@cocoon.apache.org
>
> </Steven>
> --
> Steven Noels http://outerthought.org/
> Outerthought - Open Source, Java & XML Competence Support Center
> stevenn@outerthought.org stevenn@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: supporters-unsubscribe@lists.cocoondev.org
> For additional commands, e-mail: supporters-help@lists.cocoondev.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org