[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] [External] : Re: Jakarta EE repositories proposal for specification and implementation projects
|
David,
Mail and Activation split their implementations out into the Eclipse
Angus project. What exception are you referring to below?
-- Ed
On 4/5/2022 3:01 PM, David Blevins wrote:
We really only have two exceptions, mail and activation. I think we just agree these are exceptions and disallow adding more.
-David
On Apr 4, 2022, at 2:14 PM, Emily Jiang <EMIJIANG@xxxxxxxxxx> wrote:
Hi David,
I have been thinking about this. There are cons/pros with placing implementation either on eclipse-ee4j (other supporting materials) or jakartaee (spec focused).
For jakartaee, it should store all specification related api/tcks. Since implementations might sometimes live in various places, I think it is also confusing to put impls inside jakartaee. How about creating an org jakartaee-impl to store the implementations owned by Eclipse Foundation? In this way, it is quite clear which repos are spec and which ones are spec impls? Thoughts?
Thanks
Emily
================
Emily Jiang
Java Champion
STSM, Jakarta and MicroProfile Architect @IBM
Liberty Cloud Native Architect & Advocate
E-mail: emijiang@xxxxxxxxxx
Twitter: @emilyfhjiang
LinkedIn: https://urldefense.com/v3/__https://www.linkedin.com/in/emilyfhjiang/__;!!ACWV5N9M2RV99hQ!Zzd0NGG8k3eF5KYC1zCimq5ef12sIVKWYcUBKQ3uQ6H2zua02ZrRGX4G8E5ohAc$
IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
From: jakarta.ee-spec.committee <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> on behalf of David Blevins <dblevins@xxxxxxxxxxxxx>
Sent: 04 April 2022 16:40
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [jakarta.ee-spec.committee] Jakarta EE repositories proposal for specification and implementation projects
This Message Is From an External Sender
This message came from outside your organization.
Thanks, Emily.
What are your thoughts about the guiding principle that everything a Specification Project owns lives in github.com/jakartaee and not in github.com/eclipse-ee4j?
--
David Blevins
https://urldefense.com/v3/__http://twitter.com/dblevins__;!!ACWV5N9M2RV99hQ!Zzd0NGG8k3eF5KYC1zCimq5ef12sIVKWYcUBKQ3uQ6H2zua02ZrRGX4Gw9HqPNE$
https://urldefense.com/v3/__http://www.tomitribe.com__;!!ACWV5N9M2RV99hQ!Zzd0NGG8k3eF5KYC1zCimq5ef12sIVKWYcUBKQ3uQ6H2zua02ZrRGX4GEwJfbCs$
310-633-3852
On Apr 4, 2022, at 3:52 AM, Emily Jiang <EMIJIANG@xxxxxxxxxx> wrote:
Hi David,
I'd really prefer to not have to point people at github.com/eclipse-ee4j as how to get involved with a specification project or eclipse-ee4j (which contains my competition) as the best onramp for getting involved in Specification Projects.
Are we ok with the goal that any repos, including proposals, that would owned by a spec project would be in github.com/jakartaee and disconnected from github.com/eclipse-ee4j?
I think it makes sense to create a `sandbox` repo under github.com/jakartaee for any new specification proposals. With one sandbox repo, it can hold any ideas and it does not conflict with the proposal term because the idea can be anything related to the specifications. Some ideas in the sandbox might end up with a specification proposal and then accepted as a specification. Similarly, a repo sandbox can also be created for eclipse-ee4j to hold any demo related ideas.
Thanks
Emily
================
Emily Jiang
Java Champion
STSM, Jakarta and MicroProfile Architect @IBM
Liberty Cloud Native Architect & Advocate
E-mail: emijiang@xxxxxxxxxx
Twitter: @emilyfhjiang
LinkedIn: https://urldefense.com/v3/__https://www.linkedin.com/in/emilyfhjiang/__;!!ACWV5N9M2RV99hQ!Zzd0NGG8k3eF5KYC1zCimq5ef12sIVKWYcUBKQ3uQ6H2zua02ZrRGX4G8E5ohAc$
IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
From: jakarta.ee-spec.committee <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> on behalf of David Blevins <dblevins@xxxxxxxxxxxxx>
Sent: 30 March 2022 23:59
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Subject: [EXTERNAL] [jakarta.ee-spec.committee] Jakarta EE repositories proposal for specification and implementation projects
First, let me apologize as I didn't notice this in the agenda. I hadn't realized that Google docs remembers your position and when I was clicking in the agenda doc it was showing me January -- before I flew to Ecuador.
I like the proposal. The introduction of the jakartaee-wg repository to host administrative and working group things is good. I wanted to see if we're on the same page in a key detail and ask for one change.
One of the motivations for the split was that anything owned by a Specification Project would live in github.com/jakartaee and there would be no repositories owned by a specification project in github.com/eclipse-ee4j.
The one ask for change is we allow Specification Projects can have proposal repos -- using the rule above, they'd be in github.com/jakartaee. We had one for Java EE Security back in the day and we have one in Jakarta Messaging. I frequently promoted those repos when doing talks on how to get involved with the Specification Project.
I'd really prefer to not have to point people at github.com/eclipse-ee4j as how to get involved with a specification project or eclipse-ee4j (which contains my competition) as the best onramp for getting involved in Specification Projects.
Are we ok with the goal that any repos, including proposals, that would owned by a spec project would be in github.com/jakartaee and disconnected from github.com/eclipse-ee4j?
Minus the proposals tweak, the current proposal looks in line, but I just wanted to confirm.
--
David Blevins
https://urldefense.com/v3/__http://twitter.com/dblevins__;!!ACWV5N9M2RV99hQ!Zzd0NGG8k3eF5KYC1zCimq5ef12sIVKWYcUBKQ3uQ6H2zua02ZrRGX4Gw9HqPNE$
https://urldefense.com/v3/__http://www.tomitribe.com__;!!ACWV5N9M2RV99hQ!Zzd0NGG8k3eF5KYC1zCimq5ef12sIVKWYcUBKQ3uQ6H2zua02ZrRGX4GEwJfbCs$
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee__;!!ACWV5N9M2RV99hQ!Zzd0NGG8k3eF5KYC1zCimq5ef12sIVKWYcUBKQ3uQ6H2zua02ZrRGX4Gb0UKDtI$
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee__;!!ACWV5N9M2RV99hQ!Zzd0NGG8k3eF5KYC1zCimq5ef12sIVKWYcUBKQ3uQ6H2zua02ZrRGX4Gb0UKDtI$
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee__;!!ACWV5N9M2RV99hQ!Zzd0NGG8k3eF5KYC1zCimq5ef12sIVKWYcUBKQ3uQ6H2zua02ZrRGX4Gb0UKDtI$
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee__;!!ACWV5N9M2RV99hQ!Zzd0NGG8k3eF5KYC1zCimq5ef12sIVKWYcUBKQ3uQ6H2zua02ZrRGX4Gb0UKDtI$
