Reducing kernel-maintainer burnout

Problem 1.
Stop the fragmentation that has happen in the community and make it whole again, which provides single point of entry for *everyone* to partake in every aspect of the kernel development, which in turn will make it easier for anyone to join the community and start participating.

Problem 2.
Increase the ( likelihood of ) participation in the kernel community which in turn will reduce the load on existing contributors ( more contributors == less load on everyone ).

Bear in mind in exercises like these, the amount of energy is the same, it's just a matter where it's being spent, how efficiently and more importantly *who* is spending it.

With a self hosting approach like you propose with [Insert tool like Gitea] then you are putting all the cost,time and effort onto the Linux Foundation, which means you need to sell that idea to Finance,HR,Infrastructure at LF ( which arguably will be a hard sell ) on top of having to convince everyone to consolidate to LF.

In addition to that ( which relates to problem 2 ), you need to sell people the idea of having to sign-up to participate in the community which reduces the likelihood of participation and excludes drive by contribution.

With something like github all the energy is being spent by github, no additional load whatsoever on LF or any vendor related to the community and there is nothing to sell because people already exist there ( Github is the largest and the most *financially* stable of those ) .

Yes the downside is loss of control to certain aspect and *everyone* will have to adapt to new workflow but I would consider that a little price to pay for a survival of a community.