Scaling Open Source Communitites

Slide 1

Slide 1 text

Scaling open source communities @KrauseFx

Slide 2

Slide 2 text

fastlane 12,000 commits 13,000 stars 590 contributors Top 25 most active projects https://fastlane.tools

Slide 3

Slide 3 text

4 Stages of open source projects Stage 1: Publish source code Stage 2: Developers starts using your project Stage 3: Go-to solution in its ﬁeld Stage 4: Hyper scale projects

Slide 4

Slide 4 text

Scaling open source projects is hard

Slide 5

Slide 5 text

Keeping the momentum

Slide 6

Slide 6 text

Handling support

Slide 7

Slide 7 text

Receiving feature requests GitHub issues Separate page Don’t accept new features

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

Reviewing external PRs

Slide 10

Slide 10 text

Maintainers stop being users

Slide 11

Slide 11 text

Information imbalance ⚖

Slide 12

Slide 12 text

How to scale open source projects The healthy way

Slide 13

Slide 13 text

Improve your error messages

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

Make it easy to ﬁnd existing issues

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

Use of bots Ensure available information Answers based on keywords Stale issues Lock resolved issues Respond to pull requests

Slide 22

Slide 22 text

Ensure all information is available

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

Answers based on keywords

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

Stale issues

Slide 28

Slide 28 text

Reasons for stale issues Went with a different solution Found workaround Switched company

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

Lock resolved, inactive issues

Slide 31

Slide 31 text

The lifecycle of a GitHub issue User submits issue fastlane-bot ensures issue is valid Actual issue discussion Issue get resolved or auto-closed

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

Respond to pull requests

Slide 34

Slide 34 text

Responding to pull requests danger http://danger.systems

Slide 35

Slide 35 text

Responding to pull requests PR and Run http://danger.systems

Slide 36

Slide 36 text

Steering the direction ⬆

Slide 37

Slide 37 text

Scaling contribution

Slide 38

Slide 38 text

Code of Conduct

Slide 39

Slide 39 text

Onboarding instructions

Slide 40

Slide 40 text

Keeping the code base simple

Slide 41

Slide 41 text

Be welcoming and friendly

Slide 42

Slide 42 text

Enabling users to extend the project

Slide 43

Slide 43 text

Domain Speciﬁc Language (DSL)

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

Local extensions

Slide 46

Slide 46 text

Plugins

Slide 47

Slide 47 text

Final words @KrauseFx

Slide 48

Slide 48 text

@KrauseFx