[IMPORTANT] Concrete proposals!

Andreas Raab andreas.raab at gmx.de
Mon May 12 09:44:04 UTC 2003


Hi Göran,

> I am not sure what you mean. The Guide wouldn't just decide 
> the issue - but he/she would make sure the ball is kept
> rolling and discussed and eventually also is responsible
> for boiling down a decision from it all.

Agree. But the question is (dare I say it again? ;-): Which process? How are
decisions made?

> And we are talking about a *general decision process* for the 
> community regardless of issue at hand - I can't see what
> "reducing the image" has to do with this.

I understand that this is a more general process but it seems to me that
we're doing just fine for a large part. For example, I could have posted a
[PROP] requesting that we come up with some process for solving these issues
but there seems to be a general agreement on discussing these issues right
here (or at least I haven't seen anyone saying "please shut up and discuss
it elsewhere" ;-)

In other words, it seems as if the "itch of the day" is about what happens
with contributions and that's why I was concentrating on these issues.

> But anyway - "including package XYZ." can mean different things.

Right. And I want to figure out what people can expect in this area. That's
what my note was all about.

> Since you are mentioning the update stream it sounds like you meant 
> "stuff it into the minimal/basic/full image".

That'd be one way of dealing with it.

> But if you instead meant "make package XYZ be a part of the official
> Squeak" it would mean that package XYZ, depending on its nature, would
> be a part of minimal/basic/full *as a package*.

That'd be another way of dealing with it.

> And secondly, if XYZ is an enhancement to code currently in the
> image (and said code will of course eventually be turned into a 
> package) then we can lift it into the updatestream as long as it
> doesn't go against the partitioning effort.

That'd be a third way of dealing with it.

All in all, there are various ways to go about these issues but it needs to
be understood what the process is and what happens in the course of the
process.

Cheers,
  - Andreas



More information about the Squeak-dev mailing list