|
Grex > Coop13 > #364: Agenda for BOD meeting, Tuesday, 9/26/06, 8PM | |
|
| Author |
Message |
| 25 new of 66 responses total. |
cross
|
|
response 25 of 66:
|
Sep 25 22:35 UTC 2006 |
How does M-Net go about selecting this sysadmin above all sysadmins? How are
the personality conflicts that seem inevitable to arise between that person
and others handled? What if that person just says, "no" to anything that
anyone else proposes? Like I said, you're giving one person an awful lot of
power without a lot of checks and balances. Having someone responsible for
the system is one thing. Having them responsible for and have authority over
the rest of the staff is quite another.
Regarding #22; If you have an iPod, you could get an iMic and plug it in to
take a recording.
I wanted to try and call into the meeting, but now it looks like tomorrow
night isn't going to be so hot. :-(
|
tod
|
|
response 26 of 66:
|
Sep 25 23:04 UTC 2006 |
The sysadmin is basically an appointed position by the prez. If the
membership has a beef with the choice or conduct of said sysadmin then they
can issue a request with alternative choices. If they still are unhappy, they
can ask the membership to issue a vote of no-confidence against the president
that made the appointment and ask him to step-down.
I would say that Grex should do that but once again, there are toes and
egos that might be bruised so I'd be almost completely blown away by such
an act of mature accountability.
|
cross
|
|
response 27 of 66:
|
Sep 25 23:31 UTC 2006 |
The problem is that that forces the membership to either (a) understand the
technical issues involved, or (b) just go blindly with one side or another.
The problem with grex is that it isn't so much a working democracy as it is
a popularity contest; I'm wondering if we'd just be formalizing that.
|
nharmon
|
|
response 28 of 66:
|
Sep 25 23:53 UTC 2006 |
I just think that more and more people fall into this "i am just a
volunteer" mentality because of the present way staff is organized. And
this is usually helped by instituting order on a professional level so
that instead of being "just a volunteer" you become an "unpaid
professional".
I've volunteered in a lot of organizations, most of which simply did not
accept the answer of "look, i'm just a volunteer". I mean, if my CAP
commander called for my availability for SAR sorties, what would I say..
"Gee Major, I dont really feel like flying today, uh, besides im justa
volunteer"? It'd be the last thing I said. Or when I was on a volunteer
fire fighter. Do you think those guys blew off their responsibility? No
way. Or when I taught CPR/First Aid/AED for the Red Cross...what if I
just said "nah, im just a volunteer, ill just not show up at that
class". Yes, you can fire a volunteer, and the Red Cross doesn't have
any problem with doing so.
Now you might say "Gee Nathan, thats different, we're just an
organization on the internet". And I say that is exactly the attitude
you should NOT have. Board of Directors, how many times do you sit down
and think "what is grex NOT doing to promote free speech and free access
on the internet that we COULD be doing right now?" I mean, looking at
the BoD minutes...(this is just my opinion, not trying to be
offensive)...the BoD spends WAAY too much time micromanaging Grex. I
mean, discussion of the PC weasel? You should be discussing
GOALS...planning on how you can better accomplish your mission
statement. Forming committees for initiatives. Need an
initiative?...here is one: What is Grex doing to help promote a neutral
internet?
I say you people need to THINK BIG. Not about becoming big in size, but
rather big in impact. Grex is supposed to be about much more than just
running a BBS.
|
cross
|
|
response 29 of 66:
|
Sep 26 00:00 UTC 2006 |
Good points.
|
tod
|
|
response 30 of 66:
|
Sep 26 00:02 UTC 2006 |
re #27
Most places operate that way. I mean..we're talking about gross misconduct
for a membership to make motions to remove a sysadmin but at the same time
someone with a good reason could probably muster a reaction.
|
cross
|
|
response 31 of 66:
|
Sep 26 00:49 UTC 2006 |
So the recourse to the board is only for removing sysadmins, or for change
management issues?
Look. Let's be frank. If Steve said that water turned orange when you poured
it on a Unix system, 99% of the grex population would believe him. If some
of the other staff members said the same thing, no one would believe them.
"Because Steve says it's the right thing to do..." is a strong argument for
a lot of people, no matter what the thing being considered really is. And
of course, at some point, staff needs discretion to be able to do things
without endless rounds of public debate: ``Hey, I'm upgrading emacs....''
``But wait! You can't! What about X, Y, and Z! This is EMACS we're talking
about!!'' That's exactly right; it is emacs we're talking about, not the OS
or hardware platform or anything else. Should users be able to push things
like that to the board level? I'd say no. Should they have recourse against
what must be acknowledged as the very, very strong influence of a few of the
"traditional" staff members? Yeah, but what does that mean in practice?
Marcus Watts was right about something in his posts in item #27 in garage:
staff does need to be able to build concensus. I'd rather see that
facilitated than a dictatorship emposed.
|
tod
|
|
response 32 of 66:
|
Sep 26 00:54 UTC 2006 |
Listen, I had lunch with Hellman so don't tell me about crypto, okay?
(Hellman's mayonaisse that is..)
|
cross
|
|
response 33 of 66:
|
Sep 26 00:56 UTC 2006 |
The thing is, I *really have* had lunch with Whit Diffie.
|
tod
|
|
response 34 of 66:
|
Sep 26 17:34 UTC 2006 |
re #33
(Me, too. Not only that, I was on a speaker panel with him.)
|
cross
|
|
response 35 of 66:
|
Sep 26 17:44 UTC 2006 |
He's a nice guy.
|
tod
|
|
response 36 of 66:
|
Sep 26 18:15 UTC 2006 |
His hair smells like strawberries.
|
cross
|
|
response 37 of 66:
|
Sep 26 19:24 UTC 2006 |
The snozzberries taste like snozzberries!
|
cross
|
|
response 38 of 66:
|
Sep 26 23:59 UTC 2006 |
I realize it's a bit late, but what's the phone number to dial into the board
meeting?
|
mary
|
|
response 39 of 66:
|
Sep 27 01:34 UTC 2006 |
Tonight, it's our home phone number. Bruce Howard is on that
line for the meeting.
|
cross
|
|
response 40 of 66:
|
Sep 27 01:45 UTC 2006 |
Guess that sort of rules out me calling in. Okay.
|
aruba
|
|
response 41 of 66:
|
Sep 27 03:26 UTC 2006 |
We only have the one phone line, and the one full-duplex phone,
unfortunately.
|
cross
|
|
response 42 of 66:
|
Sep 27 04:13 UTC 2006 |
Them's the breaks, I suppose.
|
tod
|
|
response 43 of 66:
|
Sep 27 16:45 UTC 2006 |
Too bad you can't skype a conference call
|
krj
|
|
response 44 of 66:
|
Sep 27 19:08 UTC 2006 |
nharmon in resp:28 :: deja vu all over again. I heard that speech
-- both parts of it, the "professional" one and "we should be a bigger
organization with more impact" one -- on M-net, maybe half a dozen times.
Usually it led to grief.
What sticks in my mind is a line from the non-profit organization
lawyer who M-net consulted once. As it was reported at the time,
the line was: "You can't make the membership go somewhere it doesn't
want to go."
|
tod
|
|
response 45 of 66:
|
Sep 27 19:26 UTC 2006 |
This isn't M-Net. Even if it was, and there was this much interest, it seems
like a basic duty of a director to review short-term and long-term goal
formulations as well as deliberating on recruitment ideas.
What I probably find the most offensive is when directors make business
decisions without being reasonably informed (aka "duty of inquiry".) As a
director, one should always be cautious that information provided strictly
for the first time at a meeting may not always be accurate.
"A director may not close his eyes to what is going on about him in the
conduct of the corporate business, and, if he is put on notice by the presence
of suspicious circumstances, he may be required to make such 'reasonable
inquiry' as an ordinarily prudent person in his position would make under
similar circumstances."
-Report of the Assembly Select Committee on Revision to the Corporations
Code p. 50 (1975).
|
nharmon
|
|
response 46 of 66:
|
Sep 27 19:38 UTC 2006 |
I dunno. I just feel that Grex has so much more potential. I feel that
Grex could do so much more for many more people if it just made that
next leap in terms of quality and intensity. So single person can get us
there, its going to need to be a team effort. Here is what we need to do:
1. Everyone needs to put more work into the organization. Everyone means
everyone, from members on the BoD to conference fairwitnesses. It isn't
enough just to attend regular meetings. We need to be creating,
experimenting, planning and implementing new ideas, encouraging new
members. I know that Grexers tend to be extremely busy people, but just
a few more minutes of brainfocus goes a long way. Maybe its just taking
5 minutes to pick up the phone and call the Free Software Foundation, or
spending a few minutes in party to meet and greet new users. Every
little effort helps.
2. Grex needs to incorporate professional development plans if it ever
hopes to recruiting more staff. You simply can't expect knowledgable
system administrators to come from nowhere. New staff should be
cultivated from the user pool because those people already have the
motivation and committment.
3. Grex needs to take advantage of its resources. I never cease to be
amazed by the talent we have on here. We have PhDs, professional system
administrators, programmers...the list goes on. We're sitting on a
goldmine of technical prowess that just isn't being tapped.
4. Grex needs to raise the level of professionalism. This isn't optional
in my opinion. And it isn't difficult. Those of us who are IT
professionals already do it every day. We simply need to bring the same
sense of responsibility to Grex that we bring to our careers.
I think if we put our personalities, egos, and personal agendas aside
and work on Grex's mission, a lot of other things will fall into place.
It is all about "service before self" for our members and for each other.
|
tod
|
|
response 47 of 66:
|
Sep 27 19:59 UTC 2006 |
It is all about "service before self" for our members and for each other.
BWAHAHAHAHAH!!
|
nharmon
|
|
response 48 of 66:
|
Sep 27 20:08 UTC 2006 |
It wasn't meant to be funny, Todd.
|
cross
|
|
response 49 of 66:
|
Sep 27 21:48 UTC 2006 |
I think Todd was expressing skepticism. I think what you're saying is great,
Nate, but I'm not sure it will ever happen.
|