Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

21–30 of 87 posts

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

#21

Post by irskep »

The title is sensationalized. I read the whole thread. Gitea doesn't seem to be "blocking" the PR. They aren't preventing it from going in a release. However, they did pull the in-progress PR into their private repo early, presumably in order to make more money. Not great, but not bad faith.

"Blocking" would suggest to me that the PR is rejected but still ends up in the closed-source codebase, which isn't the case at all.

@dang I flagged this because we're at risk of brigading a community over a nothingburger.

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

#22

Post by Buttons840 »

I wonder what the legality of saying "this PR is available under the MIT license upon being merged into this repo" would be. A PR is copyrighted, and I guess it's just implied that a PR is available under the same license as the main repository, but an explicit PR license could override this (maybe?, IANAL).

I suppose they could merge it, copy it under the MIT license, and then remove it, which overall seems kind of silly, but it would at least get your PR merged. Plus, this trick would look really bad from a PR perspective.

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

#23

Post by isodev »

This is very shady. If there were plans to introduce a certain feature in their proprietary code base, then it should have been raised much earlier in the PR so people don't spend time and energy developing this. Further, "already merged a version of this code into the private gitea repo" euh, hello licensing?

Gitea was already controversial in the sense - why leave a perfectly good closed source solution (GitHub) to another closed solution?

I think, for anyone seriously into self-hosting their source codes - https://forgejo.org is the way forward.

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

#24

Post by rjzzleep »

SamWhited wrote: post #18
dboreham wrote: post #10

Earlier quoted context omitted.

Not sure I see the conspiracy here. It's a 144-file PR that has significant management and performance issues, which seem to be the focus of the long discussion thread.

There's a specific comment in the middle that I think the title refers to where someone mentions that this has already been merged into the paid version, but now suddenly they can't get reviews for the free version: https://github.com/go-gitea/gitea/pull/24257#issuecomment-23...

End of the page he claims to have been physically impaired from working on this. No idea if that's true, just saying what's at the bottom of the page. It is a pretty huge patch though(I missed that upon first glance)

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

#25

Post by lolinder »

irskep wrote: post #21

The title is sensationalized. I read the whole thread. Gitea doesn't seem to be "blocking" the PR. They aren't preventing it from going in a release. However, they did pull the in-progress PR into their private repo early, presumably in order to make more money. Not great, but not bad faith. "Blocking" would suggest to me that the PR is rejected but still ends up in the closed-source codebase, which isn't the case at…

> they did pull the in-progress PR into their private repo early, presumably in order to make more money. Not great, but not bad faith.

Is this fact, or just speculation? I read the start and the end (though not the 175 items in the middle), and all I see is a vague block by a maintainer and speculation that it's because they have a similar feature in enterprise.

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

#26

Post by rjzzleep »

WolfeReader wrote: post #16
gjsman-1000 wrote: post #6

Earlier quoted context omitted.

> Forgejo Switch to the fork of the fork - brilliant. Especially when the fork fork doesn't seem to do much except bicker and merge controversial PRs on occasion. https://news.ycombinator.com/item?id=39393794

Instead of linking to comments (wtf), I'm gonna link to their surprisingly active list of merged PRs. https://codeberg.org/forgejo/forgejo/pulls?q=&type=all&sort=... Not sure what your claim about "doesn't seem to do much" is based on.

The first two pages are docs, dependency bot, and one XSS patch. Hard to know what's going on when 90% of those PRs are bot generated. Maybe they're active, maybe not, I certainly don't know, but it's definitely not clear from the link you posted.

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

#27

Post by GingerMidas »

irskep wrote: post #21

The title is sensationalized. I read the whole thread. Gitea doesn't seem to be "blocking" the PR. They aren't preventing it from going in a release. However, they did pull the in-progress PR into their private repo early, presumably in order to make more money. Not great, but not bad faith. "Blocking" would suggest to me that the PR is rejected but still ends up in the closed-source codebase, which isn't the case at…

Hypothetically, if they never finish reviewing the PR, isn't that the same as "blocking"? Ghosting is still considered a rejection and arguably a much worse one.

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

#28

Post by __MatrixMan__ »

__MatrixMan__ wrote: post #11

A recent comment indicates that this outcome was more like a mistake and less line the skulduggery that the title indicates. Public shaming might be a good tool for this kind of thing in general but maybe in this case it was premature.

Also let's please be careful about creating situations that pressure a maintainer to merge a PR before they're fully comfortable with it. That's how ssh got backdoored via xz (no reason to believe that that's what's happening here).

If somebody wants to embrace YOLO with their $$ project and be a bit more cautious with their OSS project, that's ok.

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

#29

Post by idle_zealot »

gjsman-1000 wrote: post #17
andrewmcwatters wrote: post #9

So? Why does a business have an obligation to give away their intellectual property for free? When you submit a PR to a business’s intellectual property, it’s still theirs. The years go by and the beggar attitude of open source users gets more and more tiring.

[flagged]

I think our ancestors would be aghast at our legal system that has outlawed the propagation of culture and knowledge without paying tariffs to whoever "owns" the relevant ideas.
Post reply on HN