1. 60

  2. 30

    This post (or something expressing a similar message) should be required reading at some point in a person’s first engagements with open source projects. Not because it is infallibly correct, but because it communicates two much needed points:

    1. The perspective of a person responsible for a large scale, long-term project, and thus whose relationship with bugs (in large projects) is necessarily different from the average programmer’s.
    2. It points out how easy it is to leap to rhetorical extremes, despite minimal engagement with the other party, and that these leaps can be just as unhelpful in technical circles as they can be in political or cultural issues.

    Again, I’m not suggesting Ashton Kemerling is wrong, or that there is no impact to be made by pointing out issues in a blog post as he did. Just that hagus' added layer to the dialogue is not often expressed and is particularly well-written. I gave it a place in my messy, unsorted collection of quotes files.

    1. 2

      This comports with my own feelings on that previous post very well. I’ve had issues on the clojure(script) JIRA that were closed, sometimes with brusque comments, but I assume that the clojure maintainers are busy people that don’t have the time to provide a massive exegesis on why something is ‘wontfix’ everytime someone opens an issue. Assuming that everyone acts with the best of intentions is very good advice!