Once I have people I can trust to collect patches into trees I can just merge large subtrees of changes like linus does it. Its very scalable. People just need to learn how to do proper git commits that are logically distinct and can be cherry picked incrementally and independently. Developers don’t have this skill anymore because github doesn’t force you to think about it.

Once people learn how to do this I would feel more comfortable letting maintainers collect many changes into their own forks that I merge all at once. I kind of do this already with #[2]​‘s translation PR but I still find myself formatting the branch and removing duplicate commits, etc.

It would save me a lot of time if contributors learned git and used it effectively so I don’t have to spend all day formatting patches, rebasing, squash merging, and fixing conflicts.