Download as PDF, PPTX
Uploaded byMichael Boelen
Getting Traction for (your) Open Source Projects
The document discusses strategies for gaining traction for open source projects, emphasizing the importance of promotion and community engagement for both developers and non-developers. It outlines various traction channels such as social media, SEO, and public relations, and gives best practices for project documentation and versioning. Key takeaways include the need for simplicity, quality, and effective marketing to ensure the project's growth and visibility.
More Related Content
Similar to Getting Traction for (your) Open Source Projects
Getting Traction for (your) Open Source Projects
- 1. Traction Getting Traction for(your) Open Source Projects Michael Boelen michael.boelen@cisofy.com T-DOSE 2016, 12 November (NLLGG track)
- 2. Why? (developers) Promote youropen source project ● Users ● Feedback ● Invisible benefits 2
- 3. Why? (non-developers) Use yourknowledge ● Contribute ● Improve software you use ● Enhance your resume 3
- 4. Michael Boelen ● OpenSource ○ Lynis, Rootkit Hunter ● Business ○ Founder of CISOfy ● Other ○ Blogger at Linux-Audit.com ○ Board member and program committee NLUUG 4
- 5. Traction? Something that is“going” and grows (quickly) Example: my open source project, that continuously gains in popularity, and becomes well-known. 5
- 6. ● Trade shows ●Affiliate programs ● Offline advertising ● Search Engine Marketing ● Social advertisements ● Viral marketing ● Business development ● Public relations 6 Traction Channels ● Search Engine Optimization ● Content management ● Demo’s ● Community building ● Speaking engagements ● Reaching out to blogs ● Social sharing ● Email marketing
- 7. Is that reallyneeded for FOSS?
- 8. Importance of Traction Softwareis written to be used 8
- 9. Translating to OpenSource Components ● Quality of software ● Promotion ● Community 9
- 10.
- 11. Experiment Great tip: …………………... by@mboelen at @TDOSE (@nllgg track) 11
- 12.
- 13. ● Remember (orforget…) ● Length ● Goal Name 13
- 14.
- 15.
- 16. Change Log ● History ●Trust ● Troubleshooting 16 Learn more: keepachangelog.com
- 17. Documentation ● README.md ● GetStarted ● Other documentation 17
- 18.
- 19. Best Practices forCLI --full-throttle-engine, -f --help, -h, or help --version, -V 19 Learn more: doctopt.org
- 20. Best Practices forCLI ● Share progress ● Dots 20
- 21. Best Practices forCLI ● Use exit codes ● Data output ● Integrations 21
- 22. Updates ● Newer isbetter? ● Perform update check ● Make it easy 22
- 23. Releases ● Release often ●Who picks it up? ● RSS Trick https://github.com/CISOfy/lynis/releases.atom 23
- 24. Packages Good ● Promotion ● Easyof use 24 Bad ● Needs maintainer ● The “stable” bug
- 25. OpenHub 25 See more details:OpenHub
- 26. Takeaways ● Structure ● Simplicity ●Quality 26
- 27.
- 28.
- 29.
- 30.
- 31. Social Media ● Interact ●Share at the right time ● Challenge 31
- 32. Takeaways ● Know goodsources ● Share and promote ● Monitor activity 32
- 33.
- 34. High traffic websites ●Hacker News ● Reddit ● Slashdot ● TechRepublic 34
- 35. Quality traffic (forsecurity) ● Packet Storm Security ● ToolsWatch 35
- 36.
- 37. HN Effect Traffic 2016-11-04: 4478 2016-11-05:1656 2016-11-06: 1201 37
- 38. HN Effect Stars 2016-11-02: 1110 2016-11-04:1200 2016-11-05: 1770 2016-11-06: 2130 2016-11-07: 2340 2016-11-08: 2670 Source: http://www.timqian.com/star-history/#CISOfy/lynis 38
- 39.
- 40.
- 41. The “sticky” effect Thereis more behind the peak 41
- 42. Jackpot Multipliers ● Ask ●Networking ● Persistance 42
- 43.
- 44. 1 - Bea Marketeer Promotion is needed 44
- 45. 2 - Humbleversus Pride Balance 45
- 46. 3 - Quality Ittakes time: ● Get the basics right ● Focus on simplicity ● Understand your users 46
- 47. More? Articles on linux-audit.com ●Why we use your open source project (or not) ● How to Promote your Open Source Project Share this presentation! ;-) 47
- 48. Questions? Connect ● Twitter (@mboelen) ●LinkedIn (Michael Boelen) 48