[ANSI-Smalltalk] Process proposal
Chris Winemiller
c-winemiller at adventact.com
Mon Feb 18 14:00:23 GMT 2008
I read the proposal, and among the "desirable" properties are these:
"* the technology compatibility kit should be available under a
*GPL-compatible
license*;
* a reference implementation working on at least one implementation of
Smalltalk should be itself available under an OSI-approved, *GPL-compatible
license.*"
The GPL is anathema to many (including myself). Why is it necessary to
put a technology compatibility kit or reference implementation under GPL
at all? If you want to ensure that commercial Smalltalk providers will
*not *absorb a reference implementation into their products, GPL is the
quickest way to do it.
Chris
Paolo Bonzini wrote:
> Hi all,
>
> I have written a draft of how our own open process might work. It is
> called STEP and, as the name may suggest, it is roughly based on the
> Python process (PEP). I mailed it to Bruce privately and he suggested
> to make it public.
>
> The main changes from PEP are the following:
>
> 1) the concepts of a reference implementation, expert group and
> maintenance are inspired from JCP (of course the RI is different due
> to Smalltalk-specific issues);
>
> 2) the editors are fixed in PEP, while I made them a voluntary position;
>
> 3) the states are a little different (with some inspiration from
> Bugzilla...), both to reflect the voluntary nature of being a STEP
> editor, and in some cases because I thought this way is better;
>
> 4) the process includes the forwarding of the open specification to
> the ANSI committee;
>
> 5) some parts (notably "Successful discussion of a STEP") are mutuated
> from Wikipedia policies and essays instead.
>
> If there is consensus for at least the basic structure of the
> proposal, I will put it on the GNU Smalltalk wiki so that it can be
> edited by anyone. The STEPs themselves could be hosted there (there
> are some modules, in the CMS I am using, that would help the management).
>
> Citing the document itself, "we try to build consensus around a STEP,
> but if that is not possible, you can always submit a competing STEP."
>
> Cheers,
>
> Paolo
> ------------------------------------------------------------------------
>
> _______________________________________________
> ANSI-Smalltalk mailing list
> ANSI-Smalltalk at lists.openskills.org
> http://lists.openskills.org/cgi-bin/mailman/listinfo/ansi-smalltalk
>
--
Chris Winemiller
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openskills.org/pipermail/ansi-smalltalk/attachments/20080218/e23a81cc/attachment.html
More information about the ANSI-Smalltalk
mailing list