Ok, let me rephrase my questions: 1) is restructuring, or some other, review required for/after intended changes? Changing project name definitely requires restructuring review together with involvement of the IP team.
2) are implementations governed by ee4j free to use org.eclipse pkg namespace/maven groupid? Or must they follow some rules, like say org.eclipse.<projectName>?
Thanks, —lukas
22. 4. 2021 v 21:54, David Blevins <dblevins@xxxxxxxxxxxxx>:
I agree with Kevin, that I don't believe the PMC needs to approve changes like this for implementation projects.
Speaking with my PMC hat off, I'd encourage you to take the opportunity to give the project a proper name rather than just using the former spec name. Krazo, Soteria, Metro, Mojarra, etc are all great examples of good names. Eclipse Activation, Eclipse Mail, Eclipse JSONP, Eclipse JAXB are anti-patterns in my opinion.
Other implementations of JSONP have names like Joy and Apache Johnzon. A similar trade name would be great.
As mentioned, that's with my PMC hat off and with no implied authority. Just me speaking as a member of the community :) You can take it or leave it.
-David
Thanks, Lukas. I
don't see an issue with your proposed changes. And, I don't believe
the PMC needs to "approve" them either (but maybe Ivar has more
experience with this aspect).
--------------------------------------------------- Kevin Sutter STSM, Jakarta EE and MicroProfile architect @ IBM e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutter
Part-time schedule: Tue, Wed, Thu (off on Mon and Fri)
From:
Lukas
Jungmann <lukas.jungmann@xxxxxxxxxx> To:
ee4j-pmc
PMC List <ee4j-pmc@xxxxxxxxxxx> Date:
04/22/2021
11:53 Subject:
[EXTERNAL]
[ee4j-pmc] Moving the jsonp implementation project to a different namespace/groupId Sent
by: "ee4j-pmc"
<ee4j-pmc-bounces@xxxxxxxxxxx>
Hi PMC,
We would like to change package namespace and project groupId
for the Jakarta JSON Processing implementation project. Our intent is to:
* change implementation package name from org.glassfish.json to org.eclipse.jsonp * change project's groupId from org.glassfish to org.eclipse.jsonp
Motivation: allow co-existence of old javax based and new jakarta based
implementations within the same instance of JVM.
The PR is: https://github.com/eclipse-ee4j/jsonp/pull/283
Questions: 1) Do we need any sort of review for this change to be OK? 2) Are we allowed to use "org.eclipse.jsonp" maven groupId and
package namespace?
thanks, --lukas _______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________ee4j-pmc mailing listee4j-pmc@xxxxxxxxxxxTo unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/ee4j-pmc__;!!GqivPVa7Brio!PoZDbFZHAD-pzqAs8CPxG6p_-AH2m1MUnZTvxjhg8VWzzBICXcGTjS9-guv7DFGHt6Q$
|