4 ms·
A "bug" is a very generous term for how severely punitive CC 1.x, 2.x and 3.x were. It was flatly bad and wrong and did exactly the opposite of what it was pro
by xbar 3y ago
A "bug" is a very generous term for how severely punitive CC 1.x, 2.x and 3.x were.
It was flatly bad and wrong and did exactly the opposite of what it was promised to do--permit rights holders to let users share their work and attribute it. It tricked people into a legal trap of minutiae and put users at risk.
It was broken for nearly two decades.
- lolc 3y agoYes "error" or "mistake" fits better than "bug". That's a general problem with the term though.
- dylan604 3y agoI originally thought bug was a strange term, but I could see how/why it might have been chosen. An error or mistake that results in incorrect/undesired/unforeseen results not caught by the compiler. s/compiler/(lawyer|judge)/
- prerok 3y agoI actually find "bug" to be the most apt name for it. Their intent was to enable a feature, therefore writing it this way was not an error: it, however, did not take into account all the side-effects. They did err on the side of caution, to protect the contributor, but when doing so, they did not take into account that it might be abused as well. Just my two cents.
- dylan604 3y agoAt what point do you differentiate a bug from a design flaw? This reads like different devs were provided conflicting requirements that had no discussion between devs. It wasn't until after the branches were merged that the problem existed as the unit tests from each dev worked as expected.
- ghaff 3y ago> minutiae This is sort of my general issue with Creative Commons. First, it's not just about attribution as the term would be understood in many other contexts. And then you have the Chinese menu of no-commercial and no-derivatives to encourage people who might otherwise hesitate to use CC to do so. But then those terms are ill-defined and people widely disagree on them.