>> It's Wednes-daaaay nite! Which means meeting and dinner.
Meeting is ostensibly in an hour, and I am the only person at
sudoroom. What's gonna happen with food? There's still time but we
need to hurry...
Hi all,
I just found out about the sudo room while looking at the JavaScript user group meetup page and noticed the weekly study group. I'm hoping to check out the space sometime after I return to Oakland on June 1st. I look forward to seeing the space and meeting you all soon!
I'm emailing now to see if anyone at sudo room is interested in setting up a darkroom? I have a pretty complete setup for B&W printing and enlarging. I also have a very cool Sinar P 4x5 view camera, though I'm still saving up for a nice lens. I would be happy to share use of the camera if others are interested in learning.
I'm going to be driving cross-country on Sunday, so I'd need to know soon if there is interest in this project as I'm currently storing it here in Wisconsin. Maybe this is all a bit too archiac, but anyway I thought I'd see if anyone is interested.
Best,
Ben Hass
415-819-6755
benhass(a)gmail.com
---------- Forwarded message ----------
From: info <info(a)sudoroom.org>
Date: Wed, May 22, 2013 at 5:48 PM
Subject: Linode Support Ticket 1952977 - sudoserver (linode316279) -
Scheduled maintenance for Thu., June 6 at 8PM PDT
To: mattsenate <mattsenate(a)gmail.com>
* --- forwarded message --- *
Wed May 22 2013 10:00:26 AM PDT from "support" <support(a)linode.com> Subject:
Linode Support Ticket 1952977 - sudoserver (linode316279) - Scheduled
maintenance for Thu., June 6 at 8PM PDT
Support Ticket 1952977 has been updated by 'bkaplan'
--------------------------------------------------
Hello -
We have scheduled a maintenance window for the physical server your Linode
is hosted on:
Friday, June 7, 2013 between 3:00 AM and 11:00 AM UTC
(Thursday, June 6, 2013 between 8:00 PM and 4:00 AM PDT)
Downtime from this maintenance is expected to be less than 120 minutes,
however please note that the entire maintenance window may be used if
required. Your Linode will be gracefully powered down and rebooted during
the maintenance. Services not configured to start on a reboot will need to
be manually started.
Additional information regarding this maintenance event can be found here: <
https://blog.linode.com/2013/05/17/fremont-upgrades/>
Please do not hesitate to contact us if you have any questions or concerns.
Regards,
Brett Kaplan
Linode Support
--------------------------------------------------
Please use https://manager.linode.com/support/ticket/1952977 to respond to
this ticket.
Thank you,
Linode.com
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(a)roshambomedia.com>
To: "Romy Ilano" <romy(a)snowyla.com>
Cc: "sudo-discuss(a)lists.sudoroom.org" <sudo-discuss(a)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(a)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(a)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(a)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(a)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(a)lists.sudoroom.org
> http://lists.sudoroom.org/listinfo/sudo-discuss
>
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
--
-------Andrew LoweCell: 831-332-2507http://roshambomedia.com
you have a number of ways to contribute:
1) online (via wepay): https://sudoroom.org/
2) online (via gittip): https://www.gittip.com/sudoroom/
3) in person (anytime): please drop cash or checks into the clear plastic
box by the door that goes to the elevator
4) in person (at meetings): bring cash or checks to wed. meetings.
and certainly i barely need to remind you of our *precarious month to month
financial situation*.
pay your dues!
Hi All,
I am going to propose the following at the meeting tonight:
"The official policy of Sudo Room is to only act on requests by the Land
Lord that are given to Sudo Room *in writing *by the Land Lord or one of
the Land Lords agreed upon representatives, except in cases of emergency
(ie. preventing injury), or compliance with already written city codes."
I will also propose that this be voted on tonight given the time
sensitivity and the severity of the issues we've had with the Land Lord.
I will also propose that pros and cons be listened to for a limited time
before voting as opposed to just taking general stack.
Thanks,
Andrew
--
-------
Andrew Lowe
Cell: 831-332-2507
http://roshambomedia.com
Practical Options for Deploying IT Equipment in Small Server Rooms & Branch
Offices Source: APC by Schneider
Electric<http://www.techrepublic.com/research-library/apc+by+schneider+electric>
Small server rooms and branch offices are typically unorganized, unsecure,
hot, unmonitored, and space constrained. These conditions can lead to
system downtime or, at the very least, lead to “close calls” that get
management’s attention. Practical experience with these problems reveals a
short list of effective methods to improve the availability of IT
operations within small server rooms and branch offices. This paper
discusses making realistic improvements to power, cooling, racks, physical
security, monitoring, and lighting. The focus of this paper is on small
server rooms and branch offices with up to 10kW of IT load.
I figure some good information can be found in this paper regarding server
options. For those interested, have a read
I'm sure it covers ground some people are familar with and some new
approaches as well,
Sincerely,
Troy