home *** CD-ROM | disk | FTP | other *** search
- Submitted-by: stephe@mks.com ("Stephen R. Walli")
-
- In the recent ballot of the IEEE TCOS/SEC Operating Procedures,
- there is the concept of an ``At-Large'' member. (There's a rude joke
- in their somewhere....) Can anyone explain to me why they should exist?
-
- ``At large'' members seem to be poorly defined.
- There is certainly no ``drop dead'' clause for missing a single meeting,
- such as their exists against IRs.
- There is no way to remove them if they're doing a bad job.
- Indeed, "At-large" members have no defined role.
-
- What is their purpose?
- Why would individual IEEE professionals care about such things as
- logistics (meeting locations?), or PAR approval,
- or any of the other collective responsibilities of the SEC?
- Yet a small number representing ONLY THEIR OWN INTERESTS
- are voting members of the SEC!
-
- There is no criteria for choosing them.
- Any member of the IEEE can come forward for consideration as an at large
- member,
- with no written restriction to prior participation in the TCOS/SS world.
- It therefore falls to the SEC to vote individuals to the positions.
- It is therefore presumed that they MUST be a known figure in the TCOS/SS
- world,
- otherwise they have no credentials.
- (There is no mention that they need to justify the reason for wanting
- ``At-large'' status,
- even in their nomination letter.)
-
- The hysteria that seemed to surround IRs having the vote and representing
- some faceless organization with suspicious intentions seems to be missing here.
- There is no requirement that this gaggle of well-meaning professionals
- needs to be balanced in any way, shape, or form.
-
- This poorly/ambiguously defined concept is too open to potential abuses.
- Sounds like we're creating a POSIX patronage position. (I have no idea if
- the ``patronage'' problem exists in the American government. It seems to be
- the way we run the Canadian government. Sometimes referred to as the
- ``Pork Barrel''.)
-
- Please enlighten me.
- Stephe Walli
- stephe@mks.com
-
- [ Please note the followup and crossposting. -- mod ]
-
- Volume-Number: Volume 26, Number 63
-
-