Captain Beyond

This - cathedral style development absolutely is a valid way to create free software and I don’t believe Eric S. Raymond (the guy who, I believe, coined the term) claimed otherwise, only that the bazaar model was “better.” Maintaining a bazaar style project is work, and it’s work that easily leads to burnout. We should normalize the idea that you don’t need to commit to being an “open source maintainer” to release a free software project; it should be enough to just release the source code (with or without binaries).

It should be noted that this is not the source code to the application itself, but rather a backend server used by the application. The application proper remains under a free software license.

However, the fact that this server (which as far as I know is a required dependency of the application) was kept secret (albeit under a free software license) is troubling, and I don’t understand how Alexander can justify removing this license given he is not the sole contributor to this repository. It’s also strange that he reprimanded Roman for “making decisions alone” when the decision to remove the license was made by Alexander alone.

Why does it need to be proprietary?

From my point of view switching from a proprietary application to a free application is always a gain. You can’t control what other people use, but you can take steps to reclaim your own freedom and control.

It’s unfortunate there’s no way to use RCS from a free application, though.

I have never used /e/ but I do not have a positive impression of it. From what I can tell it’s just LineageOS but with microG (with Google registration turned on by default) and some “app store” thing (which tells you what proprietary applications are “good”), tied to their cloud (it’s okay because it’s not Google you see) and with a proprietary map app with a “good privacy policy.”

Privacy policies are not a substitute for free software licenses and any organization suggesting they are is not reputable in my opinion.