<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:12pt"><div style="color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: 12pt; background-color: rgb(255, 255, 255);"><div><span><em>Hi all,</em></span></div><div><span></span><em> </em></div><div><span><em>Following up from last months meeting, here is a proposed key policy for possible consideration in either January for February. This policy was developed out of the on-going key policy discussion, but is largely based on comments from the November meeting and incorporates the proposal based, open vote approach.</em></span></div><div><span><em></em></span> </div><div><em>Note, this is not a set policy at this point. It is only a proposal. However, if it looks like we have enough folks supporting it, we would put it up for
vote.</em></div><div><em> </em></div><div><span><em>For the interim, please reveiw, and let me know if you have input.</em></span></div><div><span></span><span></span><em> </em></div><em> </em><div><span><em>Jeff T</em></span></div><div><span></span></div><div><span>*******************************************************************</span></div><div><span></span> </div><span><div><font face="arial, helvetica, sans-serif"># Davis Makerspace Provisional Key Policy #</font></div><div><font face="arial, helvetica,
sans-serif"></font> </div><div><font face="arial, helvetica, sans-serif">## Purpose of Provisional Key Policy ##</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica, sans-serif">This policy describes the current Davis Makerspace approach for<br>providing key access to the Davis Makerspace facilities. The intent<br>of this policy is to provide a temporary guideline for
distributing<br>key access until a more formalized policy is established. A more<br>formalized policy can be proposed at any time. As a provisional policy,<br>however, the approach described below generally uses existing<br>mechanisms defined by current Davis Makerspace Bylaws. This policy <br>does not necessarily limit other methods for distributing key access,<br>but is intended to function as the recommended method.</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica,
sans-serif">## Process ##</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica, sans-serif">Key access will be considered on a case by case basis, and granted<br>upon consensus vote as defined in the Davis Makerspace Bylaws. The<br>general process for key-holdership consideration shall be as follows:</font></div><div><font face="arial, helvetica, sans-serif"></font>
</div><div><font face="arial, helvetica,
sans-serif">1. Submit a Proposal for Key Access,<br>2. Submit an optional Statement of Nomination,<br>3. the board will arrange public meeting to consider the proposal,<br>4. the proposal will be accepted or declined by consensus vote, and<br>5. if the proposal is accepted, key-holdership will be granted, <br> subject to any conditions stated in the accepted proposal.</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica, sans-serif">## Details of Process Elements ##</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica, sans-serif">### Proposal for Key Access ###</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica, sans-serif">Due to the wide variety of reasons and opinions on why keys should or<br>should not be distributed, key access will be
considered on a case by<br>case basis. To aid consideration, potential key-holders should<br>provide a Proposal for Key Access. The Proposal for Key Access shall<br>be a written statement describing why the potential key-holder should<br>have key access to Davis Makerspace facilities. If accepted by consensus <br>vote, as prescribed by the Davis Makerspace Bylaws, the Proposal for <br>Key Access will also function as an agreement with the Davis Makerspace <br>Corporation and state the conditions for key access. Therefore, any <br>potential conditions related to the key access should be included in the <br>Proposal for Key Access. Potential key-holders can propose any conditions<br>or reasoning they see fit in justifying key access. However, since the <br>proposal is subject to consensus vote as defined in the Davis Makerspace <br>Bylaws, the contents of proposal should include provisions that all <br>eligible voting members will be agreeable to. The
Proposal for Key Access <br>will be provided to the public prior to voting, and will typically remain <br>available for public review after any vote. </font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div>To provide initial examples of proposals, existing key-holders will be asked </div><div>to prepare thier own Proposal for Key Access based on thier exisiting key </div><div>holding arrangements. These proposals would available for public review </div><div>along with future proposals.</div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica,
sans-serif">### Statement Granting Unlimited Key Revocation Rights to the Board ###</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica, sans-serif">In considering Proposals for Key Access, the Board of Directors, would <br>prefer the following statement be included
as part of any Proposal for <br>Key Access:</font></div><blockquote style="margin-right: 0px;" dir="ltr"><div><font face="arial, helvetica, sans-serif">If granted key access, I, __(name of proposed key-holder) ,<br>understand that key access to any Davis Makerspace facility can be<br>revoked, by any Davis Makerspace Board Member, for any reason,<br>without limit. I will have the opportunity to appeal any<br>revocation by consensus vote, as described by Davis Makerspace<br>Bylaws, but the revocation of key access will remain in place<br>until properly relinquished by the appeal.</font></div></blockquote><div><font face="arial, helvetica,
sans-serif">This statement will not be required as part of the Proposal for Key<br>Access, but the absence of this statement may be favored negatively by<br>voting parties.</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica,
sans-serif">### Statement of
Nomination ###</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica, sans-serif">In addition to a Proposal for Key Access, potential key-holders are<br>encouraged to submit a written Statement of Nomination prepared by any<br>party other than themselves. The Statement of Nomination is optional,<br>but will help establish the level of involvement the potential<br>key-holder has with members of the Davis Makerspace community, and as<br>such, is encouraged. The Statement of Nomination may be prepared by<br>anyone, but since it will be subject to consensus vote, as described <br>by the Davis Makerspace Bylaws, the preparing party should generally be <br>selected to satisfy all eligible voting members. Like the Proposal for <br>Key Access, the Statement of Nomination will be provided to all eligible <br>voters prior to voting, and will typically remain available for public <br>review after any
vote.</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica, sans-serif">### Public Meeting to Consider the Proposal ###</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica, sans-serif">Upon receipt of the Proposal for Key-Access and if applicable, the <br>Statement of Nomination, a meeting will be arranged by the Board of <br>Directors, typically by the President or Secretary of the Davis <br>Makerspace Corporation, per the Davis Makerspace Bylaws. In general, <br>this meeting will be a public meeting, providing adequate notice and <br>proxy voting, as described in the Davis Makespace By-laws. Furthermore, <br>since the proposed key-holder will be ineligible from voting on their <br>own Proposal for Key Access, an effort will be made to schedule the <br>meeting separately from general meetings. In general, votes to accept <br>or not accept the
proposal will be conducted at the meeting. Voting will <br>be by consensus vote as defined by the Davis Makerspace Bylaws.</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica, sans-serif">### Acceptance and Conditions of the Proposal for Key Access ###</font></div><div><font face="arial, helvetica, sans-serif"></font> </div><div><font face="arial, helvetica, sans-serif">If the Proposal for Key Access is accepted by consensus vote as defined <br>by the Davis Makerspace Bylaws, the conditions described in the Proposal <br>for Key Access will govern the key holdership. The Proposal for Key Access <br>will be typically be available for public review, and may be amended by <br>additional proposals, provided they comply with Davis Makerspace Bylaws</font></div></span></div></div></body></html>