<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 29 April 2015 at 20:17, <span dir="ltr"><<a href="mailto:bfb@riseup.net" target="_blank">bfb@riseup.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
At the last several meetings there has been lively discussion to bump up our opening time from 11:00 to sunrise. Specifically, Earl, our gatekeeper, is configured for three user types.<br>
<br>
Earl currently opens when an RFID key is scanned for:<br>
<br>
anonymous users from 11:00 - 22:00<br>
deanonymized users from 7:00 - 23:59<br>
root users with 24 hour access<br></blockquote><div><br></div><div>the second group is actually 'fulltimeusers', which is like the other users as well and 'could' be anonymous, but in practice isn't (but should probably be a requirement).</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The proposal is to change this to:<br>
<br>
anonymous users from sunrise - 22:00<br>
deanonymized users form sunrise - 23:59<br>
root users with 24 hour access<br></blockquote><div><br></div><div>I would _not_ put anonymous users in the sunrise category. We give out tokens pretty freely these days, and I would like to continue this welcoming gesture. However, if this brings in the burden to really, really be sure that this is a person I can 100% trust, then giving out tokens will be slowed down; which is not what we want. Someone coming in in early hours should be explicitly put into that category.</div><div><br></div><div>So I would like to have people who can access the space in the early hours to be known and explicitly put in the 'fulltimeuser' category.<br></div><div><br></div><div>But I am (personally) ok with having 'fulltimeuser' extended in the morning to sunrise (and would slightly endorse it).</div><div><br></div><div>-h</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
To accomplish this we use the <a href="https://github.com/cpucycle/astrotime" target="_blank">https://github.com/cpucycle/astrotime</a> library. The code is in place, perhaps ready to deploy.<br>
<br>
How do others feel about this change? If you're curious, have a look at meeting discussions.<br>
<br>
<a href="https://www.noisebridge.net/Meeting_Notes_2015_04_07" target="_blank">https://www.noisebridge.net/Meeting_Notes_2015_04_07</a><br>
<a href="https://www.noisebridge.net/Meeting_Notes_2015_04_21" target="_blank">https://www.noisebridge.net/Meeting_Notes_2015_04_21</a><br>
<a href="https://www.noisebridge.net/Meeting_Notes_2015_04_28" target="_blank">https://www.noisebridge.net/Meeting_Notes_2015_04_28</a><br>
<br>
Some salient points for me include:<br>
<br>
Early birds have described friction with the 11:00 opening hour<br>
Noisebridge is lonely when empty<br>
Noisebridge prospers when used, not abused<br>
Early birds want to hack between sunrise and 11:00 at Noisebridge<br>
Updating RFID keys with contact information requires editing a text file (not currently supported via the touchpad interface)<br>
Decoupling Noisebridge from an arbitrary and obsolete governmental definition, the PDT/PST flux, is nice<br>
Sunrise is beautiful<br>
If the change is not working out, we can always roll back<br>
<br>
Thanks much for reading,<br>
Kevin<br>
<br>
_______________________________________________<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>
</blockquote></div><br></div></div>