From an administrative stance, I’m sure any project would happily consider a patch if you emailed it to them. For local work, you can easily dump a codebase in

From an administrative stance, I’m sure any project would happily consider a patch if you emailed it to them. For local work, you can easily dump a codebase into your favourite version control system, work on it, then generate the final patch using your VCS’s tooling. Iterating towards a working change is as easy (or as hard) as exchanging patches between the feature developer and the committer of the upstream project. It’s a bit old school, but it’s a good workflow to become comfortable with. I regularly patch my own private projects from my work account by emailing patches to my personal address. Once you compress and base64 a change it’s also humbling how little content goes into a piece of work! (This isn’t a rebuttal to the parent post — more a call to arms that patch juggling isn’t as awful as others might think it is.)