See https://creativecommons.org/licenses/by/4.0/
> You are free to:
> Share — copy and redistribute the material in any medium or format
> Adapt — remix, transform, and build upon the material for any purpose, even commercially.
If that isn't the world you want to live in, let's get rid of this idea that just because I have no interest in the government stopping you from doing a thing by threatening violence (and that's all a license is - a statement that the following activities are not copyright infringement), I'm totally fine with you doing the thing.
And in the quoted statement they are not saying the W3C should improve their process for forking WHATWG's work. They are saying the W3C shouldn't fork their work at all. So despite their specifically chosen license (with easy to understand layman's summary) are WHATWG against all forking? Or are they simply against the W3C?
"In the case of the WHATWG specifications, the licenses allow broad re-use, so that implementors can copy-and-paste text into their comment blocks, so that tutorial writers can copy-and-paste text into their documentation, so that experiments we haven't considered can spring up without inhibition, and so that, if the WHATWG stops being a good steward (like the W3C stopped being a good steward in the early 2000s), the next group of spec editors doesn't have to start from scratch." (http://lists.w3.org/Archives/Public/www-archive/2014Apr/0034...)
There is a typo in the third paragraph, first sentence, FYI. "Are not" is repeated.
For example, there are derivative specifications ("forks") that are not are not prominently identified as copies of WHATWG standardsAnd Hixie/the WHATWG: "It is critically important (not just here but in life at large) to understand the difference between something being _a right_, and something being _right_." (http://lists.w3.org/Archives/Public/www-archive/2014Apr/0034...)
Whether someone should be permitted to do something is a different issue than whether they should actually do it.