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.
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.
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.
|
