So as we ask each other to approve our dependencies, I think the proposer should state:
* what is the license
* that the proposer did due diligence in looking for another CQ — and if found another version then why it can’t be piggy-backed.
If you do that Jim, and assuming there are no GPL licenses, I’ll +1 the CQs.
~ David
On Thu, Nov 12, 2015 at 12:02 PM Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
We need PMC members to approve based on technical merit. It all
tends to depend on the context. If I know, for example, that a
project is working with other projects and is asking for a different
version of a library, I might challenge them to piggyback instead of
introducing a new version. Generally with technical issues in mind,
but sometimes to reduce the impact on the IP team.
If you notice that there are particular IP concerns (e.g. license is
incompatible), you can push back. I do this sometimes, but only if
I'm sure that there is a problem (e.g. a GPL library).
As a general rule, try to avoid doing the IP Team's job for them.
They're much better at than we are.
I wonder if there are some guidelines on
approving/disapproving dependencies. For example, could any
dependency that has a license that is in some approved list
(that probably wouldn’t include GPL but may or may not include
LGPL) be approved? This question is perhaps to Andrea or others
that oversee such things. Without guidelines, I'm tempted to
just approve reflexively simply because I like Jim :-)
On Sat, Nov 7, 2015 at 2:50 PM Jim Hughes <jnh5y@xxxxxxxx>
wrote:
The first is a piggyback CQ, and the second is clearly
useful to GeoGig. I'm saying +1 to both.
I've hit the button on IPZilla to accept both.
Cheers,
Jim
On 11/07/2015 02:37 PM, Tyler Battle wrote:
Geogig also has a few waiting for PMC.
On 7 November 2015 at 07:25,
Jim Hughes <jnh5y@xxxxxxxx>
wrote:
Jody,
Sadly no. I think everyone else was on travel as
well.
The IP team usually likes to see a discussion on
the email list for CQs. Worst case, lack of
discussion/dissent can suffice;) That said
someone on the PMC still has to push the +1 button
on each. (I believe I'm not supposed to do my
own.)
Thanks for asking,
Jim
On 11/06/2015 05:19 PM, Jody Garnett
wrote:
Any update on these Jim?
Afraid I have been on the road ...
--
Jody Garnett
On 28 October
2015 at 20:27, Jim Hughes <jnh5y@xxxxxxxx>
wrote:
Hi PMC,
Here's a list of CQs for transitive
dependencies with a brief description:
Curator: curator-recipes,
curator-framework, curator-client are
used in making connecting to
Zookeepers easier
Apache Camel is used in our
geomesa-stream module to process
streams of simplefeatures; fastinfoset
and istack-commons-runtime are
transitive dependencies of jaxb-impl,
which is a transitive dependency of
Apache Camel.