It’s really easy to configure a self-hosted forgejo instance. Even if you rm your local work, you can clone it from your server. Be that hosted on the same system over localhost, or on another system in your network.

The alpha began in August of last year, and will continue to be classified as alpha until all features are finished.

The alpha began in August of last year, and will continue to be classified as alpha until all features are finished.

Alpha 5 is actually releasing next week. I’d also disagree with “very alpha” as most of the beta milestone is finished now. Regardless, I don’t understand where the disconnect is. A spin can release at any time. Doesn’t matter when COSMIC Epoch 1 releases.

That would be completely wrong. See the Fedora Miracle Spin, for example. The project (miracle-wm) is still a work in progress, and yet Fedora already officially offers a Spin for it. What you’re describing would only be true if Fedora was switching to COSMIC as the official desktop for Fedora.

There would be no reason to delay anything regardless of it being beta or not. Fedora is always doing rolling release updates of software that lends well to that paradigm, and COSMIC is one of those. It’s not like GNOME or KDE where you have to carefully and meticulously manage 100 system libraries used by the whole ecosystem. System dependencies in the COSMIC ecosystem are virtually non-existent. If they really wanted to, they could just wait a few weeks to release the spin. But I don’t think there’s any reason to.

You might be surprised how much disk space those GNOME Circle applications actually require, despite being dynamically linked to a lot of GTK/GNOME libraries. Unless they’re written in a scripting language, they’re much closer to a COSMIC application than you think.

• https://flathub.org/apps/org.gnome.TwentyFortyEight 12 MB
• https://flathub.org/apps/org.gnome.Reversi 12 MB
• https://flathub.org/apps/org.gnome.NetworkDisplays 13 MB
• https://flathub.org/apps/org.gnome.eog 12 MB
• https://flathub.org/apps/org.gnome.Photos 29 MB
• https://flathub.org/apps/org.gnome.Notes 12 MB
• https://flathub.org/apps/org.gnome.gedit 20 MB
• https://flathub.org/apps/app.drey.Warp 22 MB
• https://flathub.org/apps/com.github.flxzt.rnote 41 MB
• https://flathub.org/apps/io.gitlab.news_flash.NewsFlash 42 MB

I don’t see the issue with an application having a static binary within the realm of 15-25 MB. Even if you had 100 applications installed, that’s only 2 GB of disk usage.

I wouldn’t rule out the possibility of a cosmic-applets-community package which bundles third party applets, or the gradual inclusion of popular applets into cosmic-applets. Given that an applet would only become popular if there’s a lot of need for those use cases, then it would make sense to open a path to getting them mainlined.

Static linking is not an issue. Binaries may require more space on disk, but the benefit is that they are self-contained, portable, with excellent performance, and low memory usage. Binaries are compiled with LTO, so unused functions are stripped from the binary. What remains is highly optimized to that application’s use cases.