You are not logged in. Login Now
 0-24   25-28         
 
Author Message
popcorn
Agenda for the 4/26/95 Grex Board of Directors Meeting Mark Unseen   Apr 20 12:20 UTC 1995

Here's the tentative agenda for the 4/26/95 Grex Board of Directors Meeting.
Please yell if there are items on the list you want added/changed/deleted.

   1. Initial Gavel Banging - popcorn                             < 1 minute
  10. Treasurer's Report - danr                                    5 minutes
  11. 501(c)3 Committee Report - rcurl                             5 minutes
 100. Computer Rehabilitation Committee Report - rcurl             5 minutes
 101. Publicity Committee Report - misti                           5 minutes
 110. Technical Committee Report - STeve                          20 minutes
 111. Verification Policy - Steve                                 20 minutes
1000. JCC Sale followup - STeve                                    5 minutes
1001. Adding robh to staff - various staffers                     10 minutes
1010. WIN Consortium report - popcorn, scg, mdw, srw, STeve, etc. 20 minutes
1011. New Business - all                                           Who Knows?
1100. Final Gavel Banging - popcorn                               < 1 minute


The board meeting will be on Wednesday April 26 at 7pm at Zingermans.
Zingermans is located in Ann Arbor on Detroit Street, which is near Fifth
and Kingsley.  The board generally meets in the Zingermans coffeehouse next
door to their main building.  The meeting is likely to be held upstairs,
even if the sign says the upstairs is closed.  The public is welcome.
28 responses total.
rcurl
response 1 of 28: Mark Unseen   Apr 20 19:01 UTC 1995

And, the meeting will be conducted in binary.
carl
response 2 of 28: Mark Unseen   Apr 20 21:16 UTC 1995

Isn't that an on again off again way to run a meeting?

remmers
response 3 of 28: Mark Unseen   Apr 20 21:27 UTC 1995

Yeah, just a bit.
lilmo
response 4 of 28: Mark Unseen   Apr 21 00:25 UTC 1995

I'm sure Zing's would be pleased if you had a byte...
adbarr
response 5 of 28: Mark Unseen   Apr 21 05:09 UTC 1995

re: 1 to 4, inclusive:
<Groan!> Rane is close, but the meeting will be conducted
in "actuary", because your life depends on it.  It is easy
for a layperson to confuse the concepts, as has been 
demonstrated.
danr
response 6 of 28: Mark Unseen   Apr 21 18:18 UTC 1995

re #4:  That's certainly food for thought.
lilmo
response 7 of 28: Mark Unseen   Apr 21 19:05 UTC 1995

Re #5:  UNIXed the jokes !!!  :-(
zook
response 8 of 28: Mark Unseen   Apr 23 02:29 UTC 1995

I thought Valerie would insist on octal or hex at the meeting...  Personally,
I'd rather just nibble.
popcorn
response 9 of 28: Mark Unseen   Apr 23 12:56 UTC 1995

Hey, does anybody have any additional *agenda* items for the meeting?
remmers
response 10 of 28: Mark Unseen   Apr 23 16:41 UTC 1995

Nah.  I think 1100 agenda items is quite enough.
srw
response 11 of 28: Mark Unseen   Apr 24 04:24 UTC 1995

That was why I always used hex when I was chair. You could pack a
lot more into a meeting.

I was thinking of asking whether we should review our reap policy.
I am leaning against doing this as an agenda item, as I think it might
be better discussed as a coop item. I haven't decided yet what to do.
rcurl
response 12 of 28: Mark Unseen   Apr 24 07:11 UTC 1995

Have we established a reap policy, or isn't it still ad-hoc?
steve
response 13 of 28: Mark Unseen   Apr 24 12:39 UTC 1995

   Yes, we have.  The current policy is to reap accounts that 
haven't been used in 90 days, or if the account was used once
and then no further activity is seen on that account for three
weeks.

   I have things pretty much automated right now for this, but
have been running things by hand every couple of days.  When I
finish the automated system it can be run once a night for automatic
account zapping and will generate a report somewhere in /var/log.
davel
response 14 of 28: Mark Unseen   Apr 24 13:22 UTC 1995

What was done about an exception list?
steve
response 15 of 28: Mark Unseen   Apr 24 13:35 UTC 1995

   I have a list of one person, right now.  So it's been easy.
After running reap to come up with a list of accounts to remove
the list is run again the list of members to see if any members
would be up for deletion.  Members are removed.
   I have to fix part of the reap program that deals with the
immortals file, then the exceptions will be automatically
covered.
popcorn
response 16 of 28: Mark Unseen   Apr 24 14:05 UTC 1995

I can think of another couple of accounts that belong on the immortals list.
Should I mail them to you?
steve
response 17 of 28: Mark Unseen   Apr 24 15:07 UTC 1995

sure.
rcurl
response 18 of 28: Mark Unseen   Apr 24 16:14 UTC 1995

Is the policy stated in newuser?
popcorn
response 19 of 28: Mark Unseen   Apr 25 02:14 UTC 1995

Not last I checked, no.
srw
response 20 of 28: Mark Unseen   Apr 25 05:55 UTC 1995

No it's not. One aspect of the policy is that if an account is reaped,
it is immediately available to be recreated. Perhaps by someone else.
This happened once, and I am trying to decide what can or should be 
done about it. The person wants his account back and we cannot deliver,
because another person has it. I wondered if we should discuss this
at the board meeting.
popcorn
response 21 of 28: Mark Unseen   Apr 25 14:03 UTC 1995

Shall I add it to the agenda, or does it count as New Business?
steve
response 22 of 28: Mark Unseen   Apr 25 15:07 UTC 1995

   Another agenda item:  CO2 fire extinguisher.
gregc
response 23 of 28: Mark Unseen   Apr 26 09:11 UTC 1995

People don't own accounts on Grex. The user in question just had temporary
use of that name. He didn't use it, so he lost it.
davel
response 24 of 28: Mark Unseen   Apr 26 11:20 UTC 1995

My view exactly.  We should (and, at least in principle, do) make it possible
for people to say up front that they'll be away for more than 90 days
and be preserved.  (Though with the net, the need for this is a good deal
less urgent.  Absence from AA often will not mean that Grex is any less
available whatsoever.)  But we shouldn't have to carry the burden of tying
up disk, slowing down lookups, etc. by keeping users on when they're
not around.

Stating this policy in something new users will see (not necessarily in
newuser) would be appropriate, indeed.
 0-24   25-28         
Response Not Possible: You are Not Logged In
 

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