At the recent SPDX general call, I offered to clarify Python licensing and to suggest standard names. This set of licenses is messy, and a long discussion is below. There is not a single logical answe

Hello SPDX license list interested parties, I would like to propose that we change the License Identifier for the Eclipse Public License 1.0 on the SPDX License List from “EPL-1.0” to “Eclipse-1.0”. I

Thanks Mike, The Eclipse Foundation certainly gets the big vote regarding how their license is referred to. My experience is primarily commercial ISVs in the tools space, about a dozen, ranging in yea

Thanks all, your replies are truly appreciated. I withdraw the request to change the License identifier for the Eclipse Public License from EPL-1.0 to Eclipse-1.0. Separately, we are looking for knowl

Thanks Jilayne. A large, well-vetted, standardized and generally accepted license list is our foundation. I volunteer to assist in timely review of the new license submissions, whether as part of the

Thanks Jilayne. I may need to miss the legal workstream due to mandatory day-job meeting, but will try to dial in late. Regarding the SPDX License List description: in the sentence, “The SPDX License

As long as the licenses are - Carefully named and vetted for exact license text - Somewhat broadly applicable (“somewhat broadly” is fuzzy, but we do want the list to grow starting with very common an

Hello Phil, fine to use Micro Focus name in this context. Thanks, Tom Tom Incorvia; tom.incorvia@...; O: (512) 340-1336; M: (408) 499 6850

I recollect someone requesting this information as part of a prior press release. There are both companies that support the standard, and a larger group of companies that have standardized on the lice

Amazing. I know how much work this takes. Tom Tom Incorvia; tom.incorvia@...; O: (512) 340-1336; M: (215) 500 8838; Shoretel (Internal): X27015