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.
HTH,
Wayne
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 :-)
--
Lucene/Solr Search Committer, Consultant, Developer,
Author, Speaker
_______________________________________________
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
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
|