"Open source projects succeed when a broad group of contributors recognize the same need and agree on how to meet it. Linux gave programmers a way to build a better, leaner operating system; Woochi gives wine lovers an encyclopedia as refined as they are.
SHARE THE WORK Projects can be broken down into smaller tasks and distributed among armies of volunteers for execution. Tim O�Reilly, whose namesake company runs the Open Source Convention, calls this the �architecture of participation,� and it is the irresistible genius of open source, a tool that no corporate model can match for the sheer brainpower it yokes. But architecture demands structure: a review process that screens for the best contributions and avoids the �fork� � that horrible prospect that a project will split into a multitude of side projects.
SHARE THE RESULT Open source etiquette mandates that the code be available for anyone to tweak and that improvements to the code be shared with all. Substitute creation for code and the same goes outside of software. Think of it as the triumph of participation by the many over ownership by the few. � T.G."
Very sexy.
ReplyDeleteLooking at other online collaborative organizations. These two came up:
http://www.designthatmatters.org/
http://www.thinkcycle.org
taking a peek...?
"Open source projects succeed when a broad group of contributors recognize the same need and agree on how to meet it. Linux gave programmers a way to build a better, leaner operating system; Woochi gives wine lovers an encyclopedia as refined as they are.
ReplyDeleteSHARE THE WORK
Projects can be broken down into smaller tasks and distributed among armies of volunteers for execution. Tim O�Reilly, whose namesake company runs the Open Source Convention, calls this the �architecture of participation,� and it is the irresistible genius of open source, a tool that no corporate model can match for the sheer brainpower it yokes. But architecture demands structure: a review process that screens for the best contributions and avoids the �fork� � that horrible prospect that a project will split into a multitude of side projects.
SHARE THE RESULT
Open source etiquette mandates that the code be available for anyone to tweak and that improvements to the code be shared with all. Substitute creation for code and the same goes outside of software. Think of it as the triumph of participation by the many over ownership by the few. � T.G."
So excited that this is being vocalized.
Open source hardware bank
ReplyDelete(hackers funding their arduino-building habits)
They seem to be set up like us: a blog, a wiki, and a crazy idea.
The article:
http://blog.wired.com/gadgets/2009/03/open-source-har.html
The blog:
http://antipastohw.blogspot.com/
Very intelligent comments on how to work within the existing financial/legal system while reforming it.
The OSHB explained as chemical reactions:
ReplyDeletehttp://antipastohw.blogspot.com/2009/03/open-source-hardware-economy-as-set-of.html
Now I want to take organic chemistry. So I can understand this metaphor better, and so I can use the metaphor in the future.
I like them- let's drop a line and build a relationship. Having some crazy idea techhies would be really nice.
ReplyDelete