JJ Asghar

How do you propose handling the copyright for the contributed code?

This is a super interesting idea because if the reviewer doesn’t know who submitted it the game totally changes. Social cachet doesn’t get a faster merge.

Or differential critique based on $factors

Even though I admire this proposal to lower the bar and open up projects to a wider diversity, I cannot help myself wondering about accountability on the work being submitted. Especially with the rise of supply chain attacks on open source projects. Thoughts?

I’m my mind it would be a “mask.” I submit a PR saying make it anonymously and we can have the conversation if needed, then when it was merged the mask would be removed and the credit is applied.

I wonder how licensing and copyright work in this proposal, some sort of rights waiver if submitting anonymously?

I’m my mind it would be a “mask.” I submit a PR saying make it anonymously and we can have the conversation if needed, then when it was merged the mask would be removed and the credit is applied.

How do maintainers then answer questions like if it’s a contribution from let’s say someone who they don’t want to accept contributions from? Like someone engaging in immortal activities?

Already GitHub makes this really hard by hiding emails etc It’s also required for contributor sign off and ownership assignment and CLA enforcement etc