How: Terms of POC usage

[myrmazz]

Thinking about how we can safeguard the core values and vision of the Public Office concept while at the same time making it accessible to others. Like some sort of terms of usage. We have also talked about the idea of manifestos, guidelines, rules or even contract, with inspiration from other concepts such as Tedx http://www.ted.com/pages/tedx_rules and pecha kucha http://www.pecha-kucha.org/terms-of-use.

[myrmazz]

Any more ideas @andersjacobson @jothelander @vectorsize ?

[vectorsize]

This is very important, I was discussing with Johan earlier today about how an open source initiative has to be useful to others, understandable, extensible and documented, it's not really about only letting others look into what you are doing. IN that regard, documenting, and designing/deciding where you want people to contribute and how they should do it is as important if not more as keeping the info open to anyone. I really like the tedx rules page, pecha-kucha looks more like an application form to me...

At the beginning of this I was also talking about design patterns in programing "In software engineering, a design pattern is a general reusable solution to a commonly occurring problem within a given context in software design"
http://en.wikipedia.org/wiki/Software_design_pattern

And found this people applying that concept to hackerspaces and how to organize your own hackerspace etc, closely related to what we are looking into
http://hackerspaces.org/wiki/Design_Patterns

They have a presentation on this too where they talk about how it all started and their motivations etc:
http://www.youtube.com/watch?v=8lywXCZogsg

[vectorsize]

Also realising all this is slightly connected to franchises
some links:
http://en.wikipedia.org/wiki/Social_franchising

[myrmazz]

Social franchising: http://www.socialfranchising.coop/

[andersjacobson]

http://www.wikihouse.cc/legal/terms

[andersjacobson]

http://www.lunchbeat.org/creator-guidelines/