|Re: [eclipse.org-architecture-council] Improving license check for dependencies|
Very cool tool. Thanks for forwarding the issue to the IP team
for them to check off those CQs.
Sorry that I've been unavailable to participate more fully on calls and discussions about the tool. As a concrete suggestion, for Maven based projects, it'd be awesome for there to be a little Maven plugin to automate running it.
For that one artifact, I'm curious... the GAV is
And running the tool on that comes back empty. That said, there's info for 3.1.0-incubating. And the https://clearlydefined.io/ website will do something useful when you search for org.apache.htrace/htrace-core.
I wonder what's missing in the 3.2.0 release that is causing the tool to fail?
Thanks for running the tool against the GeoMesa build. I ran it
myself, and I did find one dependency we seemed to have missed
(and I'm following up on it). Separate from that, I'll own up to
being relaxed around 'provided' dependencies. The approach
suggests looking at system, provided, and compile dependencies.
My understanding/interpretation has been that provided
dependencies don't necessarily need to declared. (Or that
declaring them was kind of a nice-to-have / sanity check.) Is
that acceptable / correct? If not, I probably just owe another
Thanks for your input, Jim.
It may well be time to revisit the requirement that the PMC approve CQs (especially with the recent changes to the IP Policy). TBH, I'm concerned that the PMC is not engaging; as part of the project leadership chain, we depend on the PMC to help ensure that project teams are implementing the process.
We've had a streamlined process for version upgrades for some time. We have, however, been wrestling with a bug that's been putting CQs into the wrong state. I'll forward your bug list to the IP team to ask that they process them and then investigate why they're not in the right state.
More generally, recent changes in the IP Policy (at least partially motivated by your experience) is moving us in a direction where hopefully most (in some cases, all) CQs are not required. Rather than CQs being a means of tracking content, we're changing them to be purely concerned with vetting content that has not previously been vetted.
A few weeks ago, I posted on this list about a tool that we've developed in-house (and are contributing to the Eclipse Dash project) that checks the trusted sources of license information that we have available to us (IPzilla and ClearlyDefined). The tool reports that we have trusted license information for org.apache.accumulo:accumulo-core:2.0.0, org.apache.commons:commons-configuration2:2.5, and org.apache.zookeeper:zookeeper:3.4.14, so (assuming that I've correctly guessed at the right Maven coordinates) three of the CQs that you've listed aren't required (I couldn't map org.apache.htrace:htrace-core:3.2, so that CQ is required).
The tool can be used to test a single CQ, e.g.:
$ echo "org.apache.accumulo:accumulo-core:2.0.0" | java -jar /gitroot/dash/org.eclipse.dash.bom/target/org.eclipse.dash.licenses-0.0.1-SNAPSHOT.jar -
Vetted license information was found for all content. No further investigation is required.
I ran the tool on your full build (there's instructions for this in the tool's repository's README) and it came back with a pretty big list of content that it couldn't map to trusted license information. I'm pretty sure, however, that we have CQs for most/all of that content, but don't have a mapping between the content Id and corresponding CQ. I'll work through those.
In the meantime, when you do create CQs, it would be helpful if you could use the Maven id/coordinates as the name. With that, we'll have an automatic mapping.
It would helpful if the AC members could test this tool on code bases that they work with and provide feedback (issues on the GitHub repository are welcome).
I'll vent a bit myself... we've been discussing this on calls for some time and I did post about this on the mailing list with a request for assistance to develop this tool into something that can be used to save project teams time. I have stated repeatedly that I owe the community a few blog posts on this topic, but I brought the AC into the loop as far back as when we started drafting edits to the IP Policy.
On Thu, Mar 19, 2020 at 3:08 PM Jim Hughes <jnh5y@xxxxxxxx> wrote:
In the spirit of reducing friction, I'd like to share a little about my
week in trying to get some CQs approved. I work on a project called
GeoMesa which has dependencies on two different ecosystems: Java-based
geospatial and Apache Software Foundation 'big data' projects (like
HBase, Cassandra, etc). (Consequently, GeoMesa has entered over 400 CQs
over its lifetime.)
For an upcoming release, we are upgrading versions of our Apache
projects. I tossed in 4 CQs* for ASF code. All of the versions are
upgrades of software projects which have already been approved.
In order to make sure that we don't miss something, we wait for Eclipse
approval in IPZilla before merging a PR with a dependency change.
(We've got a little bit of scripting with Maven's Dependency plugin
which helps us monitor this. Let me know if you are interested; I'd be
happy to share more info.)
I'm hitting a few pieces of slow down / friction / frustration.
First, I am required to get PMC approval for each CQ. It took me two
days of pinging my fellow PMCers to get one of them to vote +1 and click
4 boxes in IPZilla.
Second, now that the CQs are back to the 'new' status, and I am
completely unsure what the next steps are. Does anyone know how long
the automated checks take to run?
Third, each of projects is an Apache Software Foundation project for
which previous versions have been used by Eclipse projects. I know
there's always a chance that something goes screwy with licensing in any
project at any time. That said, if any of these CQs fail an automated
check, then I imagine an Eclipse employee is gonna have a task to open
the CQ, they'd see that it is an ASF project and click 'approve'.
Anyhow, apologies for venting. Thanks for reading, thanks in advance
for any suggestions. For my position, I think there are some changes we
1. Remove the need to get PMC approval.
2. Provide some way to get faster approval for version upgrades.
Either of those approaches would make my life better. Together, 95% of
my frustration with IP concerns would be gone.
As the AC, what are we in a position to recommend / request?
* Interested in watching from home, the CQs are here:
eclipse.org-architecture-council mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
Director of Open Source Projects | Eclipse Foundation, Inc.
_______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
Back to the top