Hi David,
The Jakarta EE specification committee dictates the root namespace for
apis and tck tests (`jakarta.*` and `ee.jakarta`). The specification
projects can request approval to use a name under that namespace. Is a
+1 vote saying that we understand this is the case?
From my understanding, the Jakarta EE specification did not dictate the root namespace for apis and tck tests. For TCK tests, it suggested the tck projects should use ee.jarkarta but some projects did not accept it. The spec committee provides guidance but not forces the spec projects. The projects can choose a namespace as long as it does not infringe with another eclipse project according to the
Eclipse Foundation Development Process.
The option to use ee.jakarta only applies to the TCKs and was a specification committee vote to allow that flexibility. Specifically, the specification committee disallowed use jakarta.* for TCK tests which forced some projects to repackage the new TCK tests they were creating.
Both of those actions are evidence the specification committee has complete control over the namespaces. Other examples of the Specification Committee making these sort of decisions include the maven packaging and Github repository naming conventions.
Any outcome of a vote here would simply be input to the Specification Committee who would make the final decision.
Similarly, as our own Working Group we could make these decisions at the MP Steering Committee level and no project within MicroProfile WG could override them.
-David
