HacDC Wiki - User contributions [en]

HacDC Multi-touch device

2008-12-07T06:20:33Z

Rdegraci: Undo revision 1541 by 125.243.233.194 (Talk)

== Multi-Touch Display Interface==

The discussion list for this project is [http://hacdc.org/mailman/listinfo/multi-touch-int-display_hacdc.org multi-touch-int-display@hacdc.org].

=== Meeting Minutes ===
* [[MTID030708 | Roadmap Meeting]]

=== Overview ===
Build the multi-touch display interface so that it can become a user interface for future HacDC projects as well as provide a collaboration interface for real-time multi-user-multi-touch applications, created by and for HacDC and its friends. http://en.wikipedia.org/wiki/Multi-touch

==== High Level Requirements ====
* When complete, device will be donated to HacDC
* Plans, instructions, parts list will be available to the public
* Source code will be available to the public
* Implement using FTIR http://cs.nyu.edu/~jhan/ftirtouch/
===== Reference Documentation =====
* Use Harry van der Veen building instructions as a guide http://www.multitouch.nl/documents/multitouchdisplay_howto_070523_v02.pdf
* User David Smith and David Holman instructions as a guide http://dundee.cs.queensu.ca/wiki/index.php/Building_a_Multi-Touch_Sensitive_Table
* Working Flash applications with multi-touch http://www.multitouch.nl/?p=23

==== Detailed Requirements ====
===== Operating System =====
* TBD

===== Package Management =====
* TBD

===== Software =====
*TouchLib http://www.whitenoiseaudio.com/touchlib/
*TouchLib Source Code http://code.google.com/p/touchlib/

===== 3rd Party Software =====
* TBD

===== Hardware =====

====== Tools ======
* Power drill + 5mm drill
* Standard size screwdriver (flathead & cross)
* Small sharp knife
* Scissors
* Different grits of sanding paper
* Wooden cubical object to wrap sanding paper around
* Copper or silver polish + towel
* Synthetic material saw

====== Materials ======
* Screws
* Glue (hotglue / white glue)
* Frame material (for example wood, aluminium or PVC)
* Connector strips
* Electronic wire (0,5 mm)
* R-LEDs + resistors
* Acrylic also known as plexiglas
* Black photo negatives
* Power source
* Power cable
* Webcam
* Projector
* Projection material (tracing paper)
* Silicone rubber
* Working computer
* Mirror (optionally)

==== Testing Resources ====
===== Equipment =====
* TBD

==== Test Plan ====
TBD

==== Design ====
TBD

==== Human Resources ====
* Project Coordinator: [[User:Rdegraci|RBD]]

==== Task Partitioning ====
* TBD

==== Timeline ====
Assume 4 hour days.
* TBD

==== Implementation ====
TBD

==== Component Testing ====
TBD

==== Integration Testing ====
TBD

[[Category:Ongoing_Projects]]

Single Expenditure and Reimbursement Policy

2008-08-07T18:43:11Z

Rdegraci: /* PROPOSAL */

== Summary ==
Single expenditures are important to the operation of HacDC and its Events and Projects. However, multiple single-expenditures that are really outlays for a particular Event or Project, form a defacto ad-hoc budget. These de-facto ad-hoc budgets can become quite large and Membership only can only know how large, after the fact. Ad-hoc defacto budgets can easily consume most of the HacDC funds and push-back other Events or Projects that require real budgets. Real budgets are burdened by approval whereas ad-hoc defacto budgets do not require approval, even though they can theoretically spend as much funds as a real budget.

== Potential Solutions ==

* Lower the limit of single expenditures to $100 and record the expenditures in the weekley finance report and require pre-approval for reimbursements over $100
** Pros:
*** HacDC members are able to execute single expenditures
*** Any quickly organized Event/Project that attempts to use multiple single-expenditures as a defacto ad-hoc budget would be limited from doing so.
*** HacDC members would be informed at least once a week as to what single expenditures have been executed
*** Depletion of HacDC funds by defacto ad-hoc budgets would be limited
*** Single Expenditures would be limited in purpose for providing one-shot low cost resources (food, soda, etc) for Events and Projects
** Cons:
*** Quickly organized events would require the organizers to get approval from HacDC membership for funding beyond single expenditures
*** Quickly organized space building/storage infrastructure improvements would require the organizers to get approval from HacDC membership for funding beyond single expenditures
*** Quickly organized Projects over $100 in total costs would require the organizer to get approval from HacDC membership for funding beyond single expenditures
*** Quickly organized projects that may require reimbursements to be implemented would require the organizers to get approval from HacDC membership.

== PROPOSAL ==

The following Administrative Policy is submitted for discussion:
* Single Expenditures
** Single expenditures under $100 do not require approval
** Single expenditures that are $100 or over, require approval by quorum of the voting membership.
** All single expenditures must be recorded by the Minster of Finance in the weekly Finance Report as a line item that shows the day, amount, and purpose of the expenditure.
* Reimbursements
** Reimbursements over $100 require pre-approval by quorum of the voting membership.

Single Expenditure and Reimbursement Policy

2008-08-07T18:30:49Z

Rdegraci: /* PROPOSAL */

== Summary ==
Single expenditures are important to the operation of HacDC and its Events and Projects. However, multiple single-expenditures that are really outlays for a particular Event or Project, form a defacto ad-hoc budget. These de-facto ad-hoc budgets can become quite large and Membership only can only know how large, after the fact. Ad-hoc defacto budgets can easily consume most of the HacDC funds and push-back other Events or Projects that require real budgets. Real budgets are burdened by approval whereas ad-hoc defacto budgets do not require approval, even though they can theoretically spend as much funds as a real budget.

== Potential Solutions ==

* Lower the limit of single expenditures to $100 and record the expenditures in the weekley finance report and require pre-approval for reimbursements over $100
** Pros:
*** HacDC members are able to execute single expenditures
*** Any quickly organized Event/Project that attempts to use multiple single-expenditures as a defacto ad-hoc budget would be limited from doing so.
*** HacDC members would be informed at least once a week as to what single expenditures have been executed
*** Depletion of HacDC funds by defacto ad-hoc budgets would be limited
*** Single Expenditures would be limited in purpose for providing one-shot low cost resources (food, soda, etc) for Events and Projects
** Cons:
*** Quickly organized events would require the organizers to get approval from HacDC membership for funding beyond single expenditures
*** Quickly organized space building/storage infrastructure improvements would require the organizers to get approval from HacDC membership for funding beyond single expenditures
*** Quickly organized Projects over $100 in total costs would require the organizer to get approval from HacDC membership for funding beyond single expenditures
*** Quickly organized projects that may require reimbursements to be implemented would require the organizers to get approval from HacDC membership.

== PROPOSAL ==

The following Administrative Policy is submitted for discussion:
* Single Expenditures
** Single expenditures under $101 do not require approval.
** All single expenditures must be recorded by the Minster of Finance in the weekly Finance Report as a line item that shows the day, amount, and purpose of the expenditure.
* Reimbursements
** Reimbursements over $101 require pre-approval by quorum of the voting membership.

Single Expenditure and Reimbursement Policy

2008-08-07T18:26:52Z

Rdegraci: /* PROPOSAL */

== Summary ==
Single expenditures are important to the operation of HacDC and its Events and Projects. However, multiple single-expenditures that are really outlays for a particular Event or Project, form a defacto ad-hoc budget. These de-facto ad-hoc budgets can become quite large and Membership only can only know how large, after the fact. Ad-hoc defacto budgets can easily consume most of the HacDC funds and push-back other Events or Projects that require real budgets. Real budgets are burdened by approval whereas ad-hoc defacto budgets do not require approval, even though they can theoretically spend as much funds as a real budget.

== Potential Solutions ==

* Lower the limit of single expenditures to $100 and record the expenditures in the weekley finance report and require pre-approval for reimbursements over $100
** Pros:
*** HacDC members are able to execute single expenditures
*** Any quickly organized Event/Project that attempts to use multiple single-expenditures as a defacto ad-hoc budget would be limited from doing so.
*** HacDC members would be informed at least once a week as to what single expenditures have been executed
*** Depletion of HacDC funds by defacto ad-hoc budgets would be limited
*** Single Expenditures would be limited in purpose for providing one-shot low cost resources (food, soda, etc) for Events and Projects
** Cons:
*** Quickly organized events would require the organizers to get approval from HacDC membership for funding beyond single expenditures
*** Quickly organized space building/storage infrastructure improvements would require the organizers to get approval from HacDC membership for funding beyond single expenditures
*** Quickly organized Projects over $100 in total costs would require the organizer to get approval from HacDC membership for funding beyond single expenditures
*** Quickly organized projects that may require reimbursements to be implemented would require the organizers to get approval from HacDC membership.

== PROPOSAL ==

The following Administrative Policy is submitted for discussion:

Single Expenditures under $101 do not require approval.

Single Expenditures over $100 require approval by quorum of the voting membership

All single expenditures must be recorded by the Minster of Finance in the weekly Finance Report as a line item that shows the day, amount, and purpose of the expenditure.

Reimbursements over $100 require pre-approval by quorum of the voting membership.

Single Expenditure and Reimbursement Policy

2008-08-07T18:18:56Z

Rdegraci: New page: == Summary == Single expenditures are important to the operation of HacDC and its Events and Projects. However, multiple single-expenditures that are really outlays for a particular Event...

== Summary ==
Single expenditures are important to the operation of HacDC and its Events and Projects. However, multiple single-expenditures that are really outlays for a particular Event or Project, form a defacto ad-hoc budget. These de-facto ad-hoc budgets can become quite large and Membership only can only know how large, after the fact. Ad-hoc defacto budgets can easily consume most of the HacDC funds and push-back other Events or Projects that require real budgets. Real budgets are burdened by approval whereas ad-hoc defacto budgets do not require approval, even though they can theoretically spend as much funds as a real budget.

== Potential Solutions ==

* Lower the limit of single expenditures to $100 and record the expenditures in the weekley finance report and require pre-approval for reimbursements over $100
** Pros:
*** HacDC members are able to execute single expenditures
*** Any quickly organized Event/Project that attempts to use multiple single-expenditures as a defacto ad-hoc budget would be limited from doing so.
*** HacDC members would be informed at least once a week as to what single expenditures have been executed
*** Depletion of HacDC funds by defacto ad-hoc budgets would be limited
*** Single Expenditures would be limited in purpose for providing one-shot low cost resources (food, soda, etc) for Events and Projects
** Cons:
*** Quickly organized events would require the organizers to get approval from HacDC membership for funding beyond single expenditures
*** Quickly organized space building/storage infrastructure improvements would require the organizers to get approval from HacDC membership for funding beyond single expenditures
*** Quickly organized Projects over $100 in total costs would require the organizer to get approval from HacDC membership for funding beyond single expenditures
*** Quickly organized projects that may require reimbursements to be implemented would require the organizers to get approval from HacDC membership.

== PROPOSAL ==

The following Administrative Policy is submitted for discussion:

Single Expenditures under $100 do not require approval, however must be recorded by the Minster of Finance in the weekly Finance Report as a line item that shows the day, amount, and purpose of the expenditure.

Reimbursements over $100 require pre-approval by quorum of the voting membership.

HacDC Multi-touch device

2008-07-16T19:06:10Z

Rdegraci:

== Multi-Touch Display Interface==

=== Overview ===
Build the multi-touch display interface so that it can become a user interface for future HacDC projects as well as provide a collaboration interface for real-time multi-user-multi-touch applications, created by and for HacDC and its friends. http://en.wikipedia.org/wiki/Multi-touch

==== High Level Requirements ====
* When complete, device will be donated to HacDC
* Plans, instructions, parts list will be available to the public
* Source code will be available to the public
* Implement using FTIR http://cs.nyu.edu/~jhan/ftirtouch/
===== Reference Documentation =====
* Use Harry van der Veen building instructions as a guide http://www.multitouch.nl/documents/multitouchdisplay_howto_070523_v02.pdf
* User David Smith and David Holman instructions as a guide http://dundee.cs.queensu.ca/wiki/index.php/Building_a_Multi-Touch_Sensitive_Table
* Working Flash applications with multi-touch http://www.multitouch.nl/?p=23

==== Detailed Requirements ====
===== Operating System =====
* TBD

===== Package Management =====
* TBD

===== Software =====
*TouchLib http://www.whitenoiseaudio.com/touchlib/
*TouchLib Source Code http://code.google.com/p/touchlib/

===== 3rd Party Software =====
* TBD

===== Hardware =====

====== Tools ======
* Power drill + 5mm drill
* Standard size screwdriver (flathead & cross)
* Small sharp knife
* Scissors
* Different grits of sanding paper
* Wooden cubical object to wrap sanding paper around
* Copper or silver polish + towel
* Synthetic material saw

====== Materials ======
* Screws
* Glue (hotglue / white glue)
* Frame material (for example wood, aluminium or PVC)
* Connector strips
* Electronic wire (0,5 mm)
* R-LEDs + resistors
* Acrylic also known as plexiglas
* Black photo negatives
* Power source
* Power cable
* Webcam
* Projector
* Projection material (tracing paper)
* Silicone rubber
* Working computer
* Mirror (optionally)

==== Testing Resources ====
===== Equipment =====
* TBD

==== Test Plan ====
TBD

==== Design ====
TBD

==== Human Resources ====
* Project Coordinator: [[User:Rdegraci|Rodney Degracia]]

==== Task Partitioning ====
* TBD

==== Timeline ====
Assume 4 hour days.
* TBD

==== Implementation ====
TBD

==== Component Testing ====
TBD

==== Integration Testing ====
TBD

[[Category:Ongoing_Projects]]

Category:Conferences

2008-07-01T14:08:34Z

Rdegraci:

Insert new pages, for external conferences/events that you plan to go to and would like other HacDC members to know about.

* Local to DC/VA/MD area (within 50 mile radius of DC)
** [[ RubyNation | RubyNation August 1&2, 2008 Herndon, VA]]

* Out of Town (50+ radius from DC)

Category:Conferences

2008-07-01T13:59:46Z

Rdegraci: New page: Insert new pages, for external conferences/events that you plan to go to and would like other HacDC members to know about. * Local to DC/VA/MD area (within 50 mile radius of DC) ** [[ Rub...

User:Rdegraci

2008-07-01T13:46:34Z

Rdegraci:

Projects:

*[[HacDC Intranet Server|Intranet Server]]
*[[HacDC Multi-touch device|Multi-touch device]]

[[Category:Members]]

[[Category:Conferences]]

HacDC Multi-touch device

2008-06-29T17:17:42Z

Rdegraci: /* Human Resources */

== Multi-Touch Display Interface==

=== Overview ===
Build the multi-touch display interface so that it can become a user interface for future HacDC projects as well as provide a collaboration interface for real-time multi-user-multi-touch applications, created by and for HacDC and its friends. http://en.wikipedia.org/wiki/Multi-touch

==== High Level Requirements ====
* When complete, device will be donated to HacDC
* Plans, instructions, parts list will be available to the public
* Source code will be available to the public
* Implement using FTIR http://cs.nyu.edu/~jhan/ftirtouch/
* Use Harry van der Veen building instructions as a guide http://www.multitouch.nl/documents/multitouchdisplay_howto_070523_v02.pdf

==== Detailed Requirements ====
===== Operating System =====
* TBD

===== Package Management =====
* TBD

===== Software =====
* TBD

===== 3rd Party Software =====
* TBD

===== Hardware =====

====== Tools ======
* Power drill + 5mm drill
* Standard size screwdriver (flathead & cross)
* Small sharp knife
* Scissors
* Different grits of sanding paper
* Wooden cubical object to wrap sanding paper around
* Copper or silver polish + towel
* Synthetic material saw

====== Materials ======
* Screws
* Glue (hotglue / white glue)
* Frame material (for example wood, aluminium or PVC)
* Connector strips
* Electronic wire (0,5 mm)
* R-LEDs + resistors
* Acrylic also known as plexiglas
* Black photo negatives
* Power source
* Power cable
* Webcam
* Projector
* Projection material (tracing paper)
* Silicone rubber
* Working computer
* Mirror (optionally)

==== Testing Resources ====
===== Equipment =====
* TBD

==== Test Plan ====
TBD

==== Design ====
TBD

==== Human Resources ====
* Project Coordinator: [[User:Rdegraci|Rodney Degracia]]

==== Task Partitioning ====
* TBD

==== Timeline ====
Assume 4 hour days.
* TBD

==== Implementation ====
TBD

==== Component Testing ====
TBD

==== Integration Testing ====
TBD

[[Category:Ongoing_Projects]]

Welcome to the HacDC Wiki

2008-06-29T17:04:02Z

Rdegraci: /* HacDC's Live Status */

<span style="font-size:large; line-height:1.5em; color:#222">Welcome to HacDC. We are a hacker space located in Washington, DC. HacDC members improve the world by creatively rethinking technology. We break, build, and occasionally abuse technology in the pursuit of greater knowledge about how it works and repurposing it to build new things. Our shop is located in the [http://en.wikipedia.org/wiki/Columbia_Heights%2C_Washington%2C_D.C. Columbia Heights] neighborhood of DC.</span>

If you're new here, you should start by looking at our public web site at [http://www.hacdc.org/ hacdc.org]. Our Wiki is mostly for internal organization, but you're welcome to look through to get a sense of what we work on (and consider joining yourself!).

== HacDC's Live Status ==

HacDC is {{:Live Status}}

For full detail, visit the [[Live Status]] page.

Find out about current and future HacDC events by looking at our [http://www.google.com/calendar/embed?src=sb8mh1d332pbvnb2g4iob2p728@group.calendar.google.com Event Calender]

== Major Pages ==

* [[:Category:Ongoing Projects|Ongoing Projects]]
* [[Wishlist]]

== Full Organization ==

{| border="1" cellpadding="3" cellspacing="0"
|-
! style="background:#CCCCCC" | [[:Category:Topics]]
! style="background:#CCCCCC" | [[:Category:Community]]
! style="background:#CCCCCC" | [[:Category:Projects]]
! style="background:#CCCCCC" | [[:Category:In the Space]]
! style="background:#CCCCCC" | [[:Category:Policy]]
|-
| Themes and threads that span across the other categories in the Wiki. This is also where we keep things that don't easily fit in other categories:
* [[:Category:Meeting Minutes | Meeting Minutes]]
* [[:Category:Financial Reports | Financial Reports]]
* [[:Category:Meeting Agendas | Meeting Agendas]]
| Pages on people in our community :
* [[:Category:Members | Member User Pages]]
* [[:Category:Collaborators | HacDC Collaborators]]
* [[:Category:Friends | Friends of HacDC]]
* [[:Category:Heroes | Heroes and people who inspire us]]
| Where our projects collaborate and document their research and progress. They are generally classified as:
* [[:Category:Ongoing Projects | Ongoing Projects]]
* [[:Category:Proposed Projects | Proposed Projects]]
* [[:Category:Abandoned Projects | Abandoned Projects]]
| Entries relating to the space including layout and events and classes we hold
* [[:Category:Space Configuration | Configuration]]
* [[:Category:Event Planning | Event Planning]]
* [[:Category:Classes | Classes]]
* [[:Category:What_I_Stole | What I Stole]]
| Our Policy Manual is divded into the following subcategories:
* [[:Category:Command Policy | Command]]
* [[:Category:Control Policy | Control]]
* [[:Category:Communications Policy | Communications]]
* [[:Category:Collaboration Policy | Collaboration]]
* [[:Category:Khaos Policy | Khaos]]
|}

__NOTOC__

HacDC Multi-touch device

2008-06-27T21:40:29Z

Rdegraci:

== Multi-Touch Display Interface==

=== Overview ===
Build the multi-touch display interface so that it can become a user interface for future HacDC projects as well as provide a collaboration interface for real-time multi-user-multi-touch applications, created by and for HacDC and its friends. http://en.wikipedia.org/wiki/Multi-touch

==== High Level Requirements ====
* When complete, device will be donated to HacDC
* Plans, instructions, parts list will be available to the public
* Source code will be available to the public
* Implement using FTIR http://cs.nyu.edu/~jhan/ftirtouch/
* Use Harry van der Veen building instructions as a guide http://www.multitouch.nl/documents/multitouchdisplay_howto_070523_v02.pdf

==== Detailed Requirements ====
===== Operating System =====
* TBD

===== Package Management =====
* TBD

===== Software =====
* TBD

===== 3rd Party Software =====
* TBD

===== Hardware =====

====== Tools ======
* Power drill + 5mm drill
* Standard size screwdriver (flathead & cross)
* Small sharp knife
* Scissors
* Different grits of sanding paper
* Wooden cubical object to wrap sanding paper around
* Copper or silver polish + towel
* Synthetic material saw

====== Materials ======
* Screws
* Glue (hotglue / white glue)
* Frame material (for example wood, aluminium or PVC)
* Connector strips
* Electronic wire (0,5 mm)
* R-LEDs + resistors
* Acrylic also known as plexiglas
* Black photo negatives
* Power source
* Power cable
* Webcam
* Projector
* Projection material (tracing paper)
* Silicone rubber
* Working computer
* Mirror (optionally)

==== Testing Resources ====
===== Equipment =====
* TBD

==== Test Plan ====
TBD

==== Design ====
TBD

==== Human Resources ====
* Project Lead: [[User:Rdegraci|Rodney Degracia]]

==== Task Partitioning ====
* TBD

==== Timeline ====
Assume 4 hour days.
* TBD

==== Implementation ====
TBD

==== Component Testing ====
TBD

==== Integration Testing ====
TBD

[[Category:Ongoing_Projects]]

HacDC Multi-touch device

2008-06-27T21:25:51Z

Rdegraci:

HacDC Multi-touch device

2008-06-27T21:25:23Z

Rdegraci: New page: == Intranet Server == === Overview === Build the multi-touch display interface so that it can become a user interface for future HacDC projects as well as provide a collaboration interfa...

== Intranet Server ==

=== Overview ===
Build the multi-touch display interface so that it can become a user interface for future HacDC projects as well as provide a collaboration interface for real-time multi-user-multi-touch applications, created by and for HacDC and its friends.

==== High Level Requirements ====
* When complete, device will be donated to HacDC
* Plans, instructions, parts list will be available to the public
* Source code will be available to the public

==== Detailed Requirements ====
===== Operating System =====
* TBD

===== Package Management =====
* TBD

===== Software =====
* TBD

===== 3rd Party Software =====
* TBD

==== Testing Resources ====
===== Equipment =====
* TBD

==== Test Plan ====
TBD

==== Design ====
TBD

==== Human Resources ====
* Lead Engineer: [[User:Rdegraci|Rodney Degracia]]

==== Task Partitioning ====
* TBD

==== Timeline ====
Assume 4 hour days.
* TBD

==== Implementation ====
TBD

==== Component Testing ====
TBD

==== Integration Testing ====
TBD

[[Category:Ongoing_Projects]]

HacDC Intranet Server

2008-06-21T00:53:07Z

Rdegraci:

== Intranet Server ==

=== Overview ===
An Intranet server provides an on-site platform for interfacing HacDC-specific devices or scripts or files.

==== High Level Requirements ====
* All HacDC members will have an account
* Private Knowledge Base "For HacDC members eyes only"
* Programming platform
* Platform for Multi-touch Project
* Platform for interfacing remote-sensing devices

==== Detailed Requirements ====
===== Operating System =====
* Slackware 12.1 Disk 1
* Slackware 12.1 Disk 2
* Slackware 12.1 Disk 3
http://www.slackware.com/getslack/

===== Package Management =====
* Swaret

===== Software =====
* Full Installation of all Slacware 12.1 packages

===== 3rd Party Software =====
* Wagn 0.9.1

==== Testing Resources ====
===== Equipment =====
* Standard CRT
* Keyboard
* PS2 Mouse
* Laptop with web browser

==== Test Plan ====
TBD

==== Design ====
n/a

==== Human Resources ====
* Lead Engineer: Rodney Degracia
* System Admin: Rodney Degracia
* Backup Admin: Rodney Degracia

==== Task Partitioning ====
* Partition storage
* Install and configure OS
* Configure MySQL
* Configure httpd (Apache 2)
* Install Wagn 0.9.1
* Configure Wagn
* Secure OS
* Mount Server into Rack
* Supply power to Server
* Attach Server to LAN
* Test Server

==== Timeline ====
Assume 4 hour days.
* Day 1
** Partition storage
** Install and configure OS
** Configure MySQL
** Configure httpd (Apache 2)
** Install Wagn 0.9.1
** Configure Wagn
** Secure OS
* Day 2
** Mount Server into Rack
** Supply power to Server
** Attach Server to LAN
** Test Server

==== Implementation ====
TBD

==== Component Testing ====
n/a

==== Integration Testing ====
n/a

[[Category:Ongoing_Projects]]

HacDC Intranet Server

2008-06-21T00:49:58Z

Rdegraci: New page: == Intranet Server == === Overview === An Intranet server provides an on-site platform for interfacing HacDC-specific devices or scripts or files. ==== High Level Requirements ==== * Al...

User:Rdegraci

2008-06-20T23:32:24Z

Rdegraci:

Projects:

*[[HacDC Intranet Server|Intranet Server]]
*[[HacDC Multi-touch device|Multi-touch device]]

User:Rdegraci

2008-06-20T23:28:47Z

Rdegraci: New page: Projects: *Intranet Server *Multi-touch device

Projects:

*Intranet Server
*Multi-touch device