So how do we find out what that BS is ? And where can we find objective information about alternative forks ? Why not keep running an older release ? Etc, you open a can of worms with little guidance ?

The question was clearly phrased in a way to cater those who are already aware of the situation. I have no issue explaining the situation, if politely asked to. If by 'can of worms' you mean exactly what is happening with Bitcoin Core, I can't disagree, but let's simplify - Open-source development happening behind closed doors is not open-source as far as the general ethos goes. Especially when valid concerns are brought up only for the people who bring up those concerns to get banned from the discussion. You can agree or disagree. Running an older release is an option, but eventually won't be sustainable if you want to use newer features. Finally, I'm not looking so much to dwell on the happenings because that's already being discussed to length on multiple fronts, but making it known that alternatives exist and that Core (the big 'default' up to this point) is not the only option, because thinking it is, is the bigger issue in my view.

This thread summarizes the situation nicely.

I run a node for fun and giggles. I Barely use it other than getting some onchain data. Node runners are a small group. I think if you/we need more engagement we also need to point out some entrances for info ? The burden at this point, to just start from scratch finding some objective info is quite high in my perception. I know about BIP but that is only a small part. What is delivered in what release, what are potential issues ? All this basic stuff I wouldn't have a clue where to look for. There must be some discussion forums where these are discussed? Can you point them out ?

Ok it is about potential inclusion of unneeded/unwanted data onchain, with all unwanted side effects.

CoinGape

Bitcoin Core Under Threat? Top Developer Flags Incoming Codebase Update

Bitcoin Core developers are facing backlash over what some see as an hijack attempt of the protocol with the latest proposed changes

Interesting !

I guess that's one way where maybe this kind of discussion might not be of your interest, regardless of whether it really is or not, if you run a node for "fun and giggles". if you run a node without understanding both the power it gives you, but also the responsability (individual, collective or otherwise depending). Unless by "fun and giggles" you mean "as a hobby to learn more about what it actually entails". Node runners are not a small group, even in the grand scheme of things when we're talking about magic internet money. Node numbers have been increasing over the years, and not, counting with tor-nodes which can't be accurately be accounted for, we're likely around 50k+ active nodes. There are many, many knowledge bases out there, a few internet searches and likely to get you on the right path - I mean, if you're running a node I wonder where you got the software from, and the info on how to get it running. Regarding changes made on each release, many one-click OSs already make this really easy to know by presenting a changelog when there's an update to a piece of software. Examples are Start9, Umbrel, etc Look something like this: Otherwise, just the open source software's page is the very best place to look at it. Example for Core Lightning's releases page:

GitHub

Releases · ElementsProject/lightning

Core Lightning — Lightning Network implementation focusing on spec compliance and performance - ElementsProject/lightning

A lot of software source code is hosted on git platforms such as Github or Gitlab, and these have a Releases section to check on what changes have been made. If the changes made are not easily made readable for the average user, the average user probably shouldn't be running the software. As for potential issues, check the "Issues" page on the source code websites, and/or follow people who are active users or maintainers of that software. As for a one-stop place for all this, as mentioned, all-in-one OS's make it a great deal easier to get started, otherwise it's generally pretty organic. As you delve into the software you use and you find its community, you learn of the goings-on.