THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx

Difference between revisions of "Legal Team/Minutes/2013-09-25"

From SPDX Wiki
Jump to: navigation, search
(Created page with "== Attendees == * Jilayne Lovejoy * Zac White * Dennis Clark * Daniel German * Paul Madick * Mark Gisi * Scott Lamons == AGENDA == '''1) Summary of LinuxCon happenings''' A ...")
 
Line 14: Line 14:
 
#  Discussion about and outline created for Best Practices or How To guide to SPDX
 
#  Discussion about and outline created for Best Practices or How To guide to SPDX
 
#  License Matching Guidelines discussion:
 
#  License Matching Guidelines discussion:
** discussed how to better sync-up matching guidelines with templates (proposed changes to guidelines subsequently sent to mail list)
+
## discussed how to better sync-up matching guidelines with templates (proposed changes to guidelines subsequently sent to mail list)
** also discussed naming of the license list filed "standard header" and to "official license header" - generaly discussion about use of official headers, in that a license can be matched based on this
+
## also discussed naming of the license list filed "standard header" and to "official license header" - generaly discussion about use of official headers, in that a license can be matched based on this
** versioning of license templates to sync on license list versioning - aiming for next release of license list (v1.20) to include a full set of templates
+
## versioning of license templates to sync on license list versioning - aiming for next release of license list (v1.20) to include a full set of templates
** Jilayne to drive work on going through list and bring issues to legal team to (hopefully) increase pace
+
## Jilayne to drive work on going through list and bring issues to legal team to (hopefully) increase pace
 
#  Adoption Discussion - most of this revolved around relatively new proposal of file-level license tagging using the SPDX License List short identifier (a la U-Boot); Jack has posted a draft of the proposal on the wiki at: http://wiki.spdx.org/view/Business_Team/Adoption#Use_of_META_Tags  
 
#  Adoption Discussion - most of this revolved around relatively new proposal of file-level license tagging using the SPDX License List short identifier (a la U-Boot); Jack has posted a draft of the proposal on the wiki at: http://wiki.spdx.org/view/Business_Team/Adoption#Use_of_META_Tags  
** talked to a few people about this idea whilst at LinuxCon and got encouraging feedback re: support and potential adoption
+
## talked to a few people about this idea whilst at LinuxCon and got encouraging feedback re: support and potential adoption
 
#  Feedback from Samsung - Samsung gave a talk about their internal use of SPDX on Monday (see slides here: http://events.linuxfoundation.org/sites/events/files/slides/Piloting%20SPDX%20in%20Samsung%20-%20case%20studies%20and%20experiences%20%28YoungTaek%20Kim%29.pdf
 
#  Feedback from Samsung - Samsung gave a talk about their internal use of SPDX on Monday (see slides here: http://events.linuxfoundation.org/sites/events/files/slides/Piloting%20SPDX%20in%20Samsung%20-%20case%20studies%20and%20experiences%20%28YoungTaek%20Kim%29.pdf
** had a follow-up meeting with Samsung to discuss feedback for SPDX and learn how they learned about SPDX on Tuesday; good feedback and ideas on needed documentation and tututorials
+
## had a follow-up meeting with Samsung to discuss feedback for SPDX and learn how they learned about SPDX on Tuesday; good feedback and ideas on needed documentation and tututorials
 
#  Yocto integration update from Matt at UNO and Jack
 
#  Yocto integration update from Matt at UNO and Jack
 
#  Tools update from Gary
 
#  Tools update from Gary

Revision as of 18:21, 26 September 2013

Attendees

  • Jilayne Lovejoy
  • Zac White
  • Dennis Clark
  • Daniel German
  • Paul Madick
  • Mark Gisi
  • Scott Lamons

AGENDA

1) Summary of LinuxCon happenings A day's worth of various meeting on Tuesday at LinuxCon

  1. Discussion about and outline created for Best Practices or How To guide to SPDX
  2. License Matching Guidelines discussion:
    1. discussed how to better sync-up matching guidelines with templates (proposed changes to guidelines subsequently sent to mail list)
    2. also discussed naming of the license list filed "standard header" and to "official license header" - generaly discussion about use of official headers, in that a license can be matched based on this
    3. versioning of license templates to sync on license list versioning - aiming for next release of license list (v1.20) to include a full set of templates
    4. Jilayne to drive work on going through list and bring issues to legal team to (hopefully) increase pace
  3. Adoption Discussion - most of this revolved around relatively new proposal of file-level license tagging using the SPDX License List short identifier (a la U-Boot); Jack has posted a draft of the proposal on the wiki at: http://wiki.spdx.org/view/Business_Team/Adoption#Use_of_META_Tags
    1. talked to a few people about this idea whilst at LinuxCon and got encouraging feedback re: support and potential adoption
  4. Feedback from Samsung - Samsung gave a talk about their internal use of SPDX on Monday (see slides here: http://events.linuxfoundation.org/sites/events/files/slides/Piloting%20SPDX%20in%20Samsung%20-%20case%20studies%20and%20experiences%20%28YoungTaek%20Kim%29.pdf
    1. had a follow-up meeting with Samsung to discuss feedback for SPDX and learn how they learned about SPDX on Tuesday; good feedback and ideas on needed documentation and tututorials
  5. Yocto integration update from Matt at UNO and Jack
  6. Tools update from Gary
  7. met with GitHub as introduction to SPDX and discuss how www.choosealicense.com came to be; identified some areas where we can collaborate in short-term and potential future work

2) Provide feedback for revised License Matching Guidelines - discussed some edits to this; Jilayne to send another rev to group, post-call

3) Fedora List - ran out of time; see email with NEW link for Google Drive doc; if you can't access, tell Jilayne. Also see separate email re: ideas on moving this forward via email/between calls