Quick update/reminder:
There will be no legal team call tomorrow (Thursday)
We will be having our F2F in Sonoma, CA Friday.
We’ll meet at 9am in Kenwood 2
We will use the usual conference line for those who want to join from afar:
Web conference: http://uberconference.com/SPDXTeam
Optional dial in number: 415-881-1586
No PIN needed
A bit more on and re-order on agenda:
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? How to get
people to notice and understand SPDX specification fields that relate to
licenses,
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?
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.
Thanks!
Jilayne & Kate
> On Feb 27, 2018, at 7:06 AM, J Lovejoy <opensou...@jilayne.com> wrote:
>
> oops, forgot one of the topics - added to list below!
>
>
>
>> On Feb 27, 2018, at 8:05 AM, J Lovejoy <opensou...@jilayne.com
>> <mailto:opensou...@jilayne.com>> 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 <mailto:opensou...@jilayne.com>
>>
>>
>> _______________________________________________
>> Spdx mailing list
>> s...@lists.spdx.org <mailto: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
_______________________________________________
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal
