|
Re: License of an open source license text
Hi Richard, thanks for the detailed explanation -- I think I understand your use case better now.
What I'd suggest would probably be that if you do want to represent this, one way might be to use a
Hi Richard, thanks for the detailed explanation -- I think I understand your use case better now.
What I'd suggest would probably be that if you do want to represent this, one way might be to use a
|
By
Steve Winslow
·
#2828
·
|
|
Re: License of an open source license text
Hi Steve,
Thanks for the reply, it matches my first take on understanding this
situation and is what we do today, however, we're seeing some push back
from our users and I do think they have a point
Hi Steve,
Thanks for the reply, it matches my first take on understanding this
situation and is what we do today, however, we're seeing some push back
from our users and I do think they have a point
|
By
Richard Purdie
·
#2827
·
|
|
Re: License of an open source license text
"Steve Winslow" <swinslow@...> writes:
It might be worth noting that one reason for this is that some license
texts are not themselves released under an open source license, and
"Steve Winslow" <swinslow@...> writes:
It might be worth noting that one reason for this is that some license
texts are not themselves released under an open source license, and
|
By
Russ Allbery
·
#2826
·
|
|
Re: License of an open source license text
Hi Richard,
Thanks for your email. A couple of thoughts, speaking just for myself:
When it comes to the question of "what license applies to a license text," I think this is something that has
Hi Richard,
Thanks for your email. A couple of thoughts, speaking just for myself:
When it comes to the question of "what license applies to a license text," I think this is something that has
|
By
Steve Winslow
·
#2825
·
|
|
Re: Validate license cross references: New fields to be added
In the spirit of “any suggestions and/or modifications will be very much appreciated”, I have inserted comments below.
In the spirit of “any suggestions and/or modifications will be very much appreciated”, I have inserted comments below.
|
By
Kaelbling, Michael <michael.kaelbling@...>
·
#2824
·
|
|
Meeting tomorrow, June 18
Hello all,
The next regularly-scheduled SPDX legal team meeting will be tomorrow, Thursday, June 18, at 9AM PDT / noon EDT.
I'm hoping that we can take a few minutes at the beginning of the meeting to
Hello all,
The next regularly-scheduled SPDX legal team meeting will be tomorrow, Thursday, June 18, at 9AM PDT / noon EDT.
I'm hoping that we can take a few minutes at the beginning of the meeting to
|
By
Steve Winslow
·
#2823
·
|
|
Re: Validate license cross references: New fields to be added
Hi Smith,
Thanks for your well-laid-out email and your GSoC proposal. Trying to think about this from the perspective of the LicenseListPublisher repository over time, I would imagine the validity and
Hi Smith,
Thanks for your well-laid-out email and your GSoC proposal. Trying to think about this from the perspective of the LicenseListPublisher repository over time, I would imagine the validity and
|
By
Brad Edmondson
·
#2822
·
|
|
Validate license cross references: New fields to be added
Hi all,
I am working on a Google Summer of Code project that emanates from this discussion/issue; concerning the validation of license cross references. Here is a link to my GSOC proposal.
The focus
Hi all,
I am working on a Google Summer of Code project that emanates from this discussion/issue; concerning the validation of license cross references. Here is a link to my GSOC proposal.
The focus
|
By
Smith Tanjong Agbor
·
#2821
·
|
|
Re: Correct handling of snippets
To be clear: I'm agnostic about identifying snippets in a fixed work.
REUSE looks to be trying to apply snippets to living open source code
and the case that specifically concerns me is where the
To be clear: I'm agnostic about identifying snippets in a fixed work.
REUSE looks to be trying to apply snippets to living open source code
and the case that specifically concerns me is where the
|
By
James Bottomley
·
#2820
·
|
|
Re: Correct handling of snippets
We spent quite a bit of time discussing snippets in the SPDX technical working group. There are definitely a number of issues and considerations.
At the conclusion of the discussions, there was a
We spent quite a bit of time discussing snippets in the SPDX technical working group. There are definitely a number of issues and considerations.
At the conclusion of the discussions, there was a
|
By
Gary O'Neall
·
#2819
·
|
|
Re: Correct handling of snippets
I really think this is a recipe for disaster. What's wrong with simply
keeping the licence of the file? since to be contributed, the snippet
must be compatible with it. To put it another way, why
I really think this is a recipe for disaster. What's wrong with simply
keeping the licence of the file? since to be contributed, the snippet
must be compatible with it. To put it another way, why
|
By
James Bottomley
·
#2818
·
|
|
Correct handling of snippets
Hi all,
At REUSE, we currently discuss how to correctly handling snippets from a
third party, potentially under a different license [^1]. Since we strive
to make as much use of SPDX as possible, I
Hi all,
At REUSE, we currently discuss how to correctly handling snippets from a
third party, potentially under a different license [^1]. Since we strive
to make as much use of SPDX as possible, I
|
By
Max Mehl
·
#2817
·
|
|
Re: Meeting this Thursday, June 4 and joint legal/tech next Tuesday, June 9
Here a PR for the notes from the meeting:
https://github.com/spdx/meetings/pull/2
--V
Here a PR for the notes from the meeting:
https://github.com/spdx/meetings/pull/2
--V
|
By
VM Brasseur <vmb@...>
·
#2816
·
|
|
Invitation: SPDX joint legal / tech team meeting @ Tue Jun 9, 2020 1pm - 2pm (EDT) (spdx-legal@lists.spdx.org)
You have been invited to the following event.
SPDX joint legal / tech team meeting
When
Tue Jun 9, 2020 1pm – 2pm Eastern Time - New York
Where
https://zoom.us/j/663426859
You have been invited to the following event.
SPDX joint legal / tech team meeting
When
Tue Jun 9, 2020 1pm – 2pm Eastern Time - New York
Where
https://zoom.us/j/663426859
|
By
Steve Winslow
·
#2815
·
|
|
Meeting this Thursday, June 4 and joint legal/tech next Tuesday, June 9
Hello all, the next regularly-scheduled SPDX legal team meeting will be this Thursday, June 4 at 9AM PDT / noon EDT.
The main focus will be to review the status of issues for 3.10 that were assigned
Hello all, the next regularly-scheduled SPDX legal team meeting will be this Thursday, June 4 at 9AM PDT / noon EDT.
The main focus will be to review the status of issues for 3.10 that were assigned
|
By
Steve Winslow
·
#2814
·
|
|
License of an open source license text
Hi,
I work on the Yocto Project and we use SDPX identifiers when working
with open source licenses. An issue has come up and it was suggested I
ask about it here.
The question is quite
Hi,
I work on the Yocto Project and we use SDPX identifiers when working
with open source licenses. An issue has come up and it was suggested I
ask about it here.
The question is quite
|
By
Richard Purdie
·
#2813
·
|
|
Meeting this Thursday, May 21
Hello all, the next regularly-scheduled SPDX legal team meeting will be Thursday, May 21 at 9AM PDT / noon EDT.
Now that 3.9 has been released, there's a few things I'm hoping to focus on for this
Hello all, the next regularly-scheduled SPDX legal team meeting will be Thursday, May 21 at 9AM PDT / noon EDT.
Now that 3.9 has been released, there's a few things I'm hoping to focus on for this
|
By
Steve Winslow
·
#2812
·
|
|
#spdx
#spdx
donate
By
david.lebert.60@...
·
#2811
·
|
|
#spdx
#spdx
donate developpent
By
david.lebert.60@...
·
#2810
·
|
|
3.9 License List release
Hello all,
The version 3.9 release of the license list is now tagged and live at https://spdx.org/licenses.
Along with the usual assortment of documentation updates and markup tweaks, this is the
Hello all,
The version 3.9 release of the license list is now tagged and live at https://spdx.org/licenses.
Along with the usual assortment of documentation updates and markup tweaks, this is the
|
By
Steve Winslow
·
#2809
·
|