It looks like this has slipped through the cracks.
PMC members, in order to have something designated as a "Test and
Build" Dependency, we need to conduct an "open and transparent"
discussion. This gives the community an opportunity to react and
for us to take a moment for sober reflection to make sure that this
(effective) exception to the IP Due Diligence process is
reasonable.
This manifests minimally as a brief discussion (see below) with +1
responses from other members of the PMC.
So... with that in mind, can I get a couple of +1s from PMC
members?
Thanks,
Wayne
Greetings PMC.
The GeoMesa project has a need for a "Test and Build" dependency on
ScalaCheck [0] and its dependencies. Specifically,
scalacheck 1.11.4 (variation of the Scala license AFAICT)
libvirt 0.5.1 (GPL)
maven-ant-tasks 2.0.10 (ALv2)
sbt-launch 0.13.5 (BSD)
The libraries will not be distributed by the project; they are to
be obtained from external sources and used only as part of the
build process. I believe that they meet the requirements for
designation as "Test and Build Dependencies" [1].
PMC members, please signal your agreement by responding to this
note with a +1
Thanks,
Wayne
[0] https://dev.eclipse.org/ipzilla/show_bug.cgi?id=8403
[1]
https://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Dependencies
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://locationtech.org/mailman/listinfo/technology-pmc
