Re:Gitea blocks PR from community, charging $$ for open-sour...
by ironmagma on Monday September 09, 2024 @12:08PM
(#41489951)
Brigading? Well I definitely didn’t intend that, although I also don’t see anyone from here having commented on the thread so I don’t see how that is reality.
Stall may have been a better word, although this PR has been crawling along for over a year now, with little response from the maintainers. If something is neglected for long enough it’s topologically equivalent to blocking it.
Re:Gitea blocks PR from community, charging $$ for open-sour...
by irskep on Monday September 09, 2024 @04:07PM
(#41493009)
I did say "at risk of" - the front page of HN is a powerful place. :-) Looks like my fears did not come to pass.
Re:Gitea blocks PR from community, charging $$ for open-sour...
by lolinder on Monday September 09, 2024 @11:27AM
(#41489459)
> 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-sour...
by GingerMidas on Monday September 09, 2024 @11:29AM
(#41489493)
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-sour...
by TiredOfLife on Monday September 09, 2024 @01:59PM
(#41491408)
>... but not bad faith
That is literally in bad faith.
Re:Gitea blocks PR from community, charging $$ for open-sour...
by techknowlogick on Wednesday September 11, 2024 @03:57PM
(#41514832)
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.
"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.