FSF status for FSF licenses (was: meeting minutes)

[W. Trevor King]

On Tue, Feb 27, 2018 at 06:21:21PM +, Zavras, Alexios wrote:
> … on the subject of FSF “free” field: let’s make sure that FSF’s own
> licenses (GPL*, LGPL*, GFDL*, etc.) are marked as “free”.  I think
> their site lists only licenses by others, but our table seems…
> strange having an empty field for GPL’s free bit.

The FSF lists some of their own licenses, e.g. GPL-3.0 [1] but not
GPL-1.0 [2].  That's part of the reason for missing entries.  The
other part of the reason is that the versioning for the FSF API is
currently in flux [3], and until that gets sorted I think Gary is
holding off on updating the tools (but it's been a while since I've
checked, maybe my understanding is stale).

Cheers,
Trevor

[1]: https://www.gnu.org/licenses/license-list.html#GNUGPLv3
[2]: https://github.com/wking/fsf-api/issues/7
[3]: https://github.com/wking/fsf-api/issues/10

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy


signature.asc
Description: OpenPGP digital signature
___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

RE: meeting minutes

[Zavras, Alexios]

I couldn’t join that meeting, but on the subject of FSF “free” field: let’s 
make sure that FSF’s own licenses (GPL*, LGPL*, GFDL*, etc.) are marked as 
“free”. I think their site lists only licenses by others, but our table seems… 
strange having an empty field for GPL’s free bit.


-- zvr –

From: spdx-legal-boun...@lists.spdx.org 
[mailto:spdx-legal-boun...@lists.spdx.org] On Behalf Of J Lovejoy
Sent: Tuesday, 27 February, 2018 16:08
To: SPDX-legal 
Subject: meeting minutes

Hi all,

The meeting last week picked up on further discussion of things to work on and 
discuss at face-to-face. You will have also just seen the email to all re: 
topics. Please let us know if you will be there!

https://wiki.spdx.org/view/Legal_Team/Minutes/2018-02-22

Also, as the next legal call falls the day before the face-to-face on March 
8th, we’ll skip that meeting - please mark your calendars accordingly.

thanks,
Jilayne

SPDX Legal Team co-lead
opensou...@jilayne.com

Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

meeting minutes

[J Lovejoy]

Hi all,

The meeting last week picked up on further discussion of things to work on and 
discuss at face-to-face. You will have also just seen the email to all re: 
topics. Please let us know if you will be there!

https://wiki.spdx.org/view/Legal_Team/Minutes/2018-02-22 


Also, as the next legal call falls the day before the face-to-face on March 
8th, we’ll skip that meeting - please mark your calendars accordingly.

thanks,
Jilayne

SPDX Legal Team co-lead
opensou...@jilayne.com


___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

Re: agenda for OSLS

[J Lovejoy]

oops, forgot one of the topics - added to list below!



> On Feb 27, 2018, at 8:05 AM, J Lovejoy  wrote:
> 
> HI all SPDX teams,
> 
> Open Source Leadership Summit is coming up next week and the Linux Foundation 
> has been generous enough to reserve a room at the venue the morning after the 
> event ends for our face-to-face working group.  
> 
> We’ll meet on Friday, March 9th, from 9am to lunch. (room name TBD)
> 
> We have quite a few cross-functional topics lined up, so we’ll meet as a 
> group. Topics will include:
> 
> Using Github for SPDX: what is our process for different repos, identify 
> improvements, generate or update documentation
> Adding more licenses to SPDX License List: from the Linux kernel, other 
> licenses
> what about lists of non-open source licenses that other people maintain; is 
> there a way to enable that?
> Updates to spec and next release planning
> Communicating and explaining relationship and versioning for spec, license 
> list, matching guidelines, tools, etc. Where/how to update website to clarify 
> this?
> SPDX License List and it’s related material: better organization to make it 
> easier to find - should this all go into an Appendix in the Spec?
> SPDX “relaxed” - some people are providing SPDX documents that lack some of 
> mandatory fields, thus are not SPDX compliant, but this is still useful info. 
> Should we have a “relaxed” option or some kind of grading for SPDX documents 
> to encourage more use.
> 
> Please let me know if I’ve missed anything or if there is any kind of 
> preferred order of topics.  
> 
> 
> Thanks,
> Jilayne
> 
> SPDX Legal Team co-lead
> opensou...@jilayne.com 
> 
> 
> ___
> Spdx mailing list
> s...@lists.spdx.org
> https://lists.spdx.org/mailman/listinfo/spdx

___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

agenda for OSLS

[J Lovejoy]

HI all SPDX teams,

Open Source Leadership Summit is coming up next week and the Linux Foundation 
has been generous enough to reserve a room at the venue the morning after the 
event ends for our face-to-face working group.  

We’ll meet on Friday, March 9th, from 9am to lunch. (room name TBD)

We have quite a few cross-functional topics lined up, so we’ll meet as a group. 
Topics will include:

Using Github for SPDX: what is our process for different repos, identify 
improvements, generate or update documentation
Adding more licenses to SPDX License List: from the Linux kernel, other licenses
what about lists of non-open source licenses that other people maintain; is 
there a way to enable that?
Updates to spec and next release planning
Communicating and explaining relationship and versioning for spec, license 
list, matching guidelines, tools, etc. Where/how to update website to clarify 
this?
SPDX License List and it’s related material: better organization to make it 
easier to find - should this all go into an Appendix in the Spec?

Please let me know if I’ve missed anything or if there is any kind of preferred 
order of topics.  


Thanks,
Jilayne

SPDX Legal Team co-lead
opensou...@jilayne.com


___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal