All, I am both impressed by the work Jilayne and others have put into the guidelines, and in strong sympathy with the general thrust Philippe reports from the conference. I didn't go to FOSDEM, but

> +1 from me on everything David said (quoted below for convenience) +1

+1 from me on everything David said (quoted below for convenience) cheers, Matija --

Hi Jilayne: On January 31st a compliance tooling meeting and hackathon took place in Brussels before FOSDEM [1]. One of the session topics was SPDX. Everyone there agreed that SPDX license inclusion

> A new poll has been created… I would prefer another option NOT in the poll (and thus have not voted): Treat it as just another license statement. There are multiple ways this kind of

Hi all, I’m sending this to both the legal and general mailing lists to ensure greatest visibility. The legal team has come up with a final draft of the license inclusion guidelines based on

Hi all, As has been mentioned on recent general calls, the legal team has been discussing a revision of the license inclusion guidelines off and on over the past year. We have a draft iteration that

Hello all, there has been a related thread going on in the spdx-legal list: see https://lists.spdx.org/g/Spdx-legal/topic/71831424 As mentioned in that thread, I would note the Legal Team's comments

Hi Michael, One concern with an "UNCOPYRIGHTABLE" identifier is that its existence could give rise to inappropriate application by authors. It's often quite difficult to conclusively determine whether

Hi Phil, all Quick update, we will have a guest speaker this week. Matthew Crawford will be discussing "Arm’s SPDX compliance file" Thanks, Kate

No guest speakers this month. And, I will be out so Kate will chair in my stead. GENERAL MEETING Meeting Time: Thurs, March 5, 8am PT / 10 am CT / 11am ET / 15:00UTC.

GENERAL MEETING Meeting Time: Thurs, Feb 6, 8am PT / 10 am CT / 11am ET / 15:00UTC. http://www.timeanddate.com/worldclock/converter.html Conf call dial-in: New dial in number: 415-881-1586 No

~ Gary O'Neall [2020-01-27 19:38 +0100]: As a side note, if you adopt the REUSE guidelines - so marking each file with copyright and licensing information using SPDX tags - creating an SPDX document

Hi Ashok, You can keep the existing license file in the distribution but we recommend adding SPDX identifiers to the source files – see https://spdx.org/ids for more information. For the

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

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 ?

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,

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