[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] GitHub repository naming conventions?
|
I think its best to separate API, Spec, and TCK. Different people will be working on these. For example, Joe from ABC corp might be working on the spec, but its Jill from ABC Corp who is doing the API adjustments/creation and Wanda from ABC Corp doing the TCK. We don't want JIll or Wanda on the Spec project. that's Joe's job.
That is my understanding
as well, Bill. I thought the long term goal was to have the TCKs
in separate projects, but we were not going to enforce that at this time.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
Bill
Shannon <bill.shannon@xxxxxxxxxx>
To:
Scott
Stark <sstark@xxxxxxxxxx>
Cc:
Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:
06/19/2019
12:11 PM
Subject:
[EXTERNAL]
Re: [jakarta.ee-spec.committee] GitHub repository naming
conventions?
Sent
by: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx
My understanding is that that would require
them to be separate Eclipse projects, which is not the current plan.
Yes, if someone wanted to be a Committer on a TCK without their IP being
contributed to the corresponding spec, we would need them to be separate
projects.
Scott Stark wrote on 6/19/19 9:28 AM:
That should not be necessary in terms
of IP capture. The TCK is an implementation of a testing framework for
the spec, not a specification document that expands the IP commitments.
We should be able to have committers to a TCK that are not committers to
a spec.
On Jun 19, 2019, at 8:59 AM, Bill Shannon
<bill.shannon@xxxxxxxxxx>
wrote:
Since they're all part of the same Eclipse
project, they all share the same set of committers.
Scott Stark wrote on 6/19/19 7:33 AM:
We have found that a convenient organization
in our projects as it best matches the committer issues. The TCK should
have a wider committer list than the specs/apis.
On Jun 18, 2019, at 10:58 PM, Bill Shannon
<bill.shannon@xxxxxxxxxx>
wrote:
Why do you think they should all be in
the same repo?
Clearly the spec, API, and TCK will all be part of the same project,
which controls who has permission to do what. Why would two of them
be in one repo and one of them in another repo?
Scott Stark wrote on 6/18/19 9:20 PM:
I do believe the spec and api should
be in the same repo. The TCKs should be in a separate repo.
github.com/eclipse-ee4j/wombat-spec/{spec,
api}
github.com/eclipse-ee4j/wombat-tck
_______________________________________________
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
_______________________________________________
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
--
