<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><span><div><font face="times new roman, new york, times, serif">
Hi All</font></div><div><font face="times new roman, new york, times, serif"></font> </div><div><span style='color: black; font-family: "Arial","sans-serif"; font-size: 10pt; mso-fareast-font-family: "Times New Roman";'><font face="times new roman, new york, times, serif"><font size="3">Based on a few of the emails that came through this week, there seems to be 2 factions here that are stalling out the policy developement (ie, the service- verses the donation-based models). In my </font></font></span><span style='color: black; font-family: "Arial","sans-serif"; font-size: 10pt; mso-fareast-font-family: "Times New Roman";'><font face="times new roman, new york, times, serif"><font size="3">opinion, both are equally valid, but somewhat different philosophically. <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></font></font></span></div><div><font face="times new roman, new york, times,
serif">
</font></div><div style="margin: 0in 0in 10pt;" class="MsoNormal"><span style='color: black; line-height: 115%; font-family: "Arial","sans-serif"; font-size: 10pt; mso-fareast-font-family: "Times New Roman";'><font size="3" face="times new roman, new york, times, serif">Since
both sides are somewhat entrenched down a bit, could we mutally accept both approaches and construct a policy that includes
both service and monetary donations together, (i.e. one could gain key access by
either contributing service or by donating or both). I think both sides feel strongly about thier own preferred method, so constructing an either or policy may be difficult to achieve. However the space could use both volunteer efforts and donations. We could still implement a security/approval/responsibilitly process for both approaches as needed. </font></span></div><div style="margin: 0in 0in 10pt;" class="MsoNormal"><span style='color: black; line-height: 115%; font-family: "Arial","sans-serif"; font-size: 10pt; mso-fareast-font-family: "Times New Roman";'><font size="3" face="Times New Roman">Would anyone out there be absolutely against preparing a policy that includes both approaches? If so, why?</font></span></div><div style="margin: 0in 0in 10pt;" class="MsoNormal"><span style='color: black; line-height: 115%; font-family: "Arial","sans-serif"; font-size: 10pt; mso-fareast-font-family:
"Times New Roman";'><font size="3" face="Times New Roman">Jeff T</font></span></div><div style="margin: 0in 0in 10pt;" class="MsoNormal"></span> </div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <div style="margin: 5px 0px; padding: 0px; border: 1px solid rgb(204, 204, 204); height: 0px; line-height: 0; font-size: 0px;" class="hr" contentEditable="false" readonly="true"></div> <font size="2" face="Arial"> <b><span style="font-weight: bold;">From:</span></b> Braden Pellett <braden@davismakerspace.org><br> <b><span style="font-weight: bold;">To:</span></b> Davis Makerspace General Discussions <discuss@lists.davismakerspace.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, October 15, 2013 11:02 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [dms-discuss]
Comments on Key Committee and digital access<br> </font> </div> <div class="y_msg_container"><br>
Hi Tim and all,<br><br>Just to pick out one thing I wanted to ask about:<br><br>On Mon, Oct 14, 2013 at 12:21:06AM -0700, Tim Feldman wrote:<br>> We do have bylaws about eligibility for voting, so one possible decision method<br>> would be for all eligible voters to vote on granting digital access to a<br>> particular applicant. I don't think that would be responsible access, and I<br>> doubt that we could get the necessary consensus. So I don't favor that "general<br>> vote" method.<br><br>Could you explain more about why you do not think it would be responsible access, and why you do not think we could get the necessary consensus?<br><br>Frankly, simply in terms of the process of giving a key (and independent of the responsibilities of having one), I rather like the idea of treating it like any other resolution seeking consensus. In other words, somewhat similar to what we did with Lucian, but with two very important
additions:<br><br>- Like any decision, it should be specifically announced prior to the meeting as an item for seeking consensus, as stated in our bylaws about matters requiring giving notice.<br><br>- Unlike other decisions, once we officially seek the consensus of the group, the keyholder in question should not be present, due to the obvious social pressures involved with possibly rejecting someone to their face, etc. (Or, perhaps more generally, we could further say any "interested party" may not be present for that particular taking of consensus for that particular decision.)<br><br>In terms of process (vs the specifics of key-holder requirements and responsibilities), I'm curious if and how others would see the above as a tenible or untenible method.<br><br>Thanks,<br> Braden<br>_______________________________________________<br>Discuss mailing list<br><a href="mailto:Discuss@lists.davismakerspace.org"
ymailto="mailto:Discuss@lists.davismakerspace.org">Discuss@lists.davismakerspace.org</a><br>http://lists.davismakerspace.org/listinfo/discuss<br><br><br></div> </div> </div> </div></body></html>