[517] in UA Senate
Re: Senate Bylaws Maintenance Bill
daemon@ATHENA.MIT.EDU (Daniel Hawkins)
Sun Apr 4 21:09:31 2010
Reply-To: hwkns@MIT.EDU
In-Reply-To: <4BB93723.8030305@mit.edu>
Date: Sun, 4 Apr 2010 21:09:28 -0400
From: Daniel Hawkins <hwkns@MIT.EDU>
To: Tim Stumbaugh <stum@mit.edu>
Cc: Alex Dehnert <adehnert@mit.edu>, UA Senate <ua-senate@mit.edu>
--0016e647650216b866048372fbea
Content-Type: text/plain; charset=ISO-8859-1
Oh, I see - yeah, you have to specifically move to take something off the
table. RONR does allow for postponing until a certain date or meeting. We
could specify that instead of tabling...
On Sun, Apr 4, 2010 at 9:04 PM, Tim Stumbaugh <stum@mit.edu> wrote:
> OK. That's fine. I'll update it.
> The point I am trying to make is that in RONR, things on the table at the
> end of a meeting just fall to the floor. I'm just trying to make it so what
> we intend is actually what's in the bylaws.
>
>
> On 4 Apr 2010 19.14, Daniel Hawkins wrote:
>
>> If people really don't like it the first time, they can move to postpone
>> indefinitely. That's not exactly the same, but I think it serves the
>> same purpose.
>>
>> -hwkns
>>
>> On Sun, Apr 4, 2010 at 7:05 PM, Tim Stumbaugh <stum@mit.edu
>> <mailto:stum@mit.edu>> wrote:
>>
>> I was thinking that if people really don't like it the first time, we
>> save a week. I'm fine with just having the dereference to the table
>> and just say it must appear on the agenda at two separate meetings.
>>
>> On 4/4/10, Alex Dehnert <adehnert@mit.edu <mailto:adehnert@mit.edu>>
>>
>> wrote:
>> > Can you say anything about why you want a two-thirds majority at
>> each
>> > meeting? That seems like it will add unnecessary overhead to the
>> > process. I think that the idea behind requiring it sit on the
>> table for
>> > a week is to avoid surprising people who might care, and I don't
>> think
>> > requiring an affirmative vote at each meeting helps that any.
>> >
>> > Thanks,
>> > Alex
>> >
>>
>>
>> --
>> -Tim
>> "There is no emotion, there is peace."
>>
>>
>>
> --
> -Tim
> "Live right now/Just be yourself/It doesn't matter if it's good enough for
> someone else."
>
--0016e647650216b866048372fbea
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Oh, I see - yeah, you have to specifically move to take something off the t=
able.=A0 RONR does allow for postponing until a certain date or meeting.=A0=
We could specify that instead of tabling...<br><br><div class=3D"gmail_quo=
te">
On Sun, Apr 4, 2010 at 9:04 PM, Tim Stumbaugh <span dir=3D"ltr"><<a href=
=3D"mailto:stum@mit.edu">stum@mit.edu</a>></span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px =
solid rgb(204, 204, 204); padding-left: 1ex;">
OK. That's fine. I'll update it.<br>
The point I am trying to make is that in RONR, things on the table at the e=
nd of a meeting just fall to the floor. I'm just trying to make it so w=
hat we intend is actually what's in the bylaws.<div class=3D"im"><br>
<br>
On 4 Apr 2010 19.14, Daniel Hawkins wrote:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex;=
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class=
=3D"im">
If people really don't like it the first time, they can move to postpon=
e<br>
indefinitely. =A0That's not exactly the same, but I think it serves the=
<br>
same purpose.<br>
<br>
-hwkns<br>
<br>
On Sun, Apr 4, 2010 at 7:05 PM, Tim Stumbaugh <<a href=3D"mailto:stum@mi=
t.edu" target=3D"_blank">stum@mit.edu</a><br></div><div class=3D"im">
<mailto:<a href=3D"mailto:stum@mit.edu" target=3D"_blank">stum@mit.edu</=
a>>> wrote:<br>
<br>
=A0 =A0I was thinking that if people really don't like it the first ti=
me, we<br>
=A0 =A0save a week. I'm fine with just having the dereference to the t=
able<br>
=A0 =A0and just say it must appear on the agenda at two separate meetings.=
<br>
<br></div>
=A0 =A0On 4/4/10, Alex Dehnert <<a href=3D"mailto:adehnert@mit.edu" tar=
get=3D"_blank">adehnert@mit.edu</a> <mailto:<a href=3D"mailto:adehnert@m=
it.edu" target=3D"_blank">adehnert@mit.edu</a>>><div class=3D"im"><br=
>
=A0 =A0wrote:<br>
=A0 =A0 > Can you say anything about why you want a two-thirds majority=
at each<br>
=A0 =A0 > meeting? That seems like it will add unnecessary overhead to =
the<br>
=A0 =A0 > process. I think that the idea behind requiring it sit on the=
<br>
=A0 =A0table for<br>
=A0 =A0 > a week is to avoid surprising people who might care, and I do=
n't<br>
=A0 =A0think<br>
=A0 =A0 > requiring an affirmative vote at each meeting helps that any.=
<br>
=A0 =A0 ><br>
=A0 =A0 > Thanks,<br>
=A0 =A0 > Alex<br>
=A0 =A0 ><br>
<br>
<br>
=A0 =A0--<br>
=A0 =A0-Tim<br>
=A0 =A0"There is no emotion, there is peace."<br>
<br>
<br>
</div></blockquote><font color=3D"#888888">
<br>
-- <br>
-Tim<br>
"Live right now/Just be yourself/It doesn't matter if it's goo=
d enough for someone else."<br>
</font></blockquote></div><br><div style=3D"visibility: hidden; display: in=
line;" id=3D"avg_ls_inline_popup"></div><style type=3D"text/css">#avg_ls_in=
line_popup { position:absolute; z-index:9999; padding: 0px 0px; margin-=
left: 0px; margin-top: 0px; width: 240px; overflow: hidden; word-wrap: =
break-word; color: black; font-size: 10px; text-align: left; line-heigh=
t: 13px;}</style>
--0016e647650216b866048372fbea--
