You are not logged in. Login Now
 0-24   25-49   33-57   58-73       
 
Author Message
16 new of 73 responses total.
i
response 58 of 73: Mark Unseen   Aug 10 01:57 UTC 1999

Ignoring all the glowing little words in this virtual never-never land,
it appears to me that Grex's staff has a long history of working hard
and doing the right things to keep Grex up & available to the world.  

Maybe users here have a "right" to notification of an unlikely event
which would effectively take Grex down for a while, to answers from 
staff about how to deal with it, to help setting up .forward files, etc.  
Certainly there are more users who's lives are seriously harmed out in
the real world by a few-hours outage than there are staff members here 
to be hassled under any scenario. 

The user-to-staff ratio on Grex is thousands-to-one.  Staff on Grex
volunteer their time when they can.  Legit or not, that "right" of 
Grex's users is about like the "right" of the average Indian to top-
of-the-line American medical care.  The resources aren't there, and
no poetic words, rational argument, legal opinion, government program,
or anything else is going to make the resources appear.

Taking a large chance of hitting staff with a huge load right before
a very unlikely crisis that they'd need to work really hard to cope
with strikes me as crummy people & resource management. 
jshafer
response 59 of 73: Mark Unseen   Aug 12 08:42 UTC 1999

Well-said, Walter.
mary
response 60 of 73: Mark Unseen   Aug 12 10:22 UTC 1999

 "Staff on Grex volunteer their time when they can.  Legit or not,
  that "right" of Grex's users is about like the "right" of the average
  Indian to top-of-the-line American medical care."

Er, although I think the Board did the right thing here I very
much disagree with your statement above.  First, about American
Indians and secondly about Grex users not being to expect certain
basic "rights", like being kept informed.  I would not vote for
or want anyone on the Board who expressed the statement you made
above.  If someone thought they didn't have the time or energy
to include those "details" then they really shouldn't be 
involved as staff.
janc
response 61 of 73: Mark Unseen   Aug 12 12:41 UTC 1999

I think he is talking about people from India.

We certainly should be doing our best to inform users of things like
this.  We could have put something in the motd like:

    If an injunction against Michigan public act 33 of 1999 is not
    granted before Monday, Grex will be shut down until further notice.

Though this is technically accurate, I think 99% of all people reading
it would get a completely wrong idea.  That would not be a responsible
way to inform users.

You could add more disclaimers, like:

   If an injunction against Michigan public act 33 of 1999 is not
   granted before Monday, Grex will be shut down until further notice.
   However, we are almost 100% sure the injunction will be granted.

This would be better, but considering how many people misunderstood
the much longer statement I put in the minutes, I think this too would
confuse more people than it informs.

Frankly, I think no message at all is a pretty good way to give most
users the right idea of what is likely to happen - that is nothing.

I think the claim that the board should make no policies that can't be
explained to users in four lines of motd text is silly.
jep
response 62 of 73: Mark Unseen   Aug 12 14:28 UTC 1999

Or you could have put something in the minutes like this:

There is a slight possibility Grex may have to shut down for a few days, 
in response to Michigan Public Act 33 of 1999.  See item #blah in 
conference blah for further details.

This is how Grex usually handles announcements of things complex enough 
that they don't fit in the MOTD.

I just can't believe the Grex Board thinks it was urgent enough that it 
needed the decision it made, while still not being important enough to 
merit explaining to the users.  For all the claims of respecting the 
users and freedom of information and all that, some of the Grex Board 
(all of it, apparently) really believes in keeping things under wraps.  
If I seem to be attacking people a little too vigorously, I apologize 
for that, but I'm still shocked 2 weeks after I uncovered this sneaky 
action.
janc
response 63 of 73: Mark Unseen   Aug 12 15:01 UTC 1999

Darn, we thought if we hid it in the publically posted minutes, nobody
would ever notice it.

I don't understand why you think that the board makes decisions only on
important things.  We deal with an awful lot of trivia.  Recently we
considered the question of whether or not to buy a stapler.

This decision was urgent only in the sense that there wasn't much time
left to make a decision.  I thought it was better to have a basic plan
in place than not, but I didn't think it was an important decision. 
Just a stopgap contingency plan to cover an extremely unlikely
possiblity.  I consider it roughly as important as buying a stapler. 
While a stapler is a pretty small part of our operating budget, at least
it was 100% sure that we needed a stapler.  It was only about 0.1% sure
that this policy would ever be used.
jep
response 64 of 73: Mark Unseen   Aug 12 15:16 UTC 1999

From hints given in this item and the other two in which it's being 
discussed, there was a fair amount of time spent at the Board meeting 
discussing the issue.  Is that common for unimportant issues?  How much 
time was spent discussing the stapler?  Did whoever wanted the stapler 
show up at the Board meeting, ask for it, and (despite it's absence on 
the agenda) get the same treatment as the "unimportant" question of 
whether to shut down Grex?
cmcgee
response 65 of 73: Mark Unseen   Aug 12 15:33 UTC 1999

Ack, jep.  Don't you remember the stapler?  It was the people who didn't want
us to buy the stapler that caused the long discussion.
dpc
response 66 of 73: Mark Unseen   Aug 12 18:31 UTC 1999

If either of janc's MOTD messages had been posted, I think the BoD
would have performed its duty of properly implementing a very
*bad* policy.  That would have been better than *improperly*
implementing a very bad policy.
mary
response 67 of 73: Mark Unseen   Aug 12 22:34 UTC 1999

Actually, I think the discussion about modifying vs. purchasing
a stapler did go on somewhat longer than the temporary shutdown
discussion.

But, go on...
i
response 68 of 73: Mark Unseen   Aug 13 01:30 UTC 1999

Re #58/60/61:
Yes, Indian as in "a lawful citizen of the Republic of India".  As in 
India's per-capita GNP is a fraction of what's spend on the *average* 
American's health care.

The "right" of Grex users that i was referring to in #58 was the "right"
to time-consuming personal attention from a staff member who had a
hundred or more users asking for such attention - all at the same time. 
mary
response 69 of 73: Mark Unseen   Aug 13 11:03 UTC 1999

Your comparison now makes it even worse.  You're saying it's simply not
going to happen, give it up.  

I don't really think anyone was asking for "time-consuming personal
attention" here.  They're asking to be kept informed and the more
excuses I see for why we can't, don't, or won't, the more I 
understand their tenacious response.  

We screwed.  Everyone who was starting to make any plans for
a worst-case scenario and who didn't think to start a public
discussion goofed.  I was a big part of that - I'll be more
careful in the future.  There wasn't a good excuse.  

Keeping the users informed isn't a courtesy it is their
right.  It's in the bylaws.  

cmcgee
response 70 of 73: Mark Unseen   Aug 13 14:04 UTC 1999

I don't think they were trying to avoid public discussion.  They said they
were trying to avoid panic reactions from people (including me) who were
worried about a low-probabilty event, a low-probability reaction and a
short-term solution.    Yeah, the board could have done this much earlier and
could have had discussion in coop about it before they took this action.

But our board members didn't think of that ahead of time.  So they did the
best they could.  It is now being discussed in coop.  The board has time to
create a plan to put on the shelf in case the legal outcome is not what we
think is the most likely scenario.  I, for one, am not worried about a goof
of this magnitude (small to miniscule). 
lilmo
response 71 of 73: Mark Unseen   Sep 11 03:10 UTC 1999

Reading these last two items (in their entirety, I might add, except for
skimming one or two exceptionally long responses) has been somewhat
depressing.  While I didn't really expect any better from richard, I was
disappointed by the reactions of other users (but not user "other" *grin*)
who seemingly read two lines and shut off their brains.

We had just submitted a legal brief in which we went into DETAIL about how
we could not expect to continue operating were the law to go into effect.

WHAT OTHER OPTION DID THE BOARD HAVE THAN TO PASS THIS MOTION?!?!??!???!??!?

None.


Now, maybe some MOTD announcement along the lines of the one in resp:62
would have been appropriate.  I am inclined to think that it would.  However,
if the options considered were nothing versus the one in #61, I would lean
towards nothing (those seem almost designed to produce panic).

We **DID** discuss options for what the law would mean for Grex operations,
extensively.  To maintain otherwise requires a degree of ignorance I thought
would have been difficult to maintain among regular coop readers.  That the
board had the power (not to mention the responsibility) to do what it did is
similarly unteneble (sp?), considering that it is the board's responsibility
to run the corporation Cyberspace Communications, Inc. ***UNDER MI LAW***.




*sigh*
keesan
response 72 of 73: Mark Unseen   Sep 16 20:43 UTC 1999

untenable.  (it is either -able or -ible or rarely you have a choice, as in
collectible/collectable)
lilmo
response 73 of 73: Mark Unseen   Sep 21 21:17 UTC 1999

Thanks - in spanish, the verb is "tener", so I must have chosen the 'e'
subconsciously.  I knew it didn't look right, but I didn't care enuf to take
the time to find the right one.
 0-24   25-49   33-57   58-73       
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss