Starting an Open Source Project is way more than sharing the code you produced. It is very much about human interaction, achieving high quality on a zero budget, having to do things you don’t have the expertise for, being allowed to do things you don’t have the expertise for, pride, hate, friendships, big visions, hopelessness. You catch yourself thinking: Is this Open Source thing really worth it? And push away the thought, because there are pull requests to review.

1. Is
This Open
Source Thing
Really Worth it?

2. Why the heck
would you start
an Open Source
Project?

3. What does it
take to run an
Open Source
Project?

5. ✔

6. Robert Lemke
CEO Flownative
Project Founder Neos
robert@flownative.com
@robertlemke

16. Quality

23. Contribution

25. Vision

26. what's your vision for
the product?

27. what's your vision for
the project?

28. Culture

29. identity,
mission,
brand.

32. how do you want to
collaborate?

35. Communication

36. Communication
inside <

37. How do you keep
everyone updated
and foster
participation?

38. Communication
outside >

42. Support

44. Documentation

45. Infrastructure

46. Collaboration &
Partnerships

47. Conferences, Sprints,
Meetups

50. Finances

51. Business
Models
Open Core Model
Crippleware
Delayed Open Sourcing
Consulting
Development
SaaS
SLAs
…

54. Legal

56. The founder’s role?

57. don't give away
control too early

58. don't be afraid of
giving away control

59. Is it worth it?

61. robert@flownative.com
www.flownative.com
@robertlemke
share your
thoughts