Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Splitting Github orgs: eclipse-ee4jand eclipse-jesp

I agree that Splitting would confuse more than it helps.

https://github.com/eclipse has nearly 600 repositories even across TLPs and Working Groups like IoT and others. Among them 25 different Microprofile repositories alone, although that is just a single Eclipse Technology project.

 

So the EE4J TLP does not seem to need multiple GitHub organizations. If there are smart enough conventions and regular expressions for those names like “-tck” for every TCK project, I would say that is good enough to tell them apart, if 600 others can.

 

Werner

 

Sent from Mail for Windows 10

 

From: Bill Shannon
Sent: Wednesday, May 22, 2019 21:23
To: Jakarta specification committee; David Blevins
Subject: Re: [jakarta.ee-spec.committee] Splitting Github orgs: eclipse-ee4jand eclipse-jesp

 

-1

David Blevins wrote on 5/22/19 11:47 AM:

We clearly do not want to discuss splitting the EE4J PMC, fine.  But can we at the minimum split the org in github so we and the world have a chance at getting things straight?

 

I fear even we are confused.

 

I propose we sort everything into two orgs:

 

 - /eclipse-jesp/    new org for spec projects

 - /eclipse-ee4j/    implementations and misc junk

 

We have 107 repos currently.  Here's how we could split them as part of the restructuring review.

 

These 37 repos would move into the new 'eclipse-jesp' org and eventually be renamed:

 

 

 

These 70 repos would stay in the new 'eclipse-ee4j' org:

 

 

 



_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee

 

 

Back to the top