Linus himself has said that his kernel tree is focused on too much, and unfortunately I agree that the discussions on LKML can be harsh.
There was a group of people that spoke with Linus in person in the hallway after his talk at DebConf14. He said that being harsh doesn't seem to help stop bad code from coming in -- that it seems to happen anyway. So if being harsh doesn't seem to be helping, and it's clearly hurting, this seems to be more from "force of habit" than for tangible benefit, and there needs to be a more clear "feedback mechanism" showing that there are consequences to continuing bad behavior.
I think that's the spirit behind this fork, and if so it seems like a good idea.
Power management, mobile and firmware developer on Linux. Security developer at Aurora. Ex-biologist. mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer. Also on Mastodon.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
There was a need to try this
Date: 2015-10-07 06:02 am (UTC)There was a group of people that spoke with Linus in person in the hallway after his talk at DebConf14. He said that being harsh doesn't seem to help stop bad code from coming in -- that it seems to happen anyway. So if being harsh doesn't seem to be helping, and it's clearly hurting, this seems to be more from "force of habit" than for tangible benefit, and there needs to be a more clear "feedback mechanism" showing that there are consequences to continuing bad behavior.
I think that's the spirit behind this fork, and if so it seems like a good idea.