Thanks all (and Jilayne, apologies for the multiple copies!) Hi John, Jilayne is correct, I was aiming to frame this as something a bit more "user-friendly" for developers who might not be familiar with SPDX more broadly. I'll take another look at the language from the appendix, and will likely clarify the new page to recommend retaining standard license headers where provided by the license steward. Thanks for highlighting this.
Best, Steve On Wed, Apr 11, 2018 at 4:40 PM, Jilayne Lovejoy <[email protected]> wrote: > > Hi John, > > Steve Winslow <[email protected]> writes: > > > Hello all, > > > > I've been working on a few pages on the SPDX website on why and how > to use > > SPDX short-form IDs. This is intended to be developer-focused, > usable by > > someone who isn't otherwise familiar with SPDX, to get them to start > > putting SPDX identifiers in their source code. > > > > The first cut at this is now available at https://emea01.safelinks. > protection.outlook.com/?url=https%3A%2F%2Fspdx.org%2Fids& > data=02%7C01%7CJilayne.Lovejoy%40arm.com%7C103bfc98d6f64298bee708d59fe9 > e31a%7Cf34e597957d94aaaad4db122a662184d%7C0%7C1% > 7C636590749258954709&sdata=nLWJSZhEzVKkU04yPM1e8Ut9cWwxQh > mCYgVK%2BQYb9Gw%3D&reserved=0. There are a > > few "read more..." pages linked from that URL. These pages are > visible but > > not yet linked from the rest of the site. > > > > I can't find the previous links now, but I thought the previous "how to > use SPDX identifiers" page on the site recommended keeping the > file-level boilerplate text for, for example, the GPL, and included > examples along those lines. > > Yes, and it still does - the page you are thinking of is Appendix V to the > Spec https://spdx.org/specifications > (which you can go directly to via this link: https://spdx.org/spdx- > specification-21-web-version#h.twlc0ztnng3b ) > Which is the main source of explaining the use of SPDX identifiers in > source files. > Notably, in the second paragraph in Appendix V, it states: > > To the extent that a source file contains existing copyright and > license information, it is the SPDX project’s recommendation that > SPDX short identifiers be used to supplement, not replace that > information. When there is a standard header provided by the license > author, it is recommended to use such standard header (alone or in > combination with the SPDX short identifier). > > I think what Steve is doing here is trying to take that more formal advice > and create some more "user-friendly" guides for the website. > > (also removing my arm.com address from thread, so I stop getting this in > two places __ > > Jilayne > > > > > -- Steve Winslow Director of Strategic Programs The Linux Foundation Cell: +1.202.641.3047 Skype: 12026413047 [email protected]
_______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
