[IMPORTANT] Concrete proposals!

Andreas Raab andreas.raab at gmx.de
Sat May 10 12:49:33 UTC 2003


Hi Göran,

Here are a couple of comments:

> -------
> Problem #1:
> The decision process is... well, do we even have one? ;-)
> 
> The protocol is for dealing with proposals. Python has a scheme called
> PEPs - http://www.python.org/peps/.  (Python Enhancement Proposal). I
> would like to simply call ours "PROPs" - as in proposals. 
[...]
> Exactly how this Guide deals with this process is up to that person to
> figure out. That is called delegation. I would assume though that the
> Guide doing this looks hard at Python for inspiration.

I see two problems with the above. The first (and most important one) is
that it's unclear what the intended result of a [PROP] is. Let's say I'm
writing a [PROP] for including package XYZ. I write it up and the guide in
question says, "fine, let's do it". Then, what would happen? Considering
that much of the talk is about reducing image size etc. it seems unlikely
that this is just going to be pushed into an update stream, right? 

A second problem I see is the lack of documentation in the above. I liked
very much the pointer to Zope's Fishbowl process sent by Stef. There's
always a good chance that there are objections and it needs to be clear what
the problems were and how to address them. For example, consider a case in
which you have some package where someone (maybe from KCP) looks at it and
says "that's really bad engineering - there's about a gigazillion
#isKindOf:s in there not a single test etc. these guys ought to fix X, Y,
and Z before this gets in". Let's say that this goes back to the author and
the author says, okay, he's going to fix it. Then he's running out of time
and things get forgotten. Some time later, some jerk (like me ;) is angrily
requesting to know why this never made it.

It feels to me that good documentation in this process is absolutely
essential. It allows people to see what's happening without having to follow
each individual discussion on Squeak-Dev, it allows people to chime in if
help is needed (in the above for example, someone else could address the
problems if the author agrees) etc.


Cheers,
  - Andreas



More information about the Squeak-dev mailing list