GOSH Community Forum

Day 2: Scaling OSH projects

Scaling concept— everyone has a different meaning, culture creating, community building.
How do we create a campaign and a movement?

Scaling- getting other people attracting or engaging in a project, building/using, contributing knowledge/resources, getting to start having impact. Interested, but not ready to build— there’s a gulf between future end user and the team it takes to get it there. D

Balancing values and the ability to sustain work by motivating the community/commons

How can societies at large value the work of OS innovation. How can things be systemized so that work that benefits the community be supported? SRAP— put put $$ and hours and get a tax benefit (in Canada). Articulation— gears in gears: how to actirculation value proposition so that anyone can see the value of it (not just about you!+)

Scaling up— loaded, narrow term (as it’s implied), vs Scaling out— sees room for everyone to find success according to definitions.

Bridging between stakeholders— how to make these.

Things that resonate: not about you! But it starts with you. Crux— how to make that transition. Valuing yourself while offering.

Creating a collective and a hub of a team.

Theoretical concept— polycentric governance (say, like the unconference model) How to build in the idea into something more like policy? Common sense to push back at indoctrination about things like shareholder value as a goal

How to bring in the commercial?

Finds that there’s not this kind of conversation in business forums (hope things have evolved since business school). Things have to start early— sustainability as a concept in community value, so that stakeholders are shifting to share values.

Social entrepreneurship?

Creating examples to show people how things can be successful. Anyone can take things up and be innovators! Data and accounting!

There is a place for specialization in open projects, a component where it makes sense to centralize production because of the material it uses, etc (not common or accessible enough for everyone to do every part). Where do we (for practical reasons) some parts of the process?

In 14 minutes— something real- a kind of a project where scaling would work (or need to work)

Ideas: community gardens (hard to sell because of regulations). This is where data comes in— data can be generated as a tangible output to act shows how a product. Tracking? Exclusive ownership / sold at a premium?

Can cooperative business models be a good fit for the kind of work we’re trying to do?

Are there open hardware projects that have been successful!

Lending libraries

Sliding scales for price setting

In counseling we have a system where people who have been though a process are available to people who are going though it for the first time— mentorship

Communication between projects.

3D printer— stick lab and AB3D started building and selling. There were quality control issues, so what they were building wasn’t going to grow into a big community, but in some sense it served to launch people/lab into new spaces.


Report backs

Most of the discussion grounded in practice and challenges— how do you get users to give back and help grow/improve instead of just taking.

Challenge- how do you balance growing customers with evolving needs for customer service? How can users give feedback, or help them to know from the beginning what a thing does and doesn’t do (and if you want more features, how to help collaborate).

How to get investors to give to a OS company.

How to get people to stay involved (safest was big after the disaster, but less participation as time goes by)

Concerned about support for projects— transition from partners to users.

Look at open source issue of “increment.com

How to balance management skills with hardware skills.

From the corporate side of things— selling a vision that makes people want to help you.

Still questioning about how to make bridges. If outreach was the size of people around the table it might be more helpful.

Scaling with hardware isn’t easy! Easier to scale software than hardware.