Talk:Pending Proposals: Difference between revisions

From Hive76 Wiki
Jump to navigationJump to search
No edit summary
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Adam's Points =  
= Discussion of Membership Dues Payment Deadlines (for meeting 3/16/2010) =
'''I don't think we should have to wait for weds to vote on everything. Is there a good reason we can't use online polls and just have a set  time votes are accepted based on impact/urgency?'''
I like the proposal it's a good idea, and we need to get payment under control  I think stopping telephone access to the space is enough of an incentive. Stopping mail can be a real pain in the ass, and can kill a project or communication going on outside the group. I also think we should send out a mail to member on the 14th, listing who has not paid for the month yet. As of that email they are subject to the phone access being shut off, but they should get a reminder/notice that they might get shut off, and so there is some social pressure to keep paid, since everyone sees the list. In official terms, they would be marked as 'Behind Payment.'
IMHO talking in person is often the fastet way to agree or discuss something. We could just make a poll, but I think we'd make better smarter faster stronger decisions when we have some in person discussion.  It also is a good marker/end-of-timeline for voting on something if we do have an 'open poll' vote.
Then after 30 days of not being paid up, a second notice is sent out, and *then* blog, email, and voting access get turned off. In official terms, In 'Bad Standing.'
Also, often proposals get tweaked/updated during a dicussion. Long open polls (3+days)and I worry people will vote on an alpha version, but disagree with beta version, so we have to do vote-retraction or something.
I also think we should add 'If a member requests a late payment (via email to management@Hive76.org) a majority vote of Management can wave penalties' just in case as well.
Maybe the best thing would be to have an open poll, and just end it Wednesday at midnight. Part of the weekly standup could be talking over anything that is in the queue. For time-sensitive issues, I think an online poll is awesome.
=An Example of a Propoal=
'''As for the proposal process, is the original author responsible for making modifications on the wiki based on changes from discussion? We should probably also provide a link from the wiki page back to the original discussion list post.'''
<pre><nowiki>
I like both of those ideas.
=Events Coordinator - create position APPROVED=
= From Jack =
==Status==
'''Can we password protect a wiki? Certain details like phone numbers and budget stuff can't go on a wiki.'''
APPROVED 3/3/10 - 14 members present (real, IRC, proxy) Votes: For:9 Against:1
Jack has a good point on that. I'd say for stuff that is private, we can put it on google docs as 'members only' and in the wiki post a title and  
==Purpose==
a link to the protected vote/stuff.
A new position should be created for a Events Coordinator. This person will not plan events on his/her lonesome, but will instead have periodic planning meetings to delegate individual events to responsible members, and possibly Far. He/she will establish a best-practices for holding events, ensure the quality of events being held, and make sure that anyone who wants to run an event has all the necessary knowledge and resources they need.  The Event Coordinator is NOT in charge of the email sign-in-sheet but he/she probably will end up doing it anyway.
IMHO (I'm curious about others) very little/few things would need that protection, negotiation, big purchases, final budget stuff probably. But I don't think general reimbursement would have to be private.  Thoughts?
</nowiki></pre>
= (related) Docs vs Wiki: =  
And how it looks in the wiki:
'''Personally, I fully intend to continue using google docs for sharing/collecting data. We get way too much for free (access control, auto-gen forms) that wouldn't easily be replaced by a single application. I think it's completely reasonable to use google docs if there's a project you would rather keep under wraps for a while.'''
=Events Coordinator - create position APPROVED=
Hell yeah, well said.
==Status==
APPROVED 3/3/10 - 14 members present (real, IRC, proxy) Votes: For:9 Against:1
==Purpose==
A new position should be created for a Events Coordinator.  This person will not plan events on his/her lonesome, but will instead have periodic planning meetings to delegate individual events to responsible members, and possibly Far.  He/she will establish a best-practices for holding events, ensure the quality of events being held, and make sure that anyone who wants to run an event has all the necessary knowledge and resources they need.   The Event Coordinator is NOT in charge of the email sign-in-sheet but he/she probably will end up doing it anyway.

Latest revision as of 21:00, 10 March 2010

Discussion of Membership Dues Payment Deadlines (for meeting 3/16/2010)

I like the proposal it's a good idea, and we need to get payment under control I think stopping telephone access to the space is enough of an incentive. Stopping mail can be a real pain in the ass, and can kill a project or communication going on outside the group. I also think we should send out a mail to member on the 14th, listing who has not paid for the month yet. As of that email they are subject to the phone access being shut off, but they should get a reminder/notice that they might get shut off, and so there is some social pressure to keep paid, since everyone sees the list. In official terms, they would be marked as 'Behind Payment.' Then after 30 days of not being paid up, a second notice is sent out, and *then* blog, email, and voting access get turned off. In official terms, In 'Bad Standing.' I also think we should add 'If a member requests a late payment (via email to [email protected]) a majority vote of Management can wave penalties' just in case as well.

An Example of a Propoal

=Events Coordinator - create position APPROVED=
==Status==
APPROVED 3/3/10 - 14 members present (real, IRC, proxy) Votes: For:9 Against:1
==Purpose==
A new position should be created for a Events Coordinator.  This person will not plan events on his/her lonesome, but will instead have periodic planning meetings to delegate individual events to responsible members, and possibly Far.  He/she will establish a best-practices for holding events, ensure the quality of events being held, and make sure that anyone who wants to run an event has all the necessary knowledge and resources they need.   The Event Coordinator is NOT in charge of the email sign-in-sheet but he/she probably will end up doing it anyway.

And how it looks in the wiki:

Events Coordinator - create position APPROVED

Status

APPROVED 3/3/10 - 14 members present (real, IRC, proxy) Votes: For:9 Against:1

Purpose

A new position should be created for a Events Coordinator. This person will not plan events on his/her lonesome, but will instead have periodic planning meetings to delegate individual events to responsible members, and possibly Far. He/she will establish a best-practices for holding events, ensure the quality of events being held, and make sure that anyone who wants to run an event has all the necessary knowledge and resources they need. The Event Coordinator is NOT in charge of the email sign-in-sheet but he/she probably will end up doing it anyway.

Retrieved from "https://wiki.hive76.org/index.php?title=Talk:Pending_Proposals&oldid=935"