Hi  :

We are planning to migrate to SPDX Licenses.

If we are using general MIT  License . Can we replace the existing license file with SPDX Identifier  ?

Do we need to generate new  SPDX Document and publish them regularly   ?

Regards

Ashok Madugula

Hi Ashok,

Based on the license matching guidelines, the text matches MIT.  You can test the license text using the SPDX online tools at http://13.57.134.254/app/check_license/

Gary

HI  :

We are using the following license which is almost same as X11  . Do we need to raise a request for new SPDX Identifier  ?

If so , can you let us know the process ?

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

LICENSE START

Copyright (C) YYYY – YYYY Xilinx, Inc.  All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

LICENSE END 

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

This is almost same as X11 .

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

X11 License

Copyright (C) 1996 X Consortium

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium.

X Window System is a trademark of X Consortium, Inc.

Regards

Ashok Madugula

Here’s a new invite for 2020. Please accept the recurring meeting

Note there will be no SPDX General Meeting in January.

****

New dial in number: 415-881-1586  

No PIN needed

The weblink for screenshare:
https://www.uberconference.com/room/spdxteam

MEETING MINUTES FOR REVIEW: http://spdx.org/wiki/meeting-minutes-and-decisions

In addition to the General Meeting reminder: As you may know, a couple of months ago (with great help from Shane Coughlin) we launched a short survey to help steer the future of SPDX. The doors will close on the survey Dec 31. We would like to get as many responses as possible from anyone who has even the lightest level of involvement or interest. So, please, fill this out yourself and forwarded it on to any of your contacts the might be willing to provide some input. I promise we will take the feedback seriously. 

 THANK YOU!

 https://forms.gle/FK2zR5TV5E44W7Cc7

GENERAL MEETING

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

Conf call dial-in:

New dial in number: 415-881-1586

No PIN needed

The weblink for screenshare will stay the same at: 
http://uberconference.com/SPDXTeam

Administrative Agenda

Attendance

Minutes Approval:   

Technical Team Report – Kate/Gary

Legal Team Report – Jilayne/Paul

Outreach Team Report – Jack

Any Cross Functional Issues –All

I will not be available for this month’s meeting, but the show must go on.

Phil

GENERAL MEETING

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

Conf call dial-in:

New dial in number: 415-881-1586

No PIN needed

The weblink for screenshare will stay the same at: 
http://uberconference.com/SPDXTeam

Administrative Agenda

Attendance

Minutes Approval:   https://wiki.spdx.org/view/General_Meeting/Minutes/2019-10-03

Technical Team Report – Kate/Gary

Legal Team Report – Jilayne/Paul

Outreach Team Report – Jack not available

Any Cross Functional Issues –All

We are seeking public comments for the next version of OpenChain specification which will conclude on December 10^th.

For those new to the specification  - The OpenChain project has developed  a specification that defines a core set of requirements that a trusted open source compliance program is expected to satisfy.   To obtain a better understanding of the goals and the context in which the specification was developed before providing feedback, you can review the following FAQ list.

The big change over the current 2.0 version was reformatting the document layout into one acceptable for ISO submission and adoption.  Other than very minor clarification edits, the content has largely remained unchanged. If a company is conformant with version 2.0 - they would remain conformant with 2.1.

The current draft is available at:

   https://wiki.linuxfoundation.org/_media/openchain/openchainspec-2.1.draft.pdf

Past readers of the spec might find the marked up version useful:

   https://wiki.linuxfoundation.org/_media/openchain/OpenChainSpec-2.1.draft.MarkUp.pdf    

You can send feedback via:

·        the Mailing list: the list;

·        the issues wiki: issues list; or

·        replying to me directly if you wish to remain anonymous (mark.gisi@...)

best,

Mark

Mark Gisi | Wind River | Director, IP & Open Source

Tel (510) 749-2016 | Fax (510) 749-4552

The Nov General Meeting is moving out a week due to conflicts for most of the Core team.

I also have a conflict on the 14^th, so someone else will chair in my stead.

Phil  

*****

I’m extending this recurring meeting to run through 2019. Please accept so it is updated on your calendar, however no need to send a response to me.

New dial in number: 415-881-1586

No PIN needed

The weblink for screenshare will stay the same at:
https://www.uberconference.com/room/spdxteam

MEETING MINUTES FOR REVIEW: http://spdx.org/wiki/meeting-minutes-and-decisions

https://wiki.spdx.org/view/General_Meeting/Minutes/2019-10-03

< General Meeting‎ | Minutes

·         Attendance: 10

·         Lead by Kate Stewart

·         Minutes of Sept. meeting approved 

Contents

 [hide] 

·         1 Legal Team – Steve

·         2 Tech Team Report - Kate

·         3 Outreach Team Report - Jack

·         4 Cross Functional

·         5 Attendees

·         Working on the next release – 3.7

·         Looking for volunteers to put together the XML and test files

·         Targeting next week

·         Small release

·         Trend – licenses that don’t strictly follow the open source definition (e.g. source available but some proprietary restrictions)

·         Discussion on whether these should be included and update the license inclusion principles – more information available at https://github.com/spdx/license-list-XML/issues/925

·         Looking to make a decision early in the 3.8 release

·         SPDX Lite

·         Changes are added as a pull request and will likely be accepted soon

·         Security fields to be added in 2.2

·         Working with Uday on a Google Doc which will be turned into a pull request

·         Coordinating with Todo group and others

·         Looking at adjusting the minimum required fields to allow for security use cases without all the licensing

·         General support for reducing the number of mandatory fields

·         Steve will bring to the legal team the discussion on removing the of the mandatory legal related fields

·         GSoC – completed, all students passed

·         SPDX Tool updates which include the GSoC contributions are all checked in

·         Plan to update the spdxtools website within the next 2 weeks

·         Amazon will start using the namespace features soon

·         Request to add specification for the namespace

·         Mark agreed and will create a pull request

·         The license ID web page can also be updated

·         Survey

·         Working on summarizing the survey results

·         Several compliance and SPDX related talks planned for the Open Source Summit Europe in Lyon at the end of the month

·         Steve Winslow, LF

·         Gary O’Neall, SourceAuditor

·         Jack Manbeck, TI

·         Mark Atwood, Amazon

·         Paul Madick, Dimension Data

·         Nisha Kumar, VMWare

·         Rose Judge, VMWare

·         Matija Šuklje

·         William Bartholomew, Github

·         Dave McLoghlin, Rogue Wave

We are still trying to line up a presentation from one of the GSoC students who has not yet presented; that’s up in the air.

I will not be able to join so one of the other Core Team members will host.

Best regards,

Phil

GENERAL MEETING

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

Conf call dial-in:

New dial in number: 415-881-1586

No PIN needed

The weblink for screenshare will stay the same at: 
http://uberconference.com/SPDXTeam

Administrative Agenda

Attendance

Minutes Approval:   https://wiki.spdx.org/view/General_Meeting/Minutes/2019-09-05

Possible GSoC Presentations

Technical Team Report – Kate/Gary

Legal Team Report – Jilayne/Paul

Outreach Team Report – Jack

Any Cross Functional Issues –All

Uberconference changed their platform; I’ve updated the link below.

Please accept this recurring meeting.

Thanks,

Phil

*****

I’m extending this recurring meeting to run through 2019. Please accept so it is updated on your calendar, however no need to send a response to me.

New dial in number: 415-881-1586

No PIN needed

The weblink for screenshare will stay the same at:
https://www.uberconference.com/room/spdxteam

MEETING MINUTES FOR REVIEW: http://spdx.org/wiki/meeting-minutes-and-decisions

< General Meeting‎ | Minutes

·         Attendance: 17

·         Lead by Phil Odence

·         Minutes of Aug meeting approved 

Contents

 [hide] 

·         1 Special Presentations - Hiro Fukuchi, Sony

·         2 Tech Team Report - Gary

·         3 Legal Team Report - Jilayne/Paul/Steve

·         4 Outreach Team Report - Jack

·         5 Cross Functional -

·         6 Attendees

·         SPDX- Lite

·         Open Chain Japan Work Group

·         Member companies- Toyota, Denso, Panasonic, Pioneer, Sony, Fujitsu, Olympus, Renesas

·         Common Problem- Can’t get OSS information from suppliers (HW vendors, ODMs, SOC, partners…in Asia (China/Taiwan) and Japan

·         They don’t have complete information

·         Don’t have the tools to generate and evaluate

·         SPDX Lite is part of guidelines

·         Fits in at a fairly high level of maturity

·         OpenChain - “Making Process”

·         SPDX (and OSS tooling) - “Improving Process”

·         Most suppliers are at low levels of maturity

·         Looking not to fork, but to expand usage of SPDX Lite

·         Lite Description

·         Subset of SPDX

·         Minimum requirement

·         Can be manually generated

·         Proved in actual business use

·         Scenarios

·         1 Unskilled suppliers

·         Useful at a lower level of maturity than SPDX requires

·         2 Non-engineering Staff

·         More understandable by Legal and Procurement staff.

·         Skilled suppliers would still use full SPDX

·         OpenChain compliant suppliers would be sophisticated enough

·         Question: Is SPDX Lite fully SPDX compliant

·         Yes, all mandatory fields are included in SPDX Lite plus some of the optional fields may be included.

·         Spec

·         Being worked in a GitHub repo

·         Set up for pull requests for 2.2

·         Anyone who has ideas or proposed changes, please submit as a pull request

·         One in place is SPDX Lite

·         Proposal is as an Appendix

·         Thought is a profile for a specific use case

·         Could be first of a number of profiles

·         Tools

·         Successful conclusion to GSoC

·         All passed

·         A number of new libraries including Python, Golang

·         Mentors and students were great

·         Record number of projects

·         Challenge now is integrating and putting into production

·         All legal team tools have been submitted as pull requests

·         Should be up and running in a month or so.

·         Legal Team License Submittal Demo (GSoC)

·         Video and minutes available

·         Need to update contribution instructions

·         Team call today

·         License List

·         3.7 release at end of month

·         Fewer licenses in release that some recents

·         Recent discussions have been more high level on principles than specific licenses

·         Survey

·         Has been out for a few months

·         37 responses so far

·         Will make one more pass

·         Looking at presenting at Gen Meeting in Nov

·         Philipe has been talking to the Python community about using SPDX License IDs and expressions in Python package manifest

·         Could be a model for other communities

·         …some of which have been using formally or informally

·         Potentially high leverage

·         RUST and Go are using sporadically

·         None

·         Phil Odence, Black Duck/Synopsys

·         Steve Winslow, LF

·         Gary O’Neall, SourceAuditor

·         Jack Manbeck, TI

·         Nicolas Toussaint, Orange

·         Mark Atwood, Amazon

·         Jilayne Lovejoy, Canonical

·         Hiro Fukuchi, Sony

·         Shinsuke Kato, Panasonic

·         Philippe Ombrédanne- nexB

·         Michael Herzog, NexB

·         Patrice-Emmanuel Schmitz, Trasys International, European Commission

·         Richard Fontana, Red Hat

·         Mark Baushke, Juniper

·         Paul Madick, Dimension Data

·         Nisha Kumar, VMWare

·         David Marr, Qualcomm

Hi all,

Thank you for the meeting.

I would like to send my slides.