Hacker News new | past | comments | ask | show | jobs | submit login

This is the best appeal for OSS I’ve seen in a while.

Actively telling a project how to improve vs passively observing how the system is used in the aggregate: that is a choice each person should be offered to engage with the project, along with the right to lurk in peace or fix their problems their own ways.

The data itself ought to be public, and if it can’t be then it shouldn’t be gathered. The insights from that data should come from the community, not just project leads. That data’s relevance to product development and design should be annotated on feature tickets.

I am good with having a relationship with a project that involves sharing my behaviors within the system, others are not. As a user I do I want to be able to see if I’m way off the beaten path or using a popular method when I’m deciding if I should debug, research, or work around a problem. As a maintainer team, your time is precious and the BS is already thick, so I feel providing that visibility is the least I can do to contribute to your work.

I feel very differently about this with respect to for-profits and my PII tied to behavioral records.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: