Myths & The Real World of OpenSource Development

@ Codemotion ES 2014, Madrid

Transcript

1. @Kartones Myths & The Real World™ of Opensource Development
2. @Kartones CartoDB
3. @Kartones CartoDB
4. @Kartones OSS is …
5. @Kartones OSS is …
6. @Kartones OSS is … • Projects “born” open • Improving existing projects • Funding features for projects • Private projects that become open
7. @Kartones Basic Workflow • DIY – Fork – Clone -> Branch -> Pull Request • Ask for it – Maybe is on the roadmap… – Maybe can be added… • But a request is not a mandate
8. @Kartones Is CartoDB opensource? • Github.com/CartoDB • Around 95% of the code is opensource – Minus: • Account provisioning • Billing • Systems & deploy scripts • Internal wikis & docs.
9. @Kartones Is CartoDB opensource? • Mostly based on OSS stack – Ruby – PostgreSQL + PostGIS – GDAL – Node.JS – Redis – Monit – Ganglia – Graphite + Graphana – Chef – ElasticSearch + Kibana – Nginx – Varnish
10. @Kartones Tools • Dogfooding – Geocoding • Internal geocoders data • Geocoding cache – Basemaps – Common Data – Metrics
11. @Kartones Tools • Issues/Ticketing – GitHub & GitHub issues (free + paid) – In the past JIRA (paid)
12. @Kartones Tools • CI – ClinkerHQ (paid) – In the past • Travis-CI (free + paid) • Local Jenkins (free)
13. @Kartones Tools • IDEs – Vim (free) – Emacs (free) – Sublime Text (free + paid) – RubyMine/IntelliJ/Jetbrains-product-X (paid)
14. @Kartones Tools • You usually need to pay for: – Hosting – CDN – Mailing – Billing system
15. @Kartones OSS Requires Time & Effort • Developing – Code reviews – Backwards compatibility – Extra documentation for devs – Sample configuration – Whatever you publish, you should maintain
16. @Kartones OSS Requires Time & Effort • Coding conventions – Structure, naming … -> Coding standard – Source folders structure – Search for ideas but adapt to your needs
17. @Kartones OSS Requires Time & Effort • Testing conventions – HOW-TOs – Avoiding more complexity due to test env. – Testeable code – Balancing testeability vs craftmanship madness
18. @Kartones OSS Requires Time & Effort • Versioning conventions – Basically, follow semver.org (x.y.z) – Break rules if makes sense • Some OSS projects are not good guides
19. @Kartones OSS Requires Time & Effort • Documentation conventions – README – NEWS – UPGRADE – TESTING – CONTRIBUTING – LICENSE • + Web-based doc, examples, API doc…
20. @Kartones It has nice bonuses • Source code = no secrets • Recruitment & Ambassadors • Community & public exposure • Some segments prefer opensource
21. @Kartones But there are no unicorns • OSS doesn’t means: – Faster – Bug-free – Easier – Well documented
22. @Kartones We’re far away from perfection • Transparent ticketing is recent • Community is slim (many stars, few PRs) • Documentation not yet finished • PR require approval of employees • Product decisions not democratized • Public channels not (yet) taken enough care of • We don’t contribute back enough
23. @Kartones But we’re on a good path • We fund some GDAL changes • We report bugfixes on OSS, and fix a few ones • We sell online services, not licenses (SaaS) • We go fast: Continuous delivery (daily releases) • Community before sales • Investors don’t care as long as we’re successful
24. @Kartones Questions? Thanks! kartones@cartodb.com