<div dir="ltr">You know, for all the booting out of early morning sleepers from the space I do, I'll say this: I've never asked anyone during the day if they're a member of the space, or pointed out to anyone that Noisebridge is a members-only space. Even I feel uncomfortable doing that. It's completely ineffective at keeping people from treating the space like their living room instead of their workshop.<div>
<br></div><div>I pitched the members-only hours years ago to curb the sleeping problem (I think it directly addresses the issue), but it was shot down because it would limit access to Noisebridge (even though I said people could become members and then go on hiatus if member dues were the problem.) I still support non-public hours for the space.</div>
<div><br></div><div>-Al</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 9, 2013 at 9:25 AM, Jeffrey Carl Faden <span dir="ltr"><<a href="mailto:jeffreyatw@gmail.com" target="_blank">jeffreyatw@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">So I've been meaning to ask - how has the new associate membership idea been working? One of the main drives of the concept was to prevent sleeping by only allowing members or vouched guests in, but this seems to have failed.<div>
<br></div><div>It's a failure on my part as well as on any other associate member who has entertained people in the space but not asked them to leave along with them. I don't think any of my students are sleeping at the space after classes, but I haven't been explicitly asking anyone to leave. I either don't feel comfortable, or simply forget to ask.</div>
<div><br></div><div>If people are feeling safer and the amount of violence and drug abuse has gone down, then that's enough to warrant keeping these policies in place. But if the limited-hours approach was shot down in order for associate membership to take its place, it certainly seems less effective in preventing sleepers.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Mon, Dec 9, 2013 at 9:15 AM, Al Sweigart <span dir="ltr"><<a href="mailto:asweigart@gmail.com" target="_blank">asweigart@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">I'm not sure if there are any members who say they are fine with people crashing overnight at Noisebridge (please speak up if you are. I think Leif maybe? Or maybe he thinks napping is fine but overnight sleeping isn't? Either way, I don't want to speak for him.) As for the sleepers themselves, I think one has been an associate member, but the rest aren't members. And by far the majority of people who come to Noisebridge don't sleep here themselves.<div>
<br></div><div>Meanwhile, the opposition to people sleeping at the space is pretty vocal and consistent. The hacker stackers were taken down because they weren't just being used for naps. Don't confuse the exception for the rule.</div>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 9, 2013 at 8:44 AM, spinach williams <span dir="ltr"><<a href="mailto:spinach.williams@gmail.com" target="_blank">spinach.williams@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">clearly, the community thinks different things about it, because part of the community is still doing it<br>
</div>
</blockquote></div><br></div>
</div></div><br></div></div><div class="im">_______________________________________________<br>
Noisebridge-discuss mailing list<br>
<a href="mailto:Noisebridge-discuss@lists.noisebridge.net" target="_blank">Noisebridge-discuss@lists.noisebridge.net</a><br>
<a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
<br></div></blockquote></div><br></div>
</blockquote></div><br></div>