OSH Repository Discussion and Planning/Licensing

From Gosh! 2009: Open Source Hardware Summit

repository discussion - round two

how do you apply to the open hardware bank? how to get economies of scale for cost saving?

is the repository just for information? Jon: one of the types of information is where you can get stuff

how does a community signal what should be scaled? what should be built?

are complicated issues of money and marketing beyond the realm of the repository?

the site will cost money to develop - where will the funding come from?

what are the principles of who is on the board and how it is run?

instructables is going to a pro version - gives access to more and they charge for it. (http://www.instructables.com/community/Instructables-Pro-Accounts-Have-Launched/)

people from EU have difficulty getting parts - could the repository be global if one of its principal features was an API for BOM with hardware suppliers?

SparkFun http://www.sparkfun.com/commerce/categories.php "We design boards and provide tools so that engineers, students, and hobbyists can play with microcontrollers."

Gisle: repository should be on an academic level

is it possible to share information about selling in a good way?

Jon: open manufacturing initiative - aggregate orders for negotiation power with manufacturers

what are the collaborative possibilities of the repository? -which projects are active

repository needs to focus on linking from other open hardware sites

pixel.no will host

functionality of software management system and user interface of fritzing

what repositories are out there? what can be built from them? what value added that other ones don't do?

could we include information related to who is in the community, what they could do in terms of events/workshops, what they want to do...etc...

gisle: "licensing: the whole point is to be able to give back" -how should different parts of the documentation be licensed?

licensing recommendation: workshop with lawyer