[mhitza]

For me that adds to many steps, and removes collaboration transparency.

Disregarding the fact that I would need to have a way to reliably find the contact information, the review process would probably take place outside the source code platform.

[freeopinion]

Too many steps? How is it more steps than submitting an MR or PR today? You have to fork, code a patch, submit a pull request. The difference is just that it happens across forge instances.

You have a point about the review process. How much of a moat do you want around your project? You want to keep spammers out. But that creates hurdles.

I was trying to interact with the Trunk project the other day. But they required me to create accounts on multiple services just to get in the game. When you need a Github account and a Discord account and... You know what? Nevermind. It's too much effort just to be nice and inform you of an issue with your project.

I totally understand that putting a public email address out there creates a huge burden for them. I suppose if I value a product enough I will accept some smaller burden and take the load off them. But most of the time I don't value a product enough to allow the authors to offload their burden onto me. Conversely, they don't value my input enough to accept the huge burden it would take them to allow me to interact with them.

[freeopinion]

What if you could submit a PR by pasting the url of a repo commit?

The forge could automatically figure out if the submitted repo was a fork, figure out the sequence of commits in the foreign repo that diverged from itself, analyze the commit comments and commit diffs to see if they jived, and add the PR if it passed the spam filter.

Then you could submit PRs without an account or even having the contact information of a maintainer.