Unless you need a "stable" version of your in-development work I wouldn't split parts of it into branches.
Use branches to draft and explore changes, and merge them when they're accepted into the baseline draft/current state.
Don't be afraid to merge "better than before but not final or complete or conclusive" work. You're trying to evolve, not construct final parts to combine. They won't ever be final.
I'm not a user of this software, but reading the ticket I know I'd be annoyed too. I was when Windows 11 changed task bar behavior to worse.
It dumped and animated icon in my panel in the primary position where my most used launcher normally is
There was no clear way to remove this intrusion into my workflow - the context menu item of "Donation options" was not something that appeared to give me that option
From that, seems like it was a disruptive donation button rather than an informational side thing.
They opened the ticket with thanks and appreciation, and made respectful factual arguments. Far from "whining incessantly".
You mean as a library? ffmpeg can be integrated as a library but also be considered an application. GStreamer is a library only, as far as I know. You'll need to run other applications that use it to run it.
This is a community for discussing things about programming.dev itself. Things like announcements, site help posts, site questions, etc. are all welcome here.
I hate when apps use my number formatting setting to determine display language - despite Windows having a display language as well. Even Qt does (did?) that.
I think it's an interesting idea, and I'd see it as fine for simple host + fetch. But as soon as you start interacting, I see it as far worse.
A personal support email may work, but as they write by the end, ticket tracking and collaborating on a platform with a shared web interface is much superior for information sharing and but also iteration (they talk about back and forth emailing earlier).
Self-hosting yet another platform/forge with its own account system is not viable to me either. (I'm still hoping for forgejo federation for a centralized account. Until then, GitHub seems like the best choice purely because it's the biggest and everyone has an account and can contribute and post without account barriers.)
The idea that it could be a hosted repo with an integrated mailing list (and potentially bug tracker) is interesting, but ultimately, almost/actually a full forge then anyway.
The bad reputation is largely obsolete. The owner had changed to a bad owner with bad practices, but that owner was eventually replaced by a better owner again.
I still hate the UI though. We have much better alternatives today, which is why I don't see any reason for anyone to go back to (or start) using Sourceforge. It's no longer an issue of owner and bad practices, but solely of the platform itself with its UI/UX.
9785099e- what the heck - what a [shortened] commit hash, damn. Only one letter.