Update stream ideas for 3.8 (was Re: Squeak 3.8 status)

Chris Muller afunkyobject at yahoo.com
Thu Aug 12 17:48:36 UTC 2004


> I suggest we try The Simplest Possible Thing, which is probably this: 
> set up an alternate update stream, publish a code snippet that lets 
> anyone point their image to it, and hand out the upload password to 
> everyone with Master certification on SqP.  Then step back and see 
> what happens.  My guess is that, like wikis, the system will be more 
> robust than you give it credit for: 

I love this!  This is the direction I *think* I want the process to go.  Also

> if someone publishes a bad update, 
> someone else will quickly remove it, and life will go on.

emphasizes the idea I like that [minimizing the pain of bad updates] is the way
to go rather than trying to [prevent bad updates].  In other words, an upload
password still doesn't protect us from "oops" uploads from the Masters.  Even a
Master can make a mistake.  Not to mention, it seems to exclude those who are
not Masters from opportunity to participate.

So when a pain-causing update inevitably occurs, it would be nice to nimbly
side-step "utter chaos" with a simple "press of a button" to mark a particular
update to stay-out-of-my-image with a comment as to why.  If other peoples
comments build up about it, then

> someone else will quickly remove it, and life will go on.

I may be just dreaming here, perhaps this is not really possible, but it's a
nice dream nonetheless.

 - Chris



More information about the Squeak-dev mailing list