Hello all,
There will be no Legal Team call tomorrow (Thursday, Nov. 23) due to the US
holiday.
Thanks,
Steve
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#3471): https://lists.spdx.org/g/Spdx-legal/message/3471
Mute This Topic: https
On 11/10/21 11:07 PM, Warner Losh wrote:
On Wed, Nov 10, 2021 at 8:40 PM J Lovejoy wrote:
Perhaps Warner can give us an overview of the FreeBSD project’s
use of SPDX identifiers.
I'm ready to go if there's space in the agenda. My rehearsal of the
talk clocks in at about 15
On Wed, Nov 10, 2021 at 8:40 PM J Lovejoy wrote:
> Hi all,
>
> We have our regularly scheduled call tomorrow, Thursday at 10 am mountain
> standard time. (the US has now pushed our clocks forward, so we should be
> back to our normal time zone gap differences)
>
> Perha
Hi all,
We have our regularly scheduled call tomorrow, Thursday at 10 am mountain
standard time. (the US has now pushed our clocks forward, so we should be back
to our normal time zone gap differences)
Perhaps Warner can give us an overview of the FreeBSD project’s use of SPDX
identifiers
Hi all,
Tomorrow’s regularly scheduled legal team call will be a joint call with the
tech team to continue the conversation about the licensing fields and
consolidation of such for the 3.0 spec.
By way of background or reminder:
Currently, all license-related fields are contained within the
Hi all,
The SPDX legal team has its regular bi-weekly call tomorrow, Thursday at noon,
Eastern Daylight Savings time (note: The US moved our clocks forward, but I
believe the UK and Europe has yet to do that, so time diff may still be an hour
different from usual).
As noted in the email below
Hello all,
The next SPDX legal team call will be tomorrow, June 13 at 12:00PM ET /
9:00AM PT.
The agenda will be focused on identifying which of the many open issues can
be finalized prior to the 3.6 release (currently planned for the end of the
month), or which need to be pushed to 3.7.
the call tomorrow.
5. #670 - same comment as #692
[SDW] This has been outstanding with no response for longer than SATA (2 /
#717 above). I suggest closing this without adding.
6. #611 - new license: Froala - this is another one that we’ve been sitting
on for some time. We’ve had 3 lawyers lean
Hi all,
We are not in what should be the final days of prep for the next release.
Looking over the list of issues tagged for 3.4, I’m not sure we’ll
realistically get them all over the line, but we will focus on the remaining
issues and what we can close out in the next week to prepare for
miliarize yourself with this topic before our call tomorrow.
Thanks,
Jilayne
SPDX Legal Team co-lead
opensou...@jilayne.com
___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal
Happy Thanksgiving to all the US based folks and enjoy having a “free hour” on
your calendar for those outside the US.
Cheers,
Jilayne
SPDX Legal Team co-lead
opensou...@jilayne.com
___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
J Lovejoy wrote:
The issue identified on the call today (and Mark will correct me if I've
misstated) is that when AND is used at the file level (Section 4), it's
clear that both licenses apply to the given file. However, when AND is used
at the package level (Section 3), it could mean, for
Of Philippe Ombredanne
Sent: Friday, May 15, 2015 8:04 AM
To: SPDX-legal
Subject: The meaning of AND in license expressions [was:Re: call
tomorrow, agenda]
Here is my understanding of how the AND thread started:
Mark brought up a concern about the meaning of AND.
He felt this could
13 matches
Mail list logo
