Re: Import and export function of SPDX
So far our FOSS clauses are not aligned on the SPDX standard (we are already happy when suppliers can comply to our requirements without too much discussion so we did not formalize things too much)toggle quoted messageShow quoted text
What we request is the name of FOSS, the name of the license if it is OSI compliant, or a copy of the license if it is not, the nature of the FOSS: is it a library, a standalone software, an interpreter, ... in order to determine if there is some potential contamination as with GPL.
Now we have already aligned our database on the SPDX taxonomy for naming licenses, we will soon ask our suppliers to align on this taxonomy. I have already prepared a document (in copy) to distribute to our suppliers and partners on SPDX.
Software Coordination Manager, Bell Labs, Corporate CTO Dpt
Distinguished Member of Technical Staff
Tel +33 (0) 6 75 25 21 94
Alcatel-Lucent International, Centre de Villarceaux
Route De Villejust, 91620 Nozay, France
De : Jilayne Lovejoy [mailto:jilayne.lovejoy@...]
Envoyé : mercredi 13 juin 2012 16:08
À : RUFFIN, MICHEL (MICHEL); Gary O'Neall; Peter Williams
Cc : spdx-tech@...; spdx@...
Objet : Re: Import and export function of SPDX
Thanks again for sharing your information. In regards to your posting (to
both this group and the FSF legal network) about the legal clauses, I have
noticed this and apologize as well for not responding sooner (it's still
in my inbox as a to-do item, sadly). In any case, a couple thoughts. It
is my understanding from your previous email(s), that you'd like to see
some kind of FOSS-related legal clause resource, is that correct? At the
moment, this is not within the scope of SPDX (albeit a great idea
generally!). This is probably something that could be discussed further
in terms of something to consider tackling in the longer-term road map.
More specifically, your "list of FOSS" clause (a)(ii), you require the
name of the license, license text, and whether it is OSI certified or not.
This is all information capture in the SPDX License List. Do you have an
internal list as well? If so, it would be great to discuss aligning any
licenses on your list for potential inclusion on the SPDX License List, if
not already included there and otherwise coordinating.
Jilayne Lovejoy | Corporate Counsel
jlovejoy@... | 720 240 4545
10910 W 120th Ave, Suite 450
Broomfield, Colorado 80021
Twitter @openlogic @cloudswing
On 6/13/12 6:45 AM, "RUFFIN, MICHEL (MICHEL)"
Gary, I think in my previous mail I expressed our use case: