Getting your open source company to contribution
-
Upload
asavin-wattanajantra -
Category
Technology
-
view
84 -
download
0
Transcript of Getting your open source company to contribution
![Page 1: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/1.jpg)
Of horses, water, and getting them to drink
Getting your open source company to contribution
![Page 2: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/2.jpg)
Chris Jansen Developer, Deeson
Developer 5+ yearsOpen source enthusiastDrupal (core) contributor
![Page 3: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/3.jpg)
Jeffrey ‘jam’ McGuireEvangelist, DevRel, Acquia@[email protected]/podcast
Open Source Evangelist, longstanding passion for Drupal project / communityAdvisor @openstrategypartners.com
![Page 4: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/4.jpg)
Outline. Introduction
Benefits of using open source
Why contribute?
Identifying roadblocks
Removing roadblocks
Now go contribute!
Recap
Q&A
![Page 5: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/5.jpg)
“Nobody made a greater mistake than he they who did nothing because he they could do only a little.”
Edmund Burke, 1729-1797
![Page 6: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/6.jpg)
![Page 7: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/7.jpg)
![Page 8: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/8.jpg)
• Office of the CTO (OCTO)• 10 full-time Drupal Core & ecosystem
contributors• Drupal 8 Module Acceleration Program
• $500K USD investing in module upgrades• Major sponsor of events, code sprints, &c.• Acquia Labs: “Drupal beyond the browser”• Drupal security team members, module
maintainers, community organizers … !
Contributes
![Page 9: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/9.jpg)
The developer’s perspective
So what’s the problem?
![Page 10: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/10.jpg)
Map the problem.
![Page 11: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/11.jpg)
Identify negative catalysts.
![Page 12: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/12.jpg)
Identify possible solutions.
![Page 13: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/13.jpg)
Benefits of using open source software
The businessperspective
![Page 14: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/14.jpg)
License fee of zero
Lower development costs
Faster time to market
Improved ROI
Reduced vendor lock-in
…
The obvious stuff.
![Page 15: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/15.jpg)
IT costsPersonnel
Hosting Infrastructure
BandwidthSLA Support
Design
Proprietary. Open Source.IT costsPersonnelHostingInfrastructureBandwidthSLA Support Design
![Page 16: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/16.jpg)
Features: Vendor roadmapFeatures: Vendor release cycle
Vendor lock-inBuy back your data
Proprietary. Open Source.Features: What you needFeatures: When you need itFeatures: Cutting edge1000s of vendorsYou own your data
![Page 17: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/17.jpg)
License feesOne time / Annual / Recurring €€€
Pay for permission to try
Proprietary. Open Source.License fees€ 0.00
Invest in features, training, staff …Cheap, (almost) risk-free POCsBuild better, not cheaper.
![Page 18: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/18.jpg)
Build better, not cheaper.
Budget == 100 Proprietary Open Source Reallocation
License fees 30 0 -30
Infrastructure, etc. 15 15 0
Strategy, Design, UX 25 35 +10
Features 20 30 +10
Implementation, QA 10 20 +10
![Page 19: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/19.jpg)
Contribute?Of course!
Seems obvious …
![Page 20: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/20.jpg)
Seems obvious…
Because we are optimists & idealists
“Because it’s the right thing to do!”
“Push community, that’s why you are here”
“We should give back was always our mentality”
“My future took a completely different turn based on the fact that we contributed to open source.”
![Page 21: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/21.jpg)
Identifying contribution roadblocks
![Page 22: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/22.jpg)
Strategic Roadblocks
Not knowing the why
1.
![Page 23: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/23.jpg)
Simon Sinek
TEDx 2009How Great Leaders Inspire Action
BookStart With Why
https://goo.gl/S8KNUx
![Page 24: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/24.jpg)
Identified roadblocks
1. Unclear mandate/policy (“The Why”)
2. Lack of knowledge (“The How”)
3. Doubts about own skills
4. Lack of time
5. Lack of procedure (“The What”)
Operational Roadblocks
Identified roadblocks
2.
![Page 25: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/25.jpg)
Real problems in a medium sized operation.
25+ employees
![Page 26: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/26.jpg)
Removing Strategic Contribution Roadblocks
![Page 27: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/27.jpg)
The boss talk.
community contribution doesn't happen without promotion in the community (sessions, blog posts, webinars, etc.)
Long term, systematic thinking, v "quick wins" ... I want to prioritise long term, profitable systems over short term, profitable billing codes.
![Page 28: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/28.jpg)
Management:
Discuss contribution
Get consensus
Define contribution policy/mandate
Developers:
When in doubt, ask for clear policy/mandate
Define / Change Policy
![Page 29: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/29.jpg)
Let’s unblock those developers!
That sounds convincing! !?
![Page 30: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/30.jpg)
Removing Operational Contribution Roadblocks
![Page 31: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/31.jpg)
Let’s solve this problem
![Page 32: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/32.jpg)
Increase proficiency trough training and guidance
1.
![Page 33: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/33.jpg)
So we’ve reduced the knowledge problem…
Now what?
2.
![Page 34: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/34.jpg)
Proficiency +mandate = Confident contribution
But … we’re not there yet
3.
![Page 35: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/35.jpg)
Integrating dev workflow with open source
![Page 36: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/36.jpg)
Development flow.
Analyse Develop
Peer reviewPublish
![Page 37: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/37.jpg)
Share your work.
Company OS Project
Share
Share
Analyse Develop
Peer reviewPublish
Analyse Develop
Peer reviewPublish
![Page 38: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/38.jpg)
Use the work of others.
Use
Share
Analyse Develop
Peer reviewPublish
Analyse Develop
Peer reviewPublish
Company OS Project
![Page 39: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/39.jpg)
Improve the work of others.
Company OS Project
Share
Share
Use
Analyse Develop
Peer reviewPublish
Analyse Develop
Peer reviewPublish
![Page 40: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/40.jpg)
Result:
Contribution is how you work.
4.
![Page 41: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/41.jpg)
So what do we contribute!?
So whatcan we do? !?
![Page 42: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/42.jpg)
There must be 50 ways …
![Page 43: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/43.jpg)
Code
Reviews
Documentation
Sponsorship
Organise
Design
Evangelise
And more!
7+
![Page 44: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/44.jpg)
Introduction
Benefits of using open source
Why contribute?
Identifying roadblocks
Removing roadblocks
Now go contribute!
Recap
Q&A
Recap.
![Page 45: Getting your open source company to contribution](https://reader031.fdocuments.us/reader031/viewer/2022030210/58a426b51a28abec1a8b6e01/html5/thumbnails/45.jpg)
Thank you!