| Re: [jakarta.ee-spec.committee] Jakarta EE repositories proposal for specification and implementation projects |
For everyone's benefit and so it's clear I am largely in support of Ivar's proposal, not trying to introduce an alternative proposal, I've compiled a list of all our Specification Projects and every git repository they own: - https://github.com/jakarta-ee/repos/tree/61468536b0d685afffcdc65057a7e1c76dd94ac7 Now we remove all implementations and follow Ivar's recommendation that examples, demos, tutorials also not be included. Note, I've left `messaging-proposals` as noted in the initial email. - https://github.com/jakarta-ee/repos/commit/c8f16c04ffab998d06dba6306eee676ee0b0a632 We enforce the rule specification project owed repos must live in github.com/jakartaee: - https://github.com/jakarta-ee/repos/commit/d040709bc99781603d785aab56469bc352c57a3d We follow the recommendation that it is best practice for repo names to begin with the shortname of the spec: - https://github.com/jakarta-ee/repos/commit/da0e6f7c7a9fd49f567d17a15ffe0f3c7092f614 That gives us this final result: - https://github.com/jakarta-ee/repos Following the rule that all repositories owned by a Jakarta EE Specification project must live in github.com/jakartaee, that leads to these repositories being orphaned and in need of a new home. Here is each and potential new homes: - https://github.com/jakarta-ee/repos/blob/main/orphaned.adoc -- David Blevins http://twitter.com/dblevins http://www.tomitribe.com 310-633-3852