Live data from Hacker News

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

github.com

81–87 of 87 posts

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

#81
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…

The in-progress PR was not pulled in, different code was written to log a small subset of events that this PR does. I commented here: https://news.ycombinator.com/item?id=41514547, but the PR is more fully fleshed-out and has more functionality, which hopefully can be merged.

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

#82
post #30

Seems like just some people wanting to merge stuff ASAP and others having other priorities/IRL stuff and some commenters shilling our unfounded conspiracy theories. Yes, the 3k+ LOC, 144 file PR is 1 year old and still not merged. Join the club.

You're missing the point, if this was just an unmerged PR no one would care. But it's likely the paid Enterprise edition has merged this already, and now the same entity has an incentive to block this from the OSS version.

I commented here: https://news.ycombinator.com/item?id=41514547, but it's different code, much more of an MVP than the fully fleshed-out functionality of this PR. Hopefully, it can be merged once the technical feedback has been addressed. We've seen with other areas of the project how DB degradation can impact the whole application, and have to deal with reports from users when they run into that. I'd rather the performance impact had at the very least a work around before it gets merged so when those issues are opened, then triaging them is much easier.

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

#83
post #14

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.

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.

I commented here: https://news.ycombinator.com/item?id=41514547, but CommitGo was founded to ensure the longevity of the Gitea project. Due to the formation of the company more maintainers have been able to be paid for their time, and bounties/contracted work etc.. all go straight to the project.

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

#84

I'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 i…

Just to add some heads up, CommitGo was on the roadmap, but establishing a company in the US takes time, so the initial org was created so that something could exist while the primary one was established. Hopefully more entities that are localized to specific geographic regions can be created as funding maintainers cross borders is a headache.

edit: we (the project and the company) are also receiving advice from several major open-source foundations on what establishing a foundation for the project would look like.

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

#85

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.

Hi, yes. That was me. I'm dealing with some health things and wasn't able to do much until recently, and I am working on continuing that conversation.

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

#86

I'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 i…

Just to add some heads up, CommitGo was on the roadmap, but establishing a company in the US takes time, so the initial org was created so that something could exist while the primary one was established. Hopefully more entities that are localized to specific geographic regions can be created as funding maintainers cross borders is a headache. edit: we (the project and the company) are also receiving advice from seve…

Heads up would have been explaining this at the time and not silently transferring ownership of the domain to a second for-profit entity with no lead up and no announcement [0]. I'd have thought that after the trademark fiasco you'd have learned to be more open about your intentions for your for-profit arms, but it seems you might have taken the opposite lesson.

[0] This announced Gitea Cloud but gave no explanation for why a second for-profit was created instead of just using the already-controversial Gitea Ltd: http://web.archive.org/web/20231127091431/https://blog.gitea...

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

#87

Earlier quoted context omitted.

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.

I can't speak to controversial PRs, but I got very nervous about Forgejo when they memory-holed a good faith critique of the appointment of a specific new moderator. Someone on HN linked a discussion where Forgejo was appointing a moderator [0] and had received pushback. A critic of the decision had said something along the lines of "this person has severely abused authority in this community in the past and I'm not…

ouch; that does sound unfortunate, I'll look into it, thanks.
Post reply on HN