Scaling Open Source Communities trySwift Tokyo

trySwift Tokyo https://www.tryswift.co/tokyo/en

More information about the topic on my blog: https://krausefx.com/blog/scaling-open-source-communities

Transcript

1. Scaling open source communities @KrauseFx
2. fastlane 12,000 commits 13,000 stars 590 contributors Top 25 most active projects https://fastlane.tools
3. 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 field Stage 4: Hyper scale projects
4. Scaling open source projects is hard
5. Keeping the momentum
6. Handling support
7. Receiving feature requests GitHub issues Separate page Don’t accept new features
9. Reviewing external PRs
10. Maintainers stop being users
11. Information imbalance ⚖
12. How to scale open source projects The healthy way
13. Improve your error messages
19. Make it easy to find existing issues
21. Use of bots Ensure available information Answers based on keywords Stale issues Lock resolved issues Respond to pull requests
22. Ensure all information is available
25. Answers based on keywords
27. Stale issues
28. Reasons for stale issues Went with a different solution Found workaround Switched company
30. Lock resolved, inactive issues
31. The lifecycle of a GitHub issue User submits issue fastlane-bot ensures issue is valid Actual issue discussion Issue get resolved or auto-closed
33. Respond to pull requests
34. Responding to pull requests danger http://danger.systems
35. Responding to pull requests PR and Run http://danger.systems
36. Steering the direction ⬆
37. Scaling contribution
38. Code of Conduct
39. Onboarding instructions
40. Keeping the code base simple
41. Be welcoming and friendly
42. Enabling users to extend the project
43. Domain Specific Language (DSL)
45. Local extensions
46. Plugins
47. Final words @KrauseFx
48. @KrauseFx