Sudo Room - User contributions [en]

Lexmark T654dn

2018-02-01T06:04:14Z

Tlevine:

Lexmark T654dn laser printer

as shown on the Network wiki page, this printer has:
{| class="wikitable"
|-
| IP address || 100.64.64.88
|-
| MAC address || 00:21:b7:80:59:47
|-
| ppd || https://openprinting.org/ppd-o-matic.php?driver=Postscript-Lexmark&printer=Lexmark-T654&show=0
|-
| mdns || ET0021B7805947.local
|-
| web interface || http://192.168.42.2:8888/
|}

source code to the web interface:
https://thomaslevine.com/scm/horetu/artifact/3460d6212c9cffd1
[[User:Tlevine|Tlevine]] ([[User talk:Tlevine|talk]]) 21:41, 31 January 2018 (PST)

I originally installed this system in the [http://www.prishtinahackerspace.org/ Prishtina Hackerspace].

Lexmark T654dn

2018-02-01T06:01:37Z

Tlevine:

Lexmark T654dn laser printer

as shown on the Network wiki page, this printer has:
{| class="wikitable"
|-
| IP address || 100.64.64.88
|-
| MAC address || 00:21:b7:80:59:47
|-
| ppd || https://openprinting.org/ppd-o-matic.php?driver=Postscript-Lexmark&printer=Lexmark-T654&show=0
|-
| mdns || ET0021B7805947.local
|-
| web interface || http://192.168.42.2:8888/
|}

source code to the web interface:
https://thomaslevine.com/scm/horetu/artifact/3460d6212c9cffd1
[[User:Tlevine|Tlevine]] ([[User talk:Tlevine|talk]]) 21:41, 31 January 2018 (PST)

I originally installed this system in the [[http://www.prishtinahackerspace.org/|Prishtina Hackerspace]].

Lexmark T654dn

2018-02-01T05:46:31Z

Tlevine:

Lexmark T654dn laser printer

as shown on the Network wiki page, this printer has:
{| class="wikitable"
|-
| IP address || 100.64.64.88
|-
| MAC address || 00:21:b7:80:59:47
|-
| mdns || ET0021B7805947.local
|-
| web interface || http://192.168.42.2:8888/
|}

source code to the web interface:
https://thomaslevine.com/scm/horetu/artifact/3460d6212c9cffd1
[[User:Tlevine|Tlevine]] ([[User talk:Tlevine|talk]]) 21:41, 31 January 2018 (PST)

Lexmark T654dn

2018-02-01T05:41:49Z

Tlevine:

Lexmark T654dn laser printer

as shown on the Network wiki page, this printer has:
IP address: 100.64.64.88
MAC address: 00:21:b7:80:59:47
mdns: ET0021B7805947.localhttp://192.168.42.2:8888/

web interface so you can print without installing drivers:
http://192.168.42.2:8888/
[[User:Tlevine|Tlevine]] ([[User talk:Tlevine|talk]]) 21:41, 31 January 2018 (PST)

Usability

2015-01-25T06:42:45Z

Tlevine: /* Principle 7: Size and Space for Approach and Use */

Tom and Ryan looked at lists related to accessibility or whatever you call it and thinking about related things we could do in the Omni.

Here are lists:

* Principles of Universal Design
* [http://www.ada.gov/2010ADAstandards_index.htm ADAAG]

== Principles of Universal Design ==

=== Principle 1: Equitable Use ===

* Main door should be wide and otherwise accessible.
** This is usually the front door.
** If the side ballroom doors are used for ballroom-only events, this is the side ballroom door.
* It's good that the lift to the ballroom is in the main entrance.
* Stairs could be switched for ramps.
* Main bathroom should be the accessible bathroom, rather than another bathroom.
* Signage, especially front door signage should be legible for everyone
** Bad vision
** Blind
* Social norms for caregivers
** Don't expect them to donate to events.
** They're not the people to talk to.
** &c.

Different heights of table

* Tools are high
* Soldering station
* Moving shelves and tables

These are messes that occur that would be good if messes didn't happen

* Bikes
* Hallway to the backdoor could als
* Bikes in sudo
* Bikes against lift
* Bikes in paths
*

Climate control

Moving tables in Sudoroom sometime result in not enough space for Ryan

Service animals

=== Principle 2: Flexibility in Use ===

* Ramps
* Elevators
* Extendy grabber things for shelves
*

=== Principle 3: Simple and Intuitive Use ===

* Doorbell should make sense.
* Signs in more than English. Look at literature on signs from Tom's ergonomics textbooks or something.
* It should be obvious that bathrooms are bathrooms.

=== Principle 4: Perceptible Information ===

* Contrast between signs and everything else
* Signs should work for people who can't see. Like bumpy signs.
* Signs or something should indicate that accessible entrances exist.
* Color blindness, one for each color
** Color oracle color blindness simulator
* Floor textures and colors for paths
* Distinguish between spaces or be clear about trans
* Don't kill blind people.
** Maybe start with everywhere except the hackerspace
* What if you can't spell?
** Knowing that food exists.
**
* Ryan is glad that we don't rely on an intercom.
* Fire system should do more than sound.

=== Principle 5: Tolerance for Error ===

* A wheelchair can get trapped if things are just barely accessible.
* Kitchen gas is too easy to turn on.
** Large print oven dial
* Hackerspace virtues
** If you think this might kill you, don't do it.
** Ask for help if you need/want it.
* Are bookshelves safe from falling over?
* Disco room might be damaged by certain mobility aids
*

=== Principle 6: Low Physical Effort ===

* Ramps should be way better than standards
* Doors
* Elevator (in an obvious place)
*

=== Principle 7: Size and Space for Approach and Use ===

* Bottleneck for crowd control during events
** Maybe this is just in the training session
* Don't sit right behind a wheelchair

== ADA ==

== Other things ==

* Handles instead of knobs
* Doors should be light or at least well-lubricated
* Door button with hand and FOOT buttons
* 3D print Braille
* Teach people how to handle relay calls.

Usability

2015-01-25T06:33:19Z

Tlevine: /* Principle 5: Tolerance for Error */

Tom and Ryan looked at lists related to accessibility or whatever you call it and thinking about related things we could do in the Omni.

Here are lists:

* Principles of Universal Design
* [http://www.ada.gov/2010ADAstandards_index.htm ADAAG]

== Principles of Universal Design ==

=== Principle 1: Equitable Use ===

* Main door should be wide and otherwise accessible.
** This is usually the front door.
** If the side ballroom doors are used for ballroom-only events, this is the side ballroom door.
* It's good that the lift to the ballroom is in the main entrance.
* Stairs could be switched for ramps.
* Main bathroom should be the accessible bathroom, rather than another bathroom.
* Signage, especially front door signage should be legible for everyone
** Bad vision
** Blind
* Social norms for caregivers
** Don't expect them to donate to events.
** They're not the people to talk to.
** &c.

Different heights of table

* Tools are high
* Soldering station
* Moving shelves and tables

These are messes that occur that would be good if messes didn't happen

* Bikes
* Hallway to the backdoor could als
* Bikes in sudo
* Bikes against lift
* Bikes in paths
*

Climate control

Moving tables in Sudoroom sometime result in not enough space for Ryan

Service animals

=== Principle 2: Flexibility in Use ===

* Ramps
* Elevators
* Extendy grabber things for shelves
*

=== Principle 3: Simple and Intuitive Use ===

* Doorbell should make sense.
* Signs in more than English. Look at literature on signs from Tom's ergonomics textbooks or something.
* It should be obvious that bathrooms are bathrooms.

=== Principle 4: Perceptible Information ===

* Contrast between signs and everything else
* Signs should work for people who can't see. Like bumpy signs.
* Signs or something should indicate that accessible entrances exist.
* Color blindness, one for each color
** Color oracle color blindness simulator
* Floor textures and colors for paths
* Distinguish between spaces or be clear about trans
* Don't kill blind people.
** Maybe start with everywhere except the hackerspace
* What if you can't spell?
** Knowing that food exists.
**
* Ryan is glad that we don't rely on an intercom.
* Fire system should do more than sound.

=== Principle 5: Tolerance for Error ===

* A wheelchair can get trapped if things are just barely accessible.
* Kitchen gas is too easy to turn on.
** Large print oven dial
* Hackerspace virtues
** If you think this might kill you, don't do it.
** Ask for help if you need/want it.
* Are bookshelves safe from falling over?
* Disco room might be damaged by certain mobility aids
*

=== Principle 6: Low Physical Effort ===

* Ramps should be way better than standards
* Doors
* Elevator (in an obvious place)
*

=== Principle 7: Size and Space for Approach and Use ===

== ADA ==

== Other things ==

* Handles instead of knobs
* Doors should be light or at least well-lubricated
* Door button with hand and FOOT buttons
* 3D print Braille
* Teach people how to handle relay calls.

Usability

2015-01-25T06:22:03Z

Tlevine: /* Principle 1: Equitable Use */

Tom and Ryan looked at lists related to accessibility or whatever you call it and thinking about related things we could do in the Omni.

Here are lists:

* Principles of Universal Design
* [http://www.ada.gov/2010ADAstandards_index.htm ADAAG]

== Principles of Universal Design ==

=== Principle 1: Equitable Use ===

* Main door should be wide and otherwise accessible.
** This is usually the front door.
** If the side ballroom doors are used for ballroom-only events, this is the side ballroom door.
* It's good that the lift to the ballroom is in the main entrance.
* Stairs could be switched for ramps.
* Main bathroom should be the accessible bathroom, rather than another bathroom.
* Signage, especially front door signage should be legible for everyone
** Bad vision
** Blind
* Social norms for caregivers
** Don't expect them to donate to events.
** They're not the people to talk to.
** &c.

Different heights of table

* Tools are high
* Soldering station
* Moving shelves and tables

These are messes that occur that would be good if messes didn't happen

* Bikes
* Hallway to the backdoor could als
* Bikes in sudo
* Bikes against lift
* Bikes in paths
*

Climate control

Moving tables in Sudoroom sometime result in not enough space for Ryan

Service animals

=== Principle 2: Flexibility in Use ===

* Ramps
* Elevators
* Extendy grabber things for shelves
*

=== Principle 3: Simple and Intuitive Use ===

* Doorbell should make sense.
* Signs in more than English. Look at literature on signs from Tom's ergonomics textbooks or something.
* It should be obvious that bathrooms are bathrooms.

=== Principle 4: Perceptible Information ===

* Contrast between signs and everything else
* Signs should work for people who can't see. Like bumpy signs.
* Signs or something should indicate that accessible entrances exist.
* Color blindness, one for each color
** Color oracle color blindness simulator
* Floor textures and colors for paths
* Distinguish between spaces or be clear about trans
* Don't kill blind people.
** Maybe start with everywhere except the hackerspace
* What if you can't spell?
** Knowing that food exists.
**
* Ryan is glad that we don't rely on an intercom.
* Fire system should do more than sound.

=== Principle 5: Tolerance for Error ===

=== Principle 6: Low Physical Effort ===

* Ramps should be way better than standards
* Doors
* Elevator (in an obvious place)
*

=== Principle 7: Size and Space for Approach and Use ===

== ADA ==

== Other things ==

* Handles instead of knobs
* Doors should be light or at least well-lubricated
* Door button with hand and FOOT buttons
* 3D print Braille
* Teach people how to handle relay calls.

Usability

2015-01-25T06:15:53Z

Tlevine: /* Principle 6: Low Physical Effort */

Tom and Ryan looked at lists related to accessibility or whatever you call it and thinking about related things we could do in the Omni.

Here are lists:

* Principles of Universal Design
* [http://www.ada.gov/2010ADAstandards_index.htm ADAAG]

== Principles of Universal Design ==

=== Principle 1: Equitable Use ===

* Main door should be wide and otherwise accessible.
** This is usually the front door.
** If the side ballroom doors are used for ballroom-only events, this is the side ballroom door.
* It's good that the lift to the ballroom is in the main entrance.
* Stairs could be switched for ramps.
* Main bathroom should be the accessible bathroom, rather than another bathroom.
* Signage, especially front door signage should be legible for everyone
** Bad vision
** Blind
* Social norms for caregivers
** Don't expect them to donate to events.
** They're not the people to talk to.
** &c.

=== Principle 2: Flexibility in Use ===

* Ramps
* Elevators
* Extendy grabber things for shelves
*

=== Principle 3: Simple and Intuitive Use ===

* Doorbell should make sense.
* Signs in more than English. Look at literature on signs from Tom's ergonomics textbooks or something.
* It should be obvious that bathrooms are bathrooms.

=== Principle 4: Perceptible Information ===

* Contrast between signs and everything else
* Signs should work for people who can't see. Like bumpy signs.
* Signs or something should indicate that accessible entrances exist.
* Color blindness, one for each color
** Color oracle color blindness simulator
* Floor textures and colors for paths
* Distinguish between spaces or be clear about trans
* Don't kill blind people.
** Maybe start with everywhere except the hackerspace
* What if you can't spell?
** Knowing that food exists.
**
* Ryan is glad that we don't rely on an intercom.
* Fire system should do more than sound.

=== Principle 5: Tolerance for Error ===

=== Principle 6: Low Physical Effort ===

* Ramps should be way better than standards
* Doors
* Elevator (in an obvious place)
*

=== Principle 7: Size and Space for Approach and Use ===

== ADA ==

== Other things ==

* Handles instead of knobs
* Doors should be light or at least well-lubricated
* Door button with hand and FOOT buttons
* 3D print Braille
* Teach people how to handle relay calls.

Usability

2015-01-25T06:13:43Z

Tlevine: /* Other things */

Tom and Ryan looked at lists related to accessibility or whatever you call it and thinking about related things we could do in the Omni.

Here are lists:

* Principles of Universal Design
* [http://www.ada.gov/2010ADAstandards_index.htm ADAAG]

== Principles of Universal Design ==

=== Principle 1: Equitable Use ===

* Main door should be wide and otherwise accessible.
** This is usually the front door.
** If the side ballroom doors are used for ballroom-only events, this is the side ballroom door.
* It's good that the lift to the ballroom is in the main entrance.
* Stairs could be switched for ramps.
* Main bathroom should be the accessible bathroom, rather than another bathroom.
* Signage, especially front door signage should be legible for everyone
** Bad vision
** Blind
* Social norms for caregivers
** Don't expect them to donate to events.
** They're not the people to talk to.
** &c.

=== Principle 2: Flexibility in Use ===

* Ramps
* Elevators
* Extendy grabber things for shelves
*

=== Principle 3: Simple and Intuitive Use ===

* Doorbell should make sense.
* Signs in more than English. Look at literature on signs from Tom's ergonomics textbooks or something.
* It should be obvious that bathrooms are bathrooms.

=== Principle 4: Perceptible Information ===

* Contrast between signs and everything else
* Signs should work for people who can't see. Like bumpy signs.
* Signs or something should indicate that accessible entrances exist.
* Color blindness, one for each color
** Color oracle color blindness simulator
* Floor textures and colors for paths
* Distinguish between spaces or be clear about trans
* Don't kill blind people.
** Maybe start with everywhere except the hackerspace
* What if you can't spell?
** Knowing that food exists.
**
* Ryan is glad that we don't rely on an intercom.
* Fire system should do more than sound.

=== Principle 5: Tolerance for Error ===

=== Principle 6: Low Physical Effort ===
=== Principle 7: Size and Space for Approach and Use ===

== ADA ==

== Other things ==

* Handles instead of knobs
* Doors should be light or at least well-lubricated
* Door button with hand and FOOT buttons
* 3D print Braille
* Teach people how to handle relay calls.

Usability

2015-01-25T06:07:24Z

Tlevine: /* Principle 1: Equitable Use */

Usability

2015-01-25T06:05:46Z

Tlevine:

Usability

2015-01-25T05:53:34Z

Tlevine: /* Principle 2: Flexibility in Use */

Usability

2015-01-25T05:51:30Z

Tlevine: /* Principles of Universal Design */

Usability

2015-01-25T05:44:17Z

Tlevine: outline

Usability

2015-01-25T05:39:54Z

Tlevine: Created page with "Tom and Ryan looked at lists related to accessibility or whatever you call it and thinking about related things we could do in the Omni. Here are lists: * Principles of Univ..."

Tom and Ryan looked at lists related to accessibility or whatever you call it and thinking about related things we could do in the Omni.

Here are lists:

* Principles of Universal Design
* ADAAG

Hackpack

2014-06-01T21:02:08Z

Tlevine: Tom's stuff

A hackpack is a backpack with a set of "always carry" tools for hacking the world around us.

We are starting a project at sudo room to create cheap base hackpacks with optional expansion packs.

We have a [https://lists.sudoroom.org/listinfo/hackpack mailing list] where we discuss everything related to hack packs.

People currently working on project: [[User:Tunabananas|Tunabananas]], [[User:Matt|Matt]], Mackenzie, [[User:Juul|Juul]].

= Base hackpack =

Target price <= ?

This is only an initial possible version. It may be too electronics-focused. Comments/changes welcome.

*A backpack (get from thrift store and wash at high temp)
*Soldering iron (should be 30 watts)
*Set of small screwdrivers (at least philips and flat-head)
*Needle-nose pliers
*Diagonal wire-cutters (these will probably suck, but maybe we can sharpen them?)
*Tweezers
*Larger screw-driver with assortment of bits
*USB to 3.3v serial adapter
*Multimeter

*Assortment of resistors
*Small assortment of diodes, caps, mosfets, buttons, switches, LEDs
*Female to female pin header cables (like [http://letsmakerobots.com/files/userpics/u4/Female-Female_Header_Jumper_cables.jpg these])
*Some male-male and female-male pin headers
*USB stick (2 GB minimum) with bootable Linux and lots of libre books / learning materials.
*Sharpie
*White china marker/chalk...something that will write on dark surfaces
*Zip ties
*Binder clips
*Hose clamps
*A small LED flasher, and/or instructions to make one?
*Shrink tubing
*A lighter
*A hot glue stick (melt it w/the lighter)
*USB wall plug w/decent amperage
*A spare USB cable for your smart (or dumb?) device
*Pair of disposable gloves (rubber or vinyl)
*Bandanna
*Snap knife w/locking blade
*Alcohol prep wipes or a small bottle of hand sanitizer with a screw top (no flip caps)
*A 1/2 gallon ziploc bag
*List of where to buy more of everything
*List of other awesome things to add to hackpack, what they do and where to buy
*A sudo room sticker
*An invitation to sudo room
*List of places / ways to get free food
*Band aids

[https://docs.google.com/spreadsheet/ccc?key=0Akog0JI0-bB9dHphWFdtX1RpUUcxRUlpeHNuUE5uRFE Initial attempt at price assessment spreadsheet]

== Consumables ==

*Solder
*Wire of different colors and thicknesses
*Duct tape
*Yerba mate tea

== Data ==

I do not think we have to worry about using CC material with the non-commercial clause, as we are not trying to make a profit ([[User:Juul|Juul]] ([[User talk:Juul|talk]])). We are collecting libre data on our [http://datasink.sudomesh.org:8000 datasink].

=== Bootable GNU/Linux ===

Which distro? What should we include?

*UBCD and Trinity Rescue Kit should definitely be included. Maybe an older, smaller copy of Backtrack? -chrisbee
*Tails?

=== Books ===

*[http://craphound.com/ Cory Doctorow]'s works
*Most of [http://www.wetmachine.com/ John Sundman]'s works are CC, but not downloadable from his website anymore (now downloadable from [http://datasink.sudomesh.org:8000 datasink]).
*[http://manybooks.net/ ManyBooks.net] is a great resource for libre books in many formats.
*[http://ebooksgo.org/ ebooksgo has several nice libre books]
*[https://open.umn.edu/opentextbooks/SearchResults.aspx?subjectAreaId=3 The Open Textbook Library]
*Others?

=== Comics ===

*[https://xkcd.com XKCD] is cc-by-nc
*[https://archive.org/details/CoryDoctorowsFuturisticTalesOfTheHereAndNow Futuristic Tales of the Here and Now] based on stories by Cory Doctorow is cc-by-nc-sa
*There are [http://www.seosmarty.com/15-cartoonists-that-allow-using-their-web-comics-for-free/ others]

=== Music ===

There is definitely lots of CC music out there. Here are some resources:

*[http://phlow-magazine.com/ phlow magazine]
*[http://www.jamendo.com Jamendo]
*please add more

=== Audiobooks ===

*Little Brother by Cory Doctorow
*Harry Potter and the Methods of Rationality
*?

== Art ==

We could have a set of cloth pens and let sudoers or buyers of hackpacks customize them.

= Expansion packs =

== Fictionpack ==

Dead-tree versions of $1 to $3 essential hacker works. These are sold individually.

*The Dispossessed by Ursula Le Guin
*Cryptonomicon, Snow Crash or The Diamond Age by Neal Stephenson
*Little Brother by Cory Doctorow
*please add more

== Factpack ==

Dead-tree versions of $1 to $3 important non-fiction hacker literature. These are sold individually.

===Unfree===
*Hacking the xbox by Andrew Bunnie Huang
*The Cathedral and the bazaar by Eric S. Raymond

===Libre / Public Domain===
*Hackers by Stephen Levy (First chapter only)
*[http://codingfreedom.com/buy_download.html Coding Freedom] by Gabriella Coleman
*Free as in freedom by Richard Stallman
*[http://wndw.net Wireless Networking in the Developing World]
*[http://beautifultrouble.org/ Beautiful Trouble] - A toolbox for revolution and guides for creative protest.
*please add more

=== Manual for Civilization ===

A project from [http://longnow.org The Long Now]:
* http://blog.longnow.org/02010/04/06/manual-for-civilization/
* http://blog.longnow.org/02013/08/14/toward-a-manual-for-civilization/
* http://blog.longnow.org/02014/02/06/manual-for-civilization-begins/

== Clothpack ==

Mackenzie is working on this. Current target is $5.

Some things that may go in the pack:

*Scissors - $1 at dollar store
*Sewing needles
*Pins
*Thread
*Tailors chalk
*Conductive thread
*Instruction manual/booklet
*List of nearby places to access sewing machines for free

chrisbee would add-

*Dental floss
*Safety pins
*Ball o' wax
*A snap knife or razor blade
*Some gaffer's tape (makes good patches whether it's sticky or not)

== RXpack ==

Target price: $16

*A rtl-sdr compatible usb adapter (like [http://www.ebay.com/itm/New-RTL-SDR-DVB-T-HDTV-SDR-Dongle-Elonics-RTL2832U-E4000-Antenna-50MHz-2200-MHz-/181254905941?pt=LH_DefaultDomain_0&hash=item2a33a26055 this one])

== Wifipack ==

Target price: $30

*A dual-radio OpenWRT compatible router
*Instructions on how to flash with sudowrt firmware and do interesting things like spectrum analysis.

== Mate anywhere kit ==

Make tea and stay awake anywhere!

Target price: $10

*[http://www.ebay.com/itm/4Cups-Outdoor-Collapsible-Folding-Silicone-Travel-Camping-Cups-Mug-with-Handle-/221295331074?pt=LH_DefaultDomain_0&hash=item33863ac702 Silicone travel cup] - $5 (cheaper at Koreana Plaza?)
*[http://www.ebay.com/itm/Travel-Heater-Element-Boiler-Hot-Water-Coffee-Immersion-800W-Adapter-In-Stock-/201007156348?pt=LH_DefaultDomain_0&hash=item2eccf5cc7c Travel water boiler] - $3.38 (but meant for 220v :/)
*[http://www.ebay.com/itm/Stainless-Steel-Infuser-Strainer-Mesh-Tea-Spoon-Locking-Spice-Egg-Shaped-Ball-R1-/390734579644?pt=Small_Kitchen_Appliances_US&hash=item5af99887bc Tea ball] - $1
*Ziplock of yerba mate
*Piece of cloth + piece of string = reusable tea bag

== Hygiene pack ==

Target price: $5

*Toothbrush (25 cents at university/san pablo dollar store in four-packs)
*Small toothpaste (50 cents)
*Floss (50 cents)
*Hand sanitizer (50 cents)
*Small soap/bodywash (50 cents)
*Small deodorant ($1)
*T-shirt (can be used as emergency towel) (1.50)
*Condoms (free?)
*Small mirror ($1)
*Comb or hairbrush ($1)

== Sewing pack ==

[[File:Sewing hack pack.jpg|thumb|right|a hack pack for sewing with a sewing machine]]

Preferably on a belt, especially that can be easily slung across the chest, over one's shoulder. If sharing, should be adjustable to many sizes, for many-sized people.

* Adjustable bealt
* Scissors in easily accessible holster (could also use electrical cable or wires to approximate holster)
* Pin cushion in close-able container (used goofy rotating bait box here)
* Hand needle, thread, thimble or cork for hand-stitching, in small pouch
* Scraps of fabrics in large pouch—or patterns, manuals, or documents if necessary.
* (Optional) could attach machine oil lubricant container to belt as well.

== Camera pack ==

* Bag
* Foam (styrofoams from packaging materials are easy to find free)
** Use knife, scissors, and fabric+sewing to cut, arrange, and possibly cover foam padding.
* Camera
* Microphones
* Charger
* Other accessories

===Gallery===
Note: numbered by step completed & uploaded here, but re-ordered to show the process.

<gallery mode="packed-hover">
File:Camera hack pack foam scraps.jpg|Camera hack pack 4
File:Camera hack pack foam scraps 2.jpg|Camera hack pack 5
File:Camera hack pack sewing wide shot.jpg|Camera hack pack 6
File:Camera hack pack sewing.jpg|Camera hack pack 7
File:Camera hack pack small before open.jpg|Camera hack pack 2
File:Camera hack pack small before with camera.jpg|Camera hack pack 3
File:Camera hack pack small complete with camera.jpg|Camera hack pack 13
File:Camera hack pack small complete with camera and bike tube seal.jpg|Camera hack pack 14
File:Camera hack pack small complete closed.jpg|Camera hack pack 15
File:Camera hack pack large inside.jpg|Camera hack pack 8
File:Camera hack pack large inside with camera.jpg|Camera hack pack 9
File:Camera hack pack large inside with camera and covering.jpg|Camera hack pack 10
File:Camera hack pack large outside.jpg|Camera hack pack 11
File:Camera hack pack large outside in use.jpg|Camera hack pack 12
</gallery>

= Classes =

These are ideas for classes that we could

== Make something useful out of commonly found trash electronics ==

Teaches:

*Soldering
*Basic analog electronics
*Basic digital electronics

== Network class ==

Teaches:

*Programming a router
*Basic networking

== Web class ==

== Microcontroller class ==

Teaches basic C programming and how to program an arduino.

== Javascript class ==

== Physical game class ==

Have a bunch of sensors, blinkers, movers, etc. and let people figure out what kind of game they want to make, then actually make it. Use node.js to talk to the arduino and the arduino to interact with sensors.

Teaches:

*Combining multiple skills
**Soldering
**Arduino C programming
**Javascript programming
**HTML/CSS (for graphics)

=Resources=
==Suppliers==
===Local===
*99cent Store @ Shattuck
*Goodwill @ San Pablo
*Daiso in Berkeley
===Online===
*[http://alibaba.com Alibaba]
*[http://aliexpress.com Ali Express]
*[http://harborfreight.com Harbor Freight]
*[http://priceuswholesale.com PriceUSWholesale]
*[https://amazon.com Amazon]
*[https://ebay.com eBay]
==Inspiration==
*[http://en.wikipedia.org/wiki/Bug-out_bag Bug-Out Bags]
*[http://dada.pink/dada/stuff/ Tom Levine's stuff]

Room Program

2013-08-04T03:53:12Z

Tlevine: /* Things we need */

This is a program document for the physical room layout and a scratch pad for associated notes, research and observations [[User:Tlevine|Tlevine]] ([[User talk:Tlevine|talk]]) 19:59, 3 August 2013 (PDT)

== Terms ==
A program document specifies the requirements of a space without concern for how these requirements will be met. By coming up with a program before planning the specific layout, we separate the concerns of specifying requirements and implementing those specifications.

== Potentially relevant observations small inferences==
I recorded these observations on August 3, 2013, during the reorganization weekend. They should represent how the room was normally arranged before that.

I should add some pictures so that everything below makes sense.

=== Things ===
These observations focus more on objects rather than how people interact with them. You might call these "traces" or "leftovers" or other things depending on the exact observation.

* Junk often accumulates in on the main table.
* There are plants all over the place, but there's no special place for them.
* Each table has access to power plugs.
* Those big yellow papers are all over the place. (Does anyone read them?)
* High shelves aren't used very much. (Maybe they're hard to reach.)
* There's a plastic tarp between the shelf with the bio-hacking and the power tools.
* Do the things on the bulletin board ever change?

=== People ===
* The stuff on the windowsill is rarely used.
* DoraBot and empty arcades are rarely used but not stored in the closet. (These are big; maybe we should come up with a better way of storing big things.)
* People plug into the speakers quite a bit.
* Do people ever access things from the cubbies?
* Maybe like 15 people are in the Sudoroom proper at peak times. Other people might be in the common space.
* People use the refrigerator a lot
* People access the sudomate and subir stuff regularly.

=== Features that could be documented ===
The existance of these things might be particularly good to document in the room.

* space.sudoroom.org
*

=== Things people want ===
Some people like clean, and some people make messes, so we want to separate clean from messy. (Largely Jordan's suggestion)

== Things we need ==

* There should be lots of easily-accessible big shelves where can dump their junk so they don't leave it in the middle of the room.
* There should be places for plants.

== Adjacencies ==

* Storage space should be near the work areas.
* The woodworking tools should be away from the computer work table.

Room Program

2013-08-04T03:51:14Z

Tlevine: /* Adjacencies */

This is a program document for the physical room layout and a scratch pad for associated notes, research and observations [[User:Tlevine|Tlevine]] ([[User talk:Tlevine|talk]]) 19:59, 3 August 2013 (PDT)

== Terms ==
A program document specifies the requirements of a space without concern for how these requirements will be met. By coming up with a program before planning the specific layout, we separate the concerns of specifying requirements and implementing those specifications.

== Potentially relevant observations small inferences==
I recorded these observations on August 3, 2013, during the reorganization weekend. They should represent how the room was normally arranged before that.

I should add some pictures so that everything below makes sense.

=== Things ===
These observations focus more on objects rather than how people interact with them. You might call these "traces" or "leftovers" or other things depending on the exact observation.

* Junk often accumulates in on the main table.
* There are plants all over the place, but there's no special place for them.
* Each table has access to power plugs.
* Those big yellow papers are all over the place. (Does anyone read them?)
* High shelves aren't used very much. (Maybe they're hard to reach.)
* There's a plastic tarp between the shelf with the bio-hacking and the power tools.
* Do the things on the bulletin board ever change?

=== People ===
* The stuff on the windowsill is rarely used.
* DoraBot and empty arcades are rarely used but not stored in the closet. (These are big; maybe we should come up with a better way of storing big things.)
* People plug into the speakers quite a bit.
* Do people ever access things from the cubbies?
* Maybe like 15 people are in the Sudoroom proper at peak times. Other people might be in the common space.
* People use the refrigerator a lot
* People access the sudomate and subir stuff regularly.

=== Features that could be documented ===
The existance of these things might be particularly good to document in the room.

* space.sudoroom.org
*

=== Things people want ===
Some people like clean, and some people make messes, so we want to separate clean from messy. (Largely Jordan's suggestion)

== Things we need ==

* There should be lots of easily-accessible big shelves where can dump their junk so they don't leave it in the middle of the room.

== Adjacencies ==

* Storage space should be near the work areas.
* The woodworking tools should be away from the computer work table.

Room Program

2013-08-04T03:17:13Z

Tlevine: /* People */

Room Program

2013-08-04T03:15:54Z

Tlevine: /* Potentially relevant observations small inferences */

This is a program document for the physical room layout and a scratch pad for associated notes, research and observations [[User:Tlevine|Tlevine]] ([[User talk:Tlevine|talk]]) 19:59, 3 August 2013 (PDT)

== Terms ==
A program document specifies the requirements of a space without concern for how these requirements will be met. By coming up with a program before planning the specific layout, we separate the concerns of specifying requirements and implementing those specifications.

== Potentially relevant observations small inferences==
I recorded these observations on August 3, 2013, during the reorganization weekend. They should represent how the room was normally arranged before that.

I should add some pictures so that everything below makes sense.

=== Things ===
These observations focus more on objects rather than how people interact with them. You might call these "traces" or "leftovers" or other things depending on the exact observation.

* Junk often accumulates in on the main table.
* There are plants all over the place, but there's no special place for them.
* Each table has access to power plugs.
* Those big yellow papers are all over the place. (Does anyone read them?)
* High shelves aren't used very much. (Maybe they're hard to reach.)
* There's a plastic tarp between the shelf with the bio-hacking and the power tools.
* Do the things on the bulletin board ever change?

=== People ===
* The stuff on the windowsill is rarely used.
* DoraBot and empty arcades are rarely used but not stored in the closet. (These are big; maybe we should come up with a better way of storing big things.)
* People plug into the speakers quite a bit.
* Do people ever access things from the cubbies?
* Maybe like 15 people are in the Sudoroom proper at peak times. Other people might be in the common space.

=== Features that could be documented ===
The existance of these things might be particularly good to document in the room.

* space.sudoroom.org
*

=== Things people want ===
Some people like clean, and some people make messes, so we want to separate clean from messy. (Largely Jordan's suggestion)

== Things we need ==

* There should be lots of easily-accessible big shelves where can dump their junk so they don't leave it in the middle of the room.

== Adjacencies ==

*

Room Program

2013-08-04T03:11:18Z

Tlevine:

This is a program document for the physical room layout and a scratch pad for associated notes, research and observations [[User:Tlevine|Tlevine]] ([[User talk:Tlevine|talk]]) 19:59, 3 August 2013 (PDT)

== Terms ==
A program document specifies the requirements of a space without concern for how these requirements will be met. By coming up with a program before planning the specific layout, we separate the concerns of specifying requirements and implementing those specifications.

== Potentially relevant observations small inferences==
I recorded these observations on August 3, 2013, during the reorganization weekend. They should represent how the room was normally arranged before that.

I should add some pictures so that everything below makes sense.

=== Things ===
These observations focus more on objects rather than how people interact with them. You might call these "traces" or "leftovers" or other things depending on the exact observation.

* Junk often accumulates in on the main table.
* There are plants all over the place, but there's no special place for them.
* Each table has access to power plugs.
* Those big yellow papers are all over the place. (Does anyone read them?)
* High shelves aren't used very much. (Maybe they're hard to reach.)

=== People ===
* The stuff on the windowsill is rarely used.
* DoraBot and empty arcades are rarely used but not stored in the closet. (These are big; maybe we should come up with a better way of storing big things.)
* People plug into the speakers quite a bit.
* Do people ever access things from the cubbies?

=== Features that could be documented ===
The existance of these things might be particularly good to document in the room.

* space.sudoroom.org
*

=== Things people want ===
Some people like clean, and some people make messes, so we want to separate clean from messy. (Largely Jordan's suggestion)

== Things we need ==

* There should be lots of easily-accessible big shelves where can dump their junk so they don't leave it in the middle of the room.

== Adjacencies ==

*

Room Program

2013-08-04T03:07:30Z

Tlevine: /* People */

Room Program

2013-08-04T03:00:38Z

Tlevine:

Room Program

2013-08-04T02:59:15Z

Tlevine:

This is a program document for the physical room layout and a scratch pad for associated notes, research and observations.

[[User:Tlevine|Tlevine]] ([[User talk:Tlevine|talk]]) 19:59, 3 August 2013 (PDT)

== Terms ==
A program document specifies the requirements of a space without concern for how these requirements will be met. By coming up with a program before planning the specific layout, we separate the concerns of specifying requirements and implementing those specifications.

== Potentially relevant observations small inferences==
I recorded these observations on August 3, 2013, during the reorganization weekend. They should represent how the room was normally arranged before that.

I should add some pictures so that everything below makes sense.

=== Things ===
These observations focus more on objects rather than how people interact with them. You might call these "traces" or "leftovers" or other things depending on the exact observation.

* Junk often accumulates in on the main table.
* There are plants all over the place, but there's no special place for them.
* Each table has access to power plugs.

=== People ===
* The stuff on the windowsill is rarely used.
* DoraBot and empty arcades are rarely used but not stored in the closet. (These are big; maybe we should come up with a better way of storing big things.)
* People plug into the speakers quite a bit.

=== Features that could be documented ===
The existance of these things might be particularly good to document in the room.

* space.sudoroom.org
*

== Adjacencies ==

Room Program

2013-08-04T02:58:54Z

Tlevine: /* Potentially relevant observations small inferences */

This is a program document for the physical room layout and a scratch pad for associated notes, research and observations.

== Terms ==
A program document specifies the requirements of a space without concern for how these requirements will be met. By coming up with a program before planning the specific layout, we separate the concerns of specifying requirements and implementing those specifications.

== Potentially relevant observations small inferences==
I recorded these observations on August 3, 2013, during the reorganization weekend. They should represent how the room was normally arranged before that.

I should add some pictures so that everything below makes sense.

=== Things ===
These observations focus more on objects rather than how people interact with them. You might call these "traces" or "leftovers" or other things depending on the exact observation.

* Junk often accumulates in on the main table.
* There are plants all over the place, but there's no special place for them.
* Each table has access to power plugs.

=== People ===
* The stuff on the windowsill is rarely used.
* DoraBot and empty arcades are rarely used but not stored in the closet. (These are big; maybe we should come up with a better way of storing big things.)
* People plug into the speakers quite a bit.

=== Features that could be documented ===
The existance of these things might be particularly good to document in the room.

* space.sudoroom.org
*

== Adjacencies ==

Room Program

2013-08-04T02:55:32Z

Tlevine: /* Potentially relevant observations */

This is a program document for the physical room layout and a scratch pad for associated notes, research and observations.

== Terms ==
A program document specifies the requirements of a space without concern for how these requirements will be met. By coming up with a program before planning the specific layout, we separate the concerns of specifying requirements and implementing those specifications.

== Potentially relevant observations small inferences==
I recorded these observations on August 3, 2013, during the reorganization weekend. They should represent how the room was normally arranged before that.

I should add some pictures so that everything below makes sense.

* Junk often accumulates in on the main table.
* There are plants all over the place, but there's no special place for them.
* The stuff on the windowsill is rarely used.
* DoraBot and empty arcades are rarely used but not stored in the closet. (These are big; maybe we should come up with a better way of storing big things.)
* Each table has access to power plugs.

== Adjacencies ==

Room Program

2013-08-04T02:51:25Z

Tlevine: /* Terms */

Room Program

2013-08-04T02:50:19Z

Tlevine: Outline