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
Steve:
On Wed, Apr 11, 2018 at 8:56 PM, Steve Winslow
wrote:
> 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 star
Hi Steve,
Nice page!
It may be worth noting (perhaps in the ‘How’ section) that the SPDX ID should
only replace license text, and that copyright notices should remain (otherwise
there is a danger of overzealous replacement of both license text + copyright).
From: spdx-tech-boun...@lists.spdx.
Thanks Philippe!
Were you looking for the v3.0 License List form of IDs? There's a
"GPL-2.0-or-later" expression in the animation =)
(...or if it's not showing up, let me know...)
Awesome to hear that Scancode is detecting these.
On Wed, Apr 11, 2018 at 3:38 PM, Philippe Ombredanne
wrote:
> S
Thanks Sam! Good point on the copyright notice. I'll add something to
clarify that those should remain in place.
I also think that this site could benefit from an FAQs page to go into more
detail on some items. If people have suggestions for questions / answers,
feel free to send them my way and I
There is a FAQ page on the site or do you mean for the new pages you are
working on? The existing one could always use an overhaul.
By the way, great job.
Jack
From: spdx-tech-boun...@lists.spdx.org
[mailto:spdx-tech-boun...@lists.spdx.org] On Behalf Of Steve Winslow
Sent: Wednesday, April 11
That looks amazing! Please give a shout when it’s OK to share.
From: on behalf of Steve Winslow
Date: Wednesday, April 11, 2018 at 2:57 PM
To: "spdx-tech@lists.spdx.org"
Cc: "jilayne.love...@arm.com"
Subject: [spdx-tech] SPDX short-form IDs site
Resent-From: Yev Bronshteyn
Resent-Date: Wedne
On Wed, Apr 11, 2018 at 02:56:38PM -0400, Steve Winslow wrote:
> I've been working on a few pages on the SPDX website on why and how
> to use SPDX short-form IDs.
This looks good to me :). A few minor nits:
> This is intended to be developer-focused, usable by someone who
> isn't otherwise famil
Hi John,
Steve Winslow 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
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 cl
Hi Steve,
Steve Winslow 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
On Wed, Apr 11, 2018 at 01:39:03PM -0700, W. Trevor King wrote:
> The centered entries in the table from [11] caught me out, and I
> initially thought the beginning ong the “Apache-2.0 AND (MIT OR
> GPL-2.0-only)” explanation was a later paragraph in the “Apache-2.0
> AND MIT” explanation. You may
No problem, Steve. I think this all looks great, but we definitely need to be
consistent. The advice we came up with in Appendix V was pretty well vetted, so
I think that’s safe to stay within those boundaries.
Along the same lines: this suggestion should NOT be added: “The MIT and
BSD-1-
Jilayne Lovejoy writes:
> Hi John,
>
> Steve Winslow 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
Way cool 😊
Looks great.
Gary
From: spdx-tech-boun...@lists.spdx.org On
Behalf Of Steve Winslow
Sent: Wednesday, April 11, 2018 1:57 PM
To: spdx-tech@lists.spdx.org
Cc: Jilayne Lovejoy
Subject: [spdx-tech] SPDX short-form IDs site
Hello all,
I've been working on a few pages on th
On Wed, Apr 11, 2018 at 02:59:20PM -0600, Jilayne Lovejoy wrote:
> No problem, Steve. I think this all looks great, but we definitely
> need to be consistent. The advice we came up with in Appendix V was
> pretty well vetted, so I think that’s safe to stay within those
> boundaries.
>
> Along the s
W. Trevor King:
> I think that would be clearer if, instead of scoping this as “SPDX IDs”, you
> scoped it as “SPDX License Expression Comments” or some such.
Agreed. Perhaps call these "SPDX license comments" - since that's what they
are?
> Along those lines, I wish the comment tag had been
>
On Wed, Apr 11, 2018 at 09:52:39PM +, Wheeler, David A wrote:
> W. Trevor King:
> > I think that would be clearer if, instead of scoping this as “SPDX
> > IDs”, you scoped it as “SPDX License Expression Comments” or some
> > such.
>
> Agreed. Perhaps call these "SPDX license comments" - since
18 matches
Mail list logo