|
|
| Author |
Message |
cross
|
|
The Staff and Board Alert Item
| 
Sep 24 17:00 UTC 2006 |
This is the staff and board alert item. Post pointers to items in other
conferences that require staff or board attention here.
|
| 92 responses total. |
cross
|
|
response 1 of 92:
|
Sep 24 17:02 UTC 2006 |
There is ongoing discussion in the garage conference, item #27, of replacing
grex's custom password hashing algorithm with the standard OpenBSD
algorithm. Please read the discussion and post your comments.
|
naftee
|
|
response 2 of 92:
|
Sep 25 22:01 UTC 2006 |
thanks, dan
|
arthurp
|
|
response 3 of 92:
|
Oct 1 04:45 UTC 2006 |
Perhaps we should start another website that has pointers to additional
places that staff and board should monitor for impoartant discussions.
Or perhaps a public access cable timeslot.
The thing is Staff issues are discussed in the Staff conference.
Period. Board issues are discussed in coop. Period.
It has always been this way and everyone entering either of those
organizations is briefed on this.
Items that need the attention of either group that must be raised by
someone without access to the two above fora is sent to the board and/or
staff mailing list. Everyone who joins Grex is briefed on this fact.
There are well established methods of definitively reaching either
group, and it makes no sence to require yet more time from volunteers to
check myriad additional locations for things that someone wishes them to
keep informed of.
One of the basic principles of effective leadership is to act as a
member of the team rather than as an individual and comply with accepted
protocols and communication channels. Even if you feel correct and
justified in acting completely on your own.
I know the things that are told to a staffer when they join the team. I
know the hoops that they have to go through. I find it impossible to
believe that anyone has been admitted to staff without knowing what an
honor it is to get that priviledge from the board, how select and
controlled the process is, and how much discretion the board gives to
staff with regard (only) to reacting to security breaches. Anyone who
claims otherwise, I believe, is subconsciously or knowingly choosing to
ignore such because they are so sure of their actions as to regard
themselves as above review.
Everything reguarding non-emergency action is discussed by staff and
board. Making a posting in an obscure location and claiming that lack
of response is equal to consent or claiming that they should have known
is a thinly veiled attempt at justifying renegade behavior.
|
mcnally
|
|
response 4 of 92:
|
Oct 1 05:56 UTC 2006 |
re #3:
> I know the things that are told to a staffer when they join the team. I
> know the hoops that they have to go through. I find it impossible to
> believe that anyone has been admitted to staff without knowing what an
> honor it is to get that priviledge from the board, how select and
> controlled the process is, and how much discretion the board gives to
> staff with regard (only) to reacting to security breaches. Anyone who
> claims otherwise, I believe, is subconsciously or knowingly choosing to
> ignore such because they are so sure of their actions as to regard
> themselves as above review.
Thanks, I guess.. The above helps crystallize a decision I've been leaning
towards for a while now and to which the recent situation had contributed.
Effective immediately, I wish to resign from Grex staff. Will someone
please delete my staff-related group memberships and remove me from
staff-related mailing lists? I'll explain more about my reasoning later
in the unlikely event that people care to know why..
|
naftee
|
|
response 5 of 92:
|
Oct 1 06:15 UTC 2006 |
I am sorry that you decided to resign, Mike.
|
nharmon
|
|
response 6 of 92:
|
Oct 1 12:59 UTC 2006 |
:-(
I care to know why.
|
spooked
|
|
response 7 of 92:
|
Oct 1 13:44 UTC 2006 |
Mike is (sorry, now was) one of Grex's finest Staff and technical
resources.
Again, it's wankers that spoil Grex staff... and, it is obvious, again,
who the wanker/s are.
|
scholar
|
|
response 8 of 92:
|
Oct 1 13:48 UTC 2006 |
:(
|