Where open-source really shines, though, is in the ability to empower people to make completely custom interfaces without prior knowledge. They can literally copy-and-paste their way into a brand new interface and, even in the end, have no idea how it works.
While I was at the Summit I heard the term "empowerment" used a few times by other speakers. It is casually dropped in place, like standard marketing speak. It lacks the impact that I think a little bit of context can give.
Take a few moments and follow along in this visualization to help understand what I mean by empowerment: You're in the home of a child who has a physical disability. Over the years you've become quite familiar with the medical system, as she needs regular attention. Your home has been modified so that she can get around in her wheel chair by herself. You had to raise enough money from your local community to purchase a van so that you could transport her with her chair. When she goes to elementary school, she draws attention, or worse, is ignored because she looks different, moves different, and acts different. All she wants when she comes home is a little while in a video game where she can just be like everyone else.
As a parent, you want to do anything and everything for your child. You recognize that the psychological effect of playing a video game can be incredibly good for her, but you are helpless to do anything about it. All you can possibly do is put an expensive gaming controller on the list of "things we want to buy but can't afford," because many custom systems end up being $1,000 or more by the time you buy all the parts necessary. The feeling of helplessness can be overpowering.
Now imagine that someone showed you where you could spend only $50 and get easy-to-follow diagrams and code that could be simply copied and pasted to produce a fully functional, custom interface for your child. You can now help, despite not knowing what you were doing at all. This is the true feeling of being empowered: going from helpless to completely in charge of the problem.
The open-source community has a habit of sharing as much information as possible about a project. Often, they go further than just sharing the design files. They publish example projects as well. Not just examples, but fully documented examples in tutorial style using products that are readily available.
You could see all the images in the world and read all the descriptions possible about welding, but still feel unable to modify a van to carry a wheelchair. However, with a comparably tiny budget, you could easily plug wires into an Arduino and copy code to get an interface.
I realize that what we have isn't perfect. We expect people who use these tools to learn the basics of how a protoboard works, and we know that anyone can potentially run into issues if the code needs to be modified in some way. However, I've found in the short amount of time I've been doing this, that people are often happy to take those tiny steps.
I would love to see a system that was more modular and plug 'n' play, but that's where the costs start to increase. Developing a system specifically for custom computer interfaces in a modular fashion today would result in something approaching the cost of true custom devices. Right now, though, the open attitude of the community is getting us a good fraction of the way there.
If you would like to learn more, here are a few great places to look:
And here are my slides from the actual presentation: