remove recommendation re: standard license headers

Hi all, We have some text at the bottom of this page https://spdx.dev/ids/ regarding the use of SPDX ids related to a recommendation about using and retaining standard headers when using/adding an SPDX id in source code. If memory serves, we wrote this at the time when use of SPDX ids in sou

Re: remove recommendation re: standard license headers

On Mon, Oct 25, 2021 at 9:43 AM J Lovejoy wrote: > Hi all, > > We have some text at the bottom of this page https://spdx.dev/ids/ > regarding the use of SPDX ids related to a recommendation about using and > retaining standard headers when using/adding an SPDX id in source code. > > If memory ser

Re: remove recommendation re: standard license headers

Thanks Warner! On 10/25/21 3:35 PM, Warner Losh wrote: On Mon, Oct 25, 2021 at 9:43 AM J Lovejoy > wrote: Hi all, We have some text at the bottom of this page https://spdx.dev/ids/ regarding the use of SPDX ids related to a

Re: remove recommendation re: standard license headers

Dear Jilayne, > Now that SPDX ids are used more widely and we know a bit more about > how scanning tools identify license headers in total - I think we can > remove this section altogether. I don't think SPDX needs to make a > statement either way and projects can make their own call, as we've > s

Re: remove recommendation re: standard license headers

On Sun, Nov 14, 2021 at 1:41 PM Sebastian Crane wrote: > Dear Jilayne, > > > Now that SPDX ids are used more widely and we know a bit more about > > how scanning tools identify license headers in total - I think we can > > remove this section altogether. I don't think SPDX needs to make a > > sta

Re: remove recommendation re: standard license headers

On Sun, Nov 14, 2021 at 9:35 PM Warner Losh wrote: > > > > On Sun, Nov 14, 2021 at 1:41 PM Sebastian Crane > wrote: >> >> Dear Jilayne, >> >> > Now that SPDX ids are used more widely and we know a bit more about >> > how scanning tools identify license headers in total - I think we can >> > remo

Re: remove recommendation re: standard license headers

On Mon, Nov 22, 2021 at 8:42 PM Neal Gompa wrote: > When code travels (e.g. Linux drm/ -> FreeBSD), > it's super-easy for compliance and understanding to be missed because > you've gutted the important information from the code itself. > There's no Linux drm code in FreeBSD proper. Certainly non

Re: remove recommendation re: standard license headers

On Mon, 2021-11-22 at 22:41 -0500, Neal Gompa wrote: > I'd personally rather we didn't even make the *appearance* of a > recommendation that SPDX-License-Identifiers are suitable replacements > for standard license headers. Especially with licenses that declare > *how* you're supposed to leverage a

Re: remove recommendation re: standard license headers

On Tue, Nov 23, 2021 at 3:47 AM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Mon, 2021-11-22 at 22:41 -0500, Neal Gompa wrote: > > I'd personally rather we didn't even make the *appearance* of a > > recommendation that SPDX-License-Identifiers are suitable replacements > > for

Re: remove recommendation re: standard license headers

On Tue, Nov 23, 2021 at 11:12 AM Warner Losh wrote: > > > > On Tue, Nov 23, 2021 at 3:47 AM Richard Purdie > wrote: >> >> On Mon, 2021-11-22 at 22:41 -0500, Neal Gompa wrote: >> > I'd personally rather we didn't even make the *appearance* of a >> > recommendation that SPDX-License-Identifiers ar

Re: remove recommendation re: standard license headers

top-posting as I'm not sure I can keep up with the various comments, but a bit of background: - the first idea of using the identifiers in source files from outside the main SPDX community came by way of a developer in Germany who wrote a blog post about it and sent me the link (I still don't re

Re: remove recommendation re: standard license headers

On Tue, Nov 23, 2021 at 11:12 AM Warner Losh wrote: > > I'll point out that the variations are an enormous pain in the ass for > FreeBSD > and create more uncertainty and compliance issues not less. If I don't > reproduce > every single license in the tree, verbatim, is that a material breach of

Re: remove recommendation re: standard license headers

: Richard Purdie , Neal Gompa , Sebastian Crane , SPDX-legal Subject: Re: remove recommendation re: standard license headers On Tue, Nov 23, 2021 at 11:12 AM Warner Losh mailto:i...@bsdimp.com>> wrote: I'll point out that the variations are an enormous pain in the ass for FreeBSD and

Re: remove recommendation re: standard license headers

X heading and leaving it up to projet what else then include in the file. FROM: Spdx-legal@lists.spdx.org on behalf of Michael Dolan DATE: Tuesday, November 30, 2021 at 8:28 PM TO: Warner Losh CC: Richard Purdie , Neal Gompa , Sebastian Crane , SPDX-legal SUBJECT: Re: remove recommendation re: st

Re: remove recommendation re: standard license headers

December 2021 19:05 To: phil.ode...@synopsys.com Cc: Michael Dolan ; Warner Losh ; Richard Purdie ; Neal Gompa ; Sebastian Crane ; SPDX-legal ; Geoffrey S. Knauth, Treasurer, FSF ; John Sullivan Subject: Re: remove recommendation re: standard license headers [External] I'm a bit confuse

Re: remove recommendation re: standard license headers

~ Steve Kilbane [2021-12-02 10:16 +0100]: > That said, I recognise projects with multiple contributors are a > different animal: removal of a license text from a contributed file by > a project maintainer who is not the original contributor is > potentially more problematic (IANAL), except possibly

Re: remove recommendation re: standard license headers

behalf >> of Michael Dolan >> DATE: Tuesday, November 30, 2021 at 8:28 PM >> TO: Warner Losh >> CC: Richard Purdie , Neal Gompa >> , Sebastian Crane , >> SPDX-legal >> SUBJECT: Re: remove recommendation re: standard license headers >> On Tue, Nov 23

Re: remove recommendation re: standard license headers

On Thu, Dec 2, 2021 at 12:18 PM J Lovejoy wrote: > > > Given that the Apache Foundation suggests either (their standard header or > the SPDX identifier) be used > http://www.apache.org/foundation/license-faq.html#Apply-My-Software and > the FSF supports generally the use of SPDX identifiers (not

Re: remove recommendation re: standard license headers

Dear Karen, > We know that the licenses require that license information and notices be > retained, as Mike Dolan pointed out. (In GPL-2.0 this text is "keep intact > all the notices that refer to this License"). Indeed, the full text of the license should always been available when using SPDX Li