Re: [License-discuss] Copyright on APIs

2019-07-07 Thread Henrik Ingo
While I haven't closely followed the details of Oracle vs Google, purely from a layman and business standpoint it seems clear that Google did create Android / Dalvik exactly to be interoperable with Java. This means one can run the same Java source code on either platform and the java.* namespace o

Re: [License-discuss] Copyright on APIs

2019-07-07 Thread Pamela Chestek
On 7/7/2019 4:23 AM, Henrik Ingo wrote: > While I haven't closely followed the details of Oracle vs Google, > purely from a layman and business standpoint it seems clear that > Google did create Android / Dalvik exactly to be interoperable with > Java. This means one can run the same Java source c

Re: [License-discuss] Copyright on APIs

2019-07-07 Thread Lawrence Rosen
Hi Pam, Pam Chestek wrote this on 6/30/2019: > The [Oracle v. Google] case is about whether it was lawful to copy portions > of software to enhance the ease of development of software for an entirely > different software ecosystem. What is the relevance (or indeed, what is the definition

Re: [License-discuss] Copyright on APIs

2019-07-07 Thread Chris DiBona
On Sun, Jul 7, 2019 at 7:30 AM Pamela Chestek wrote: > > On 7/7/2019 4:23 AM, Henrik Ingo wrote: > > While I haven't closely followed the details of Oracle vs Google, purely > from a layman and business standpoint it seems clear that Google did create > Android / Dalvik exactly to be interoperabl

Re: [License-discuss] Copyright on APIs

2019-07-07 Thread John Cowan
On Sun, Jul 7, 2019 at 10:29 AM Pamela Chestek wrote: I believe this is an important distinction that is often missed. No, > Android is not compatible with Java and was not meant to be. > I don't know what that means. It's true that not every Java program can run on every platform, because plat

Re: [License-discuss] Copyright on APIs

2019-07-07 Thread Russell McOrmond
On Sun, Jun 30, 2019 at 6:44 PM Lawrence Rosen wrote: > Thank you again Patrice-Emanuel, and thanks also to the EU for a much > clearer explanation of functional software interfaces ("APIs") than the > brief but equally relevant provision in 17 USC 102(b). I hope the US > Supreme Court is as clea

Re: [License-discuss] Copyright on APIs

2019-07-07 Thread Bruce Perens via License-discuss
My opinion has been that gift-style licensing makes you an unpaid, and unappreciated, employee of big companies. The GPL and AGPL terms are hardly an unfair expectation of those folks. Having had my software installed in literally all lines of network-connected consumer devices, I feel that complia

Re: [License-discuss] Copyright on APIs

2019-07-07 Thread Thorsten Glaser
Bruce Perens via License-discuss dixit: >My opinion has been that gift-style licensing makes you an unpaid, and >unappreciated, employee of big companies. Definitely not. Employees get told what they can work on, how it should look in the end, and often enough how to work on it. With Ⓕ Copyfree

Re: [License-discuss] Copyright on APIs

2019-07-07 Thread Lawrence Rosen
Bruce Perens wrote: > My opinion has been that gift-style licensing makes you an unpaid, and > unappreciated, employee of big companies Having had my software installed > in literally all lines of network-connected consumer devices, I feel that > compliance with those [GPL] terms is a fair

Re: [License-discuss] Copyright on APIs

2019-07-07 Thread Russell McOrmond
On Sun, Jul 7, 2019 at 7:41 PM Bruce Perens via License-discuss < license-discuss@lists.opensource.org> wrote: > My opinion has been that gift-style licensing makes you an unpaid, and > unappreciated, employee of big companies. > We are talking about two entirely different things. This is not ab