Steven Noels wrote, On 10/07/2003 9.23:
On 10/07/2003 8:59 Paul Hammant wrote:
Nicola,
Nope.
@see http://cocoon.apache.org/lenya/community/mailing-lists.html
No Incubator logo, no @incubator.apache.org mailing lists, no
reference to the incubation status.
I stand corrected.
Isn't http://coc
On 10/07/2003 8:59 Paul Hammant wrote:
Nicola,
Nope.
@see http://cocoon.apache.org/lenya/community/mailing-lists.html
No Incubator logo, no @incubator.apache.org mailing lists, no
reference to the incubation status.
I stand corrected.
Isn't http://cocoon.apache.org/lenya/";>Apache Lenya is a
Nicola,
...
No change necessary.
...
As is happening presently.
Nope.
@see http://cocoon.apache.org/lenya/community/mailing-lists.html
No Incubator logo, no @incubator.apache.org mailing lists, no
reference to the incubation status.
I stand corrected.
> No need for vote?
These are sparse
Paul Hammant wrote, On 09/07/2003 8.38:
Nicola,
As I told Steven some mails back, I understand the point. Hence I agree
with the incubator-projectname CVS module name and separate mailing
list(s) if the project is big enough (as I gather this is).
Here is a rewrite of those points:
...
No ch
Nicola,
> As I told Steven some mails back, I understand the point. Hence I agree
> with the incubator-projectname CVS module name and separate mailing
> list(s) if the project is big enough (as I gather this is).
>
> Here is a rewrite of those points:
>
> ...
>
> 4. Making the incubating pro
Paul Hammant wrote, On 08/07/2003 17.44:
Nicola,
What is the problem you are trying to solve here?
There have been discussions on the PMC lists; mainly the problem is
about having a project look like and act like a normal Apache project,
while in fact it's not. It's *becoming* an Apache Proje
> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 08, 2003 4:39 PM
>> Also, I think our charter mentions Forrest for docs specifically?
>
> Nope. If it does, it shouldn't.
No, only for the incubator docs itself.
Sander
Nicola,
> > What is the problem you are trying to solve here?
>
> There have been discussions on the PMC lists; mainly the problem is
> about having a project look like and act like a normal Apache project,
> while in fact it's not. It's *becoming* an Apache Project, but it might
> as well fa
Paul Hammant wrote, On 08/07/2003 16.17:
Nicola,
Looking at how Lenya is now incubating, here are some notes, that aim to
resolve some problems that have arised in incubation.
Lenya is marked (at least in CVS copy opf xdocs) as being affiliated to Incubator.
It's code is in
Cocoon CVS.
1,2,3,4,
Nicola,
> Looking at how Lenya is now incubating, here are some notes, that aim to
> resolve some problems that have arised in incubation.
Lenya is marked (at least in CVS copy opf xdocs) as being affiliated to Incubator.
It's code is in
Cocoon CVS.
> 1,2,3,4,5
What is the problem you are tr
Michael Wechner wrote:
2. What about having the incubated project send the incubator PMC
monthly status reports of what has happened, and more important, of
the things done in the incubation process?
I think this is a good idea, because it helps the incubated project to
refocus on its status.
Nicola Ken Barozzi wrote:
Looking at how Lenya is now incubating, here are some notes, that aim to
resolve some problems that have arised in incubation.
1. Appointing someone from this PMC to look over a project is a good
idea. If I weren't on that list (via gmane in case anyone checks ;-)
this
12 matches
Mail list logo
