Social Architecture: Building Online Communities by Pieter Hintjens

  1. Preface – The Wisdom of Crowds
  2. Chapter 1. The Toolbox
  3. Chapter 2. Sidebars
  4. Chapter 3. The ZeroMQ Community
  5. Chapter 4. The ZeroMQ Process: C4
  6. Chapter 5. Designing for Innovation

https://hintjens.gitbooks.io/social-architecture

Preface – The Wisdom of Crowds

Chapter 1. The Toolbox

The 20 tools:

What do do:

Chapter 2. Sidebars

Another topics worth discussing.

Market Curve

How different types of people join your project at different periods of time. This is not hard science, and can overlap, but usually happens like this:

Volunteer Burnout

Volunteer work is amazing, but it can lead to burnout of not well managed. It manifests in the community a per project basis, when someone suddenly perceives the project as toxic and leaves. It takes some time to get there, but it’s curable and preventable.

People usually invest their time – thus, their economy – in projects because somehow they feel it’s gonna be good for then, it will propel them somewhere or it’s an investment that will pay off at some point in time. These people will burn out if they think that all the effort they’ve put into the project was a wast of time, that the mission statement is a lie, the praise was fake etc etc. People will quit.

You can avoid this by not letting people work alone in the product, having a business plan (roadmap, process), preventative education in burnout and good tools and processes that let people work if less dependency of any one other person.

The Myth of Individual Intelligence

Less experts group of people are way more intelligent than a group of experts. The Internet being a good example as a project created by lots and lots of smart people, through RFCs that anyone could improve and open source software that anyone could remix.

How to Capture an Open Source Project

A section about the possibility of Google capturing Android into a closed source software. Basically, you release an open source project into a market with a lot of unsatisfied users, let them use, improve and become dependent on it. When the software/product is established, you slowly “Capture the Flag” by closing the product little by little.

Needless to say, that’s awful shit. Decision made out of self interest and low sense of ethics.

We can avoid these by using a “share-alike” license and have a contribution policy (who owns the contributions made to the project?).

Licenses:

Contribution policy: Who owns the project? Can it be bought? Do I need agreement through the whole contributors to be able to sell it?

Wanna be cool? Go with share-alike and distributed copyright.

Trademarks

A whole thing about trademarks. Not much to take notes on. Buy it if you really need kinda stuff 🤷‍♀️

Chapter 3. The ZeroMQ Community

Psychology of Software Architecture

The Importance of Contracts

The Process

Care and Feeding

Chapter 4. The ZeroMQ Process: C4

Chapter 5. Designing for Innovation

Trash-Oriented Design (TOD)

Complexity-Oriented Design (COD)

Simplicity Oriented Design (SOD) – a hill climbing algorithm

Burnout: too much investment in a project with too little economic rewards for too long

Chapter 6. Living Systems

See book.