|
|
Re: New License/Exception Request
Hi Jilayne et al.
As Richard says, this is90% or more a direct translation of GPLv3. I haven’t done a detailedcomparison (this means doing a bilingual 3-way diff, and will do so during my
|
Hi Jilayne et al.
As Richard says, this is90% or more a direct translation of GPLv3. I haven’t done a detailedcomparison (this means doing a bilingual 3-way diff, and will do so during my
|
By
Malcolm Bain <malcolm.bain@...>
·
#1613
·
|
|
Re: New License/Exception Request
It appears to be for the most part a translation of GPLv3 into Spanish.
|
It appears to be for the most part a translation of GPLv3 into Spanish.
|
By
Richard Fontana
·
#1610
·
|
|
Re: New License/Exception Request
Thanks Jilayne,
As we discussed on today's call, I reviewed a Google translation of the license web page. Based on quick overview, it seems to be pretty standard copyleft. I agree that we should plan
|
Thanks Jilayne,
As we discussed on today's call, I reviewed a Google translation of the license web page. Based on quick overview, it seems to be pretty standard copyleft. I agree that we should plan
|
By
Brad Edmondson
·
#1609
·
|
|
Re: Net-SNMP license stack v. using license expressions
Thanks Mark,
FWIW I believe that Mark Baushke looked at the current version of the net-SNMP package during our call today and found that its constituent parts all pointed to a single top-level license
|
Thanks Mark,
FWIW I believe that Mark Baushke looked at the current version of the net-SNMP package during our call today and found that its constituent parts all pointed to a single top-level license
|
By
Brad Edmondson
·
#1608
·
|
|
Re: Net-SNMP license stack v. using license expressions
Mark,
Would appreciate being looped into the package licensing discussions. I
wrote the current npm package licensing metadata spec, as well as the
validating implementation.
Very grateful for all
|
Mark,
Would appreciate being looped into the package licensing discussions. I
wrote the current npm package licensing metadata spec, as well as the
validating implementation.
Very grateful for all
|
By
Kyle Mitchell
·
#1607
·
|
|
Re: Net-SNMP license stack v. using license expressions
http://net-snmp.sourceforge.net/about/license.html isnot a license but a license notice file. License expressions were initially designed to represent the licensing of a single file whether it be a
|
http://net-snmp.sourceforge.net/about/license.html isnot a license but a license notice file. License expressions were initially designed to represent the licensing of a single file whether it be a
|
By
Mark Gisi
·
#1606
·
|
|
Re: legal call Thursday
Meeting minutes have been posted for today and Dec 8:
http://wiki.spdx.org/view/Legal_Team/Minutes/2016-12-08
http://wiki.spdx.org/view/Legal_Team/Minutes/2016-12-22
Our next call will be January 8th
|
Meeting minutes have been posted for today and Dec 8:
http://wiki.spdx.org/view/Legal_Team/Minutes/2016-12-08
http://wiki.spdx.org/view/Legal_Team/Minutes/2016-12-22
Our next call will be January 8th
|
By
J Lovejoy
·
#1605
·
|
|
Net-SNMP license stack v. using license expressions
Hi Tech team,
We had a request to add the Net-SNMP license, which is actually a stack of 6 licenses: http://net-snmp.sourceforge.net/about/license.html
We’d like to get some input from the tooling
|
Hi Tech team,
We had a request to add the Net-SNMP license, which is actually a stack of 6 licenses: http://net-snmp.sourceforge.net/about/license.html
We’d like to get some input from the tooling
|
By
J Lovejoy
·
#1604
·
|
|
Re: New License/Exception Request
Hola,
We would like to add this license to the SPDX License List. None of us reviewing the license are fluent Spanish speakers. Could you verify that this is an open source license according to the
|
Hola,
We would like to add this license to the SPDX License List. None of us reviewing the license are fluent Spanish speakers. Could you verify that this is an open source license according to the
|
By
J Lovejoy
·
#1603
·
|
|
legal call Thursday
At the usual time!
Thursday at 18:00 GMT (10:00AM PT, 11:00 MT, 12:00 CT, 1:00PM ET).
Call this number: (United States): +1-857-216-2871
User PIN: 38633
International: visit the URL at
|
At the usual time!
Thursday at 18:00 GMT (10:00AM PT, 11:00 MT, 12:00 CT, 1:00PM ET).
Call this number: (United States): +1-857-216-2871
User PIN: 38633
International: visit the URL at
|
By
J Lovejoy
·
#1602
·
|
|
FYI - Changes to the git.spdx.org tools repositories
Greetings legal team,
Those of you on the tech mailing list have already seen the message below on the plans to change the git repositories which are currently on git.spdx.org over to
|
Greetings legal team,
Those of you on the tech mailing list have already seen the message below on the plans to change the git repositories which are currently on git.spdx.org over to
|
By
Gary O'Neall
·
#1601
·
|
|
Re: Short identifiers
Thanks Jilayne and Gary - that was the kind of information I was looking for!
Richard
|
Thanks Jilayne and Gary - that was the kind of information I was looking for!
Richard
|
By
Richard Fontana
·
#1600
·
|
|
Re: Short identifiers
Hi Richard,
Of course there are conventions! Gary already sent you the link. The only other thing I’d add that is too obvious to state on that list is that we make sure there are no other
|
Hi Richard,
Of course there are conventions! Gary already sent you the link. The only other thing I’d add that is too obvious to state on that list is that we make sure there are no other
|
By
J Lovejoy
·
#1599
·
|
|
Re: Short identifiers
Hi Richard,
I found this which describes the short identifier conventions:
https://spdx.org/spdx-license-list/license-list-overview#fields
Gary
|
Hi Richard,
I found this which describes the short identifier conventions:
https://spdx.org/spdx-license-list/license-list-overview#fields
Gary
|
By
Gary O'Neall
·
#1598
·
|
|
Short identifiers
Hi,
Are there any established SPDX standards or conventions for devising a
short identifier for a license? I assume not but wanted to check.
Richard
|
Hi,
Are there any established SPDX standards or conventions for devising a
short identifier for a license? I assume not but wanted to check.
Richard
|
By
Richard Fontana
·
#1597
·
|
|
SPDX Legal call reminder and Agenda
Reminder: SPDX legal call scheduled for tomorrow (Thursday) at 10am Pacific and 1pm Eastern Time.
Join the call:https://www.uberconference.com/spdxteam
Optional dial in number: 857-216-2871
PIN:
|
Reminder: SPDX legal call scheduled for tomorrow (Thursday) at 10am Pacific and 1pm Eastern Time.
Join the call:https://www.uberconference.com/spdxteam
Optional dial in number: 857-216-2871
PIN:
|
By
Paul Madick
·
#1596
·
|
|
Errors in "OSET Public License version 2.1" on SPDX
Team,
I noted some errors in your "OSET Public License version 2.1" while prepping it for inclusion in our KnowledgeBase here at Black Duck.
See: Paragraphs 6, 7 & 10 where the title of the paragraph
|
Team,
I noted some errors in your "OSET Public License version 2.1" while prepping it for inclusion in our KnowledgeBase here at Black Duck.
See: Paragraphs 6, 7 & 10 where the title of the paragraph
|
By
Steve Snow <ssnow@...>
·
#1595
·
|
|
Re: XML license review update & questions
Hi all,
Can two other attorneys review my edits to the <optional> and <body> tags for W3C? I think this is ready to merge but would like to get some more eyes on my call in commit
|
Hi all,
Can two other attorneys review my edits to the <optional> and <body> tags for W3C? I think this is ready to merge but would like to get some more eyes on my call in commit
|
By
Brad Edmondson
·
#1594
·
|
|
Re: XML license review update & questions
Thanks Jilayne,
It does help to get a reminder every once in a while to work on these. I'll see what I can do over the next few weeks.
1) License version & date in title field: I agree that version
|
Thanks Jilayne,
It does help to get a reminder every once in a while to work on these. I'll see what I can do over the next few weeks.
1) License version & date in title field: I agree that version
|
By
Brad Edmondson
·
#1593
·
|
|
XML license review update & questions
Hi All,
Quick update and a couple questions I came across in the XML markup that I am hoping we can resolve via email.
There are 89 remaining pull requests; 28 of those have been reviewed and tagged
|
Hi All,
Quick update and a couple questions I came across in the XML markup that I am hoping we can resolve via email.
There are 89 remaining pull requests; 28 of those have been reviewed and tagged
|
By
J Lovejoy
·
#1592
·
|
