Dear Scott,
On Oct 3, 2013, at 12:33 PM, "Lamons, Scott (Open Source Program
Office)" mailto:scott.lam...@hp.com> wrote:
>
> Thanks for updating this page. In particular for adding the rationale
> for why tagging is important in the Introduction section. For me, the
> main impetus of adding the l
Dear David,
In message <9f8e44bc27e22046b84ec1b9364c66a1a8054aa...@exch07-4850.ida.org> you
wrote:
>
> If there can be agreement on a very short license "meta-tag" - and I
> have a strong preference for a version that lets me do it in 1-line-
> then I'll start using it. I suspect others would do
Dear D M German,
In message <524e2cda.c22de00a.39d5.8...@mx.google.com> you wrote:
>
> David> From a programmer's perspective I think the "cryptic" approach is FAR
> David> superior. There are lots of tools that can quickly examine files and
> David> return text with the pattern "SPDX-Lic
Dear Philip Odence,
In message you wrote:
> LICENSE ID
> I think I'm on the same page as Daniel. From "SPDX-License-Identifier:
> MIT" someone ignorant of SPDX can infer/guess at the meaning, but you can
> imagine one liners (like Bradley's suggestion "License:
> spdx-license=IDENTIFIER") that wo
Dear Mark,
In message <01813e194c768044a6486db30b5338ccb711e...@ala-mba.corp.ad.wrs.com>
you wrote:
>
> I understand the need to keep it simple for the sake of adoption.
> However, if it is too simple we run the risk of mega-tagging doing
> more damage than good. If one is concerned about pursui
Dear Mark,
In message <01813e194c768044a6486db30b5338ccb711e...@ala-mba.corp.ad.wrs.com>
you wrote:
>
> Example 1:
> --
> File: ./cairo-1.10.2.tar.gz.txt/cairo-array.c (see attachment 1)
> NOTICE (simplified): "The file is licensed to you under either the LGPL-2.1
> or MPL-1.1 at your o
Dear David,
In message <9f8e44bc27e22046b84ec1b9364c66a1a8054aa...@exch07-4850.ida.org> you
wrote:
>
> SPDX-License-Identifier: LGPL-2.1 OR MPL-1.1
...
> In general, we all want both simplicity (so people will USE it) and
> expressiveness (so it can be USEFUL). The trick is getting there...
I d
Hi Wolfgang,
The "AND" situation would occur if you have a file which contains code from
two or more different sources using two or more different licenses. In that
case, I believe you would need to satisfy the obligations of all licenses
(note: I'm not a lawyer so I am not proposing or providing
