| Re: [jakarta.ee-spec.committee] Jakarta EE repositories proposal for specification and implementation projects |
|
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
LinkedIn: https://www.linkedin.com/in/emilyfhjiang/
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 http://twitter.com/dblevins http://www.tomitribe.com _______________________________________________ jakarta.ee-spec.committee mailing list jakarta.ee-spec.committee@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee |