| Re: [ee4j-community] Charter Feedback - Establishing new projects |
|
Personal view here but my understanding is that it is for the PMC of the EE4J top level project to decide on the creation of a new sub-project. Again personal view my suggestion is get a bunch of people interested start prototyping some code, drafting an api etc. Possibly in a sandbox repo within EE4J. If it gets a level of traction ask
the PMC for a formal sub-project. When the new api has reached a level of maturity that it has an agreed first cut API, TCK and Specs then it would be considered for inclusion in the future overall Jakarta EE platform by the Working
Group. Personally I don’t see the WG getting involved until a level of maturity is reached.
Others may have a different view as this is still all being worked out. Steve From: ee4j-community-bounces@xxxxxxxxxxx <ee4j-community-bounces@xxxxxxxxxxx>
On Behalf Of John D. Ament While reviewing the charter (btw is there a public link somewhere to the latest? I only see it via email) I had one question pop up. How do new projects get established for the working groups? Right now we have a slew of projects coming in from the initial donation, at some point we're going to want to dive into newer technologies. Some features may make sense to go into existing projects, but others may make more sense to start
to become their own project; with their own APIs, specs and TCKs. Which committees are responsible for reviewing and establishing these new projects, as well as determining the lines between two projects? John |