having some thoughts on the mailing list workflow....
i find that almost every time i email a patch there's some stupid simple issue with it that has to be addressed with a new revision...
my attention to detail when it comes to patches is really bad, for sure a part of it is lack of experience, but I'd be remiss (haha) to pretend that ADHD doesn't play a part. I really struggle with the whole checklist thing, making sure i do everything i need to before sending.
When contributing via a git forge, versioned patchsets are replaced by a source and target branch, and a log of force-push history. This means that when I spot these stupid mistakes I can just fix them. It drastically lowers the barrier of entry for me and reduces the impact both on me (not having to be super self aware of my stupid mistakes) and maintainers/reviewers (not having to point out stupid mistakes that i already noticed myself immediately after sending).
idk, im sure this is something that improves over time. I just wonder if there's any merit to this being a repelling force for folks who would otherwise really enjoy working on projects like the kernel....
@cas Yeah, I think that's my only gripe with (technical part of) the process. I do have to be in a certain state of mind to be able to complete the submission process. I still have some patches that have been waiting for me to follow up on for many many months. Thankfully tools like b4 help a lot and it's not like web forges completely solve it either, so I wouldn't overstate its influence, but it does contribute to the struggle at least a bit.
