<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">Thanks Jim!<div><br></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"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> Jim Stewart <jstewart@jkmicro.com><br> <b><span style="font-weight: bold;">To:</span></b> Jeff Tolentino <jefftolentino@yahoo.com>; Davis Makerspace General Discussions <discuss@lists.davismakerspace.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Monday, October 14, 2013 10:02 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [dms-discuss] Key Policy thoughts<br> </font> </div> <div class="y_msg_container"><br>
<div id="yiv525825293">
<div>
<div class="yiv525825293moz-cite-prefix">
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">My comments in
violet - Jim</span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;"> </span></div>
<i style=""><span style="color:red;">Jim,
See my
responses/comments below. Thanks for taking the time to
prepare this!</span></i>
<div class="yiv525825293MsoNormal"><i><span style="color:red;"> </span></i></div>
<div class="yiv525825293MsoNormal"><i style=""><span style="color:red;">Jeff T</span><span style="color:#548DD4;
"><br style="">
<br style="">
<span style=""></span><span style="color:red;"></span></span></i></div>
<div class="yiv525825293MsoNormal"><span style="color:#548DD4;"><br style="
">
<br style="">
<span style="
"></span></span></div>
<div class="yiv525825293MsoNormal"><span style="color:#548DD4;"><span style="
">After reading over the Key Policy Development wiki
page,<br>
here are my thoughts...<br>
<br>
<br>
Prerequisites for all keyholders:<br>
<br>
Age 18 or greater. <span style=""> </span></span></span><i style=""><span style="color:red;">Good</span></i><span style="color:#548DD4;"><br>
<span style=""><br>
Member in good standing. <span style=""> </span></span></span><i style=""><span style="color:red;">Agreed</span></i><span style="color:#548DD4;"><br>
<span style=""><br>
Ability and willingness to assist and/or mentor other<br>
Makerspace members or the public in at least one skill<br>
supported by the space. <span style=""> </span></span></span><i style=""><span style="color:red;">Agreed</span></i><span style="color:#548DD4;"><br>
<span style=""><br>
Examples would be 3D printers, electronics,<br>
Arduino development, art projects, carpentry<br>
or metalworking. </span></span><i style=""><span style="color:red;">Good</span></i><span style="color:#548DD4;"><br>
<span style="
"><br>
Willingness to accept the role of Davismakerspace<br>
representative to the community. <span style=""> </span></span></span><i style=""><span style="color:red;">Good</span></i><span style="color:#548DD4;"><br>
<span style=""><br>
New visitors can be easily discouraged by being<br>
ignored or treated with annoyance or condescension.<br>
Keyholders would be expected to greet visitors,<br>
explain the resources available, and encourage<br>
them to attend the next meeting. <span style=""> </span></span></span><i style=""><span style="color:red;">Good</span></i><span style="color:#548DD4;"><br>
<span style=""><br>
Signed Keyholder Agreement on file </span></span><i style="
"><span style="color:red;">Good suggestion</span></i><span style="color:#548DD4;"><br>
<span style=""><br>
Another project. I think a Keyholder Agreement<br>
is needed to clearly spell out the responsibilities<br>
of the job. I'm willing to help develop it. <span style=""> </span></span></span><i style="
"><span style="color:red;">Good.<span style="">
</span>I’d love if you’d like to develop this!</span></i><span style="color:#548DD4;"><br>
<span style=""><br>
<br>
Members meeting all of the above requirements are<br>
also expected to contribute to the Davismakerspace<br>
in at least one of the following ways:<br>
<br>
Financial. <span style=""> </span></span></span><i style=""><span style="color:red;">I
feel that this
could to be a sticking point for the group.<span style="">
</span>There have been a couple comments that monetary
donations should not be
a part of the key access process.<span style=""> </span>To
help aid the discussion, could you expand a little on why
you support the fee
model?<span style=""> </span>One of the
criticisms was that
giving money doesn’t necessarily equal trustworthiness.</span></i><span style="color:#548DD4;"><br style="">
<br style="">
<span style=""></span></span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">Two reasons, one
selfish and the
other not so much.<span style=""> </span>Personally,
the
financial model works for me.<span style="">
</span>I already
have access to three separate well-stocked shops in the
evenings and on
weekends.<span style=""> </span>Currently,
I’d get less done
at the Makerspace than at home or work.<span style="">
</span>OTOH, resources like the 3D printers and the large
graphics printer
would make access worth the $30/month.<span style="">
</span>And being part of the community through the Makerspace.<span style=""> </span></span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;"> </span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">The
not-so-selfish reason is that
just about any business needs a reliable, recurring source of
income.<span style=""> </span>Since there is
no longer a membership fee
model, I feel that another recurring</span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">source of income
will be needed
for the ongoing financial health of the group.</span></div>
<div class="yiv525825293MsoNormal"><span style="color:#548DD4;"> </span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">As to the
argument “giving money
doesn’t necessarily equal trustworthiness”, I agree.<span style=""> </span>But neither does giving
time.<span style=""> </span>I structured my
proposal firstly with a
series of prerequisites for everyone.<span style="">
</span>The idea is to do the trustworthiness vetting with
them, not whether a
person gives time or money.<span style=""> </span><span style=""> </span></span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;"> </span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">Just in passing,
over the years
I’ve trusted a couple dozen people with keys to my business.<span style=""> </span>Most of them had a very
high level of
personal integrity.<span style=""> </span>A
few of them had
questionable levels of personal integrity.<span style="">
</span>None of them ever stole a penny’s worth of goods, tools
or anything
else.<span style=""> </span>I don’t believe
this is because I’m
a good judge of character.<span style=""> </span>More
likely,
it’s because our interests preselect for people that are
inherently</span><span style="color:fuchsia;">
honest.<span style=""> </span></span>
</div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;"> </span></div>
<div class="yiv525825293MsoNormal"><span style="color:#548DD4;"><br>
A continuing level of donation. $30 per month<br>
has been discussed.<br>
<br>
Time<br>
<br>
A minimum committment of 5 hours a month. Board<br>
member activity would be counted towards the<br>
time committment as would fundraising, public<br>
relations and educational work. General meeting<br>
attendance would not count. <span style=""> </span></span><i style=""><span style="color:red;">OK</span></i><span style="color:#548DD4;"><br>
<span style=""><br>
The 5 hours number was just pulled out of the<br>
air. <span style=""> </span></span></span><i style=""><span style="color:red;">OK</span></i><span style="color:#548DD4;"><br>
<span style=""><br>
Service<br>
<br>
At the board's pleasure, keyholder privilages<br>
might be granted for extraordinary service in<br>
support of the goals of the organization, the<br>
community, or the Makers movement. </span></span><span style="color:red;"><span style=""> </span><i style="">Noted.</i></span><span style="color:#548DD4;"><br>
<span style=""><br>
<br>
<br>
Keyholder Approval Process<br>
<br>
I propose the creation of a 3 member Keyholder<br>
committee of <b style="">board
members</b> and/or
current<br>
keyholders. The committee would meet in private<br>
with perspective keyholders, review the pre-<br>
requisites and either recommend or decline to<br>
recommend keyholder privileges be granted to<br>
the applicant.<br>
<br>
Committee members declining a member for keyholder<br>
privileges would be expected to explain their reasoning,<br>
offer suggestions for remedying issues standing<br>
in the way of keyholder status and advise when the<br>
member can reapply. All information and discussion<br>
of declined keyholder privileges must remain confidential.</span></span></div>
<div class="yiv525825293MsoNormal"><i style=""><span style="color:red;">This seemed slightly ambiguous, so I just
want to clarify,
the committee members would only need to explain their
reasoning for denial,<br>
offer suggestions for remedying issues standing<br>
in the way of keyholder status and advise when the<br>
member can reapply to the proposed keyholder, correct?<span style=""> </span>Otherwise, that
information would be
confidential to everyone else.<span style="">
</span>Similarly, would discussion of approved keyholder
privilages be public
information?</span></i><span style="color:#548DD4;"><br style="
">
<br style="">
<span style=""></span></span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">Sorry for the
ambiguity.<span style=""> </span></span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;"> </span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">To put it another
way, the
keyholder approval process should</span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">be treated like a
Human
Resources activity, with discretion</span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">and appropriate
confidentiality.<span style=""> </span></span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;"> </span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">By “approved
keyholder
privilages”, do you mean global privilages,</span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">Or <span style=""> </span>possibly restricted
privilages for a specific
member?<span style=""> </span><span style=""> </span><span style=""> </span>As to</span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">global
privilages, I see no
reason why that would be confidential.</span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;"> </span></div>
<div class="yiv525825293MsoNormal"><span style="color:fuchsia;">I have not
considered restricted
privilages.<span style=""> </span></span></div>
<div class="yiv525825293MsoNormal"><span style="color:#548DD4;"> </span></div>
<div class="yiv525825293MsoNormal"><span style="color:#548DD4;"> </span></div>
<div class="yiv525825293MsoNormal"><span style="color:#548DD4;"><br>
Members recommended for keyholder privilege will<br>
be recommended to the board at the next general meeting.<br>
<br>
<span style=""> </span>The intention here is
that the board
would unanimously<br>
approve anyone recommended for keyholder privileges.<br>
Making the event public would give recogition to the<br>
new keyholder. <span style=""> </span></span><i style=""><span style="color:red;">Noted</span></i></div>
<div class="yiv525825293MsoNormal"> </div>
<style>
<!--
#yiv525825293
#yiv525825293 p.yiv525825293MsoNormal, #yiv525825293 li.yiv525825293MsoNormal, #yiv525825293 div.yiv525825293MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New Roman";}
_filtered #yiv525825293 {margin:1.0in 1.25in 1.0in 1.25in;}
#yiv525825293 div.yiv525825293Section1
{}
-->
</style><br>
<br>
<br>
Jeff Tolentino wrote:<br>
</div>
<blockquote type="cite">
<div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt;">
<div class="yiv525825293MsoNormal"><br>
<i style=""><span style="color:red;">Jim,
See my responses/comments below. Thanks for taking the
time to prepare this!</span></i></div>
<div style="color:red;font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:italic;" class="yiv525825293MsoNormal"><br>
<i style=""><span style="color:red;"></span></i></div>
<div style="color:red;font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:italic;" class="yiv525825293MsoNormal"><i style=""><span style="color:red;">Jeff
T</span></i><span style="color:#548DD4;"><br>
</span></div>
<div style="color:rgb(84, 141, 212);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;" class="yiv525825293MsoNormal"><span style="color:#548DD4;
"><br>
</span></div>
<div style="color:rgb(84, 141, 212);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;" class="yiv525825293MsoNormal"><span style="color:#548DD4;
">After reading over the Key Policy Development wiki
page,<br>
here are my thoughts...<br>
<br>
<br>
Prerequisites for all keyholders:<br>
<br>
Age 18 or greater.<span style=""> </span></span><i style=""><span style="color:red;">Good</span></i><span style="color:#548DD4;"><br>
<br>
Member in good standing.<span style=""> </span></span><i style=""><span style="color:red;">Agreed</span></i><span style="color:#548DD4;"><br>
<br>
Ability and willingness to assist and/or mentor other<br>
Makerspace members or the public in at least one skill<br>
supported by the space. <span style=""> </span></span><i style=""><span style="color:red;">Agreed</span></i><span style="color:#548DD4;"><br>
<br>
Examples would be 3D printers, electronics,<br>
Arduino development, art projects, carpentry<br>
or metalworking. </span><i style=""><span style="color:red;">Good</span></i><span style="color:#548DD4;
"><br>
<br>
Willingness to accept the role of Davismakerspace<br>
representative to the community.<span style=""> </span></span><i style=""><span style="color:red;">Good</span></i><span style="color:#548DD4;"><br>
<br>
New visitors can be easily discouraged by being<br>
ignored or treated with annoyance or condescension.<br>
Keyholders would be expected to greet visitors,<br>
explain the resources available, and encourage<br>
them to attend the next meeting.<span style=""> </span></span><i style=""><span style="color:red;">Good</span></i><span style="color:#548DD4;"><br>
<br>
Signed Keyholder Agreement on file </span><i style=""><span style="color:red;">Good
suggestion</span></i><span style="color:#548DD4;"><br>
<br>
Another project. I think a Keyholder Agreement<br>
is needed to clearly spell out the responsibilities<br>
of the job. I'm willing to help develop it.<span style=""> </span></span><i style=""><span style="color:red;">Good.<span style=""> </span>I’d love if you’d
like to develop this!</span></i><span style="color:#548DD4;"><br>
<br>
<br>
Members meeting all of the above requirements are<br>
also expected to contribute to the Davismakerspace<br>
in at least one of the following ways:<br>
<br>
Financial.<span style=""> </span></span><i style="
"><span style="color:red;">I feel that this could to be
a sticking point
for the group.<span style=""> </span>There
have been a couple
comments that monetary donations should not be a part of
the key access process.<span style=""> </span>To
help aid the discussion, could you expand
a little on why you support the fee model? <span style=""> </span>One of the criticisms
was that giving money
doesn’t necessarily equal trustworthiness.</span></i><span style="color:#548DD4;"><br>
<br>
A continuing level of donation. $30 per month<br>
has been discussed.<br>
<br>
Time<br>
<br>
A minimum committment of 5 hours a month. Board<br>
member activity would be counted towards the<br>
time committment as would fundraising, public<br>
relations and educational work. General meeting<br>
attendance would not count.<span style="">
</span></span><i style=""><span style="color:red;">OK</span></i><span style="color:#548DD4;"><br>
<br>
The 5 hours number was just pulled out of the<br>
air.<span style=""> </span></span><i style="
"><span style="color:red;">OK</span></i><span style="color:#548DD4;"><br>
<br>
Service<br>
<br>
At the board's pleasure, keyholder privilages<br>
might be granted for extraordinary service in<br>
support of the goals of the organization, the<br>
community, or the Makers movement. </span><span style="color:red;"><span style=""> </span><i style="">Noted.</i></span><span style="color:#548DD4;"><br>
<br>
<br>
<br>
Keyholder Approval Process<br>
<br>
I propose the creation of a 3 member Keyholder<br>
committee of <b style="">board
members</b> and/or
current<br>
keyholders. The committee would meet in private<br>
with perspective keyholders, review the pre-<br>
requisites and either recommend or decline to<br>
recommend keyholder privileges be granted to<br>
the applicant.<br>
<br>
Committee members declining a member for keyholder<br>
privileges would be expected to explain their reasoning,<br>
offer suggestions for remedying issues standing<br>
in the way of keyholder status and advise when the<br>
member can reapply. All information and discussion<br>
of declined keyholder privileges must remain confidential.</span></div>
<div class="yiv525825293MsoNormal"><i style=""><span style="color:red;">This seemed slightly ambiguous, so I
just want to clarify,
the committee members would only need to explain their
reasoning for denial,<br>
offer suggestions for remedying issues standing<br>
in the way of keyholder status and advise when the<br>
member can reapply to the proposed keyholder, correct?<span style=""> </span>Otherwise, that
information would be
confidential to everyone else.<span style="">
</span>Similarly, would discussion of approved keyholder
privilages be public
information?</span></i><span style="color:#548DD4;"><br>
<br>
Members recommended for keyholder privilege will<br>
be recommended to the board at the next general meeting.<br>
<br>
<span style=""> </span>The intention here is
that the board
would unanimously<br>
approve anyone recommended for keyholder privileges.<br>
Making the event public would give recogition to the<br>
new keyholder.<span style=""> </span></span><i style=""><span style="color:red;">Noted</span></i><span style="color:red;"></span></div>
<div><span></span></div>
<div><br>
</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">
<hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> Jim
Stewart <a rel="nofollow" class="yiv525825293moz-txt-link-rfc2396E" ymailto="mailto:jstewart@jkmicro.com" target="_blank" href="mailto:jstewart@jkmicro.com"><jstewart@jkmicro.com></a><br>
<b><span style="font-weight:bold;">To:</span></b>
<a rel="nofollow" class="yiv525825293moz-txt-link-abbreviated" ymailto="mailto:discuss@lists.davismakerspace.org" target="_blank" href="mailto:discuss@lists.davismakerspace.org">discuss@lists.davismakerspace.org</a> <br>
<b><span style="font-weight:bold;">Sent:</span></b>
Wednesday, October 9, 2013 9:56 PM<br>
<b><span style="font-weight:bold;">Subject:</span></b>
[dms-discuss] Key Policy thoughts<br>
</font> </div>
<div class="yiv525825293y_msg_container"><br>
After reading over the Key Policy Development wiki page,<br>
here are my thoughts...<br>
<br>
<br>
Prerequisites for all keyholders:<br>
<br>
Age 18 or greater.<br>
<br>
Member in good standing<br>
<br>
Ability and willingness to assist and/or mentor other<br>
Makerspace members or the public in at least one skill<br>
supported by the space.<br>
<br>
Examples would be 3D printers, electronics,<br>
Arduino development, art projects, carpentry<br>
or metalworking.<br>
<br>
Willingness to accept the role of Davismakerspace<br>
representative to the community.<br>
<br>
New visitors can be easily discouraged by being<br>
ignored or treated with annoyance or condescension.<br>
Keyholders would be expected to greet visitors,<br>
explain the resources available, and encourage<br>
them to attend the next meeting.<br>
<br>
Signed Keyholder Agreement on file<br>
<br>
Another project. I think a Keyholder Agreement<br>
is needed to clearly spell out the responsibilities<br>
of the job. I'm willing to help develop it.<br>
<br>
<br>
Members meeting all of the above requirements are<br>
also expected to contribute to the Davismakerspace<br>
in at least one of the following ways:<br>
<br>
Financial<br>
<br>
A continuing level of donation. $30 per month<br>
has been discussed.<br>
<br>
Time<br>
<br>
A minimum committment of 5 hours a month. Board<br>
member activity would be counted towards the<br>
time committment as would fundraising, public<br>
relations and educational work. General meeting<br>
attendance would not count.<br>
<br>
The 5 hours number was just pulled out of the<br>
air.<br>
<br>
Service<br>
<br>
At the board's pleasure, keyholder privilages<br>
might be granted for extraordinary service in<br>
support of the goals of the organization, the<br>
community, or the Makers movement.<br>
<br>
<br>
<br>
Keyholder Approval Process<br>
<br>
I propose the creation of a 3 member Keyholder<br>
committee of board members and/or current<br>
keyholders. The committee would meet in private<br>
with perspective keyholders, review the pre-<br>
requisites and either recommend or decline to<br>
recommend keyholder privileges be granted to<br>
the applicant.<br>
<br>
Committee members declining a member for keyholder<br>
privileges would be expected to explain their reasoning,<br>
offer suggestions for remedying issues standing<br>
in the way of keyholder status and advise when the<br>
member can reapply. All information and discussion<br>
of declined keyholder privileges must remain confidential.<br>
<br>
Members recommended for keyholder privilege will<br>
be recommended to the board at the next general meeting.<br>
<br>
The intention here is that the board would unanimously<br>
approve anyone recommended for keyholder privileges.<br>
Making the event public would give recogition to the<br>
new keyholder.<br>
<br>
<br>
<br>
_______________________________________________<br>
Discuss mailing list<br>
<a rel="nofollow" ymailto="mailto:Discuss@lists.davismakerspace.org" target="_blank" href="mailto:Discuss@lists.davismakerspace.org">Discuss@lists.davismakerspace.org</a><br>
<a rel="nofollow" class="yiv525825293moz-txt-link-freetext" target="_blank" href="http://lists.davismakerspace.org/listinfo/discuss">http://lists.davismakerspace.org/listinfo/discuss</a><br>
<br>
<br>
</div>
</div>
</div>
</div>
<br>
<fieldset class="yiv525825293mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
Discuss mailing list
<a rel="nofollow" class="yiv525825293moz-txt-link-abbreviated" ymailto="mailto:Discuss@lists.davismakerspace.org" target="_blank" href="mailto:Discuss@lists.davismakerspace.org">Discuss@lists.davismakerspace.org</a>
<a rel="nofollow" class="yiv525825293moz-txt-link-freetext" target="_blank" href="http://lists.davismakerspace.org/listinfo/discuss">http://lists.davismakerspace.org/listinfo/discuss</a>
</pre>
</blockquote>
<br>
</div>
</div><br><br></div> </div> </div> </div></body></html>