Gitea blocks PR from community, charging $$ for open-source contributions

Re:Gitea blocks PR from community, charging $$ for open-sour... by tempfile on Monday September 09, 2024 @11:56AM (#41489828)

GitHub's TOS include a clause that says you agree your PRs are under the same license as the project ("license in = license out"). I don't know what happens if you assert a specific license that contradicts that. It would be bad to do what you say, because if the PR is never merged, then third parties could never use the PR in forks. A better alternative would be to offer the patch under MIT or GPL at the maintainer's discretion, but that would create more confusion than it's worth.

After all, nobody is currently prevented from maintaining Gitea with the linked PR merged. The problem is that the major community maintainer is prevented from merging it due to a conflict of interest. License juggling won't help with that.

Your proposed "trick" does not seem to achieve anything - the code is still not present in the main ditribution, no?

[ Parent | on HN ]

Re:Gitea blocks PR from community, charging $$ for open-sour... by Buttons840 on Monday September 09, 2024 @05:44PM (#41494337)

Good to know.

My proposed "trick" was just to illustrate that it's futile to make a contribution MIT licensed for some people/purposes and not others. I think we're in agreement on this.

[ Parent | on HN ]