Live data from Hacker News

FFmpeg moves to Forgejo

code.ffmpeg.org

311–320 of 374 posts

Re: FFmpeg moves to Forgejo

#311
post #149

Earlier quoted context omitted.

> some others would find triggering/improper I guess the main point is branding clash if you're a large company website (most companies care a lot about how their brand is shown, if they care about spacing/padding around their logo they also care about what pictures are shown when joining), hopefully nobody is triggered by this kind of art. (though resentment could build up if actual humans get frequently unexpectedl…

> hopefully nobody is triggered by this kind of art Apparently a good chunk of HN is. Anubis-tan seems to me the main reason that this comment section about FFmpeg and Forgejo has devolved into a debate about Anubis; more than the intersitial page itself.

That's too bad, I wonder what's so triggering about it.

OSS projects are mostly done by people on their free time, they can do whatever they want with their mascots/branding/project. And those OSS projects tend to be significantly more respectful of users than the average modern software so on my side I tend to see those kind of harmless personal touches quite positively, sign of software that is made with the user in mind.

Re: FFmpeg moves to Forgejo

#312
post #65

Earlier quoted context omitted.

I wish a certain open source project would take notice of the reasoning here...

The friction and overhead of mailing list development is seen as a feature, not a bug, for certain devs who prefer an exclusive environment. Moving to a modern platform with real collaborative development features is a mature move.

For those with a power-user email setup geared towards mailing lists and patch handling, modern web-based platforms are a substantial usability regression.

Re: FFmpeg moves to Forgejo

#313
post #233

It's interesting (and a little sad) how all git "forges" (for want of a better word) converge on the same layout. An alphabetical list of files, when they were last modified, and an expanded readme file. IMO a list of recent commits would be more useful as a landing page, or maybe even just the readme. When checking out a new project, I'm interested in what it does, not in its folder structure when its LICENSE.md was…

You might like cgit, git-arr, or one of the other static git generators. They generally have a different mode of navigation. They're not 'forges' in that they don't have in-built tools for things like bug-tracking and managing PRs though, but lately it seems like projects are becoming more interested in the git email workflow anyway

Re: FFmpeg moves to Forgejo

#314

The comments on this page are a complete cesspool. A full third of them complaining about the anti-bot protection mascot (yes, it's a cartoon character; get over it), others splitting the finest of hairs over software development groups and company politics, and more. Self-hosting is generally good, well done to FFmpeg. Many large projects self-host, and my own ex-company has physical servers in the city we work at t…

It's frustrating. As someone who is into self-hosting, I was hoping to find answers in the comments to questions like:

- How self-hosted is it? Is it on somebody's computer at home? A colo? One of those university linux servers that runs for decades? Hetzner? Is there any redundancy?

- How are the costs and responsibilities for the hardware broken down?

- How is admin and patching handled?

I'm actually very curious about that stuff, but nobody's really talking about it here

Re: FFmpeg moves to Forgejo

#315
post #310

Earlier quoted context omitted.

It’s all in the approach: start with a “thank you for the project”, and a “hope you don’t mind but I’ve corrected a few typos” and nobody will shout you down. Only go with a blank PR description and it’ll come across as arrogant and spammy.

As a counterpoint, these kinds of formulaic ingratiating preambles turn me off. Get to the point of your PR, so I can judge on its merits!

completely agree, I'll take "fix typos" any day over three sentences that don't add anything of value

Re: FFmpeg moves to Forgejo

#316
post #20

Earlier quoted context omitted.

> it's hard to take them seriously when they've been saying very nasty things about the project their whole foundation is built upon I'm not sure why that would make them hard to take seriously unless the things they're saying are false. Is that what you're claiming? > If you look at forgejo commits, more than half of them are merges of library updates made by the renovate bot, which artificially inflates the level o…

None of the really heavy hitters from the "core team" have left. As long as 100% FOSS Gitea pulls ahead in functionality, and can be downgraded relatively easily with an hour of work, I personally see no reason to move anywhere. You can part in different ways, the vibes you give off certainly matter, even when you're 100% technically correct. And I suggested comparing releases, not commits; Gitea is ahead here both i…

Thank You. It was an obvious question as to why Forejo. Something that is not popular and not well known for many compared to Gitea. And what happened with the fork. I thought it should have been the first question on HN. Instead, even when asked it is not upvoted, and when it does, it is at the bottom of the comments section.

From the context in that mailing list it does seems there is more to it. Not to mention Gitea is still MIT license and continued development. But competition is good, I hope both project do well.

Re: FFmpeg moves to Forgejo

#317
post #218

Earlier quoted context omitted.

I'm not calling people or reasons unreasonable, but the level at which they are triggered. And I stand by my point: being mad that someone chooses to self host is unreasonable and no amount of accusing me of doing armchair psychology will change anything to this.

There’s an irony to becoming so triggered by a couple angry comments that you become triggered and leave your own angry comments.

Oh no, we are trapped in a angry comments infinite loop! :-)

Yeah, I wouldn't say it triggered me but we should definitely have flagged the angry comment and moved on, as per the HN guidelines. I was negatively surprised, I'm not usually surprised by comments on HN.

In the end, all these comments were flagged and downvoted to death anyway.

Re: FFmpeg moves to Forgejo

#318
post #272

Earlier quoted context omitted.

I fix documentation typos or broken links because they really annoy me. There are some egregious examples of people doing it for GitHub-as-a-social-network reasons, but I think some are like me and just want to fix the writing.

I similarly contribute only minor language and writing corrections to Wikipedia, and usually anonymously (unless my phone has randomly pulled a blocked IP and I need to sign in). I don’t consider myself enough of an expert in any Wiki-worthy topic to do anything more, but I’ll make damn sure small mistakes get addressed. I feel even less qualified to contribute corrections on GitHub mostly for the same reasons mentio…

[deleted]

Re: FFmpeg moves to Forgejo

#319

Earlier quoted context omitted.

> Can't fault the logic. Will never use it if that's part of what they've chosen to paywall. Is pretty damn rude. It's the kind of thing you say online but would never say face-to-face.

I'm not sure we agree on what constitutes "pretty damn rude". It was an inelegant, hastily expressed opinion.

Yes, inelegant, hasty, and with no regard to the person across the wire you're communicating with. Self serving and rude.

Re: FFmpeg moves to Forgejo

#320

It's cool to see such an impactful project choose sovereignty. I hope more projects follow their example. If you're a backbone-of-the-internet project like FFmpeg is, living on GitHub seems horrible. You will be subjected to thousands of low quality pull requests and issues from people searching for typos to fix, adding a line of white space for a contrived reason, or similar nonsense changes. Just so they can put "F…

I have to say you're exaggerating, ignoring prs isn't such a chore.

If you are ignoring all of them. Filtering PRs to see which are worth having might take time in a large popular project. Even if it isn't much time, it is more than zero. You also have to deal with all the other comms associated: people submitting genuinely useful patches which accidentally get rejected querying (maybe politely, maybe not) and people who submitted less useful ones bitching about their rejection, both to the project and in public forums.
Post reply on HN