Open Licensing for future Squeak

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Open Licensing for future Squeak

Brad Fuller
In July, Squeak 1.1 was released with the APSL2 license. Is that right?
There was further discussion on how other/future versions of Squeak
could be open - or at least discussion of what needed to be done. Was
there any conclusion? Does anyone know the status? Is there a team
looking at this? Squeak Foundation perhaps?

My recollection is that the discussion stopped w/o conclusion.

brad

--
brad fuller
sonaural: www.sonaural.com
personal: www.bradfuller.com
www.oreillynet.com/pub/au/2184



Reply | Threaded
Open this post in threaded view
|

Re: Open Licensing for future Squeak

Markus Gälli-3
Andreas Raab told me after my quest to change the license "at least"  
for the current vms:

- The VM is a binary and not source, thus the OSS discussion would  
not apply.
- None of the VM makers/maintainers is interested in this task at the  
moment, as the task is not important enough for them _now_
- Changing the license of the VM might actually be _harder_ than  
relicensing the image code as all the plugins had to be looked through
- If you wanted to help, you needed to classify all the changes to  
the VM from 1.1: Who did what and when... then you had to ask the  
authors for their agreement with a relicensing.

In the long future it looks like Ian Piumarta's new Pepsi and Coke  
Meta-VM might lift off:

"2. Alan Kay, Kim Rose, and the eToys team spent the week in  
Cambridge at
the OLPC offices. They continue to make rapid progress towards the
integration of eToys into the laptop software environment (they also
provided useful feedback) and have eToys running on the laptop. Ian
Piumarta gave the OLPC team an update on his “dynamically reconfigurable
virtual machine”, which may be—in the longer term—the basis of  
programming
environment for the Laptop, in that it is simple, fast, extremely  
flexible
and quite eloquent."
http://laptop.media.mit.edu/laptopnews.nsf/latest/news?opendocument=
from yesterday.

Cheers,

Markus

  Squeak1.1 die Modifikationen zur VM zu klassifizieren: Was, wann,  
wer. Dann kannst Du die originalen Autoren fragen ob sie mit einer  
Relizensierung einverstanden sind.

On Sep 17, 2006, at 7:13 PM, Brad Fuller wrote:

> In July, Squeak 1.1 was released with the APSL2 license. Is that  
> right?
> There was further discussion on how other/future versions of Squeak
> could be open - or at least discussion of what needed to be done. Was
> there any conclusion? Does anyone know the status? Is there a team
> looking at this? Squeak Foundation perhaps?
>
> My recollection is that the discussion stopped w/o conclusion.
>
> brad
>
> --
> brad fuller
> sonaural: www.sonaural.com
> personal: www.bradfuller.com
> www.oreillynet.com/pub/au/2184
>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Open Licensing for future Squeak

Brad Fuller
Thanks Markus. To me, it would seem the image, with it's many classes,
is much more difficult to relicense than the VM.
See below

Markus Gaelli wrote:
> Andreas Raab told me after my quest to change the license "at least"
> for the current vms:
>
> - The VM is a binary and not source, thus the OSS discussion would not
> apply.
The VM is shipped binary, but the source is readily available. The
language seems ambiguous about the requirement to make VM source
available; even after modification of the VM (because, the modified
software would naturally be made available (in binary form) and satisfy
the license requirement)

> - None of the VM makers/maintainers is interested in this task at the
> moment, as the task is not important enough for them _now_
> - Changing the license of the VM might actually be _harder_ than
> relicensing the image code as all the plugins had to be looked through
I could see that. But, there are not a lot of plugins so finding each
owner and asking them if they are willing to license it openly (with
APSL2, or whatever the Squeak Foundation deems appropriate) should be
pretty easy. I remember reading Tim saying about his code, to the
effect: "sure"

But, what is the difference between "relicensing" and "changing the
license"? Seems the same to me.
> - If you wanted to help, you needed to classify all the changes to the
> VM from 1.1: Who did what and when... then you had to ask the authors
> for their agreement with a relicensing.
I could see that.
But, I wonder if we could:
 * find out who did what as much as we can.
 * contact them for the license change.
 * Where we can't identify the code author, we advertise looking for the
author.
   Give it 1 month for them to reply. No reply means that code portion
is now open source.
* For those who refuse to relicense, the code is removed

If we don't do it this way, it may never get done.
>
> In the long future it looks like Ian Piumarta's new Pepsi and Coke
> Meta-VM might lift off:
Ian: How is your code licensed? Is it owned by VP?