Stephan Eggermont wrote:

>  >There is one problem which we had in the past: a team of dedicated
>  >people doing a black voodoo behind the scenes, and nobody aware what
>  >exactly they doing, and then when they finally made a release, the got
>  >burned because of major unacceptance among community.
>  >What you think , in order to prevent that in future, wouldn't it
>  >better to make a development process as much as open as possible?
> 
> This is not open. It is spam. The community does not read commit messages
> or the reactions on them, it just ignores them. Non-core developers simply
> don't have the time to read all of this, and have no way to decide what 
> to read
> and what not. What is important?  It is up to the core developers to 
> explain
> the choices, sollicit comments, and make and document  their decisions.
> That is where an open development proces comes from. If you want a
> reaction from Dan, ask him.

Clearly spam is definitely in the eye of the beholder.

Chalk me up on the "keep commit messages in squeak-dev" side, even 
though I'm more of one of Igor's "those who stick around" group!

frank