ApacheCon US 2007: Open Source Community Antipatterns

1

Open Source Community Antipatterns

Ted LeungOpen Source Applications Foundation

1

What’s a good community?

• Level playing field• Diverse/Sustainable

–Innovation happens elsewhere–Hit by a bus number

• That human sense of community

2

2

3

Categories

• Governance• Communication• Culture/Environment• Merit• Decision Making• Leadership• Balancing Forces

3

3

4

Governance

4

5

Wrongly Sized Governance

• Too little is bad• But too much is also bad

5

5

6

Fail to document clearly

• how the governance operates

7

6

7

Communications

7

8

Keep things private

• This is the root of all evil when it comes to building communities

10

8

9

Be restrictive about approved media

• It’s 2007... do you know what a blog is?

11

9

10

Culture

10

11

Don’t actively pass the culture on

• Fail to inculcate culture / way of doing things–leave it undocumented–Don’t actively mentor newcomers

• Say “how” but not “why”• The Starfish and the Spider:

–The unstoppable power of leaderless organizations– Ori Brafman and Rod. A Beckstrom

13

11

12

Rules not guidelines

• Insist on rules without principles• Prefer rules and not principled guidelines

14

12

13

Be privilege oriented

• The opposite is to be responsibility oriented• The bad result is that people seek privileges as

opposed to responsibility

15

13

14

Build a talk-o-cracy not a do-ocracy

• Doing is more important than talking• Talker-not-doer’s are a DOS against the

community

16

14

15

Make criteria arbitrary or vague

• for success, advancement, inclusion• capricious, secret or otherwise arbitrary

17

15

16

Keep it professional

• That’s a bunch of hooey• Talk like a human not a droid or lawyer

18

16

17

Environment

17

18

Make an environment unfriendly to

• Under-represented groups• Women• Non-Caucasion people• Non-English speakers

20

18

19

Don’t be respectful

• This should be an explicitly stated norm

21

19

20

Geographical Colocation

• is an antipattern

22

20

21

Merit

21

22

Believe that merit

• is absolute and absolutely measurable• can be defined along a single or small number

of dimensions

24

22

Don’t recognize Merit

• or do it slowly

23

23

24

Decision Making

24

25

Use lots of procedures

• Don’t explain how decisions get made• Have different decision making styles/

procedures for different contexts

25

26

Leadership

26

27

Ignore the need for leadership

• “I don’t think that word means what you think it means”

30

27

28

Try to “manage”

• Managing != leading

31

28

29

Balance Forces

29

30

Be Partisan

• Make sure that one or more parties obtain the majority of the benefit / benefit disproportionately

33

30

31

Other

31

32

Make community building someone’s job

36

32

33

Fail to apply open source tools to the governance itself

• Accountability for governance/foundation tasks

37

33

34

Centralize:Give people turf

• The Starfish and the Spider• The trouble starts when there are resources to

manage/allocate• Property rights (too much ownership)

38

34

Questions?

35

35