Consider supporting only OSI-approved licenses

[sdruskat]

Reasons:

• The list is much shorter and thus more maintainable

Potential catch

• OSI may use wrong/different SPDX identifiers

[hainesr]

My strong personal preference here is to remain with SPDX. Narrowing the options available to people feels like it would be a reason for some to avoid using CFF. I do understand the maintainability question though.

[sdruskat]

My strong personal preference here is to remain with SPDX. Narrowing the options available to people feels like it would be a reason for some to avoid using CFF. I do understand the maintainability question though.

Thanks @hainesr! if I remember correctly, we were considering to stick with SPDX identifiers, but boil down the list itself to include only those in the OSI list. Which may in itself create its own maintenance issues (mapping/conversion/updating, etc.)...

[hainesr]

Yes, I would imagine that going with the intersection of SPDX/OSI is more work than just plain SPDX!

Honestly, I would stick with being as permissive as possible, within some constraints, and sticking with the SPDX superset.