On Mon, Jun 18, 2018 at 9:20 AM, Mark Hatle <[email protected]> wrote:
> On 6/15/18 7:23 PM, Khem Raj wrote:
>> On Fri, Jun 15, 2018 at 3:48 PM Andre McCurdy <[email protected]
>> <mailto:[email protected]>> wrote:
>>     On Fri, Jun 15, 2018 at 3:36 PM, Khem Raj <[email protected]
>>     <mailto:[email protected]>> wrote:
>>     > On Fri, Jun 15, 2018 at 3:14 PM Mark Hatle <[email protected]
>>     <mailto:[email protected]>> wrote:
>>     >>
>>     >> On 6/15/18 3:16 PM, Andre McCurdy wrote:
>>     >> > From: AndrĂ© Draszik <[email protected] 
>> <mailto:[email protected]>>
>>     >> >
>>     >> > Some projects are starting to use it.
>>     >> >   https://spdx.org/licenses//BSD-1-Clause.html
>>     >> >
>>     >> > Signed-off-by: AndrĂ© Draszik <[email protected]
>>     <mailto:[email protected]>>
>>     >> > Signed-off-by: Ross Burton <[email protected]
>>     <mailto:[email protected]>>
>>     >> > (cherry picked from commit 77f692ecb39d880b2cb420850a31534860eb2cc5)
>>     >> > Signed-off-by: Andre McCurdy <[email protected]
>>     <mailto:[email protected]>>
>>     >> > ---
>>     >> >  meta/files/common-licenses/BSD-1-Clause | 9 +++++++++
>>     >> >  1 file changed, 9 insertions(+)
>>     >> >  create mode 100644 meta/files/common-licenses/BSD-1-Clause
>>     >> >
>>     >> > diff --git a/meta/files/common-licenses/BSD-1-Clause
>>     b/meta/files/common-licenses/BSD-1-Clause
>>     >> > new file mode 100644
>>     >> > index 0000000..ded8897
>>     >> > --- /dev/null
>>     >> > +++ b/meta/files/common-licenses/BSD-1-Clause
>>     >> > @@ -0,0 +1,9 @@
>>     >> > +
>>     >> > +Copyright (c) <YEAR>, <OWNER>
>>     >> > +All rights reserved.
>>     >> > +
>>     >> > +Redistribution and use in source and binary forms, with or without
>>     modification, are permitted provided that the following conditions are 
>> met:
>>     >> > +
>>     >> > +Redistributions of source code must retain the above copyright 
>> notice,
>>     this list of conditions and the following disclaimer.
>>     >> > +THIS SOFTWARE IS PROVIDED BY Berkeley Software Design, Inc. "AS IS"
>>     AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
>>     >>
>>     >> Hate to nitpick, but isn't BSDi defunct?  I don't think it makes 
>> sense to
>>     list
>>     >> BSDI, since as far as I know they never had a '1-Clause' license.
>>     >>
>>     >> Maybe a <Organization Here> would be more appropriate.
>>     >>
>>     >
>>     > I think we should sync the files we carry with SPDX e.g.
>>     > https://github.com/spdx/license-list-data/tree/master/text
>>
>>     It doesn't look like that will fix the inconsistencies... those
>>     versions are inconsistent too:
>>
>> We should report that to spdx folks since they
>> Work on licenses and might be interested in addressing this
>
> Agreed.  I think we need to get the SPDX to fix their examples, and then use
> them once they are fixed.
>
> As for our version of the code, I'd suggest the "<COPYRIGHT HOLDER>" (as in 
> the
> BSD-4-clause example) in all cases.

Agreed. So while Mark and Khem fix up master, is it OK for Armin to
backport the current version to rocko? Or should master and sumo be
updated first?

>>
>>     
>> https://github.com/spdx/license-list-data/blob/master/text/BSD-1-Clause.txt
>>     : THIS SOFTWARE IS PROVIDED BY Berkeley Software Design, Inc. "AS IS"
>>
>>     
>> https://github.com/spdx/license-list-data/blob/master/text/BSD-2-Clause.txt
>>     : THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>>     "AS IS"
>>
>>     etc...
>>
>>     >
>>     >> --Mark
>>     >>
>>     >> IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
>>     PURPOSE ARE
>>     >> DISCLAIMED. IN NO EVENT SHALL Berkeley Software Design, Inc. BE LIABLE
>>     FOR ANY
>>     >> DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 
>> DAMAGES
>>     >> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 
>> SERVICES;
>>     >> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 
>> CAUSED
>>     AND ON
>>     >> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR 
>> TORT
>>     >> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 
>> OF THIS
>>     >> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>>     >> > +
>>     >> >
>>     >>
>>     >> --
>>     >> _______________________________________________
>>     >> Openembedded-core mailing list
>>     >> [email protected]
>>     <mailto:[email protected]>
>>     >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>
-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to