After reading the entire post, I feel really bad for him, and I hope he gets the time off and the support necessary to recover from this incident. I also feel quite angry with how he has been treated. So please let me vent it out here as politely as I’m able to.
I can imagine something like this or worse happening on social media groups, but an ostentatious “committee” that listens only to one side and never gives the other side the chance to get details on how things were perceived or why it’s a violation? And the chuckling in the call when someone has already said they’re not in a proper emotional state is just bullying.
I personally don’t think CoC or any other set of laws can be written to be precise and comprehensive. There will always be edge cases that need many hearings and re-hearings, with some discretion based on past precedence, nuances, etc., in the interpretation of written words in the code in an effort to make the code clearer for the future (this is how we improve laws, don’t we?).
This committee has, IMNSHO, been the opposite of kind and doesn’t deserve to hold the responsibility of handling CoC enforcement or violations. I’m sure this committee is not even capable of explaining clearly to a potential speaker what the CoC really means as per the written words and what’s expected.
This CoC needs to be torn apart and rebuilt, and the people in this particular committee must be sent to other areas where their expertise can be best used. Their proper place is certainly not in a CoC committee, for sure.
The 17 USC (2)(c)(1)(C) safe-harbour protections apply only to hosting of infringing works, and neither youtube-dl nor its test suites infringe on any RIAA or member copyrights as averred in RIAA's notice.
The RIAA's letter does not claim infringement within the text of youtube-dl source or test suites, though it tries hard to appear so, but rather anti-circumvention of a "copyright protection mechanism", under §1201. That is also part of the DMCA, but falls outside the safe-harbour.
At best, youtube-dl's test suite may be infringing works when run, in which case infringement would accrue to the operator, presumably a tester or Github's CI/CD process. Even that argument is specious.
Given output is discarded, no permanent copy is retained, and the action is for research and development, and numerous Fair Use affirmative defence claims exist under §107, notably (1) and (4), test suite execution falls outside exclusive rights. Any one fair-use test is sufficient, or none at all. Test suite execution could be argued non-infinging under numerous theories, including reverse engineering, research, interoperability, all under §1201, or under general limitations on exclusive rights in §112, §117, or elsewhere.
Please add `return false` or `event.preventDefault()` to your keyboard handlers!
Otherwise the browser assumes the page didn't do anything with the events and uses its default keyboard handlers. I have find-as-you-type enabled, and pressing keys launches search for me. Handlers need to "eat" the keyboard events to prevent default browser behavior.
I like Graham's points about overconfidence, peer groups and (judicious amounts of) ignorance, all of which he champions quite strongly. But drilling deeper on "rate of change" is an undervalued element that deserves a closer look.
The best innovators are really good at taking Version 1.0 and figuring out what rework will turn it into a better 2.0, and then 2.1, 2.2, 3.0, etc. This is an identifiable skill! It can be cultivated. Once you've got it, the failings of Version 1.0 do not ruin your self-esteem. You just get to work on fixing them. And not enough people think about this systematically.
One of my favorite museum stops of all time was the British Library, where a glass case held Paul McCartney's first draft of "Yesterday." You could see, cross-out by cross-out, how a somewhat awkward ballad got turned into a pop classic.
I like Graham's points about overconfidence, peer groups and (judicious amounts of) ignorance, all of which he champions quite strongly. But drilling deeper on "rate of change" is an undervalued element that deserves a closer look.
The best innovators are really good at taking Version 1.0 and figuring out what rework will turn it into a better 2.0, and then 2.1, 2.2, 3.0, etc. This is an identifiable skill! It can be cultivated. Once you've got it, the failings of Version 1.0 do not ruin your self-esteem. You just get to work on fixing them. And not enough people think about this systematically.
One of my favorite museum stops of all time was the British Library, where a glass case held Paul McCartney's first draft of "Yesterday." You could see, cross-out by cross-out, how a somewhat awkward ballad got turned into a pop classic.
I like Graham's points about overconfidence, peer groups and (judicious amounts of) ignorance, all of which he champions quite strongly. But drilling deeper on "rate of change" is an undervalued element that deserves a closer look.
The best innovators are really good at taking Version 1.0 and figuring out what rework will turn it into a better 2.0, and then 2.1, 2.2, 3.0, etc. This is an identifiable skill! It can be cultivated. Once you've got it, the failings of Version 1.0 do not ruin your self-esteem. You just get to work on fixing them. And not enough people think about this systematically.
One of my favorite museum stops of all time was the British Library, where a glass case held Paul McCartney's first draft of "Yesterday." You could see, cross-out by cross-out, how a somewhat awkward ballad got turned into a pop classic.
I personally don’t think CoC or any other set of laws can be written to be precise and comprehensive. There will always be edge cases that need many hearings and re-hearings, with some discretion based on past precedence, nuances, etc., in the interpretation of written words in the code in an effort to make the code clearer for the future (this is how we improve laws, don’t we?).
This committee has, IMNSHO, been the opposite of kind and doesn’t deserve to hold the responsibility of handling CoC enforcement or violations. I’m sure this committee is not even capable of explaining clearly to a potential speaker what the CoC really means as per the written words and what’s expected.
This CoC needs to be torn apart and rebuilt, and the people in this particular committee must be sent to other areas where their expertise can be best used. Their proper place is certainly not in a CoC committee, for sure.