@mehdi MariaDB follows this as per Wikipedia: https://en.wikipedia.org/wiki/Business_models_for_open-source_software#Delayed_open-sourcing
It's even okay if the delayed open-source release is restricted to individuals and not corporates - to protect the revenue stream. But we must find a way to direct our resources towards improving public and community goods.
Thanks. I don't mind paying 15$/month or even working on porting open-source webapps to these solutions, but open-source just feels better because the benefits of my contribution will be more widely shared.
+1 for Pleroma as an more resource-efficient alternative to Mastodon.
@girish Have you considered releasing Cloudron code under an open-source license with, say, a 6 months delay behind the latest one? So, my money at least eventually improves the open-source version? A license like that would seal the deal for me in a heartbeat.
@jodumont I know. My own project https://learnawesome.org/ is listed there. I presented it at ActivityPub conference in October. 
+1 for Akkoma. It's quite popular. For example, the linux kernel community https://social.kernel.org runs on Akkoma.
Has anyone done a comparison of Cloudron vs Homelabos? Both of these work with Docker-based apps. Cloudron seems to have better UI, but HomeLabos is open-source.
Besides comparison, is there any collaboration possible between these two projects? For eg: Can Cloudron's Docker images be used as a starting point for porting apps to HomeLabOs?
+1 for WriteFreely. Among all the Medium-equivalents, this one stands out as polished and ActivityPub-compliant.
Points taken for Cloudron being better. But that's precisely why it feels bad not to back a truly open-source project which needs all our help we can give, as opposed to yet another closed-source project that encourages vendor lock-in.
FWIW, HomeLabOS uses Docker and Traefik so the approach is very simple and it supports about 50 apps in all. The main developer is quite responsive and they have a good community going at their Zulip chat group.
@girish Were these issues ever reported to ERPNext? I couldn't find any mention of cloudron ever in their repository: https://github.com/frappe/erpnext/issues?q=is%3Aissue+is%3Aopen+cloudron
+1 for this. v0.10.0 was released in May this year.
+1 for this
