[License-review] For Legacy Approval: LBNL BSD (Sebastian Ainslie)

[Sebastian Ainslie]

Hello all,

I'm not 100% sure how this works but I will try answer some of the questions
raised:

1. Berkeley Lab still uses this license for OSS releases today,
2. We use it because we cannot staff up/afford to have people to admin the
huge number of CLAs that would be required to accept all the contributions
we get across hundreds of software projects we run - this added para gives
us the necessary automatic grant if contributors contribute code back to
Berkeley Lab,
3. We wish it to be added to the OSI list somewhere much like the NASA Open
Source Agreement (federal) is. Note that as we are Dept of Energy (DOE)
funded we cannot use the verbatim BSD as DOE requires us to make certain
slight modifications therein anyway.

Thanks

Sebastian


Sebastian Ainslie
Principal Commercialization & Licensing Lead
Computing Sciences Area & Energy Geosciences Division
Intellectual Property Office
Lawrence Berkeley National Laboratory
www:   ipo.lbl.gov
e mail:  sainslie at lbl.gov



-----Original Message-----
From: License-review <license-review-bounces at lists.opensource.org> On Behalf
Of license-review-request at lists.opensource.org
Sent: Sunday, May 19, 2019 5:00 AM
To: license-review at lists.opensource.org
Subject: License-review Digest, Vol 78, Issue 42

Send License-review mailing list submissions to
	license-review at lists.opensource.org

To subscribe or unsubscribe via the World Wide Web, visit
	
http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource
.org

or, via email, send a message with subject or body 'help' to
	license-review-request at lists.opensource.org

You can reach the person managing the list at
	license-review-owner at lists.opensource.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of License-review digest..."


Today's Topics:

   1. Re: For Legacy Approval: LBNL BSD (Richard Fontana)


----------------------------------------------------------------------

Message: 1
Date: Sat, 18 May 2019 14:37:22 -0400
From: Richard Fontana <rfontana at redhat.com>
To: License submissions for OSI review
	<license-review at lists.opensource.org>
Subject: Re: [License-review] For Legacy Approval: LBNL BSD
Message-ID:
	<CAC1cPGwHXRLrLG93zDE_G_9dr-3NF2Cxn60JGT31wx77O_d7Fw at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

On Fri, May 17, 2019 at 9:48 AM Kevin P. Fleming <kevin+osi at km6g.us> wrote:
>
> The request is for "legacy" aprpoval, and if approved that will mean 
> that usage of the license is discouraged, right?
>
[Bruce Perens:]
> >>> Why do they still need to use this rather than the plain BSD license?

 Something I had overlooked: I gather from re-reading Sebastian's initial
post that LBNL is continuing to use this license. If so, why is it
appropriate for "Legacy" approval?  I had the sense that Legacy Approval was
for licenses that were no longer in active use but for which OSI approval
was for whatever reason considered desirable.

Richard



------------------------------

Subject: Digest Footer

_______________________________________________
License-review mailing list
License-review at lists.opensource.org
http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource
.org


------------------------------

End of License-review Digest, Vol 78, Issue 42
**********************************************