<div dir="ltr">What did/does Noisebridge's access control look like, that made it so effective? I know nil on the subject, so I ask for myself and anyone else who might not know what this entails.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 25, 2015 at 2:44 PM, Patrick O'Doherty <span dir="ltr"><<a href="mailto:p@trickod.com" target="_blank">p@trickod.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">at the risk of this sounding preachy (it's 100% not intended as such,<br>
but it's hard to convey tone / emotion in text) one of the biggest<br>
contributors in helping pull noisebridge back together was implementing<br>
access control coupled with using the 86 page to effectively document<br>
those who were asked to leave the space.<br>
<br>
I realise given the physical layout of both the OMNI and sudo in<br>
particular that any amount of physical access control might be a lot<br>
more difficult (multiple entrances to both the OMNI and sudoroom, and<br>
all the various routes between the rooms in the OMNI) but maybe it's<br>
worth exploring?<br>
<br>
a really neat side effect of access control is that all new visitors to<br>
the space interact with someone on arrival, with the cultural<br>
expectation on their host giving them a tour and explaining everything<br>
about the space and its ethos.<br>
<br>
lurking in #sudoroom it seems that there is some sort of card system at<br>
the moment? sudobot pipes up occasionally about folks being swiped into<br>
the building. I haven't been to the OMNI since this was put in place,<br>
but is this a card swipe system at the main front entrance?<br>
<br>
</$0.02><br>
<br>
p<br>
<br>
Jake:<br>
<div class="HOEnZb"><div class="h5">> i think we need to work on more practical and effective ways to keep the<br>
> space free of banned persons at all times.<br>
><br>
> what can people do when a banned person repeatedly returns whenever they<br>
> feel like they can get in? there are no consequences for trying.<br>
><br>
> I know that we do not call police for these types of issues, but what<br>
> about telling people that if they return again, the police will be<br>
> called and they will not know it until a cop shows up to grab them?<br>
><br>
> Does that go against our values? If so, what is a reasonable motivator<br>
> to get people to stop returning all the time?<br>
><br>
> If the response is "we just need to keep leaning on members and<br>
> volunteers to constantly beg trespassers to leave again" i fear that we<br>
> are going to burn people out faster than we can replace them.<br>
><br>
> -jake<br>
><br>
> On Tue, 25 Aug 2015, Stephen Whitmore wrote:<br>
><br>
>> Not sure if you're aware of it, but Omni/sudo<br>
>> has <a href="https://omnicommons.org/wiki/Asked_to_Leave" rel="noreferrer" target="_blank">https://omnicommons.org/wiki/Asked_to_Leave</a>. Photograph existence<br>
>> varies wildly, of<br>
>> course.<br>
>><br>
>> On Tue, Aug 25, 2015 at 1:36 PM, Patrik D'haeseleer<br>
>> <<a href="mailto:patrikd@gmail.com">patrikd@gmail.com</a>> wrote:<br>
>><br>
>> Ah - so he was already banned anyway, but was still coming in?<br>
>><br>
>> You know, I have a really hard time putting names to faces. It<br>
>> would be<br>
>> extremely useful if we actually had photographs of the people<br>
>> that are<br>
>> banned, similar to noisebridges 86 page. That way we might<br>
>> actually have some<br>
>> hope of enforcing the bans already in place...<br>
>><br>
>> Patrik<br>
>><br>
>> On Aug 25, 2015 1:15 PM, "yar" <<a href="mailto:yardenack@gmail.com">yardenack@gmail.com</a>> wrote:<br>
>> On Tue, Aug 25, 2015 at 1:10 PM, yar <<a href="mailto:yardenack@gmail.com">yardenack@gmail.com</a>><br>
>> wrote:<br>
>> > hackerspace inside the Omni, and it sounds like the people<br>
>> involved<br>
>> > were not Sudoroom members nor did they claim to be, and the<br>
>> events<br>
>><br>
>> Actually I stand corrected, James Moon applied to be a<br>
>> Sudoroom<br>
>> member<br>
>> a couple months ago, before he went on a yelling spree that<br>
>> scared a<br>
>> bunch of people away, and was then blocked from membership<br>
>> and<br>
>> banned.<br>
>> _______________________________________________<br>
>> sudo-discuss mailing list<br>
>> <a href="mailto:sudo-discuss@lists.sudoroom.org">sudo-discuss@lists.sudoroom.org</a><br>
>> <a href="https://sudoroom.org/lists/listinfo/sudo-discuss" rel="noreferrer" target="_blank">https://sudoroom.org/lists/listinfo/sudo-discuss</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> sudo-discuss mailing list<br>
>> <a href="mailto:sudo-discuss@lists.sudoroom.org">sudo-discuss@lists.sudoroom.org</a><br>
>> <a href="https://sudoroom.org/lists/listinfo/sudo-discuss" rel="noreferrer" target="_blank">https://sudoroom.org/lists/listinfo/sudo-discuss</a><br>
>><br>
>><br>
>><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> sudo-discuss mailing list<br>
> <a href="mailto:sudo-discuss@lists.sudoroom.org">sudo-discuss@lists.sudoroom.org</a><br>
> <a href="https://sudoroom.org/lists/listinfo/sudo-discuss" rel="noreferrer" target="_blank">https://sudoroom.org/lists/listinfo/sudo-discuss</a><br>
><br>
_______________________________________________<br>
sudo-discuss mailing list<br>
<a href="mailto:sudo-discuss@lists.sudoroom.org">sudo-discuss@lists.sudoroom.org</a><br>
<a href="https://sudoroom.org/lists/listinfo/sudo-discuss" rel="noreferrer" target="_blank">https://sudoroom.org/lists/listinfo/sudo-discuss</a><br>
</div></div></blockquote></div><br></div>