Thanks Richard! And thank you Colin for all the work you've put in at this
space and the last one. I'm personally impressed by the speed at which
Colin's set things up and appreciate the work he's put in. (I still have no
idea how he managed to neatly install those wires while seemingly leaving
the door-frame untouched)

In the meantime, just a gentle reminder that if you want the access issue
to be resolved quicker, you're best approach is to take Colin up on the
request for help that he made at the last meeting.

That said, going by some of the comments I've heard off-list and on this
mailing list, I think some people are under the impression that Colin (and
everybody else working on the doors) is SkullSpace's bitch. This is not the
case. He's doing this for no other reason than because he wants to. Respect
his work as such.

We are a community of people who actually like doing things (a do-ocracy if
you will). People who like doing things often don't appreciate people who
just criticize their work and ask them to do more things. We have outright
lost good people on account of this behavior and have de-motivated several
others.

Please, be mindful of how you treat the people doing things to help the
space. I know all of us, myself included, can find ways to do better.

Do:
- Ask how you can help
- Ask to do it yourself
- Give constructive advice and suggestions
- Be thankful for the people actively working to make the space better

Don't:
- Bitch
- Insult
- Give others more work to do
- Micromanage the people actively working to make the space better

No member has the right to boss around other members. Even us directors try
to avoid such behavior whenever possible.


On Wed, Nov 21, 2012 at 1:14 PM, Roswyne <[email protected]> wrote:

> I will happy pay to have my own key cut and whatever surcharge you deem
> necessary for the "inconvenience".
>
> I find being locked out to be an inconvenience.  If Colin can just get the
> fobs working on the outside door, I don't see what the issue is with
> cutting keys that will automatically expire if/when the interior lock gets
> changed.
>
>
>
>
> On Wed, Nov 21, 2012 at 12:47 PM, Ron <[email protected]> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> As a last option, let's look at that. As a first option, let's look at
>> something easier/better. :)
>>
>> Ron
>>
>> On 2012-11-21 12:45, Michael Kozakewich wrote:
>> > We'd be paying, so that answers that. Take a last-call order now and at
>> Tuesday's meeting, then get that many made. Not every member
>> > comes often enough to need a key, so those who specifically need it
>> (those who always come outside of Tuesdays, Fridays, and
>> > Hackathons) enough to want to pay a few dollars for rental can buy
>> theirs. (Make it clear that we don't own our key.)
>> >
>> > -----Original Message-----
>> > From: Ron
>> > Sent: Wednesday, November 21, 2012 12:15 PM
>> > To: [email protected]
>> > Subject: Re: [SkullSpace-Discuss] Fwd: Noble Locksmith Quote
>> >
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA1
>> >
>> > When I had the directors' keys cut, they were $3 each. Other places
>> > might be cheaper. According to a list I just saw, we have 42 members,
>> > which means $126 to cut keys for everybody. Our budget for this is
>> > currently about $0. I paid out of my own pocket for the directors' keys
>> > (10 keys =~ $35 after tax).
>> >
>> > We could do it on-demand, if we needed to, but that's a lot of extra
>> > work for somebody, plus getting the keys back after - at Adelaide, we
>> > never did get everybody's keys back, which proves that people can't be
>> > trusted with keys (or to maintain lists of who has keys :) ).
>> >
>> > I'd rather go with the easier and cheaper solutions first, if possible,
>> > before getting more complicated/expensive.
>> >
>> > Ron
>> >
>> > On 2012-11-21 12:06, Michael Kozakewich wrote:
>> > > How much would it cost to cut a key, really? I'd personally pay a few
>> dollars to rent a newly-cut key until a fob system is put in
>> > > place.
>> > >
>> > > -----Original Message-----
>> > > From: Ron
>> > > Sent: Wednesday, November 21, 2012 11:47 AM
>> > > To: [email protected]
>> > > Subject: Re: [SkullSpace-Discuss] Fwd: Noble Locksmith Quote
>> > >
>> > > -----BEGIN PGP SIGNED MESSAGE-----
>> > > Hash: SHA1
>> > >
>> > > As a stopgat measure, we have a few choices:
>> > > - - Find a door that will fit and replace our door with it
>> > > - - Cut keys for the internal door, get the fob hooked up to the
>> external
>> > > - - Put a lockbox inside and put a key in the lockbox
>> > >
>> > > I don't know which is the most possible/cheap, but let's wait till
>> > > Justin measures the sksp1 doors before we make any decisions.
>> > >
>> > > Ron
>> > >
>> > > On 2012-11-21 11:37, Roswyne wrote:
>> > > > The "decision" at the meeting was to see if we could simply replace
>> the
>> > > > door instead of installing a lock guard.  Justin was going to see
>> if any of
>> > > > the doors we installed at SkSp1 would work, or if he could find one
>> of the
>> > > > correct size at the Re-Store.
>> > > >
>> > > > If that didn't work out, then we would probably, painfully, have to
>> get the
>> > > > locksmith to do the work.
>> > > >
>> > > > However, with a 3-4 week lead time for the locksmith to order the
>> plate,
>> > > > that will push us far past the beginning of December for us to have
>> a
>> > > > working interior door.
>> > > >
>> > > > Honestly, I think it's time to start cutting keys so we can use the
>> > > > existing door as is.  It'll be cheaper than having the work
>> professionally
>> > > > done on the door, and it can be done much more quickly, so we can
>> continue
>> > > > to search for a replacement door at our leisure.
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > On Wed, Nov 21, 2012 at 9:17 AM, R Rodd <[email protected]>
>> wrote:
>> > > >
>> > > > >  Attached is the quote I received from Noble after their visit
>> > > > > yesterday.  I'm not sure if it was discussed at the meeting last
>> night butI assume it
>> > > > > was mentioned so I'm not providing the context and background
>> that Colin
>> > > > > can speak to if there are any questions.
>> > > > >
>> > > > >
>> > > > > Action items at this point, I think, would be input from members
>> and a Go
>> > > > > | No-Go from exec.  Due to the older design and construction of
>> the door necessitating
>> > > > > a unique handset the quote is about 60% higher than I was
>> expecting
>> > > > > initially, before meeting with the locksmith yesterday.
>> > > > >
>> > > > >
>> > > > > If it is a Go from exec, probably someone with a key should
>> schedule a
>> > > > > time for the work.
>> > > > >
>> > > > >
>> > > > >  - Richard
>> > > > >
>> > > > >  **
>> > > > >
>> > > > > *From:* Frank Senden [mailto:[email protected]]
>> > > > > *Sent:* Wednesday, 2012 November 21 7:50
>> > > > > *To:* [email protected]
>> > > > > *Subject:* Noble Locksmith Quote****
>> > > > >
>> > > > > ** **
>> > > > >
>> > > > > Hi Richard,****
>> > > > >
>> > > > > Please see Quote 12-619.****
>> > > > >
>> > > > > ** **
>> > > > >
>> > > > > Sincerely,****
>> > > > >
>> > > > > Frank Senden****
>> > > > >
>> > > > > Noble Locksmith Ltd.****
>> > > > >
>> > > > > ** **
>> > > > >
>> > > > > ** **
>> > > > >
>> > > > >
>> > > > >
>> > > > > _______________________________________________
>> > > > > SkullSpace Discuss Mailing List
>> > > > > Help:
>> http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
>> > > > > Archive:
>> https://groups.google.com/group/skullspace-discuss-archive/
>> > > > >
>> > >
>> > > > _______________________________________________
>> > > > SkullSpace Discuss Mailing List
>> > > > Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
>> > > > Archive:
>> https://groups.google.com/group/skullspace-discuss-archive/
>> > >
>> > > -----BEGIN PGP SIGNATURE-----
>> > > Version: GnuPG v2.0.19 (GNU/Linux)
>> > >
>> > > iEYEARECAAYFAlCtE6MACgkQ2t2zxlt4g/STGQCfcsNkldgKS2D1T6Wz4jdtnT3M
>> > > uokAoLENKwiV0vW5kfon8d5TLMAL9akQ
>> > > =Ud6m
>> > > -----END PGP SIGNATURE-----
>> > > _______________________________________________
>> > > SkullSpace Discuss Mailing List
>> > > Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
>> > > Archive: https://groups.google.com/group/skullspace-discuss-archive/
>> > >
>> > > _______________________________________________
>> > > SkullSpace Discuss Mailing List
>> > > Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
>> > > Archive: https://groups.google.com/group/skullspace-discuss-archive/
>> > -----BEGIN PGP SIGNATURE-----
>> > Version: GnuPG v2.0.19 (GNU/Linux)
>> >
>> > iEYEARECAAYFAlCtGjUACgkQ2t2zxlt4g/RBFQCZAeDo1L2JfdlgNt052dZkQuZA
>> > KtQAn3g3jlSxhEFyD6tBulIcgARA0nd+
>> > =dtWb
>> > -----END PGP SIGNATURE-----
>> > _______________________________________________
>> > SkullSpace Discuss Mailing List
>> > Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
>> > Archive: https://groups.google.com/group/skullspace-discuss-archive/
>> >
>> > _______________________________________________
>> > SkullSpace Discuss Mailing List
>> > Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
>> > Archive: https://groups.google.com/group/skullspace-discuss-archive/
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.19 (GNU/Linux)
>>
>> iEYEARECAAYFAlCtIboACgkQ2t2zxlt4g/RDzwCgw7WYS+TOMVvNkgX5/2RSAaj5
>> YGUAoMW0u/x2b23nis3NYoED1RkQaCTI
>> =tT7b
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> SkullSpace Discuss Mailing List
>> Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
>> Archive: https://groups.google.com/group/skullspace-discuss-archive/
>>
>
>
> _______________________________________________
> SkullSpace Discuss Mailing List
> Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
> Archive: https://groups.google.com/group/skullspace-discuss-archive/
>
_______________________________________________
SkullSpace Discuss Mailing List
Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
Archive: https://groups.google.com/group/skullspace-discuss-archive/

Reply via email to