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.
Gitea blocks PR from community, charging $$ for open-source contributions
11–20 of 87 posts
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#12So the evidence here is that the Gitea Enterprise page now advertises an audit feature? Mainly for thoroughness: how sure are we that it's the same code?
We're not, and they're still in the process of discussion. It seems a bit early to fork and witch-hunt [0]:
> So clarification here: you asked me about that, but I haven’t been able to respond to you due to my illnesses and I’m just getting back on my feet now. So it’s not that it hasn’t been well received, it’s that I’ve been physically unable to respond to you.
[0]: https://github.com/go-gitea/gitea/pull/24257#issuecomment-23...
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#13The controversy here is described in the following comment:
> Unfortunately, they have already merged a version of this code into the private gitea repo and are charging $$ for it. So Gitea Ltd. (owners group) has no incentive to review and merge this in an open source repo, even though the open source community has funded and developed it.
> This is a cynical take, but I have raised these concerns in private channels and there has been no evidence to refute it. If Gitea Ltd. wants to focus its efforts on the private fork and to make money, that is fine with me, but unfortunately, they also decide what gets merged here, so there is a massive conflict of interest (cough open core). Since Lunny has blocked it and refuses to say why, it appears we are stuck.
> I have asked them to commit publicly to not merging code in their private codebase that is still open for review upstream, but that hasn’t been well received, leaving me and some other members of the community pretty disheartened.
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#14So? 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.
Open source contributors don’t get paid for their contributions, but gitea org does.
Expecting your volunteer contributions to not get paywalled is not a beggar attitude…
Gitea specifically has a track record of taking advantage of the good will of open source contributors, which is why the forgejo fork exists.
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#15In the link is a comment describing how Gitea LTD is stalling on a pull request and instead merged it into their private repo which they charge money for. This is a PR that was funded with a bounty with the idea of contributing to open source. Now is a great time to switch to Forgejo :-)
> 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
I don't know how they're run internally, but they seem to have merged a lot of good features that the Codeberg folks developed, so they must do at least a bit more than bicker.
What controversial PRs have they merged? I haven't heard about that and it makes me a bit nervous, but I'm not finding anything obviously wrong searching for it.
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#16In the link is a comment describing how Gitea LTD is stalling on a pull request and instead merged it into their private repo which they charge money for. This is a PR that was funded with a bounty with the idea of contributing to open source. Now is a great time to switch to Forgejo :-)
> 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.
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#17So? 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]
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#18In the link is a comment describing how Gitea LTD is stalling on a pull request and instead merged it into their private repo which they charge money for. This is a PR that was funded with a bounty with the idea of contributing to open source. Now is a great time to switch to Forgejo :-)
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...
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#19I've been very wary of Gitea since Gitea Cloud and CommitGo, Inc. became a thing. One commercial entity (Gitea Ltd.) is one thing (although the trademark fiasco around that was a bad look on its own [0]), but when a second for-profit quietly spun up around the same open source project with little explanation I got a bit sketched out and have been cautiously using Forgejo instead (it has its own problems I won't get into here).
That said, I'd like to see more information before we jump on the outrage bandwagon. The only thing we have here is a PR that was blocked by a maintainer who's not very communicative and the speculation of a random participant in the PR discussion that they're intentionally blocking the merge because of a conflict of interest with the enterprise version. That's not a lot to go on, and there are other possible explanations besides malfeasance.
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#20In the link is a comment describing how Gitea LTD is stalling on a pull request and instead merged it into their private repo which they charge money for. This is a PR that was funded with a bounty with the idea of contributing to open source. Now is a great time to switch to Forgejo :-)
That patch doesn't exist in forgejo though does it? (I find it to be a terrible name by the way)
Forgejo is a word from a non-English language (Esperanto). It's pronounced "for-jay-o" which I find pretty easy to say.