Open source at the workplace - trivago

Small presentation (8m) about trivago Engineers contribute to OSS projects while managing a normal work schedule.

Transcript

1. Jorge Luis Betancourt Open Source at the workplace @jorgelbgm
2. Software Engineer at trivago Apache Nutch Committer & PMC / Member of @TheASF Passionate about Search (Solr/ES), metrics and performance
3. 55 PLATTFORMS ~5TB LOGS /DAY ~300ms RESPONSE TIME
4. & Open Source Software (some) tech.trivago.com
5. Photo by Michał Parzuchowski on Unsplash
7. https://medium.com/@biratkirat/step-8-the-boy-scout-rule-robert-c-martin-uncle-bob-9ac839778385
8. We are a tech company, not a software company
10. • Avoid forking a project unless it is really necessary. • Try not to make features too specific about what you want/need. • Communicate with the maintainers. Be polite. Contributing to an existing project
11. • Avoid dependencies on internal libraries/systems • Choose the right license. • Build (if possible) a community around the project. • If the project is big enough (i.e Kafka) think on a governance model, the Apache Software Foundation can help. Sharing a new project
12. Not all contributions have to be “complicated” … really!
14. https://tech.trivago.com/opensource/ http://github.com/trivago/ • logstash-codec-protobuf • Cluecumber-Report-Plugin • Cucable-Plugin • Gollum • Parallel-Webpack • nomad-pot-driver • hamara • boerewors • Melody • …