Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orbit-dev] Continue to require ATO CQs?

To be clear, the requirement is that we have license information from a trusted source for intellectual property. IPZilla is one of those sources and ClearlyDefined is the other. We may potentially add other sources (when such sources present themselves). 

We no longer require piggyback CQs. From the perspective of the IP Policy and EMO Intellectual property team, there is no longer any need to treat Orbit as special. That is, we'd like to see ATO eliminated. If a library is "license certified" or "approved" by any project, then it can just be used by any other project.

For ClearlyDefined, we consider the license information for content to be acceptable if the effective score is at least 50.

I've developed a prototype tool that can be used to vet the license of content based on identifiers (e.g. Maven GAV). I'm moving this to Eclipse Dash. One of the things that the tool does now is cite the source of the vetted license information ("CQ999", "clearlydefined", or "projectcode"). I've been thinking of extending this to include a URL pointer to the source.

For this new regime to work, we depend on regular IP Log checks. We do IP Log checks when projects engage in release reviews. Per the EDP, a project needs to engage in a release review only once every year. 

Since I believe that Eclipse Orbit engages in what could be considered releases, I believe that it is reasonable to require that the project engage in an annual review like every other open source project at the Eclipse Foundation. Feel free to argue with me.


On Fri, Apr 3, 2020 at 9:50 PM Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
Hello folks,

Should Orbit continue to require ATO CQs now that the new IP process does not require CQs for third-party bundles that pass clearlydefined checks?

I am assuming that the ATO CQs are an easy way to keep track and make sure that bundles added to Orbit are OK. As such I have raised  Bug 561759 to update the CQ UI to allow creating such CQs.

Jonah Graham
Kichwa Coders
orbit-dev mailing list
To unsubscribe from this list, visit


Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Back to the top