Open ariel11 opened 5 years ago
@pombredanne , @royaljust - FYI
The license list shown in the websites' dropdown is likely from the service. Fix dropdown list first, then figure out how to migrate old definitions.
@jeffmendoza and @MichaelTsengLZ - any update with this? I still get a quite a lot curations using deprecated identifiers and it eats up a lot of time fixing them.
Are the curations coming from the Website, or from "Microsoft Automation"?
Both, but right now, mainly from automation.
I'll create a Microsoft bug for the ones from automation. This bug can stay here, referring to curations from the website.
Hi @capfei! Could you link me to a few recent curations where you are seeing this? It will help a lot with giving me the context to diagnose and fix this issue.
@nellshamrell Here are some that I have had to update within the last month or so:
LGPL-3.0: https://github.com/clearlydefined/curated-data/pull/8357 LGPL-2.1+: https://github.com/clearlydefined/curated-data/pull/8346 GPL-2.0-with-classpath-exception: https://github.com/clearlydefined/curated-data/pull/8361 GPL-3.0: https://github.com/clearlydefined/curated-data/pull/8301
@nellshamrell and @jeffmendoza - Yes, seeing this too -e.g. LGPL-2.1+ from the automation tooling - https://github.com/clearlydefined/curated-data/pull/6287
It looks like all of those examples came from Microsoft tooling, which I know @jeffmendoza has opened an internal Microsoft bug for.
Has anyone seen this happen from curations from the website?
I can probably find some older ones, but we don't receive many curations from the website. The deprecated licenses are in the license list on the website.
My screenshot shows some of the deprecated licenses.
Thank you! Looks like we need to at least remove the deprecated licenses from the list on the website.
We should decide if we want the deprecated license identifiers in the license drop down menu in ClearlyDefined - e.g. GPL-2.0, LGPL-3.0, etc. (see https://spdx.org/licenses/index.html).