Compare the cost and you will find the reason

Some will argue that it is Open Source. But Open Source came from commercial interests against Free Software.

It's clearly not free software, since the user freedom is restricted.

It's not libre, since that also refers to freedoms.

It's not really Open Source.

Source-Available has been used to describe this: https://en.wikipedia.org/wiki/Source-available_software

Stalebot closing is a problem. There's no problem with stalebot adding a stale label (but really, a filter with last update x time ago does the same).

Adding filters so that developers only look at actionable tickets would be much more sane.

> Adding filters so that developers only look at actionable tickets would be much more sane.

That's a reasonable approach, but I don't understand how it's any more or less sane than autoclosing them with a stale label.

Whether these sorts of bugs are "open but stale" or "closed because stale" seems like it depends on whether the project defines "closed" as "no work planned" or "fixed", which both seem valid.

Either way these bugs will be hidden from developer dashboards but still available in the database so there's no practical difference, you just need to make sure everyone is on the same page about the meaning of "closed".

I've heard various suggestions of only committing spec.md or change requests in the git repo and using that as source of truth.

We have spent decades working on reproducible builds or deterministic compilation. To achieve this, all steps must be deterministic. LLMs are not deterministic. You need to commit source code.

use gemini and ask it to summarize a youtube link

Teamspeak is using matrix under the hood

There are several independent clients and servers. None of them support all features, not even synapse/element. But most keep improving steadily.

There are other terminal clients.

Maybe put the git repos on radicle?