[sudo-discuss] [Big Changes] Access Crisis 2013

[William Budington]

Sunday is always a good day for me.  I know Yardena is combining all the
door projects into one git repo with multiple subtrees, which should
make it easier to git clone and hack on any one of these.  So here's the
access issues projects I see currently:

Adiministrative:
- Getting a comprehensive membership list (roadblock: Tommy needs access
to the bank acct to get a list of dues paying members, no?)
- Updating https://sudoroom.org/wiki/Door_Access

Hardware Hacking:
- Getting a raspi attached to the sudo <=> (common space) door.
- Installing a circuit on both doors that will be able to send signals
to their respective raspi's.

Software Hacking:
- Getting the mouse buzzer working
- Creating an API for the door open/closed states
- Whipping up some code for the homepage to interface with the API

I've put this up on the wiki, please add if I missed anything:
https://sudoroom.org/wiki/Door_access_hacking

-Bill


On 05/21/2013 07:23 AM, mattsenate at gmail.com wrote:
>  Think you're right that we are very close to completing item (b) I listed below. There are four others that require our attention.
> 
> // Matt
> 
> ----- Reply message -----
> From: "Andrew" <andrew at roshambomedia.com>
> To: "Romy Ilano" <romy at snowyla.com>
> Cc: "sudo-discuss at lists.sudoroom.org" <sudo-discuss at lists.sudoroom.org>
> Subject: [sudo-discuss] [Big Changes] Access Crisis 2013
> Date: Tue, May 21, 2013 1:26 AM
> This can be resolved immediately with the technology we already have. There is no reason anyone to keep the door propped open.
> 1. door.sudoroom.org is up and running, we also have the mouse buzzer, which I hear is not working, but should be easy to fix.
> 2. Intercom still works3. RFID works. I have RFID fobs if anyone who doesn't already have one wants one.
> I also don't think that it's always Sudo Room that props the door open, Public School does this as well. But, as far as Sudo Room is concerned, no reason to keep the door open.
> 
> --Andrew
> --Andrew
> 
> 
> 
> On Mon, May 20, 2013 at 10:35 PM, Romy Ilano <romy at snowyla.com> wrote:
> 
> That is awesome! It is wonderful to see people hacking at sudoroom 
> That's what it's all about 
> 
> Enjoying a lot of positive hacker energy at Mitch circuit microcontroller night at noisebridge 
> 
> 
> 
> ---
> Romy IlanoFounder of Snowylahttp://www.snowyla.comromy@snowyla.com
> 
> On May 20, 2013, at 21:44, Marina Kukso <marina.kukso at gmail.com> wrote:
> 
> Yes! I would like to hack on the articles, the meeting, finance mgmt, and outreach.
> 
> What are folks doing sunday? I bet it would be a good day to hide from the filthy sunshine ;) or another weekend...
> - marina
> On May 20, 2013 9:28 PM, "Matthew Senate" <mattsenate at gmail.com> wrote:
> 
> How do folks feel about a hackday or a hackathon (not a glamorous event, but a marathon of coding) over a weekend to resolve this and perhaps a number of other logistical sudo matters? A sort of work-party version of the "State of the Room" event perhaps--something like--"Hack the Room"?
> 
> 
> 
> // Matt
> 
> On Mon, May 20, 2013 at 6:42 PM, William Budington <bill at inputoutput.io> wrote:
> 
> 
> 
> It seems like we can combine this with the recent interest in coding for
> 
> access and creating a "sudoroom is open" API.  Perhaps a sudo-access
> 
> working group?  I'm willing to meet with others after the meeting on
> 
> Wednesday as a Sudoroom Open Door Access working group (SODA Workers!)
> 
> 
> 
> Bill
> 
> 
> 
> On 05/20/2013 03:34 PM, Matthew Senate wrote:
> 
>> Hey all,
> 
>>
> 
>> Got word and confirmation from George today that he is dissatisfied with
> 
>> our current access system--meaning we may no longer leave the door on 22nd
> 
>> propped open whatsoever.
> 
>>
> 
>> We need to (a) resolve our membership identification problem and (b) unify
> 
>> and maintain our full access management solution and provide it to all
> 
>> members (c) set up a telephone inside sudo room (d) expand access solutions
> 
>> to the public school, possibly other tenants up to a fair exchange (e) keep
> 
>> the hallway on 22nd to the elevator absolutely clear of all items.
> 
>>
> 
>> Seriously, we are on thin ice and if we want to remain committed to public
> 
>> access and thriving events, we need to get our shit together.
> 
>>
> 
>> I personally cannot commit to resolving any of the above items--but I do
> 
>> offer help and feedback to folks who can commit.
> 
>>
> 
>> // Matt
> 
>>
> 
>>
> 
>>
> 
>> _______________________________________________
> 
>> sudo-discuss mailing list
> 
>> sudo-discuss at lists.sudoroom.org
> 
>> http://lists.sudoroom.org/listinfo/sudo-discuss
> 
>>
> 
> 
> 
> _______________________________________________
> 
> sudo-discuss mailing list
> 
> sudo-discuss at lists.sudoroom.org
> 
> http://lists.sudoroom.org/listinfo/sudo-discuss
> 
> 
> 
> 
> _______________________________________________
> 
> sudo-discuss mailing list
> 
> sudo-discuss at lists.sudoroom.org
> 
> http://lists.sudoroom.org/listinfo/sudo-discuss
> 
> 
> 
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss at lists.sudoroom.org
> 
> http://lists.sudoroom.org/listinfo/sudo-discuss
> 
> _______________________________________________
> 
> 
> sudo-discuss mailing list
> 
> sudo-discuss at lists.sudoroom.org
> 
> http://lists.sudoroom.org/listinfo/sudo-discuss
> 
> 
> 
> 
> 
> 
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss at lists.sudoroom.org
> http://lists.sudoroom.org/listinfo/sudo-discuss
>