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

Re:Gitea blocks PR from community, charging $$ for open-sour... by __MatrixMan__ on Monday September 09, 2024 @01:22PM (#41490937)

Yes but the exhaustion was not 100% organic. There was a bit of social engineering towards wearing the maintainer down even further.

I'm just pointing it out because I think it's going to be a tricky balance to strike. How can we, as a community of people who care about free and/or open source software tell the difference between:

- a good faith effort to inform the wider community of a maintainer who is behaving badly

- a bad-faith contributor pressuring an overworked maintainer to include a malicious commit

I think you're the former, but I'm rather worried about the latter. And I'm interested in strategies for telling the two apart.

[ Parent | on HN ]

Re:Gitea blocks PR from community, charging $$ for open-sour... by ironmagma on Monday September 09, 2024 @01:48PM (#41491271)

I’m actually neither. I’m a big fan of forks. If something isn’t working out well, it should be very easy to create a fork and switch to the fork (i.e. forks should be lightweight just like branches).

We can’t rely on everyone to follow our schedules, so if there’s a desire we should take the lead on getting it done instead of dragging each other down. As such, I didn’t post this to shame anyone, mostly to provide an onus for switching to a fork. (Or I should say, another onus, since there are already a few reasons to not contribute to Gitea, mostly coming down to size of the project and inertia preventing refactors or redesigns.)

[ Parent | on HN ]

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

That's a very reasonable position to have, sorry for jumping to conclusions :)

[ Parent | on HN ]