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.
dang
response 50 of 135: Mark Unseen   Jul 3 01:39 UTC 1997

I don't know.  I think 0 is a proposal for an amendment, and I think enough
time has passed...
srw
response 51 of 135: Mark Unseen   Jul 3 04:24 UTC 1997

I'm inclined to agree that #0 can be considered, so the vote doesn't appear
premature to me. I'm not a board member, but that's my opinion.
rcurl
response 52 of 135: Mark Unseen   Jul 3 05:42 UTC 1997

#0 is just an idea, without any particulars. There are many ways to carry
it out, and better or worse ways to word it. The wording of a bylaw amendment
does have some importance, for clarity, conciseness, consistency with other
bylaws and/or policies, etc. I can understand why those that agreed with
the idea would think that the required period of discussion of the motion
had passed - especially if they agreed with the wording eventually proposed.
But, as we saw, the wording presented on 25 June was changed by Jan. It was
clear that a process of discussion was underway, which was prematurely
terminated. 
remmers
response 53 of 135: Mark Unseen   Jul 3 12:54 UTC 1997

Hmm. Here's the relevant bylaws section:

     a.  Any member of Grex may make a motion by entering it as the
         text of a discussion item in a computer conference on Grex
         designated for this purpose.  The item is then used for
         discussion of the motion.  All Grex users may participate in
         the discussion.  No action on the motion is taken for two
         weeks.  At the end of two weeks, the author may then submit a
         final version for a vote by the membership.  The vote is
         conducted on-line over a period of ten days.

If #0 can't be considered as "entering a motion" for purposes of
starting the clock ticking, then I don't think that anything else
in this item can either. Section a says that the proposal has to be
entered as the "text of a discussion item". This rules out its
being a response entered somewhere after the discussion has begun.

My thinking was that because the title of the item clearly announced
that this was a bylaw amendment proposal, and the substance of the
proposal was given in #0, that the clock could start ticking with #0.
From the fact that he called for a vote, I inferred that this was Jan's
intent as well, although I could be wrong.

But I also don't want to set bad precedents, as they open the door to
future abuses. Would we be doing that by letting the current vote
continue?
rcurl
response 54 of 135: Mark Unseen   Jul 3 16:16 UTC 1997

I consider "make a motion" as the critical phrase. A motion has a particular
structure. It states precisely what will be done, by whom, when, etc. A
general proposal is not a motion. 

As a compromise, I suggest that the vote be continued, but that the motion
be open to amendment up until 9 July, and then proceed for the requisite
voting period after that. If any change is made in the motion before 9 July,
notice of it should be made in the motd. This is all possible because of the
flexibility of the voting program to allow one to change one's vote.
valerie
response 55 of 135: Mark Unseen   Jul 3 16:44 UTC 1997

This response has been erased.

wh
response 56 of 135: Mark Unseen   Jul 3 21:06 UTC 1997

I agree with the compromise proposed by Rane in #54. We are not voting
on the general idea discussed in #0, but on the specifid text as
written on June 25. On all future items, we should adhere to the
concept that the two week discussion period begins when the final
text of the proposal has been entered. 

Since we have already started the vote, I think we should continue
it this time. If this happens again, I think we should cancel voting
and begin after two weeks of discussion have taken place.
mary
response 57 of 135: Mark Unseen   Jul 3 21:54 UTC 1997

Think about that Bill.  What would be the good of having
a set two week discussion period that follows the finished
wording?  We have never stipulated this be done.  In fact,
with most votes the final wording of a motion hasn't been
put together until just before the vote started.  The final
wording *follows* the discussion.

Jan made his intentions clear when he stated in #0 he
was proposing a change to the bylaws to clarify
organizational-type accounts.   I think Rane is just
doing what Rane does best. ;-)
janc
response 58 of 135: Mark Unseen   Jul 4 16:54 UTC 1997

I'm not sure if the vote is premature or not.  I think Rane's compromise would
be OK.  I think changing "never" to "not" would be an improvement.  But it
doesn't seem a big thing one way or another.
janc
response 59 of 135: Mark Unseen   Jul 4 17:08 UTC 1997

I guess that when I originally entered the item, I was suggesting an idea and
feeling out what people would want to see in such a proposal.  I got a sense
of general support for the idea, and some good suggestions, like calling it
"institutional membership" rather than "corporate membership".  Then I posted
some suggested wording for the bylaw changing.  After a bit more discussion
I incorporated that wording into a proposal for the bylaw change.

I'm not exactly sure at what point along this sequence the "discussion period"
started.  The subject has certainly been discussed for far longer than this
item has existed.  I think the concept of "institutional memberships" has
recieved adequate discussion, but the specific wording (eg, "never" vs "not")
might have been given a little more time.

I am, however, not happy with making even trivial changes to the wording after
some people have voted.  That's worse than bad grammar.

I would also be unhappy about stopping the vote and starting it again in a
few days.  Many people who voted during the first period, won't vote during
the second because they think they have already voted on this issue.  This
would screw up the vote pretty badly.  That's worse than bad grammar too.

So I think that (1) this vote should continue as started, to minimize
confusion, (2) we should talk about clarifying the bylaws on when exactly the
discussion period starts (if they aren't clear enough already), and (3) we
should someday do a "clean-up" amendment on the bylaws, making a bunch of
non-substantive changes to the bylaws to improve wording and clarity.  We
could fix "never" then.
rcurl
response 60 of 135: Mark Unseen   Jul 4 18:20 UTC 1997

What happened was that the current bylaw was not followed. That bylaw
provides that a motion be offered, which was not done until 25 June. There
is then supposed to be two weeks of discussion before the 'final' version
of the motion is presented, and the vote starts. However this period was
abbreviated to 6 days.

I agree that any change now would create confusion, but no more than the
departure from the bylaws. I also agree that things can be fixed later. 
Fortunately, this motion does not make a significant change in Grex
operation, and no one seems worried about it.

The current provisions for amendments need fixing. They do not allow for
the *membership* to amend the motion that is offered, except by the more
ponderous procedure of either accepting or rejecting an imperfected
motion, and then offering a substitute or new motion. It would be more
orderly to allow amendments, require a second (to bypass totally
unsupported motions or amendments), and generally follow ordinary
procedures for handling motions in meetings. 

wh
response 61 of 135: Mark Unseen   Jul 5 01:42 UTC 1997

Yes, Mary, you're right. The final version comes *after* the two
weeks of discussion. I guess the point I disagree on is the meaning
of "make a motion by entering it as the text of a discussion item..."
as quoted by Rane in #43. To make a motion, to me, means to propose
formal wording as one would at a meeting. It follows from that
assumption that the discussion period would begin after the first
proposed formal wording was posted.

The other interpretation I see here, with which I do not agree,
is that the motion can be made simply entering the text of a discussion
item as a proposed idea. E.g.

Would other members think it was a good idea to do such and such
because...

That would certainly be a good start to a discusion item, but would
it be the same as making a motion?
rcurl
response 62 of 135: Mark Unseen   Jul 5 18:10 UTC 1997

When people do start such discussion items someone often says, "why don't you
write up a motion and offer it for a vote" (or similar). 
remmers
response 63 of 135: Mark Unseen   Jul 6 14:47 UTC 1997

I agree that wording shouldn't be changed during a vote.

So is the gist of things to treat the clock tick as starting
with the first response in which Jan proposed a formal wording,
and extend the voting period accordingly?
rcurl
response 64 of 135: Mark Unseen   Jul 6 18:34 UTC 1997

I support that (though what I think what was really needed was more
discussion of the motion).
davel
response 65 of 135: Mark Unseen   Jul 7 16:58 UTC 1997

It would have been nice to have the announcement of the motion (in the motd,
I mean) occur near the start of the discussion period, not at the start of
voting.

If it was, my apologies - I've been on relatively infrequently lately,
& normally skim the motd rather fast due to its bloat.
rcurl
response 66 of 135: Mark Unseen   Jul 7 17:42 UTC 1997

davel has a good point. Since the posting of a motion starts a timed process,
notice of that should be posted to the motd.
tsty
response 67 of 135: Mark Unseen   Jul 8 09:24 UTC 1997

the strength of  'never' instead of 'not' is important for this change, imo,
adn let the voting extend... adn also put soemtihng in motd.
remmers
response 68 of 135: Mark Unseen   Jul 8 14:03 UTC 1997

Re #65: Motd bloat is one reason I'm reluctant to add things
there. Haven't done it in the past when a proposal is still in
the discussion stage, but I suppose it could be done in the
future. I guess my tacit assumption has always been that folks
who are interested in grex governance are already reading coop,
so there's not a strong need for motd notification.

Re #66: It's a timed process, but at the discussion stage has
no precisely defined endpoint. Voting starts at some point after
a two week period has elapsed, when the proposer comes up with
a final wording, but the timing of that is under the propoer's
control. Some discussions have gone on for quite a bit longer
that two weeks, so notification messages could potentially
linger in the motd for a long time. Is that what people want?
(Remember, "motd" stands for "message of the DAY"... :-)

If I had my druthers, I wouldn't put proposal discussion
announcements in the motd, only vote announcements. But if
there's wide support for it, I'll do it. How do other people
feel?
e4808mc
response 69 of 135: Mark Unseen   Jul 8 16:58 UTC 1997

dont put proposal discussions in the motd.  One only has to look at the
Feb/March/April confusion about wording and proposals on read-only access
via the web to see what a mess that would make the MOTD.  We had several
proposals going at once and votes queued up so that they wouldnt overlap.  

Blechh!

rcurl
response 70 of 135: Mark Unseen   Jul 8 17:38 UTC 1997

Nobody has said that democracy is neat and clean.
arianna
response 71 of 135: Mark Unseen   Jul 11 18:57 UTC 1997

It's a good thing I logged in today; I voted at the last possible moment,,
just about...  {:
remmers
response 72 of 135: Mark Unseen   Jul 12 01:45 UTC 1997

Oops, you have a few more days actually -- see the discussion
above. I'll update the announcement.
srw
response 73 of 135: Mark Unseen   Jul 12 03:32 UTC 1997

I don't like putting discussion notifications in the motd.
I agree that it is expected for people who care to be reading coop.
tsty
response 74 of 135: Mark Unseen   Jul 12 05:12 UTC 1997

i agreew ith not putting 'discussion notificatins' into the motd.
 
 i do agree, however, support and recommend that 'voting notice' be
qyite prominent in motd.
 .

po
 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