https://rocwiki.org/FarMcKon/TalkRecent Changes of the page "FarMcKon/Talk" on Rochester Wiki.en-us https://rocwiki.org/FarMcKon/Talkhttps://rocwiki.org/FarMcKon/Talk?action=diff&version1=0&version2=1&ts=11268030832005-09-15T16:51:23ZFarMcKon <div id="content" class="wikipage content"> Differences for FarMcKon/Talk<p><strong></strong></p><table> <tr> <td> <span> Deletions are marked with - . </span> </td> <td> <span> Additions are marked with +. </span> </td> </tr> <tr> <td> Line 1: </td> <td> Line 1: </td> </tr> <tr> <td> </td> <td> <span>+ == Proposal: CoOp Policy on Proposal Alteration ==<br> + <br> + Purpose: To allow reasonable Proposal Modification during a CoOp voting meeting.<br> + <br> + 1) Each proposal will begin with a 'purpose' statement, which cannot be changed during it's lifetime. This allows people to absentee table or absentee object to an issue. <br> + <br> + 2) If during a meeting a proposal change is requested, it will happen as follows:<br> + a) a members requests a 'proposal alteration', and must give his alterations in writing (the purpose is not editable).<br> + b) If consent is reached that the alteration makes a better proposal, the propsal will resume the consensus making process with the updated text/wording.<br> + <br> + <br> + -----<br> + <br> + == Proposal: Gridlock Extreme Override ==<br> + <br> + Purpose: To provide a way to avoid a single member from blocking everything, or becoming a nusance to the decision making process by being non-cooperative.<br> + <br> + <br> + If a proposal has been tabled or has been Majorly Objected twice in rather similar forms, the proposer can ask for a 'Gridlock Override' as follows.<br> + a) a members gives proof of previous blocking, and requests 'Gridlock Override'. The member may request a secret vote.<br> + <br> + b) The proposal is voted on, by secret ballot if requested. If the proposal passes by 2/3 of the entire CoOp population, or 3/4 of the current meeting attendeed (whichever is less), than the proposal is passed.<br> + <br> + -----<br> + == Proposal: House Naming ==<br> + <br> + Purpose: To make writing stuff about the house eaiser offically, and unoffically<br> + <br> + 1) I propose each Ant Hill Cooperative managed house have a unique name. 2) Since 960 and 972 S Plymouth Ave. are used as a single house, they together should be refered to as 'Ant House'.<br> + <br> + -----<br> + <br> + == Proposal: CoOpPolicy - House Position Kitchen Manager ==<br> + <br> + The Kitchen manager is a house position. A house can accept General Members to be part of it's Foodshare at it's own discretion. <br> + <br> + Responsiblities:<br> + * Managing the Foodshare kitchen<br> + * Managing other private kitchens, <br> + * managing the purchasing and supply of foodstuffs,<br> + * managing cooking related equipment. <br> + * managing cooking tasks, to be equally distributed amoung Foodshare members<br> + * Drawing up a Session Forecast Foodshare Budget with the Treasurer within a week of the start of the new 'housing session'.<br> + * Collecting and compiling all recepts from Kitches/Foodshare purchaes to be turned over to the Treasurer for reembursement weekly on Sunday evenings.<br> + * Collecting payment from Dinner guests, to be turned over to the treasurer weekly on Sunday.<br> + * At the end of each month, with the treasurer's help, checking the last month's costs vs. budget, for the Treasurers record.<br> + <br> + The Kitchen Manager will recieve proper credit for work done in the post when a workshare system is implemented. The kitchen manager can take </span> </td> </tr> </table> </div>