Date   

Rescheduling important SPDX General Meeting

Philip Odence
 

The Feb 5 meeting will be postponed 1 week to Thurs. Feb 12. (outside US, note that US will be on daylight savings time next week so the call will be an hour off of normal for you).

The main thrust of the call will be to answer questions about the SPDX 2.0 Spec. We’ll do a very compressed version of the team updates and spend most of the time discussing questions about the new spec and the license list (which has also gone through significant change). 

IMPORTANT: See the instructions below the meeting agenda and the attached copy of the spec, and please take time to review the spec in advance of the meeting. 

Lastly, unfortunately, I have a conflict, so Kate will chair.

Best, 
Phil



****************

GENERAL MEETING

Meeting Time: Thurs, Feb12, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html

Conf call dial-in:
Conference code:  7812589502
Toll-free dial-in number (U.S. and Canada):  (877) 435-0230
International dial-in number: (253) 336-6732
For those dialing in from other regions, a list of toll free numbers can be found: 
https://www.intercallonline.com/portlets/scheduling/viewNumbers/viewNumber.do?ownerNumber=6053870&audioType=RP&viewGa=false&ga=OFF

 
Administrative Agenda
Attendance

Technical Team Report - Kate

Legal Team Report - Jilayne

Business Team Report – Jack

Cross Functional Issues – 2.0 Spec and License List Review - Kate





********



Greetings SPDX Community,

 

We are pleased to announce that the penultimate version of the SPDX 2.0 Specification and the new  SPDX License List are ready for community review.  With 2.0 there have been great strides forwards in the expressiveness of an SPDX document through relationships and the license expression syntax.

 

There will be a general question and answer session on these at the March 12th General Meeting.   Any comments regarding the material below should be submitted no later than March 23rd as directed below. We are hoping to finalize the material and officially release it at the April 2nd General Meeting. This should allow you plenty of time to do a thorough review. 

 

Background Information

---------------------------------

For an overview of the  2.0 requirements you may read this http://wiki.spdx.org/images/SPDX-TR-2014-3.v1.0.pdf

 

The Use Cases are documented on the Technical team wiki athttp://wiki.spdx.org/view/Technical_Team/Use_Cases/2.0

 

For a presentation given at LinuxCollab in February 2015 on changes to the specification go here. It’s a nice overview.

http://spdx.org/sites/spdx/files/publications/SPDX%202.0%20Collab%202015%20Presentation.pptx

 

Specification Review Material

------------------------------------

SPDX 2.0 Specification, dated 20150303 is attached to this email as a PDF for your convenience.     The same file is also available athttp://wiki.spdx.org/view/Technical_Team/SPDX_Specification_Versions

as SPDX-2.0rc3.pdf

 

The technical team would prefer comments were made in the google doc located athttps://docs.google.com/a/linaro.org/document/d/1wE_zvLU4c291ACi9wIJmQoE4ltKRW4rzM1TYiIvEVOs/edit#heading=h.x7jjfaxtluz1.

Comments may also be directed to the technical team mailing list at mailto: spdx-tech@... . You will need to be a member of the list to send an email.

The schema for the RDF can be found athttp://spdx.org/rdf/ontology/spdx-2-0-rev-12/ .

The model diagram can be found at  http://wiki.spdx.org/view/Technical_Team/Model_2_0. The model is a great way to see how all the old and new pieces fit together.

Tools

-------

The tools for the 2.0 Specification are located in the SPDX GIT repository.

 

To try them, you will need to download the source and build them.  You can access the repository here:http://git.spdx.org/?p=spdx-tools.git;a=snapshot;h=refs/heads/develop;sf=tgz

 

Instructions on building the tools can be found in the README.md file in the root directory of the source tree here: http://git.spdx.org/?p=spdx-tools.git;a=blob_plain;f=README.md;hb=5efe1f1e4727d7d7be48488225b68c65e71b84b9and here: http://spdx.org/publications/tool-documentation/how-to-use-the-software-package-document-exchange-spdx-tools

 

SPDX License List

-------------------------

The SPDX License List v2.0-rc3 and  can be reviewed at http://spdx.org/licenses/preview/ .  Due to the adoption of the License Expression Syntax, license exceptions have their own sub-list and some licenses have been deprecated.  Information for all of this can be linked to from this page.

 

The master files for the license list can be found here:  http://git.spdx.org/?p=license-list.git;a=summary

 

General information about the SPDX License List can be found here: http://spdx.org/spdx-license-list/license-list-overview

 

The Matching Guidelines can be found here:http://spdx.org/spdx-license-list/matching-guidelines

 

Feedback is welcome and can be sent to: spdx-legal@...  . You will need to be a member of the list to send an email.

 

Best regards,

 

SPDX Technical, Legal and Business Teams


SPDX General Meeting Minutes

Philip Odence
 

Meeting minutes below.

Also, here’s information on SPDX participation at CollabSummit. Big thanks to Jack for pulling it all together. 



L. Philip Odence
General Manager Audit Services
Vice President of Corporate and Business Development
Black Duck Software, Inc.
8 New England Executive Park, Suite 211, Burlington MA 01803
Phone: 781.810.1819, Mobile: 781.258.9502
Skype: philip.odence




General Meeting/Minutes/2015-02-05

  • Attendance: 5
  • Lead by Phil Odence
  • Minutes of January meeting approved


Biz Team Report - Jack[edit]

  • Collab Summit
    • Agenda set
    • Tech Team will meet on Wed
    • Friday afternoon meeting
    • Jack will post 
  • Looking like 2.0 spec won’t be finalized
    • Likely to be the subject for Friday afternoon
  • Starting to gear up for another Google Summer of Code


Tech Team Report - Jack[edit]

  • Some delay in finalizing due to last minute issues arising
  • Has gotten very good detailed review by Tech Team
  • 2.0 will go out for community review prior to Collab


Legal Team Report - Jilayne[edit]

  • Beta LL list posted, feedback welcome


Cross Functional Topics - Phil[edit]

  • Future Presentations for General Meeting
    • TI would be happy to after Collab
    • Would love to get other companies to share


Attendees[edit]

  • Phil Odence, Black Duck
  • Jack Manbeck, TI
  • Hassib Khanafer, Protecode
  • Pierre LaPointe, nexB 
  • Kirsten Newcomer, Black Duck


Minutes from January SPDX General Meeting

Philip Odence
 

Again, thanks to Bruno Grasset from Valeo for a great presentation.
Hope to see everyone at CollabSummit. Time to make your plans. 


MINUTES



General Meeting/Minutes/2015-01-08

  • Attendance: 6
  • Lead by Phil Odence
  • Minutes of December meeting approved

Cross Functional Issues – Phil[edit]

  • Great Presentation from Bruno Grasset
  • He opened and closed with thanks to everyone involved with SPDX for providing something so useful to the industry
    • Valeo
      • Supplier to Automotive Industry- Autonomous Cars, Connected Car, Intuitive Control
      • Middle of complex supply chain
    • Why they think SPDX is important
      • Industry is “likes” standards, procedures, rules
      • Have an explicit program to ensure respecting licenses and meeting obligations in all products
      • Bruno is in charge of OSS compliance
    • How they use
      • License List
        • Internal policy started with the SPDX list
        • They use the SPDX license IDs in all of their documents and databases (including promoting publicly)
        • And they check any licenses anyone supplies against our standard text
      • Document Spec
        • Prototyped use internally
        • Have been looking for hierarchy, so 2.0 is important; evaluating in 2015
    • Future Intent
      • Large OEMs (car companies) are starting to require
      • Customer requirements are making this a priority in 2015
      • Will need to require from their own suppliers
      • Integration with Yocto is critical
      • Aiming for chain of trust, based on SPDX
    • Questions
      • When you evaluated SPDX, any features beyond hierarchy that they require?
        • Not yet mature enough to completely evaluate
      • How did you hear of? How can we promote?
        • LinuxCon Europe session- Bruno came then promoted internally. 
        • He expects that in his space that SPDX will catch on quickly because of car makers requirements
      • SPDX and Yocto- Is there only interest in Yocto integration or more general integration?
        • Broader interest in integrating into process


General Status - Phil[edit]

  • On track for 2.0 release at CollabSummit
  • Jack has been working hard to get a good agenda together
  • We will be sharing a room with OpenChain so that folks can participate in both
  • Looking forward to seeing everyone


Attendees[edit]

  • Phil Odence, Black Duck
  • Kirsten Newcomer, Black Duck
  • Matt Germonprez, UNO
  • Scott Sterling, Palamida
  • Gary O’Neill, SourceA
  • Bruno Grasset, Valeo


Reminder: Important Scheduling Announcement and Minutes from SPDX General Meeting

Philip Odence
 

The January meeting with be on Jan 8 at 8am PST, 11am EST, and 16:00 GMT.

We’ll start with Bruno Grasset from Valeo describing their use of SPDX. Please make every effort to join. His slides are attached.


Minutes from Dec meeting:



General Meeting/Minutes/2014-12-04

  • Attendance: 6
  • Lead by Phil Odence
  • Minutes of Nov meeting approved

Cross Functional Issues – Phil[edit]

  • Postponed presentation from Valeo to January 8


Biz Team Report - Phil[edit]

  • Mostly focused on Collab Summit agenda
    • Need to have rough agenda before holidays
    • Coordinating with Open Chain who will share our room for 1/2 day 
    • Plugfest will likely take different form
      • Anticipating tooling will not be fully in place
      • More manual testing 
    • Discussion: Ideas for sessions
      • SPDX 101 and 102 (the latter being update on 2.0)
      • Update on License List
      • 2.0 Tooling 


Legal Team Report - Paul[edit]

  • Beta LL list (targeting Dec 18) to include
    • Continuing to add new licenses
    • Deprecated licenses
    • Exceptions list & some FAQs
    • Templates


Tech Team Report - Scott[edit]

  • Heads down reviewing 2.0 spec
    • Cleaning up
    • Adding/improving examples
  • In pretty good shape


Attendees[edit]

  • Phil Odence, Black Duck
  • Paul Maddick, HP
  • Mike Dolan, Linux Foundation
  • Pierre LaPointe, nexB 
  • Scott Sterling, Palamida
  • Mark Gisi, Wind River


SPDX General Meeting

Philip Odence
 

When: Thursday, January 08, 2015 11:00 AM-12:00 PM. (UTC-05:00) Eastern Time (US & Canada)
Where: Bridge info enclosed

*~*~*~*~*~*~*~*~*~*
Rescheduling the January meeting as it would normally fall on New Year’s day. Reminder: We will have a presentation by Valeo on their use of SPDX.

***

DIAL IN:
Toll-free dial-in number (U.S. and Canada): (877) 435-0230
International dial-in number: (253) 336-6732

Conference code: 7812589502





Call for SPDX Presentations at the Linux Collaboration Summit

Philip Odence
 

Hello all,

If you have any interesting SPDX story to tell, even a short one, we would love to have you share it at the Collab Summit. 

The event is Feb 18-20 in Santa Rosa, California. http://events.linuxfoundation.org/events/collaboration-summit   We have dedicated track and room for SPDX for the full length of the conference and are now putting together a rough agenda (that will include 1/2 day that we will share our brethren in the OpenChain group).  There will be a mix of introductory/high level and deeper topics, maybe of interest only to those actively involved in our work group.

We would love to hear about how companies are using or planning to use SPDX and/or the License List. Even if it’s only a 10 minute tale, we could put you on a panel to share. Or, if you have a topic that is deeper into the technical guts of SPDX, that would of great interest as well.

If you have any interest at all, please contact Jack and Mikael who are roughing out an agenda later this week.

Thanks,
Phil

L. Philip Odence
Vice President and General Manager
Black Duck
8 New England Executive Park, Suite 211, Burlington MA 01803
Phone: 781.810.1819, Mobile: 781.258.9502
Skype: philip.odence




Important Scheduling Announcement and Minutes from SPDX General Meeting

Philip Odence
 

Scheduling
The January meeting with be on Jan 8 (normally it would fall on New Year’s Day)
 We have postponed the Valeo presentation to that meeting; please make every effort to join.

Minutes:



General Meeting/Minutes/2014-12-04

  • Attendance: 6
  • Lead by Phil Odence
  • Minutes of Nov meeting approved

Cross Functional Issues – Phil[edit]

  • Postponed presentation from Valeo to January 8


Biz Team Report - Phil[edit]

  • Mostly focused on Collab Summit agenda
    • Need to have rough agenda before holidays
    • Coordinating with Open Chain who will share our room for 1/2 day 
    • Plugfest will likely take different form
      • Anticipating tooling will not be fully in place
      • More manual testing 
    • Discussion: Ideas for sessions
      • SPDX 101 and 102 (the latter being update on 2.0)
      • Update on License List
      • 2.0 Tooling 


Legal Team Report - Paul[edit]

  • Beta LL list (targeting Dec 18) to include
    • Continuing to add new licenses
    • Deprecated licenses
    • Exceptions list & some FAQs
    • Templates


Tech Team Report - Scott[edit]

  • Heads down reviewing 2.0 spec
    • Cleaning up
    • Adding/improving examples
  • In pretty good shape


Attendees[edit]

  • Phil Odence, Black Duck
  • Paul Maddick, HP
  • Mike Dolan, Linux Foundation
  • Pierre LaPointe, nexB 
  • Scott Sterling, Palamida
  • Mark Gisi, Wind River


Re: Next week's SPDX General Meeting & Nov Meeting Minutes

Philip Odence
 

Attached are the slides for the Valeo presentation at the beginning of the meeting today. 

From: Phil Odence <podence@...>
Date: Wednesday, November 26, 2014 at 9:51 AM
To: "spdx@..." <spdx@...>
Subject: Re: Next week's SPDX General Meeting & Nov Meeting Minutes

corrected date…apologies

From: Phil Odence <podence@...>
Date: Wednesday, November 26, 2014 at 9:37 AM
To: "spdx@..." <spdx@...>
Subject: Next week's SPDX General Meeting & Nov Meeting Minutes

ANOTHER SPECIAL PRESENTATION: In addition to our normal agenda, I’ve asked my friend Bruno Grasset from Valeo to talk about his company’s adoption of SPDX. Valeo is one of the world’s largest suppliers to the automotive industry. Bruno runs Valeo's open source compliance program and one of the technical leaders of GENIVI. 

I’m trying to line up other speakers from complementary projects and companies using SPDX for future General Meetings…ideas welcome.


GENERAL MEETING

Meeting Time: Thurs, Dec 4, 8am PT / 10 am CT / 11am ET / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html

Conf call dial-in:
Conference code:  7812589502
Toll-free dial-in number (U.S. and Canada):  (877) 435-0230
International dial-in number: (253) 336-6732
For those dialing in from other regions, a list of toll free numbers can be found: 
https://www.intercallonline.com/portlets/scheduling/viewNumbers/viewNumber.do?ownerNumber=6053870&audioType=RP&viewGa=false&ga=OFF

 
Administrative Agenda
Attendance

Valeo Presentation


Technical Team Report - Kate


Legal Team Report - Jilayne


Business Team Report – Jack


Cross Functional Issues – Phil




General Meeting/Minutes/2014-11-06

  • Attendance: 15+
  • Lead by Phil Odence
  • Minutes of October meeting approved

Cross Functional Issues, Special Presentation from Polarsys – Phil[edit]

  • Presentation from Polarsys COTSAQ project http://polarsys.org/proposals/cotsaq
    • OSS tool for managing software BoMs
    • SPDX connections
      • First will use SPDX License List
      • Connecting with code scanners through SPDX


Biz Team Report - Jack[edit]

  • Last call cancelled. Call in an hour.
  • Current focus is revamping the website homepage to guide new users


Legal Team Report - Jilayne[edit]

  • Working through 2.0 task list
  • Syncing with tech team schedule for release
  • Cross team topic- Standard Header field in list that applies to a subset of licenses (e.g. GPL, Apache)
    • Proposal is to remove the field as it becomes problematic with 2.0
    • Notice will go out to tech team/legal team


Tech Team Report - Kate[edit]

  • Fleshed out external SPDX document reference syntax. (currently sec 3.5, but may spin off to own section) and working on self reference (2.4)
  • Finishing off clarifying examples for relationship references (sec 8)
  • Extended the recognized checksums to include SHA256, MD5 (sec. 4.9, 6.4)
  • Decided to start off separate spec for inline references rather than include it in Appendix.
  • What's up for this month...
    • Gluing it all together and making available for other reviewers
    • Near term schedule: Draft Nov 14, feedback by Dec 1. 


Attendees[edit]

  • Phil Odence, Black Duck
  • Kirsten Newcomer, Black Duck
  • Pierre LaPonte, nexB 
  • Gary O’Neill, SourceA
  • Mark Gisi, Wind River
  • Scott Sterling, Palamida
  • Matt Germonprez, UNO
  • Jilayne Lovejoy, ARM 
  • Jack Manbeck, TI 
  • Mike Dolan, Linux Foundation
  • Paul Maddick, HP
  • Michael Herzog, nexB
  • Pierre G, AirBus
  • Others from project COTSAQ


Re: Next week's SPDX General Meeting & Nov Meeting Minutes

Philip Odence
 

corrected date…apologies

From: Phil Odence <podence@...>
Date: Wednesday, November 26, 2014 at 9:37 AM
To: "spdx@..." <spdx@...>
Subject: Next week's SPDX General Meeting & Nov Meeting Minutes

ANOTHER SPECIAL PRESENTATION: In addition to our normal agenda, I’ve asked my friend Bruno Grasset from Valeo to talk about his company’s adoption of SPDX. Valeo is one of the world’s largest suppliers to the automotive industry. Bruno runs Valeo's open source compliance program and one of the technical leaders of GENIVI. 

I’m trying to line up other speakers from complementary projects and companies using SPDX for future General Meetings…ideas welcome.


GENERAL MEETING

Meeting Time: Thurs, Dec 4, 8am PT / 10 am CT / 11am ET / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html

Conf call dial-in:
Conference code:  7812589502
Toll-free dial-in number (U.S. and Canada):  (877) 435-0230
International dial-in number: (253) 336-6732
For those dialing in from other regions, a list of toll free numbers can be found: 
https://www.intercallonline.com/portlets/scheduling/viewNumbers/viewNumber.do?ownerNumber=6053870&audioType=RP&viewGa=false&ga=OFF

 
Administrative Agenda
Attendance

Valeo Presentation


Technical Team Report - Kate


Legal Team Report - Jilayne


Business Team Report – Jack


Cross Functional Issues – Phil




General Meeting/Minutes/2014-11-06

  • Attendance: 15+
  • Lead by Phil Odence
  • Minutes of October meeting approved

Cross Functional Issues, Special Presentation from Polarsys – Phil[edit]

  • Presentation from Polarsys COTSAQ project http://polarsys.org/proposals/cotsaq
    • OSS tool for managing software BoMs
    • SPDX connections
      • First will use SPDX License List
      • Connecting with code scanners through SPDX


Biz Team Report - Jack[edit]

  • Last call cancelled. Call in an hour.
  • Current focus is revamping the website homepage to guide new users


Legal Team Report - Jilayne[edit]

  • Working through 2.0 task list
  • Syncing with tech team schedule for release
  • Cross team topic- Standard Header field in list that applies to a subset of licenses (e.g. GPL, Apache)
    • Proposal is to remove the field as it becomes problematic with 2.0
    • Notice will go out to tech team/legal team


Tech Team Report - Kate[edit]

  • Fleshed out external SPDX document reference syntax. (currently sec 3.5, but may spin off to own section) and working on self reference (2.4)
  • Finishing off clarifying examples for relationship references (sec 8)
  • Extended the recognized checksums to include SHA256, MD5 (sec. 4.9, 6.4)
  • Decided to start off separate spec for inline references rather than include it in Appendix.
  • What's up for this month...
    • Gluing it all together and making available for other reviewers
    • Near term schedule: Draft Nov 14, feedback by Dec 1. 


Attendees[edit]

  • Phil Odence, Black Duck
  • Kirsten Newcomer, Black Duck
  • Pierre LaPonte, nexB 
  • Gary O’Neill, SourceA
  • Mark Gisi, Wind River
  • Scott Sterling, Palamida
  • Matt Germonprez, UNO
  • Jilayne Lovejoy, ARM 
  • Jack Manbeck, TI 
  • Mike Dolan, Linux Foundation
  • Paul Maddick, HP
  • Michael Herzog, nexB
  • Pierre G, AirBus
  • Others from project COTSAQ


Next week's SPDX General Meeting & Nov Meeting Minutes

Philip Odence
 

ANOTHER SPECIAL PRESENTATION: In addition to our normal agenda, I’ve asked my friend Bruno Grasset from Valeo to talk about his company’s adoption of SPDX. Valeo is one of the world’s largest suppliers to the automotive industry. Bruno runs Valeo's open source compliance program and one of the technical leaders of GENIVI. 

I’m trying to line up other speakers from complementary projects and companies using SPDX for future General Meetings…ideas welcome.


GENERAL MEETING

Meeting Time: Thurs, Nov 6, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html

Conf call dial-in:
Conference code:  7812589502
Toll-free dial-in number (U.S. and Canada):  (877) 435-0230
International dial-in number: (253) 336-6732
For those dialing in from other regions, a list of toll free numbers can be found: 
https://www.intercallonline.com/portlets/scheduling/viewNumbers/viewNumber.do?ownerNumber=6053870&audioType=RP&viewGa=false&ga=OFF

 
Administrative Agenda
Attendance
Approve Minutes- http://wiki.spdx.org/view/General_Meeting/Minutes/2014-11-06

Valeo Presentation


Technical Team Report - Kate


Legal Team Report - Jilayne


Business Team Report – Jack


Cross Functional Issues – Phil




General Meeting/Minutes/2014-11-06

  • Attendance: 15+
  • Lead by Phil Odence
  • Minutes of October meeting approved

Cross Functional Issues, Special Presentation from Polarsys – Phil[edit]

  • Presentation from Polarsys COTSAQ project http://polarsys.org/proposals/cotsaq
    • OSS tool for managing software BoMs
    • SPDX connections
      • First will use SPDX License List
      • Connecting with code scanners through SPDX


Biz Team Report - Jack[edit]

  • Last call cancelled. Call in an hour.
  • Current focus is revamping the website homepage to guide new users


Legal Team Report - Jilayne[edit]

  • Working through 2.0 task list
  • Syncing with tech team schedule for release
  • Cross team topic- Standard Header field in list that applies to a subset of licenses (e.g. GPL, Apache)
    • Proposal is to remove the field as it becomes problematic with 2.0
    • Notice will go out to tech team/legal team


Tech Team Report - Kate[edit]

  • Fleshed out external SPDX document reference syntax. (currently sec 3.5, but may spin off to own section) and working on self reference (2.4)
  • Finishing off clarifying examples for relationship references (sec 8)
  • Extended the recognized checksums to include SHA256, MD5 (sec. 4.9, 6.4)
  • Decided to start off separate spec for inline references rather than include it in Appendix.
  • What's up for this month...
    • Gluing it all together and making available for other reviewers
    • Near term schedule: Draft Nov 14, feedback by Dec 1. 


Attendees[edit]

  • Phil Odence, Black Duck
  • Kirsten Newcomer, Black Duck
  • Pierre LaPonte, nexB 
  • Gary O’Neill, SourceA
  • Mark Gisi, Wind River
  • Scott Sterling, Palamida
  • Matt Germonprez, UNO
  • Jilayne Lovejoy, ARM 
  • Jack Manbeck, TI 
  • Mike Dolan, Linux Foundation
  • Paul Maddick, HP
  • Michael Herzog, nexB
  • Pierre G, AirBus
  • Others from project COTSAQ


Blog post about compliance status on the .NET core

Nuno Brito
 

Hello,

Sharing a blog post about my look into the open source compliance practice of the .NET core.

http://nunobrito1981.blogspot.com/2014/11/looking-into-net-license-compliance.html

The result is made available in SPDX format and posted on github.


With kind regards,
Nuno Brito

--
http://triplecheck.net
phone: +49 615 146 03187


You had 940 site visitors in October - see more with Google Analytics

Scott Lamons
 

FYI...    Since May of this year (our first full month of data collection), we're averaging around 900 visits per month ranging from roughly 850-950.   No noticeable growth trend although the percentage of new visitors seems encouraging.   The bounce rate seems a bit high but I don't have a point of reference -- might be interesting if someone knows what it is for other sites; for example, linuxfoundation.org.    

-Scott

---------- Forwarded message ----------
From: Google Analytics <analytics-noreply@...>
Date: Wed, Nov 12, 2014 at 6:15 AM
Subject: You had 940 site visitors in October - see more with Google Analytics
To: spl518@...


Google Analytics Your Customer ID: All Web Site Data
Sign in
A snapshot of your website in October.
Take a few minutes to review last month's website performance for SPDX. We hope that these key metrics and our monthly tip will help you identify new opportunities for your business.
VISITS
940
The total number of visits to your site this month
BOUNCE RATE
54%
Your bounce rate shows how many people leave your site without visiting any other pages on your site
TIME ON SITE
02:08
The average amount of time someone spends on your site in a single session
AVERAGE PAGES
3
The average number of pages viewed in a single session
Did you know your bounce rate is 54% this month?
Have a clear purpose or call to action on your landing page — one of the biggest causes of a high bounce rate is visitor confusion.
         Sign in         
Your Audience
TOP COUNTRIES
TOP COUNTRY  
319
Visits

United States
124
Visits

Germany
63
Visits

Japan
58
Visits

United Kingdom
39
Visits

Brazil
Your Location report tells you where your visitors live around the world. Make sure you’re promoting your business in all the right areas.
    View your Location report    
UNIQUE VISITORS
586 New Visitors
95 Return Visitors
681 Unique Visitors
New Visitors / Return Visitors
How people are finding you
TOP KEYWORDS
spdx 11 Visits
spdx fossology 3 Visits
package data 2 Visits
commercial tools 1 Visits
lega teams 1 Visits
ADWORDS VISITS
0 AdWords Visitors
940 Non-AdWords Visitors
940 Total Visitors
547 New Visitors / 547 Return Visitors
Did you know you can attract more potential customers to your site with paid online ads? Learn more about how Google AdWords can help or link your existing AdWords account.
    Sign up for AdWords    
TOP SOCIAL SOURCES
62%
Stack Overflow
12%
LinkedIn
12%
YouTube
12%
WordPress
0%
TOP REFERRERS
google / organic  
401 Visits
(direct) / (none)  
357 Visits
semalt.semalt.com / referral  
35 Visits
linuxfoundation.jp / referral  
21 Visits
linuxfoundation.org / referral  
19 Visits
What’s happening when users come to your site
TOP PAGES
Visits
Homepage /spdx-license- ... /SPDX-specific ... /tools /spdx-license- ...
  Pageviews   Page Exits
379
EXITS
Did you know that 379 (40.3%) people exited your site at Homepage?
    View your Exit Pages    
Your Goals
NO GOALS SET UP YET
0
Use goals to track customer interactions that matter to your business the most, such as purchases or number of pages viewed.
ABANDONMENT RATE
0%
The percentage of people who start but do not complete one of your goals
Your goals completion sources
Looks like you don’t have any Goals set up yet. Use Goals to keep an eye on customer actions that matter to you, like clicks and sales.
    Set up Goals    
Thank you for reviewing our report. If you have questions please see our more detailed reporting overview. And please take a few minutes to provide feedback.
    Go to your account    
Join the Community Ask Experts Learn
© 2014 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043

This email was sent to spl518@... because you indicated that you'd like to receive updates and tips about your Google Analytics account. If you don't want to receive such emails in the future, please unsubscribe here. You can also change your preferences on your account's Google Analytics Email Communications page by logging into https://www.google.com/analytics/settings/my_account




SPDX in Action webinar announcement - November 11th @ 12pm PST (3pm EST)

Mark Gisi
 

I would like to  announce an upcoming SPDX webinar on Tuesday November 11th  @ 12pm PST  - it  will include  a commercial case study on how SPDX data was used in the license compliance review process to deliver higher quality license data that also reduced the time and overall cost of the review.

   

Registration  Link: http://www.omm.com/SnapshotFiles/54302027-c9b6-4403-968f-37baaeea7fd3/Subscriber.snapshot

 

- Mark

 

Mobile friendly | Online version

 

Date & Time
Tuesday, November 11
Noon - 1:00pm PT

RSVP
Click here
 to register to attend by webinar or in person 

Webinar

Live streaming and available for playback for 30 days

Live Location

O’Melveny & Myers LLP
Two Embarcadero Center, 28th Floor
San Francisco, CA 94111

Open source software is the foundation of today’s computing landscape. Companies using open source software need to implement business processes to help them comply with open source licenses. SPDX is a community project, sponsored by the Linux Foundation, that helps standardize the delivery of open source licensing information.

Heather Meeker, partner at O’Melveny & Myers, and Mark Gisi, Senior IP Manager, Wind River Systems (and member of the SPDX working group), discuss the benefits of SPDX, and how you can leverage SPDX to streamline license compliance.


An application will be made in California and New York for 1 hour of CLE credit.

 

 

Portions of this communication may contain attorney advertising. Prior results do not guarantee a similar outcome. Please direct all inquiries regarding our conduct under New York's Code of Professional Responsibility to O’Melveny & Myers LLP, Times Square Tower, 7 Times Square, New York, NY, 10036, Phone:+1-212-326-2000. © 2014 O'Melveny & Myers LLP. All Rights Reserved.

Unsubscribe | Forward to a Friend

 

 


Reminder: Thursday SPDX General Meeting with SPECIAL presentation

Philip Odence
 

PLEASE MAKE A EFFORT TO JOIN FOR THIS SPECIAL PRESENTATION: In addition to our normal agenda, we will be getting a presentation about project from Polarsys that is complementary to and looking to leverage SPDX. Polarsys is an organization cultivating the development of open source tools for embedded systems development. Their project COTSAQ aims to help systems companies manage IP. Presenters will be Pierre Gaufillet from AirBus and Mickael Bouet, the COTSAQ project lead.

I’m trying to line up other speakers from complementary projects and companies using SPDX for future General Meetings…ideas welcome.


GENERAL MEETING

Meeting Time: Thurs, Nov 6, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html

Conf call dial-in:
Conference code:  7812589502
Toll-free dial-in number (U.S. and Canada):  (877) 435-0230
International dial-in number: (253) 336-6732
For those dialing in from other regions, a list of toll free numbers can be found: 
https://www.intercallonline.com/portlets/scheduling/viewNumbers/viewNumber.do?ownerNumber=6053870&audioType=RP&viewGa=false&ga=OFF

 
Administrative Agenda
Attendance

Polarsys Presentation 
2. If requested, enter your name and email address. 
3. If a password is required, enter the meeting password: P0lar$ys 
4. Click "Join"

Technical Team Report - Kate


Legal Team Report - Jilayne


Business Team Report – Jack


Cross Functional Issues – Phil


October SPDX General Meeting Minutes

Philip Odence
 




  •  Attendance: 7
  • Lead by Phil Odence
  • Minutes of Sept meeting approved

Cross Functional Issues – Phil

  • 2.0 Schedule
    • Proposed reset of phased release to be ratified by Tech Team - roughly:
      • Release candidate targeted early Nov
      • Presentations to and feedback for OpenChain group- Dec
      • RC 2 January; tooling development in parallel
      • Final Release at CollabSummit in Feb


Biz Team Report - Jack

  • Website
    • University Participation page is up
    • Looking at Google Analytics
      • Pointed to need to revamping front page to make it roll-based
      • Continuing to look for improvements for website
  • 2.0 Press Release on hold


Legal Team Report - Jilayne

  • Call today agenda
  • Focus is what’s needed for 2.0
    • Need to work out license list release timing implications
    • How do we have pre-release version of LL?


Tech Team Report - Kate

  • No meeting this week
  • Still cleaning up relationship types, license types
  • Email discussion about new release schedule and approach.


Attendees

  • Phil Odence, Black Duck
  • Scott Sterling, Palamida
  • Jack Manbeck, TI
  • Pierre LaPonte, nexB
  • Scott Lamons, HP
  • Matt Germonprez, UNO
  • Jilayne Lovejoy, ARM 


SPDX General Meeting today.

Philip Odence
 

It’s that time again. Sorry for the late reminder.

GENERAL MEETING

Meeting Time: Thurs, Oct 2, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html

Conf call dial-in:
Conference code:  7812589502
Toll-free dial-in number (U.S. and Canada):  (877) 435-0230
International dial-in number: (253) 336-6732
For those dialing in from other regions, a list of toll free numbers can be found: 
https://www.intercallonline.com/portlets/scheduling/viewNumbers/viewNumber.do?ownerNumber=6053870&audioType=RP&viewGa=false&ga=OFF

 
Administrative Agenda
Attendance

Technical Team Report - Kate


Legal Team Report - Jilayne


Business Team Report – Jack


Cross Functional Issues – Phil
SPDX 2.0 Schedule
Synergy with OpenChain



Re: GitHub announces license selection in SPDX format

Hen
 

On Thu, Sep 18, 2014 at 8:32 AM, Philip Odence <podence@...> wrote:
Of course. Good thinking. (or, limited thinking on my part)
Would be interested to hear if anyone has more details. 

From: Kate Stewart <kate.stewart@...>
Reply-To: Kate Stewart <kate.stewart@...>
Date: Thu, 18 Sep 2014 06:44:14 -0700
To: Phil Odence <podence@...>, Nuno Brito <nuno.brito@...>, "spdx@..." <spdx@...>
Subject: Re: GitHub announces license selection in SPDX format

Hi Phil,
    I think that's just the drop down menu being shown (human readable), for selection.
Key is what's being stored (which is probably the short form).   But I'm just guessing here.

Hi Nuno,
    Thanks for flagging!

Kate 


On Thursday, September 18, 2014 5:37 AM, Philip Odence <podence@...> wrote:


It¹s rewarding to see the keepers of such a popular platform tip their hat
to SPDX and to continue to encourage proactive license selection in
general. I/we pushed this hard with them several years ago and there
wasn¹t a lot of interest. I have to say, though, I¹m not sure what Mr.
Balter means by ³SPDX compliant.² They didn¹t go with the short names as
we had advocated, more like our long form names but abbreviated in some
cases (e.g. GNU GPL v2.0 vs. GNU General Public License v2.0). Still I
don¹t want to detract from the effort.



On 9/18/14, 5:26 AM, "Nuno Brito" <nuno.brito@...> wrote:

>Good morning,
>
>Some good news to start the day:
>https://twitter.com/BenBalter/status/512330244729344000/photo/1
>
>
>With kind regards,
>Nuno Brito
>
>--
>email: nuno.brito@...
>phone:  +49 615 146 03187
>_______________________________________________
>Spdx mailing list
>Spdx@...
>https://lists.spdx.org/mailman/listinfo/spdx


_______________________________________________
Spdx mailing list
Spdx@...
https://lists.spdx.org/mailman/listinfo/spdx



_______________________________________________
Spdx mailing list
Spdx@...
https://lists.spdx.org/mailman/listinfo/spdx



Re: GitHub announces license selection in SPDX format

Philip Odence
 

Of course. Good thinking. (or, limited thinking on my part)
Would be interested to hear if anyone has more details. 

From: Kate Stewart <kate.stewart@...>
Reply-To: Kate Stewart <kate.stewart@...>
Date: Thu, 18 Sep 2014 06:44:14 -0700
To: Phil Odence <podence@...>, Nuno Brito <nuno.brito@...>, "spdx@..." <spdx@...>
Subject: Re: GitHub announces license selection in SPDX format

Hi Phil,
    I think that's just the drop down menu being shown (human readable), for selection.
Key is what's being stored (which is probably the short form).   But I'm just guessing here.

Hi Nuno,
    Thanks for flagging!

Kate 


On Thursday, September 18, 2014 5:37 AM, Philip Odence <podence@...> wrote:


It¹s rewarding to see the keepers of such a popular platform tip their hat
to SPDX and to continue to encourage proactive license selection in
general. I/we pushed this hard with them several years ago and there
wasn¹t a lot of interest. I have to say, though, I¹m not sure what Mr.
Balter means by ³SPDX compliant.² They didn¹t go with the short names as
we had advocated, more like our long form names but abbreviated in some
cases (e.g. GNU GPL v2.0 vs. GNU General Public License v2.0). Still I
don¹t want to detract from the effort.



On 9/18/14, 5:26 AM, "Nuno Brito" <nuno.brito@...> wrote:

>Good morning,
>
>Some good news to start the day:
>https://twitter.com/BenBalter/status/512330244729344000/photo/1
>
>
>With kind regards,
>Nuno Brito
>
>--
>email: nuno.brito@...
>phone:  +49 615 146 03187
>_______________________________________________
>Spdx mailing list
>Spdx@...
>https://lists.spdx.org/mailman/listinfo/spdx


_______________________________________________
Spdx mailing list
Spdx@...
https://lists.spdx.org/mailman/listinfo/spdx



Re: GitHub announces license selection in SPDX format

kate.stewart@...
 

Hi Phil,
    I think that's just the drop down menu being shown (human readable), for selection.
Key is what's being stored (which is probably the short form).   But I'm just guessing here.

Hi Nuno,
    Thanks for flagging!

Kate 


On Thursday, September 18, 2014 5:37 AM, Philip Odence <podence@...> wrote:


It¹s rewarding to see the keepers of such a popular platform tip their hat
to SPDX and to continue to encourage proactive license selection in
general. I/we pushed this hard with them several years ago and there
wasn¹t a lot of interest. I have to say, though, I¹m not sure what Mr.
Balter means by ³SPDX compliant.² They didn¹t go with the short names as
we had advocated, more like our long form names but abbreviated in some
cases (e.g. GNU GPL v2.0 vs. GNU General Public License v2.0). Still I
don¹t want to detract from the effort.



On 9/18/14, 5:26 AM, "Nuno Brito" <nuno.brito@...> wrote:

>Good morning,
>
>Some good news to start the day:
>https://twitter.com/BenBalter/status/512330244729344000/photo/1
>
>
>With kind regards,
>Nuno Brito
>
>--
>email: nuno.brito@...
>phone:  +49 615 146 03187
>_______________________________________________
>Spdx mailing list
>Spdx@...
>https://lists.spdx.org/mailman/listinfo/spdx


_______________________________________________
Spdx mailing list
Spdx@...
https://lists.spdx.org/mailman/listinfo/spdx



Re: GitHub announces license selection in SPDX format

Philip Odence
 

It¹s rewarding to see the keepers of such a popular platform tip their hat
to SPDX and to continue to encourage proactive license selection in
general. I/we pushed this hard with them several years ago and there
wasn¹t a lot of interest. I have to say, though, I¹m not sure what Mr.
Balter means by ³SPDX compliant.² They didn¹t go with the short names as
we had advocated, more like our long form names but abbreviated in some
cases (e.g. GNU GPL v2.0 vs. GNU General Public License v2.0). Still I
don¹t want to detract from the effort.

On 9/18/14, 5:26 AM, "Nuno Brito" <nuno.brito@...> wrote:

Good morning,

Some good news to start the day:
https://twitter.com/BenBalter/status/512330244729344000/photo/1


With kind regards,
Nuno Brito

--
email: nuno.brito@...
phone: +49 615 146 03187
_______________________________________________
Spdx mailing list
Spdx@...
https://lists.spdx.org/mailman/listinfo/spdx