Goal: be able to have hackerspaces and events that are welcoming places where people are able to get things done as well as exchange knowledge and collaborate.
for example, the mission of Pumping Station: One is to foster a collaborative environment wherein people can explore and create intersections between technology, science, art, and culture. How can I personally help make sure this mission never becomes impossible in a community I am a member of?
I want to observe the success and failure modes of communities. What are the right search terms for this?
keywords
- communities of practice
- ???
Actions to cultivate a successful community of practice a wikipedia ref to follow
Management of a community of practice often faces many barriers that inhibit individuals from engaging in knowledge exchange. Some of the reasons for these barriers are egos and personal attacks, large overwhelming COP's, and time constraints (Wasko & Faraj 2000)
Rights and Obligations of Hackerspace Members, a Noisebridge post. good example?
The spirit of excellence from Noisebridge not only covers how members must treat each other, it extends to how members should treat the community outside their membership, those that benefit from having a space nearby. This obligation is not a static one, as new members are almost always casual users first. There are also many casual users that spend a lot of time in hackerspaces, perhaps making more significant contributions than regular members, but decline to officially join for many different reasons.
Without these casual users, hackerspaces run the risk of disappearing like the L0pht and New Hack City did. Being welcoming to the outside world helps ensure our collective success and sustainability, helps show the world what hacking is all about and helps feed and cultivate projects and activities going on locally and globally. It leads to more hackerspaces and more resources for existing hackerspaces. It’s the kind of thing we should keep in mind when we build and maintain our spaces, that we’re not just in it for ourselves, we’re in it for our neighbors and our world.
- conflict resolution (but not harassment resolution patterns). http://hackerspaces.org/wiki/Design_Patterns
- group intelligence essay http://edge.org/conversation/collective-intelligence (he mentions that they've cataloged many design patterns or "genes" based on observations of groups. Harnessing Crowds: Mapping the Genome of Collective Intelligence
- How Open Source Projects Survive Poisonous People (And You Can Too)
- FreeGeekChicago has a very nice and concise code of conduct which also has an excellent point to focus people on the conduct with respect to the mission of their space
- Hacker School day one! I like how it is focused on telling people not to be disingenuous. instead do things so that people can learn and get things done. very kick-ass. No "but actually".
- Gabriella Coleman http://gabriellacoleman.org/?page_id=6 Coding Freedom: The Ethics and Aesthetics of Hacking
more random links
geek social fallacies http://www.plausiblydeniable.com/opinion/gsf.html
http://dashes.com/anil/2011/07/if-your-websites-full-of-assholes-its-your-fault.html
I like the openhatch irc coc https://openhatch.org/wiki/IRC_code_of_conduct
in particular it makes explicit things that have been tacit for me in what "feels comfortable" to me about how I want people to behave in an openhatch context. that explicit description gives me insight.