5 ms·
Pertinent follow-up. Jake was naive about open source norms. See twitter conversations: https://twitter.com/jonathanwallace/status/533680518009614336 https://t
by jonathanwallace 12y ago
Pertinent follow-up. Jake was naive about open source norms.
See twitter conversations:
https://twitter.com/jonathanwallace/status/533680518009614336 https://twitter.com/jonathanwallace/status/53368051800961433...
https://twitter.com/jonathanwallace/status/533679332590628864 https://twitter.com/jonathanwallace/status/53367933259062886...
- dmpk2k 12y agoMaybe naive, but also impolite. Opening an issue with a passive-aggressive tone isn't likely to be productive.
- aaronem 12y agoThat's really the problem here. Ignorance is excusable, especially in someone who hasn't got a lot of experience yet. Rude ignorance is never so, especially around a library on Github where, if it's really that big a damn deal to you, you can always just fork, edit a big "THIS IS NOT APPLE COLOR EMOJI" note into the readme, open a PR, and see what happens.
- 332451b 12y agoI think this misses the point, if someone doesn't understand open source etiquette then I would give them a friendly reply. Even if it was mentioned somewhere in the documentation, I understand that people can miss it. It's just that if someone speaks to me in that tone, regardless if this is an open source project or if I'm working customer service for a product, I'll still think they're acting like an ass. It's not a huge deal, people act like asses all the time, but why not just raise the issue in a friendly manner?