Spdx-legal@lists.spdx.org

Home Messages Hashtags Subgroups

Messages

Between

and

Hi folks, I made some updates to some of the documentation files in the Github repo today related to some conversation on the call. Would love to have some feedback. See:

By J Lovejoy · #2725 ·

Meeting today, Feb. 27

Hello all, the next regularly-scheduled SPDX legal team meeting will be today, Thursday, Feb. 27 at 9AM PT / noon ET. = = = = = Join Zoom Meeting https://zoom.us/j/611416785 Meeting ID: 611 416

By Steve Winslow · #2724 ·

Re: Invitation: SPDX joint tech/legal team call @ Tue Feb 25, 2020 1pm - 2pm (EST) (spdx-legal@lists.spdx.org)

Hi Steve, I think the description of the event contains an error: 13:00 EST ought to be 18:00 in UTC, not 17:00. Sending this to the list in case anybody was going by what the description says

By Carmen Bianca Bakker · #2723 ·

Invitation: SPDX joint tech/legal team call @ Tue Feb 25, 2020 1pm - 2pm (EST) (spdx-legal@lists.spdx.org)

You have been invited to the following event. SPDX joint tech/legal team call When Tue Feb 25, 2020 1pm – 2pm Eastern Time - New York Where https://zoom.us/j/663426859

By Steve Winslow · #2722 ·

Meeting today, Feb. 13

Hello all, the next SPDX legal team meeting will be today, Thursday, Feb. 13 at 9AM PT / noon ET. = = = = = Join Zoom Meeting https://zoom.us/j/611416785 Meeting ID: 611 416 785 One tap

By Steve Winslow · #2721 ·

3.8 License List release

Hello all, The version 3.8 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, 9 new licenses

By Steve Winslow · #2720 ·

Meeting today, Jan. 30

The next SPDX legal team meeting will be today, Thursday, Jan. 30 at 9AM PT / noon ET. We'll focus on finalizing items to be included in the upcoming 3.8 release. Best, Steve = = = = = Join Zoom

By Steve Winslow · #2719 ·

Re: New License/Exception Request: selinux-nsa-declaration

Thanks Mark, I've created an issue to track this new request at: https://github.com/spdx/license-list-XML/issues/966 Steve -- Steve Winslow Director of Strategic Programs The Linux

By Steve Winslow · #2718 ·

New License/Exception Request: selinux-nsa-declaration

1. Provide a proposed Full Name for the license or exception. selinux-nsa-declaration-1.0 2. Provide a proposed Short Identifier.

By Mark Atwood (Amazon.com) · #2717 ·

Re: Meeting today, Jan. 16

Hi Steve, I got called out of town for a family emergency and won't be able to make it today. Things are going ok. Sorry, Paul Sent from my Verizon, Samsung Galaxy smartphone

By pmadick · #2716 ·

Meeting today, Jan. 16

The next SPDX legal team meeting will be today, Thursday, Jan. 16 at 9AM PT / noon ET. Today we'll focus on following up on status for the pending 3.8 issues that were selected during the last call

By Steve Winslow · #2715 ·

[ANNOUNCE] Open source license compliance tooling meeting and hackathon on January 31st 2020 pre-FOSDEM fringe event in Bruxelles, Belgium

If you care about open source compliance automation and if you are going to FOSDEM there is a one day hackathon and meeting taking place the day before FOSDEM on Friday January 31st as "fringe" event,

By Philippe Ombredanne · #2714 ·

Meeting today, Jan. 2

Happy new year, all! The next SPDX legal team meeting will be today, Thursday, Jan. 2 at 9AM PT / noon ET. Since the 3.8 release was delayed due to the holidays and canceled team meetings, today's

By Steve Winslow · #2713 ·

Invitation: SPDX legal team meeting @ Every 2 weeks from 12pm to 1pm on Thursday from Thu Jan 2, 2020 to Thu Dec 31, 2020 (EST) (spdx-legal@lists.spdx.org)

You have been invited to the following event. SPDX legal team meeting When Every 2 weeks from 12pm to 1pm on Thursday from Thu Jan 2, 2020 to Thu Dec 31, 2020 Eastern Time - New

By Steve Winslow · #2712 ·

Happy Holidays (and let's reconvene in the New Year)

Hi all, Due to the end of the year craziness many of us are experiencing and resulting low-turnout at recent meetings and on the mailing list, we are going to call it for the year and reconvene (with

By J Lovejoy · #2711 ·

Re: SPDX-License-Identifier for composite-licensed source files

Hi Richard, I think both your possibilities work, and with the current state of art, I would agree with Kate, Jilayne and Gary. On the other hand it seems to me that exactly how to mark source

By Matija Šuklje · #2710 ·

Re: SPDX-License-Identifier for composite-licensed source files

+1 on Kate’s recommendation. This format will be properly parsed by the SPDX Tools parsers (the 3 parsers I am aware of) and I believe represents the intent behind the AND operator. Gary

By Gary O'Neall · #2709 ·

Re: SPDX-License-Identifier for composite-licensed source files

Agree. And also agree with Richard’s comment about avoiding legal interpretations. When you say that the license is “X AND Y” you are saying both licenses apply. Which is the fact for this file.

By J Lovejoy · #2708 ·

Re: SPDX-License-Identifier for composite-licensed source files

Hi Richard, I suspect the others will comment as well, but I would hope to see "SPDX-License-Identifier: MPL-2.0 AND Apache-2.0" as a summary. The second approach may become ambiguous to

By Kate Stewart · #2707 ·

SPDX-License-Identifier for composite-licensed source files

Suppose you're dealing with the following source file legal notice (example taken from https://www.mozilla.org/en-US/MPL/2.0/permissive-code-into-mpl/, itself adapted from the examples discussed by

By Richard Fontana · #2706 ·

681 - 700 of 3405

Home Hashtags Subgroups Terms