Closed lukasmittag closed 6 months ago
@sophokles73 if you want to take a look as well
I looked at the Dash output and saw this. Do we need to do anything?
[main] INFO Querying Eclipse Foundation for license data for 208 items.
[main] INFO Found 46 items.
[main] INFO Querying ClearlyDefined for license data for 162 items.
[main] INFO Found 162 items.
[main] INFO License information could not be automatically verified for the following content:
[main] INFO
[main] INFO crate/cratesio/-/kuksa/0.1.0
[main] INFO
[main] INFO This content is either not correctly mapped by the system, or requires review.
Do we need to do anything?
The Dash tool tries to find licensing information for dependencies on Clearly Defined and the Eclipse Foundation systems. The kuksa
crate seems to not have been analyzed yet, neither by CD nor the EF.
What you could do is run the Dash tool with the --review
switch to automatically create a corresponding review request with the EF. You would then need to provide the source location manually in the issue created in the EF GitLab instance for the review.
However, before you do so, you might want to think about
kuksa
is the right name for the crate. IMHO it is quite abstract and can mean anything or nothing.kuksa
is actually a crate that is helpful to others as well and therefore should be published to crates.io
This adds integration tests for authorizing against databroker and checking for the right permissions.
675 needs to be merged first because it is based on the new client lib. Therefore also some changes in the existing integration test took place.