|
Grex > Coop12 > #129: Board Minutes: Thursday September 3, 2002 Meeting | |
|
| Author |
Message |
mooncat
|
|
Board Minutes: Thursday September 3, 2002 Meeting
| 
Sep 6 16:04 UTC 2002 |
Appearing: Mooncat*, Bhelliom, Aruba*, Other*, Mary* and STeve*
(* indicates Board Member)
1. Called to Order at 7:34 pm
2. Chair report- "I'm feeling much better"
3. Treasurer's Report: We're down again for the fifth month in a row.
We took in $536, but paid out $913 (in part due to insurance fiasco)
Good news! We received our first CafePress Commission of $20.
We have three new members, 83 members total, 80 paid up.
Aruba (and the rest of us) wishes to thank Jan Wolters for
filling in as treasurer while Aruba was out of town.
Discussion re: Remainder of Grex Store- just what do we want to do
with it? Include in Auction (starting soonish!), buy a new one get an
old one free, perhaps include one wiht every new membership? No
decision made at this time.
4. Publicity Committee: "We're working on it"
Have icons that people can place on their personal websites to
advertise Grex.
5. Staff finally had a meeting! Remmers is installing OpenBSD on the
computer he is donating to Grex for this developmental purpose, STeve
is trying to get a Sparc from MDW to load OpenBSD onto it. Staff
apparently had a long discussion on the technical means/issues
surrounding porting Grex to OpenBSD- still in the works. Expect another
staff update soonish.
There is also work being done to get the PortMaster up and running.
Documentation (lack thereof) has been a major stumbling block, but we
may be able to get the information we need to get it running.
Per STeve the current Grex hardware has been 'boringly reliable.'
He did not that at some point we will need to pick up some disks (not
in the near future). Scott (Scott Helmke) reported a few errors listed
at the end of his last data dump.
Also, Scott donated an ethernet hub to Grex as the one we had died.
A developmental machine, Grease (name?) has been having it's own
booting issues since the last power outage (dead battery) and work to
repair it is ongoing.
6. Next meeting: October 3rd, Thursday 7:00 pm, Zingerman's Next Door
in the Kids Room
7. New Business- 2 Items Under Discussion: ID and Remote Board Members.
a. ID Collection / Information Preservation: Very, very long discussion
on this one relating to items posted here in coop. The board's
unofficial opinion was that we should simply continue as we have been-
with some changes. Two options were mentioned to improve the integrity
of the current security for the data- 1- get a laptop for the treasurer
specifically for that purpose- a lap top that would never attach to the
internet. 2- Get some sort of encryption tool to protect the
information on a machine that does access the internet.
b. Remote Board Members- after much (much... much) discussion on the
feasibility of an online board meeting (in party) the general consensus
was that trying it could be a very good idea. Time- not determined,
methodology- not determined. Feasibility of teleconferencing- some
objections, but overall it seems like something that could work.
Discussion on ways to work with remote board members (via phone, party,
etc.) are still ongoing, and in the end no real concensus was reached.
More discussion is needed, primarily in conferences (agora and coop),
on the concept and the means by which to get it accomplished.
8- Meeting adjourned at 9:46 pm
|
| 39 responses total. |
aruba
|
|
response 1 of 39:
|
Sep 6 18:47 UTC 2002 |
Thanks for posting the minutes so quickly, Anne. A couple of things:
1) STeve didn't suggest buying new disks, only that we might want to
consider changing over to some of the ones we already have but aren't using.
2) We discussed the possibility of staff entering an item in coop (possibly
linked to garage and agora) to keep everyone updated on what progress has
been made in getting the new system up and running.
3) I don't think it's fair to say the consensus was that an online board
meeting could be a good idea; but I think we agreed to try an (unofficial)
meeting and see how it works. I think the board was sharply divided on
whether we thought it *would* work, but we were all willing to try.
|
mary
|
|
response 2 of 39:
|
Sep 6 19:52 UTC 2002 |
I'm not sure any of us thought it would work, actually. Some
simply thought it would be an interesting experiment and we
may learn something from the experience.
|
carson
|
|
response 3 of 39:
|
Sep 7 01:20 UTC 2002 |
(the chair report sounded like something from the previous chair.)
(no, really, continuity IS good.)
|
polytarp
|
|
response 4 of 39:
|
Sep 7 18:20 UTC 2002 |
If STeve gets his name capitalized as such, I demand that my name always be
P01yT/. Any diviation from this will be taken as a personal offense.
|
jp2
|
|
response 5 of 39:
|
Sep 7 19:48 UTC 2002 |
This response has been erased.
|
polytarp
|
|
response 6 of 39:
|
Sep 7 21:53 UTC 2002 |
No.
|
flem
|
|
response 7 of 39:
|
Sep 8 01:39 UTC 2002 |
Sorry I missed the meeting. My internal calendar has been thoroughly confused
about what day it is for all of September. 'swhat I get for leaving my pda
lying on the kitchen table.
|
aruba
|
|
response 8 of 39:
|
Sep 8 03:45 UTC 2002 |
Oh, BTW: 4 board members were present at 7:00, and STeve showed up at 7:30.
|
other
|
|
response 9 of 39:
|
Sep 8 05:05 UTC 2002 |
re #7: This attitude issue will be reflected in your performance review.
;)
|
mdw
|
|
response 10 of 39:
|
Sep 8 07:51 UTC 2002 |
I wasn't there because between my work schedule and the staff meeting
the previous night, I got hopelessly confused about why Sept 5 was
special.
|
glenda
|
|
response 11 of 39:
|
Sep 8 14:06 UTC 2002 |
STeve will almost always be late, is his nature and the fact that he works
in Lansing. the I96/I23 route is terrible.
|
janc
|
|
response 12 of 39:
|
Sep 8 14:55 UTC 2002 |
I think that for an online meeting to work, some different software will
be needed. party will not cut it.
|
mary
|
|
response 13 of 39:
|
Sep 8 15:04 UTC 2002 |
If we changed the scheduled start time do you think he could
be there on time?
|
glenda
|
|
response 14 of 39:
|
Sep 8 17:00 UTC 2002 |
Higher chance of it, but I wouldn't hold my breath. :-) He's the type that
will be late for his own funeral. The only way he made it to our wedding on
time was that Josh picked him up and forced him to drop what he was doing and
get in the car.
|
glenda
|
|
response 15 of 39:
|
Sep 8 17:01 UTC 2002 |
My family tells us (him) that dinner will be at least 1/2 hour before it is
actually planned, and even then we are often a few minutes late.
|
mary
|
|
response 16 of 39:
|
Sep 8 17:10 UTC 2002 |
My understanding is the Board will wait for 1/2 hour after
the agreed upon start time, for late-comers to arrive. If
after 30 minute we don't have a quorum then those board
members who don't want to wait any longer are free to go.
At that point any official meeting can't be held as the
meeting was essentially declared "no quorum". Of course
those who want to wait an hour or more to see who comes
are welcome to do so, and they can have informal conversation,
but the board meeting was a no-go.
No hard feelings but there has to be a limit on what's
a fair time to wait for a meeting to begin.
|
mary
|
|
response 17 of 39:
|
Sep 8 17:12 UTC 2002 |
s/latecomers/late-comers
|
aruba
|
|
response 18 of 39:
|
Sep 8 17:44 UTC 2002 |
As I've said before, I'm with Mary on this one.
|
mdw
|
|
response 19 of 39:
|
Sep 8 23:42 UTC 2002 |
Actually what would have helped in my case would have been email a day
or so before. I probably would have found that when I was looking
through my email for "meeting" to try to figure out what I was supposed
to be doing sept 5th. Various grex presidents seem to have interpreted
"arranging a meeting" differently; we've had some that sent out e-mail
reminders, and some that did not. I'm not sure that I like the idea of
yet more low-content email, and I really should have figured out to get
to the meeting anyways; but a reminder probably would have improved my
chances of making it there despite myself.
|
jep
|
|
response 20 of 39:
|
Sep 9 02:30 UTC 2002 |
Marcus, why don't you use a scheduler, such as calendar, to remind you
of meetings?
|
malymi
|
|
response 21 of 39:
|
Sep 9 07:57 UTC 2002 |
re #12: a private irc daemon should be trivial to operate for
the purpose, perhaps only until the meeting is adjourned.
|
malymi
|
|
response 22 of 39:
|
Sep 9 07:59 UTC 2002 |
heh. yahoo's is even free, so to speak.
|
mooncat
|
|
response 23 of 39:
|
Sep 9 21:48 UTC 2002 |
re #1- Mark, thanks for the corrections, I must have misinterpreted
what I head STeve say. As for point #3- I guess I wasn't clear in that
I thought we came to the conclusion that *trying* an online meeting
would be a good idea- not that it would be a good thing to do, or a
successful thing. Does that make sense?
re #11- Not to be rude, but I really don't think the excuse that
someone is just late by nature is reasonable- not for an adult. I know
that some people are just more prone to constinetly being late, what I
can't accept is that it is somehow an unfixable condition. When I was
in college my friends always joked about AST (Anne Standard Time)
because I was consistently late. What it really boiled down to was
making a concerted effort to pay more attention and to realize that the
world does not revolve around my time.
It's all well and good to be late if you're not putting other people
out, but there's this thing called respect too. So the late by nature
thing isn't going to work for me. Now the bit about Lansing I can
understand and have no problem with that making him late. However, we
all know ahead of time when the meeting is- if someone can't get out of
work with enough time to get to the meeting at 7 we should change it.
No one person's time is more important than mine, or the three other
board members (and one non-board member) who were sitting around for
1/2 an hour waiting to see if we could actually have a meeting that
night.
Starting later in the evening (say 7:30) would be fine with me- if that
makes it easier for everyone to get there on time- or at least try to.
|
other
|
|
response 24 of 39:
|
Sep 9 22:30 UTC 2002 |
Sounds harsh but it is a legitimate point. If the time is too early,
we'll adjust it. If it will always be too early, then we're not
responsible for the adjustment.
|