So if a new working group is to be established, it would just come through as a new project request?
Overall, I agree with Steve's assessment.
But... I don't think it's up to the EE4J PMC to propose new
projects. Anybody can do an Eclipse project proposal. When
a proposal is submitted, a top-level project is selected. The PMC
for that project will then be notified and asked to review it. So,
if somebody wants to create a new EE4J sub-project, they could submit a
proposal to the EE4J PMC, and it would be evaluated. If the PMC approves
it then it would be submitted to the Eclipse team for provisioning of the
new project.
For now, all of the "Java EE"
projects are being proposed by the EE4J PMC (specifically, Dmitry is doing
most of that leg work, thank you!). But, after Jakarta EE gets established,
then I would not expect that responsibility to fall on the PMC shoulders.
We would become a bottleneck if that were to happen. We need
more participation from the community and new project proposals would be
part of that activity.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
"Steve Millidge
(Payara)" <steve.millidge@xxxxxxxxxxx>
To:
EE4J community discussions
<ee4j-community@xxxxxxxxxxx>
Date:
03/01/2018 12:37 PM
Subject:
Re: [ee4j-community]
Charter Feedback - Establishing new projects
Sent by:
ee4j-community-bounces@xxxxxxxxxxx
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
Sent: 01 March 2018 18:18
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: [ee4j-community] Charter Feedback - Establishing new projects
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_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_ee4j-2Dcommunity&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=R9dtOS3afYnRUmu_zogmh0VnVYl2tse_V7QBUA9yr_4&m=JtnfBFS_lath3Y7RG4LgVts_kwHMGTfkD9hCMz0OFfM&s=WgQAA2QqkHmI1Hq1BnBI4CU-goKAxjM4HOhxnjGdjOg&e=
_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community