Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Charter Feedback - Establishing new projects

Except that individual parts under the Jakarta/EE4J umbrella will not have their own working groups, the WG itself is closest to the Java EE Umbrella EG in the JCP.

@Wayne, of course there are other TLPs, but unless there is a specific matching one the new projects get created under Technology, see Microprofile.

Werner 




On Fri, Mar 2, 2018 at 5:02 PM, <ee4j-community-request@xxxxxxxxxxx> wrote:
Send ee4j-community mailing list submissions to
        ee4j-community@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        https://dev.eclipse.org/mailman/listinfo/ee4j-community
or, via email, send a message with subject or body 'help' to
        ee4j-community-request@eclipse.org

You can reach the person managing the list at
        ee4j-community-owner@eclipse.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ee4j-community digest..."


Today's Topics:

   1. Re: Charter Feedback - Establishing new projects (Wayne Beaton)
   2. Re: Charter Feedback - Establishing new projects
      (Mike Milinkovich)


----------------------------------------------------------------------

Message: 1
Date: Fri, 2 Mar 2018 10:12:29 -0500
From: Wayne Beaton <wayne.beaton@eclipse-foundation.org>
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Charter Feedback - Establishing new
        projects
Message-ID:
        <CALXWXwfWgsyvy3FiKdTBVh8GNdOqLKzdLQ7gXDjb6bg0ppxY2Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

This is not correct:

Eclipse projects get created in "Technology" and if either there or under
> another TLP (e.g. Runtime in case of Jetty, etc.) a project is found to
> have a different scope, it is usually not a problem to relocate them to
> EE4J if that PMC agrees it is a good match.
>

Eclipse open source projects are created directly under various Top-level
Projects. There is no extra step of "starting in Technology".

Wayne


On Fri, Mar 2, 2018 at 7:00 AM, Werner Keil <werner.keil@xxxxxxxxx> wrote:


--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/20180302/c06755bf/attachment.html>

------------------------------

Message: 2
Date: Fri, 2 Mar 2018 11:02:14 -0500
From: Mike Milinkovich <mike.milinkovich@eclipse-foundation.org>
To: ee4j-community@xxxxxxxxxxx
Subject: Re: [ee4j-community] Charter Feedback - Establishing new
        projects
Message-ID:
        <76522a7a-b089-380f-4b32-55b4e0ecc30b@eclipse-foundation.org>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

John,

I am not sure if it is terminology or what, but you do seem to be
confused about some things. And if you're confused, I am sure that
others are as well.

The EE.next working group (which will be renamed to use the Jakarta
name) is an umbrella organizations that will host a specification
process. Think of it as the replacement for the JCP for Jarkarta EE
going forward. I *think*, but obviously do not know for sure, that you
are thinking that the term "working group" is analogous to what we
currently call a JSR expert group. There will be many of those in the
future, but we don't even have a name for what those will be called yet.
But roughly you can think of the idea that there is one working group
that supports many expert groups.

You are correct that we are overdue in posting a revised draft of the
working group charter. We will try to get that done today.

HTH

On 2018-03-02 6:07 AM, John D. Ament wrote:
> I'm not sure what you're implying there.? Reading the FAQ doesn't give
> me any inclination that there's a single working group for the entire
> Jakarta EE vs a working group per related technology.? In addition,
> considering that the link charter is not to up to date with what has
> been shared via email, I do have concerns over its completeness.? It
> was also heavily implied in other conversations (I've been involved
> in) that there would be multiple working groups, so it seems odd to
> now hear there's a single working group.
>
> John
>
> On Thu, Mar 1, 2018 at 4:47 PM Steve Millidge (Payara)
> <steve.millidge@xxxxxxxxxxx> wrote:
>
>     BTW I would recommend reading the Proposed Working Group FAQ it
>     clarified things a lot in my mind.
>
>     https://www.eclipse.org/org/workinggroups/eclipse_ee_next_faq.php
>
>     *From:*ee4j-community-bounces@eclipse.org
>     <mailto:ee4j-community-bounces@xxxxxxxxxxx>
>     <ee4j-community-bounces@eclipse.org
>     <mailto:ee4j-community-bounces@xxxxxxxxxxx>> *On Behalf Of *John
>     D. Ament
>     *Sent:* 01 March 2018 21:15
>
>
>     *To:* EE4J community discussions <ee4j-community@xxxxxxxxxxx
>     <mailto:ee4j-community@eclipse.org>>
>
>     *Subject:* Re: [ee4j-community] Charter Feedback - Establishing
>     new projects
>
>     So if a new working group is to be established, it would just come
>     through as a new project request?
>
>     On Thu, Mar 1, 2018 at 2:58 PM Kevin Sutter <sutter@xxxxxxxxxx
>     <mailto:sutter@xxxxxxxxxx>> wrote:
>
>         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 <mailto:sutter@xxxxxxxxxx> ? ?
>         Twitter: ?@kwsutter
>         phone: tl-553-3620 (office), 507-253-3620
>         <tel:%28507%29%20253-3620> (office)
>         LinkedIn: https://www.linkedin.com/in/kevinwsutter
>
>
>
>         From: "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx
>         <mailto:steve.millidge@payara.fish>>
>         To: EE4J community discussions <ee4j-community@xxxxxxxxxxx
>         <mailto:ee4j-community@eclipse.org>>
>         Date: 03/01/2018 12:37 PM
>         Subject: Re: [ee4j-community] Charter Feedback - Establishing
>         new projects
>         Sent by: ee4j-community-bounces@eclipse.org
>         <mailto: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@eclipse.org
>         <mailto:ee4j-community-bounces@xxxxxxxxxxx>
>         <ee4j-community-bounces@eclipse.org
>         <mailto:ee4j-community-bounces@xxxxxxxxxxx>> *On Behalf Of
>         *John D. Ament*
>         Sent:* 01 March 2018 18:18*
>         To:* EE4J community discussions <ee4j-community@xxxxxxxxxxx
>         <mailto:ee4j-community@eclipse.org>>*
>         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
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/20180302/9a22e609/attachment.html>

------------------------------

_______________________________________________
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


End of ee4j-community Digest, Vol 7, Issue 16
*********************************************


Back to the top