It’s a good thing for the owners of the codebase, but often, a bad thing for the community (even if the community contributes to said codebase).
For example, FOSS maintainers sometimes will (want to) relicense to protect their income stream:
https://github.com/CaffeineMC/sodium-fabric/issues/2400
https://github.com/LizardByte/Sunshine/pull/150
While corporations might literally have maintainers sign away their rights so they can take the work from their own community:
https://lwn.net/Articles/937369/ (canonical requires a CLA, though this + the subsequent re-license might have happened anyway)
https://lwn.net/Articles/935592/ (RPM spec files are MIT licensed at the Fedora level. There are likely chnages to RPM files contributed by the community that are now source-restricted in RHEL)
https://networkbuilders.intel.com/docs/networkbuilders/accelerate-snort-performance-with-hyperscan-and-intel-xeon-processors-on-public-clouds-1680176363.pdf (See section 2.2. Previously, this work was BSD)
Mixed bag, really.
To everyone saying you can’t mirror a flatpak repo… you’re absolutely right. There should be a far easier way to set up your own mirror without needing to build everything from scratch. That being said, if you wanted to try to make your own repo with every one of flathub’s apps, here you go:
https://github.com/flathub
https://docs.flatpak.org/en/latest/hosting-a-repository.html
Edit: Some did get a flathub mirror working. The issue is that a. Fastly works good enough and b. There is no concept of “packages” on the server side. It’s just one big addressed content store because of ostree, and syncing is apparently difficult? Idk, not being able to sync the state of content is like the entire point of ostree…
https://github.com/flathub/flathub/issues/813