Hi all,

Today I got a call asking how to get into sudo/CCL by a sudoroom member.

As I said in previous messages, I don't think it's appropriate to shut/lock the
door without first putting up a sign explaining who to contact in case of being
unable to get through the door.

I don't think it's a huge big deal for someone to make the sign and put it up
there, so I don't understand why it hasn't happened yet, but people keep
locking the door.  Who knows how many people wanted to access the space and
couldn't figure out how to get in?  Hopefully not too many.

If nobody cares about access through this door enough to figure out a phone
tree and a sign, at the very least, then I will take the latch back off the
door so that we don't have any more problems with people being locked out.

-jake


On Wed, 3 Aug 2022, Patrik D'haeseleer wrote:

> I am in favor of starting to use the door lock to CCL/Sudo on a more
> regular basis, now that it is operational. But I agree with Jake that we
> need to have some agreements between CCL and Sudo members on when and how
> to use it.
>
> If anyone would like to discuss, feel free to join us later today at the
> CCL Working Meeting - every Wednesday 7pm:
> https://us02web.zoom.us/j/820128495?pwd=dE1kMHcxQ2o4UlI5dWdudk9YV1Q4Zz09
>
> Patrik
>
>
> On Wed, Aug 3, 2022 at 1:06 AM Jake via sudo-discuss <
> sudo-discuss@sudoroom.org> wrote:
>
>> It is not appropriate for a single person to unilaterally make and
>> implement
>> policy for a lot of people in the form of an announcement like this.
>>
>> I understand that you're concerned about security, and if you want to have
>> a
>> discussion about progress on locking the door, it would make sense to
>> engage in
>> the discussion I started in the access group, where I described the secret
>> of
>> the door-opening button.
>>
>> I mentioned that before we start locking the door, we need to at least
>> make a
>> sign on the door for people who find themselves needing to be on the other
>> side
>> of it, and who haven't seen the email you sent about it.  I mentioned that
>> someone set fire to the building because the door closed while their
>> property
>> was on the other side of it (not the only reason we need a sign, but not a
>> lesson to ignore).
>>
>> We need volunteers to discuss a phone tree (the sign must say phone
>> numbers)
>> and make the sign, to install the sign, as well as work on finishing the
>> RFID
>> access card project.
>>
>> Please don't just jump the gun and send out policy announcements like this
>> without engaging in ongoing planning and discussion.
>>
>> Also if an announcement is sent out once the sign is ready, it should say
>> "the door can be propped open using the metal hook and loop just below eye
>> level, don't put items in the walkway that block the path"
>> and step 3 should say PULL the door open, not "push open the door".
>>
>> -jake
>>
>> On Tue, 2 Aug 2022, Edwinsaurus via sudo-discuss wrote:
>>
>>> We have been waiting for a sensing system to be programmed for security
>> in
>>> CCL and sudo room.
>>> Meanwhile, there have been incidents in and around the Omni that raise
>>> security concerns.
>>> Starting in August we will start closing and locking the entry door.
>>> If someone is having a workshop and wants to keep an open door for the
>>> duration, that's cool, prop it open.
>>> When you exit the area please close the door and check that it locked.
>>> Here's how to unlock the door:
>>> 1. check to see no one is watching you
>>> 2. press the lever/switch on the box to the left of the door
>>> (see photo) while saying "open sesame"
>>> 3. push open the door and enter.
>>> [image: opensezme.jpg]
>>> to lock the door, just close it.
>>> The door also opens from inside.
>>> This message is coming to you via Sudo-discuss or CCL members at google
>>> groups.  Please pass it on to anyone who needs to know the procedure.
>>>
>> _______________________________________________
>> sudo-discuss mailing list -- sudo-discuss@sudoroom.org
>> To unsubscribe send an email to sudo-discuss-leave@sudoroom.org
>> More options at
>> https://sudoroom.org/lists/postorius/lists/sudo-discuss.sudoroom.org/
>>
>