A Guide to Responsible Data Collection In Open Source
summary
Argues that open-source usage analytics are practical if done with expectation fit and clear governance, not banned; cites Scarf and its scarf JS post-install hook backlash as a cautionary example. Describes concrete collection methods: server access logs and hashed IPs, tracking pixels in docs, registry access logs, opt-in vs opt-out tradeoffs, and GDPR considerations. Claims opt-in defaults yield almost no telemetry, recommends salting/hashing IPs, temporary retention, encryption, and careful access controls before adopting analytics.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 2:25Why collect open source data
- 7:01Challenges of tracking users
- 9:11Handling personal data and PII
- 13:11Compliance and consent in analytics
- 16:22Ethics of data collection in open source
- 19:13Managing user expectations
- 22:06Methods for data collection
- 25:00Summary and key takeaways
related talks
32mA Guide to Responsible Data Collection In Open Source
35mRegulations, Ethics And Messy Data: Tales From An Open Source Analyst
23mThar Be Dragons - Ethical, Legal, and Policy Challenges when Measuring Open Source
29mThe Rising Ethical Storm in Open Source
35mThe Benefits and Pitfalls of OSS Project Metrics: Measuring Health and Risk in Open Source Communities
40mData Doesn't Lie: How to Influence Open Source Programming Through..
20mTowards open gov't through OSS for web analytics: the case of Matomo
22mThe Rising Storm of Ethics in Open Source