You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-135     
 
Author Message
25 new of 135 responses total.
pfv
response 50 of 135: Mark Unseen   Jul 27 23:59 UTC 1996

"enfranchisement", (disenfranchisement) and "empowerment" are all cute
bureacratic "sound-bites"..

        The first and last presuppose you either never had any "power" or
rights, the innermost means you somehow lost it.. IAE, all are hogwash as
this is NOT Arbornet-The-Movie, and this is not the Borg.

        Frankly, I think you are still barking up the wrong tree and in
the  wrong place - seeing things that are not even there..


        Interesting how you get a feel for the political bent of folks by
reading thru these conferences..

janc
response 51 of 135: Mark Unseen   Jul 28 00:17 UTC 1996

(Gate reads the number of columns from your "stty" settings.  Apparantly
Richard not only has an oversized window, but a telnet smart enough to pass
the window size through to Grex.  Probably Gate should use a default column
size of no more than 80, even if the user has a wider window.  In fact, I
thought I'd programmed it that way...but I guess I didn't.  So using gate
doesn't help Richard's line length problem.  Until I fix this (and even after)
adding the following line to your .login should solve the problem:

   setenv GATEOPTS "maxcol=79 hotcol=75"

)
mdw
response 52 of 135: Mark Unseen   Jul 28 00:42 UTC 1996

Kerouac - if you *really* feel that staff isn't being democractic,
here's an experiment *you* can try.  Enter an item calling for a
membership vote that telnetd be restored *exactly* to the pre-waitlist
form.  There are no technical obstacles in the way of doing just this.
The file /usr/local/libexec/telnetd-- is the original pre-waitlist
version that "everyone" seemed happy with, at the time.  There are, of
course, other issues, such as attack telnetting, and putting higher
speed modems on a terminal server, that either can't be resolved, or
will have to go on the back burner, if this is done.  You will have
greater success with your proposal, if you are prepared to address these
points.
janc
response 53 of 135: Mark Unseen   Jul 28 01:20 UTC 1996

Responding to #49:  Why are you screaming for user input and veto power? 
Haven't we just seen an item full of user input on the multiple login zapper?
Hasn't the staff installation of the multiple login zapper been vetoed?
What more do you want?  Why do you need to insist on things that seem to be
to be already here?

What people are calling for isn't "user input" and "veto powers".  We
obviously have those.  What they are calling for is a more rigid procedure
in which staff members have a fixed set of bureaucratic hoops they have to
jump through in a fixed order.  If they don't do them in the "right" order,
they get their hands slapped by being called Nazis all over the system.

The benefit of a nice clean bureaucracy is that you will never be surprised
by any change in the system.  This has nothing to do with democracy, but it
is comforting for the users and radiates oodles of professionalism.

The disadvantage of a nice clean bureaucracy is that all the staff will
disappear, so there will be no changes, and no maintainance.  Basically,
M-Net.

I repeat.  This isn't a democracy debate.  The staff has always listened to
and acted on user input.
chelsea
response 54 of 135: Mark Unseen   Jul 28 04:25 UTC 1996

I'll make one little suggestion here, which I believe I've
made before, but what the heck...  I'd suggest there be two
"What I Did" items in Staff.  One would be linked to coop and
would be for all entries where there isn't a security concern.
The other, "What I Did - Security Involved" would of course
not be linked.

That way folks can see all the work staff folk are doing, on 
an ongoing basis, to keep Grex functioning.  There will also
be a mechanism in place for users to see what work is being done
and be able to ask questions or offer suggestions before it
becomes a communication issue.

Could an item be left open for responses in staff but frozen in Co-op? 
Like, is it technically possible?  We really need to look for a ways to
improve communication between staff and the rest of us without making
additional demands on staff's time.

And janc, who is it who is calling staff Nazis?  For heaven's sake. 
(If it's kerouac, I withdraw the question.  I don't read kerouac.)
sidhe
response 55 of 135: Mark Unseen   Jul 28 04:40 UTC 1996

        until he started using gate, I COULDN'T read kerouac.
pfv
response 56 of 135: Mark Unseen   Jul 28 05:43 UTC 1996

Well, if it is 'fix' related - it should be with the problems, neh?

If it is _upgrade_ or _prototyping/test_ related, yeah.. A new item might
make sense.

All of these ideas are predicated on the users BOTHERING to read the
entries and the staff BOTHERING to make an entry..

Run into the same probs on mnet's systems (yeah, the Borg's Arbornet) -
and the root gets peeved if he has to stop programming/fixing to keep the
users posted..

rcurl
response 57 of 135: Mark Unseen   Jul 28 06:36 UTC 1996

I would like to suggest, to add to Mary's #54, that not only should there
be the "What I did" items from staff in coop, but also "What I'm thinking
of doing" items.

My response to Jan in his #s 44 and 53, is....let's not get all excited. 
No one is (or should be) "accusing" staff of anything. Certainly all I
have been asking is that staff talk to us users along the way as they come
up with ideas and work on them. Jan has been very willing to discuss with
us some justifications for acting first and discussing later, but it
really is very easy to discuss first and act later. This order of things
allows the interested users to at least feel involved, even if they are
not doing the work. They might, of course, contribute some good ideas,
just as a bonus. 

Do you know why I keep pursuing this issue? Because I have been led by
other users, staff and board members to accept the idea of Grex at least
acting as a cooperative, and pursuing decisions by consensus. I spent some
time suggesting a more efficient - and formal - decision making process
(shhhh...rro...), which few found acceptable or even desirable. So, I've
been grexified. But lo - what do I then see? Even some of those that
grexified me appear to be acting outside "cooperative" and "consensus". I
don't shift my perspectives without a lot of consideration, so having
shifted *one* way, I'm resisting shifting again by giving up "cooperative"
and "consensus". 

janc
response 58 of 135: Mark Unseen   Jul 28 06:42 UTC 1996

Who's asking you too?  The multiple-login zapper was turned off pending a
consensus that such thing is needed.  When you give speeches about how you
think we ought to be working cooperatively, you tend to imply that someone
disagrees with you.  Who?
janc
response 59 of 135: Mark Unseen   Jul 28 06:48 UTC 1996

(And my previous comments about gate not responding right when you have a
 wider than normal screen were mistaken.  Gate does just what it should and
 will never default to more than 80 columns, no matter how my columns your
 screen has.  Kerouac has evidentally done !use_gate six times.  He can stop
 once was enough.  He is using gate.  My best guess is that he is firing up
 an editor out of gate, and since pico happily uses every column on your
 screen, as long as he is in the editor, he can merrily enter 85 character
 lines.  Gate autowraps lines for you at the > prompt, but it won't reformat
 stuff you have entered in an editor.)
rcurl
response 60 of 135: Mark Unseen   Jul 28 07:09 UTC 1996

I thought you were asking me to, Jan, by making speeches stating that it
was fine for staff to implement new ideas that change the interface of
Grex, without prior discussion. But it isn't that anyone is *asking* me to
take a new perspective - it is the actions that have been speaking louder
than words (to con a phrase). Now, can we stop fencing, and just act
cooperatively and by consensus (and maybe now and then vote on the most
significant issues)? 

tsty
response 61 of 135: Mark Unseen   Jul 28 07:51 UTC 1996

(curious here ... PicoSpan indents responses by 1 character ... suggest
making 78 the max-number of characters)
remmers
response 62 of 135: Mark Unseen   Jul 28 12:35 UTC 1996

Let me echo something Marcus mentioned in #52: There *is* a
mechanism -- it's in tne bylaws -- whereby any member of Grex
can make a proposal in Coop and have it brought to a vote.
Read the bylaws (I think they're posted in Item 2) and see
for yourself how to do it.

There's a lot of talk above Grex users are helpless in the
face of an autocratic staff, but it's simply not true. If
people don't like telnetd or some other change to the system,
they can force a vote on it.
janc
response 63 of 135: Mark Unseen   Jul 28 16:54 UTC 1996

Re 60:  Yes, I think it's OK for the staff to make system changes without
consulting the users.  So long as they remain open to user feedback, and are
willing to back out or adapt the change in response to that feedback.  Sure,
in many cases it is nicer if staff consults with users first, but it is not
a major problem so long as in the long run the board remains in control and
the users remain in the loop.  Day-to-day autocracy is OK, so long as week-to-
week we operate democratically.  I think this way of thinking about it is a
good way to allow staff the short-term authority to correspond to their short-
term responsibility, but still keep the system working fundamentally
cooperative.

So we allow staff the authority to use their best judgement day-to-day, the
coop conference discusses and considers things week-to-week, and the board
makes official decisions month-to-month.  Anything the staff does can be
influenced by user discussion, or overruled by board vote.  Sometimes that
happens before the change, sometimes it happens after.

We've been working like this a long time.  It works fine.  What's wrong
with it?
rcurl
response 64 of 135: Mark Unseen   Jul 28 20:25 UTC 1996

No it doesn't, and Grex has not been operating that way for a long time. 
It used to be pretty customary to bring up in coop any changes that made a
significant difference in the appearance and operation of the system,
except for those that increased speed and facilitated use of the system as
it was, or of course that implemented changes that had been discussed and
agreed upon.

I don't think that forcing votes to overcome staff autocracy, as John
suggests, leads to a very friendly discourse, much less cooperation or
consensus. All it does is breed antagonisms, when it is perfectly feasible
to be open and friendly and cooperative in advance.

Exactly what is *wrong* with being open about what staff is doing and
planning? Discussing these things in coop takes a tiny fraction of the
time that the technical work itself takes.

It is a figment that "it is not a major problem so long as in the long run
the board remains in control", since the board consists of mostly staff. 
Given the nature of Grex, I don't have an inherent difficulty with staff
also serving on the board, but *as board members*, they should be first
and foremost responsible to members (and users), not to staff. That's
pretty hard to do when the board and staff are mostly the same. 

The direction I see signs of here is toward Grex becoming an ISP, with
members just paying the bills and putting up with what staff thinks is
good for them. 

pfv
response 65 of 135: Mark Unseen   Jul 28 22:52 UTC 1996

ludicrous..

kerouac
response 66 of 135: Mark Unseen   Jul 29 16:45 UTC 1996

I think there is an inherent problem because there is too much
overlap between staff and the board.  How is one supposed to
objectively oversee staff operations when one is on staff?  Right
now, submitting software changes to board votes is a useless 
gesture because staff is the board.  If there is staff 
consensus, there is automatically board consensus (well 99% of
the time)   Therefore the only way to check the autocratic
nature of staff is to use the !vote program and let the membership
have the final say.   Why is there a !vote program in the first
place, if it isnt to be used in these situations.

Such would be good also because the staff attitude seems to be that
if something is good for technical reasons, it is good period.  There
ARE instances where even when some change is technically the right
thing to do, it is aesthically the wrong thing to do.  This is the
case IMO with the wait que.  The wait que is regressive.  It
discourages people from logging in at times, because being way down
the wait list kills initiative.   When you get "all ports are busy"
you might be first in line for all you know, soyou will call back...
you have the incentive.

As for the idle timer zapper, I have no problem with
the concept of it, just the way Valerie went about it and the
pre-set time limit (should be an hour, not less)
pfv
response 67 of 135: Mark Unseen   Jul 29 17:28 UTC 1996

Seems to me that the staff is of volunteers, while the Borg is elected...

Why didn't more people run for the Borg? Why where their not more offers
of staff-volunteers.. Why are the Board unsuitable to be staff? Are they
raising the taxes?

rcurl
response 68 of 135: Mark Unseen   Jul 29 18:19 UTC 1996

A completely neutral answer is that there are more "positions" for
volunteers to serve Grex if persons don't take on two jobs, like both a
board post and a staff post. In many organizations the roles are also
different - the staff carrying out the business of the organization, and
the board *finding the resources for carrying out the business*, in
addition to setting policy.  In reality, most small organizations always
overlap staff and board because there is a lack of qualified volunteers to
efficiently separate the functions, and the staff are often the most
visible active members, and hence most easily elected, unless this is
depermitted by agreeing that a person can be staff or board, but not both. 
The problem generally disappears when an organization grows to the point
of hiring staff, and the board does the hiring (other problems then arise,
but that is beyond the current scope....). 

kerouac
response 69 of 135: Mark Unseen   Jul 29 18:43 UTC 1996

#68...exactly...I think the only way to solve the
situation where staff members end up being the ones elected to
board seats, simply because theya re they most visible, is
to either disallow staff members from running for the board, or
limit the number of board openings available for staffers.

With all the members of grex, there are plenty of people besides
the eleven members of the staff who should be able to serve on the board
but will never be able to because they just arent ever going to be as
visible.  Someone like Sidhe never had a chance to get elected
to the board, becuase he simply isnt involved in the day to day
operations in the way robh and scg are.  rob and steve dont neee
er...need to be on the board to have influence.  They are on staff\
and had their voice in these matters already.

Every staff member who ran for the board last time won.  Its basically an
incumbency advantage, something that discourages other people from even
running at all.
pfv
response 70 of 135: Mark Unseen   Jul 29 20:48 UTC 1996

I dunno enough about the polit-licks here to bother commenting, but it
still sounds like a sourgrapes/Borg thang <shrug>

brighn
response 71 of 135: Mark Unseen   Jul 29 20:54 UTC 1996

I'm curious.  I looked.  I tried to find something.  But I can't, so I thought
I'd ask.  Was there anything substantive in the last 20 posts or so that
wasn't a direct response to Kerouac making the same silly "This is a volunteer
organization but I still want this place run like a for-profit
staff-get-pai-$60K-a-year" comments?  I note some of the longest posts along
the lines of refuting those being some of the people who in another item
informed us so eloquently of the twit-filter capabilities of Grex.

I would rather not have to start forgetting co-op items, but this is getting
absurd.
Kerouac is obviously *not* going to learn a sou about what most of the people
here think this system is all about, so why, for Great Gods' sakes, WHY is
everyone rushing to spam responses to sway his oxen mind?
pfv
response 72 of 135: Mark Unseen   Jul 29 21:14 UTC 1996

Sorry, I have yet to try filtering in conferences.. ANd, I sorta' await
some of the staff to mail a lil' note to this guy to relax a bit...

besides, even if it is a dit, I prefer to politely suffer it - for now...
Until there is a way to twit based on content.. ;-)

ryan1
response 73 of 135: Mark Unseen   Jul 29 22:53 UTC 1996

        This item is making me SICK.  How dare you criticize staff like
that?  This system is FREE to the public.  Let me say taht again, this
system is FREE to the public.  If you want internet access, you can have
it for 6 dollars a month.  Do you know of a different place where you can
get a shell account with full internet access for 6 dollars a month?  The
staff here volunteers their time to keep this system up and running 95% of
the time.  Do you know of many people who can secure a unix system so that
it is protected from hackers or other people who just want to cause
trouble?  Many systems consider giving shell access to users a
security hole.  The staff here gives shell access to ANYBODY.  THey don't
have to fill out a form, make a phone call--or anything.  All the person
needs to do is telnet to grex.cyberspace.org and type "newuser".

        If you don't think Grex is run "democratically" then leave.
Perhaps m-net will be sufficient. (Gag)

In summary, this staff has done a DAMN good job keeping this system up and
running, and nobody has a reason to complain.
kerouac
response 74 of 135: Mark Unseen   Jul 29 22:54 UTC 1996

*sigh* Im making valid points...there are few enough people here who
even care enough to speak out so it isnt constructive to criticize
those who do.  Just speak to the issues ok...
 0-24   25-49   50-74   75-99   100-124   125-135     
Response Not Possible: You are Not Logged In
 

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