- Pharo-dev - lists.pharo.org

Re: [Pharo-project] How do we deal with submitted code

by David Pennell

I think you should get the agreements. Perhaps if you provided an easier way to send the agreement than physical mail or fax (e.g. signed, scanned and e-mail), you might get more signed agreements. Sending international mail is not something us provincial American's do very often. My sweet wife stood in the post office line to figure out how much postage it required. -david On Fri, Dec 19, 2008 at 8:51 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi guys > > sorry to insist on that point but should I get the license agreement > of commiters else we do not include their code? > or since the code is published on mantis and code published on mantis > is MIT we can use it. > > Personally I would favor that we do both > - collect the agreement from the good souls > - collect the fixed that are MIT and make sense. > > Stef > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 19, 2008

[Pharo-project] Fwd: could you sign the pharo license?

by StÃ©phane Ducasse

for archive Begin forwarded message: > From: Keith Hodges <keith_hodges(a)yahoo.co.uk> > Date: December 19, 2008 5:36:26 PM CEST > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: could you sign the pharo license? > > StÃ©phane Ducasse wrote: >> Because I would like to have a look at some of your code and I would >> like to avoid >> making mess. >> >> Stef > All my work is licenced FRFGPL > > FREELY RECEIVED FREELY GIVEN PUBLIC LICENSE > Version 1, December 2006 > > Copyright (C) 2006 Keith Hodges > > Everyone is permitted to copy and distribute verbatim or modified > copies of this license document, and changing it is allowed as long > as the name is changed. > > FREELY RECEIVED FREELY GIVEN PUBLIC LICENSE > TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION > > 0. You just DO WHATEVER YOU WANT TO > > this is my own derivative of the WTFPL > > Keith >

Dec. 19, 2008

Re: [Pharo-project] Fwd: [Etoys] [RELEASE] Etoys 4.0

by StÃ©phane Ducasse

do you know if Yoshiki has the list of method he changed to be clean? Stef On Dec 19, 2008, at 5:26 PM, Michael Rueger wrote: > > Hi all, > > did we agree whether to make sure Pharo 1.0 is license clean as well? > Just can't remember... > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 19, 2008

Re: [Pharo-project] Fwd: [Etoys] [RELEASE] Etoys 4.0

by Adrian Lienhard

The list for 1.0 is on the wiki: http://code.google.com/p/pharo/wiki/Milestones Adrian On Dec 19, 2008, at 17:28 , StÃ©phane Ducasse wrote: > I do not remember the list that we wrote on the board at Bern. > I'm sure we sent it to the list. > > Stef > > On Dec 19, 2008, at 5:26 PM, Michael Rueger wrote: > >> >> Hi all, >> >> did we agree whether to make sure Pharo 1.0 is license clean as well? >> Just can't remember... >> >> Michael >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 19, 2008

Re: [Pharo-project] Fwd: [Etoys] [RELEASE] Etoys 4.0

by StÃ©phane Ducasse

I do not remember the list that we wrote on the board at Bern. I'm sure we sent it to the list. Stef On Dec 19, 2008, at 5:26 PM, Michael Rueger wrote: > > Hi all, > > did we agree whether to make sure Pharo 1.0 is license clean as well? > Just can't remember... > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 19, 2008

Re: [Pharo-project] Fwd: [Etoys] [RELEASE] Etoys 4.0

by Michael Rueger

Hi all, did we agree whether to make sure Pharo 1.0 is license clean as well? Just can't remember... Michael

Dec. 19, 2008

[Pharo-project] Fwd: [Etoys] [RELEASE] Etoys 4.0

by StÃ©phane Ducasse

Begin forwarded message: > Resent-From: Bert Freudenberg <bert(a)freudenbergs.de> > From: Bert Freudenberg <bert(a)freudenbergs.de> > Date: December 17, 2008 12:28:26 AM CEST > Resent-To: Sugar Devel <sugar-devel(a)lists.sugarlabs.org> > To: Sugar Devel <sugar-devel(a)lists.sugarlabs.org> > Resent-Cc: OLPC Etoys <etoys(a)lists.laptop.org>, OLPC Development <devel(a)lists.laptop.org > > > Subject: [Etoys] [RELEASE] Etoys 4.0 > > (resent with new download URLs and a bit more prose) > > Hi folks, > > this is the first release of Etoys 4.0. The major version jump > signifies the end of our two-year relicensing effort. > > Originally released in 1996, Apple relicensed the Squeak core under > the Apache 2.0 license in October 2006 - thanks to Steve, Alan, and > the lawyers involved. Then, Viewpoints Research collected written > relicensing agreements from several hundred later contributors under > the MIT license - thanks to Kim, and the Squeak community volunteers. > Finally, all the code in Etoys not explicitly covered by a relicensing > agreement was removed, or rewritten, or reverted to an earlier version > - kudos to Yoshiki for the bulk of that work. > > Looking forward to see Etoys properly packaged in more distros now :) > > We may have broken stuff while removing and rewriting, so please > report any oddities you notice. > > Note: Etoys comes in two parts, one is the base (in Sugar Glucose, but > will actually run on all platforms given a recent Squeak virtual > machine) and one the activity bundle (in Fructose). Following the > naming conventions the lower-case "etoys" package is the base while > the activity is capitalized as "Etoys". > > == Sources == > > http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-4.0.2201.… > > http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-97.tar.gz > > == Packaged == > > http://etoys.laptop.org/rpms/etoys-4.0.2201-1.noarch.rpm > > http://etoys.laptop.org/rpms/Etoys-97.xo > > == News == > > * removed/reverted/rewrote all methods not covered by Apache/MIT > license > * various fixes (#8928, #8929, #8879, #9058, and others) > > - Bert (for the Etoys team) - > > > _______________________________________________ > Etoys mailing list > Etoys(a)lists.laptop.org > http://lists.laptop.org/listinfo/etoys >

Dec. 19, 2008

[Pharo-project] How do we deal with submitted code

by StÃ©phane Ducasse

Hi guys sorry to insist on that point but should I get the license agreement of commiters else we do not include their code? or since the code is published on mantis and code published on mantis is MIT we can use it. Personally I would favor that we do both - collect the agreement from the good souls - collect the fixed that are MIT and make sense. Stef

Dec. 19, 2008

[Pharo-project] cleaned pharo inbox

by StÃ©phane Ducasse

Just that you know. I will continue later but cleaned already some old submissions

Dec. 19, 2008

Re: [Pharo-project] New pharo-dev based on 10196

by StÃ©phane Ducasse

Thanks damien this is cool to see you doing that. THANKS! Stef On Dec 19, 2008, at 1:32 PM, Damien Cassou wrote: > http://code.google.com/p/pharo/wiki/Downloads?tm=2 > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 19, 2008