Earlier quoted context omitted.
[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 .
Gitea blocks PR from community, charging $$ for open-source contributions
31–40 of 87 posts
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#32So? 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]
Calling people greedy solely because "it could be worse" is rude and misanthropic. Calling them greedy for wanting a bounty-funded, community contribution to be merged into the community version not just the paywall version is ridiculous to me. Maybe the "shocking revelation" about the open source community is how easily some turn to corporate bootlicking.
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#33Seems 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.
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.
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#34Earlier 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
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.
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 comfortable with them getting new authority". They went back and forth for a bit with the maintainers, but by the time the link ended up on an HN thread they'd edited out the critic's comments with a warning not to post ad hominem attacks. At the time you could still read the critic's actual comments in the edit history and it was clear that they were being very reasonable.
A few weeks later I went back to that thread and the entire discussion with the critic was gone. The moderator was appointed, and all record of the dissent was eliminated. If you go to that issue thread now, there are 10-12 comments that I read before that are now missing, and it looks like this person was appointed without dissent.
That sketched me out, and I've been very cautious of Forgejo since. I trust Gitea even less, so I stick with Forgejo, but I wish I had better options.
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#35Earlier quoted context omitted.
[flagged]
This reads like "eat your dinner; there are starving kids in " which hints at a valid point but even the toddlers know isn't a good argument. Calling people greedy solely because "it could be worse" is rude and misanthropic. Calling them greedy for wanting a bounty-funded, community contribution to be merged into the community version not just the paywall version is ridiculous to me. Maybe the "shocking revelation" a…
On the other hand, the unsympathetic side of me says, "That's the license; those are the rules of the game which everyone voluntarily agreed to; and you don't have to like how some people play the game."
There's no place in FOSS licenses for "Rule #7: Don't do anything that isn't nice."
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#36Re: Gitea blocks PR from community, charging $$ for open-source contributions
#37Seems 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.
Says who? A random commenter on the thread who's not even the submitter of the code?
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#38Why would someone be motivated to contribute free code to Gitea after everything? Is "forgejo" really so stupid a name that people are willing to risk being exploited by Gitea?
I added more details here for the curious: https://news.ycombinator.com/item?id=41489578
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#39In 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 :-)
If this doesn't track well, I suggest you repost indicating, in subject, that they're also withholding the patch from the OSS version. I'm not sure how to write the subject that way, within character limits, but there is zero outrage at charging $$ for OSS contributions, so the subject seems very "meh". After all, millions of companies do that.
Re: Gitea blocks PR from community, charging $$ for open-source contributions
#40Earlier quoted context omitted.
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.
> it's likely Says who? A random commenter on the thread who's not even the submitter of the code?
The reviewers of the OSS code are still heavily incentivized to block this PR. Worse, if they knew a similar feature was being built for enterprise and this would never be merged into the free version, they be wasting months of contributors' time and effort.