You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At All Things Open, @dizquierdo and I met with Patrick and Nick from OSI. They want to have some publicity around an “Open Source Metric”. Yesterday during the CHAOSS Risk WG, we defined “Open Source Metric” to be a filter “is OSI approved” on top of License Coverage.
If OSI follows through to create some marketing around this “Open Source Metric” and they highlight the CHAOSS project — it would be great to also extend COCOLic to have this metric. Augur implemented the metric using the SPDX license list (json available) to check whether a license is OSI approved — maybe an approach we can do as well.
I imagine that we add a yes/no field "is-osi-approved-license" or something like that.
Is this a Graal issue or should it be in GrimoireELK?
The text was updated successfully, but these errors were encountered:
At All Things Open, @dizquierdo and I met with Patrick and Nick from OSI. They want to have some publicity around an “Open Source Metric”. Yesterday during the CHAOSS Risk WG, we defined “Open Source Metric” to be a filter “is OSI approved” on top of License Coverage.
If OSI follows through to create some marketing around this “Open Source Metric” and they highlight the CHAOSS project — it would be great to also extend COCOLic to have this metric. Augur implemented the metric using the SPDX license list (json available) to check whether a license is OSI approved — maybe an approach we can do as well.
I imagine that we add a yes/no field "is-osi-approved-license" or something like that.
Is this a Graal issue or should it be in GrimoireELK?
The text was updated successfully, but these errors were encountered: