[squeak-dev] The future of Squeak & Pharo
Miguel Enrique Cobá Martinez
miguel.coba at gmail.com
Sun Jun 28 20:58:22 UTC 2009
El dom, 28-06-2009 a las 08:59 -0700, Randal L. Schwartz escribió:
> >>>>> "Stéphane" == Stéphane Rollandin <lecteur at zogotounga.net> writes:
>
> Stéphane> I would suggest you switch to Pharo: it's there exactly to fit your
> Stéphane> expectations. Then you can let Squeak live its life, be it overly eccentric.
>
> For some, what I'm about to say is obvious. But for others, this might be a
> deal killer.
>
> Once Squeak core is included as part of the SFC, it will be a lot easier for a
> business to base its work on Squeak. If there's a question of code heritage,
> the SFLC will assist to provide "we stand together" support.
>
> For Etoys, this has already happened, in that VPRI is willing to put *its*
> legal resources behind the current code base.
>
> I know Pharo has just announced "mit license for everything", but there's
> no organization with other-than-volunteer resources that can certify that.
>
> And given that Pharo is derived from the same original apple-licensed
> code that had troubled Etoys and now taints Squeak core (until the 4.0
> effort is complete), I see this as a problem.
>
> For me, that means I cannot recommend Pharo for business development.
>
> What I would *like* to see, and am working towards as a member of the
> Squeak Leadership Team is:
>
> (a) squeak core gets clean MIT license, and joins SFC
> (b) Pharo's license-known updates get rewritten to apply to squeak core
>
> This would make something that is equivalent to Pharo, but with a clean
> license history.
>
> In essence, I'd like to bring Pharo "back into the fold", because there *are*
> advantages to having a clean license history that *is* supported by someone's
> paid lawyers, just as there are advantages to have "modernized" the legacy
> Squeak look-and-feel.
I don't know of any organization backing with lawyers the
FreeBSD/NetBSD/OpenBSD (MIT/BSD license) effort and of course that has
not avoid using this OSes in real organizations and for mission critical
operations.
Maybe that is not *as* necessary as thought.
Miguel Cobá
>
> I know this will mean some work to unruffle some feathers and make things work
> again for everyone. But I want that to happen.
>
More information about the Squeak-dev
mailing list
|