response 13 of 61:

Sep 27 22:32 UTC 2006

re #12
 If Steve truly felt that grex was in danger, then he surely did the right
 thing in the moment.  But then it surely became clear that the immediate
 cause of the incident was a communication breakdown and a difference of
 policy interpretation and not any malicious intent.

I agree.  And don't call me Shirley.

response 15 of 61:

Sep 28 05:22 UTC 2006

I suppose if Mic was aware of that that's one thing.

response 17 of 61:

Sep 28 12:59 UTC 2006

Mic's root access has been restored.

Root long and prosper.

response 19 of 61:

Sep 28 13:20 UTC 2006

Roto-rooter.

response 21 of 61:

Sep 28 23:18 UTC 2006

*roots* 

response 23 of 61:

Sep 29 03:59 UTC 2006

wow, nate; i'm impressed.

i've never had anything that i've written on BBS be read aloud at a board
meeting.

response 25 of 61:

Oct 6 21:16 UTC 2006

re #24
 Ahem.  "The membership" speaks only through elections or user
 initiatives.  Say "a member explicitly requested..." or "a couple of
 members requested..." and that statement becomes accurate.  Otherwise
 you have no right to speak for "the membership".  The Board does that.
Nice way to explain why nobody gives a shit why a couple great staff folks
quit.  *golf clap*

response 27 of 61:

Oct 6 22:57 UTC 2006

 I find nothing to disagree with in #24.  I think its relevance is limited
 (pertaining only to the fact that in #5 Dan wrote that "the membership"
 requested something rather than writing "a member" or "some members") but
 jep makes a good point.  There's no cause for sloppy writing or sloppy
 thinking.

response 29 of 61:

Oct 7 01:42 UTC 2006

I agree that jep has a point; I could have phrased that better.  But, the
readership (better?) requested that something be discussed at a board meeting,
and someone should have discussed it.

Further, the board doesn't speak for the membership: the membership speaks
for the membership, and the board listens.

That said, I agree that quibbling over semantics isn't going to solve any of
the problems with grex which, it is becoming apparant, run very deep.

response 31 of 61:

Oct 7 03:12 UTC 2006

Or maybe, "members of the readership" or "elements of the readership"

response 33 of 61:

Oct 7 04:02 UTC 2006

 re #28:
 > It only spins the conversation away from the Board's inaction
 > toward resolving a rogue staff.

 Can you be a little clearer who you're referring to?  I wouldn't
 use the term "rogue staff" to describe either of the two principal
 players (mic or steve) in the latest incident.

 Also, if you're going to be critical of "inaction", then what action
 is it that you want to see the board take?  Reduce their pay?  Put an
 official letter of reprimand in their Permanent Record?  Ground them
 for 48 hours and impose a curfew for the rest of the month?

response 35 of 61:

Oct 7 04:39 UTC 2006

The situation appears to me to have been resolved between steve and
spooked.  Mistakes were made aplenty.  That happens sometimes.  With
good will it is sometimes possible to work things out.  That has
happened, with some assistance from aruba and the couragement of the
Board.  I see no reason why I should be unsatisfied with what has been
done to work out the issue.

STeve has been part of Grex since the beginning.  He's trustworthy,
technically excellent, not as diligent as he used to be but geez it's
been 15 years and he's still here.  We're lucky to have him.  I think so
and I think almost everyone would agree.

Now, what should be done differently?  And why?

About the request that they "discuss" the steve/spooked/cross thing...
when has the Board *ever* acted hastily on anything?  I can't recall a
case.  They deliberate and discuss and take their time.  Usually by the
time they get around to doing anything, it's clear to everyone that it's
what they're going to do and most agree it's what they ought to do. 
They try to do what the membership wants and what will allow Grex to
survive.  I couldn't stand to be part of a Board that works that way
myself, but... well... I'm not *on* the Board.  It doesn't keep me from
recognizing the way that it operates, nor from noticing it's worked
pretty well for 15 years.

response 37 of 61:

Oct 7 04:55 UTC 2006

A technical committee and change control processes would be a good place to
start.  The garage cf has some good ideas simmering and if people don't know
how to get them implemented then a technical committee should embrace that
challenge and document the procedures everyone on staff can agree to.