Hello Edgar,

EJDC> Keith you should think in start your own fork as Juan, Pavel, me , and
EJDC> others do.
EJDC> My 5 centavos de peso , what worth almost 1/100 euro.

only problem with this approach is that Keith implements a community
process in software. His work is more or less oblivious to the
features that are implemented under it. Something along the lines if
somebody put a lot of work in rewriting methods for the relicensing
process.

OTOH all the forks produce an artifact with a set of features defining
the difference to Squeak. Most of them en passant bring a new process
which is working fine due to the small number of contributors and the
good alignment of purpose. Pharo being a bit different in this
respect.

"Pissing somebody off" or "stepping on somebody's toes" are not
describing what happens here. It's simply "undermining authority". The
result is as simple, people won't take responsibility. And the board
AFAIK explicitly stated they are not here to do the work. Not even
team leading.

I have seen no criticism in how Keith fulfills his team leadership.
Letting him find out in the newspaper (aka SqueakDev) that the process
he is implementing has been ditched is a very effective form of
publicly undermining authority.

This should be resolved gracefully, as such things are harmful to
community, especially to one which right now has problems with being a
community.

One thing to be learned is that a team needs a "communication officer"
like Ken provides for the Box admins Team and the board.

Actually I envy Keith for being able to handle this with only very few
lapses into "being pissed off mode".

Best regards,

Herbert                            mailto:herbertkoenig at gmx.net