Ted,

> Before proposing this release to the incubator committee, we 
> should have the project otherwise ready to exit. 

sounds good. Since we notice a *growing* community I think
time is right to leave incubator. Btw. will MyFaces
be a TLP? 

> We've met the technical criteria and just need to finsh the 
> website.  Ideally, it should contain all the elements of the 
> MyFaces.org site. Specifically, we need 

Ok, we have to *convert* the documentation etc into
forrest xml stuff, that should be added to
http://incubator.apache.org/myfaces/

> * Community Page - Add link to JIRA on Community page.
> 
> * Downloads - Have we been able to setup the nightly builds yet? 
> 
> * Status page - An ancient Apache tradition is to maintain a 
> "project status file". This file should list the Committers, 
> Recent Action Items (like this release vote), and any project 
> resources not listed elsewhere. Personally, I'd just add it 
> to the website.

Where did you add it? I didn't saw it...

Btw. Committers are here allready:
http://incubator.apache.org/myfaces/community/contributors.html


> * Decision making guidelines - I'd suggest setting up a 
> bylaws page that outline the decision making process MyFaces 
> will follow. 
> 
> This is not part of the standard Incubation process, but I 
> would suggest adding a set of bylaws to the site. You will 
> have to do this eventually, so why not do it now. The ones I 
> setup for iBATIS, which are typical to ASF projects, are 
> here: [http://incubator.apache.org/ibatis/site/bylaws.html ]. 

that looks very *generic* but why the mention of Struts inside
of ibatis?

<snip>
Subprojects

Subprojects are the Project's unit of release. Each subproject should
represent an implementation of the Struts core or a related component.
</snip>

I guess this is an accident :-)
If it is *generic*, then we could also *copy* it to our website.

> I need to lookup some historical dates for the Incubator 
> status page, but we seem otherwise good to go. 

Thanks for help

Matthias

> -Ted.
> 
> 

Reply via email to