Why not make Cloudron fully open source again?

[adison]

@necrevistonnezr said in Why not make Cloudron fully open source again?:

p

what did hashicorp do? i mean, i use hashicorp vault and that works fine.

[fbartels]

@adison https://thenewstack.io/hashicorp-abandons-open-source-for-business-source-license/

[adison]

@fbartels said in Why not make Cloudron fully open source again?:

https://thenewstack.io/hashicorp-abandons-open-source-for-business-source-license/

uh what? if that is the case, how is vault still maintained?

[necrevistonnezr]

I have posted a few warnings about this - any commercial competitive offering to Hashicorp products is endangered.
Reliability and stability in licensing is a value by the way if you’re running a business and have proper budgeting.

I know a couple of businesses really struggling now: Vague license, absurd new license fees, and total dependence makes for a toxic cocktail.

[fbartels]

Especially around Terraform a lot of business has been built. I'm too lazy to check, but I think there are now two endorsed community forks of the last version before the license change.

[msbt]

@fbartels https://opentofu.org/blog/opentofu-announces-fork-of-terraform/ that's one, not sure what's the second

[fbartels]

@msbt opentofu was recently still opentf. Maybe that was because i thought there were two projects.

[ryangorley]

@necrevistonnezr said in Why not make Cloudron fully open source again?:

Or they pull a Hashicorp.

Yeah. I guess this led to the OpenTofu (aka OpenTF) fork that is now under the stewardship of the Linux Foundation.

Directus made a similar move over to a BSL license a few months ago. I was really sympathetic to BSL licensing in principle, but soured when in the specific case of Directus the product went from open source to any business that makes more than $5M in revenue must now pay them $500~$700/mo. to self host Directus. They don't actually publish that information. I've got clients operating very low-margin businesses who would find themselves in serious trouble. I don't imagine most people installing Directus on Cloudron understand what licensing cliff they're eventually going to walk off of.

Still, I'll take an open source product that could go this direction any day over a proprietary commercial product that can make such arbitrary changes without accountability or recourse.

[avatar1024]

I wonder if a possible solution would be for Cloudron to use Canonical's approach to snap where it's all open source but the Snap Store, with the snapd deamon having the Snap Store somehow hardcoded has the source for apps.

Not that I often use Canonical as an example, especially not on this, but it feels that this could be a half way house for Cloudron.

I also like the idea of open sourcing all of Cloudron but without update push from Cloudron repo and support (other than the forum and docs) for not not paying customer.

[adison]

@avatar1024i mean, i guess its an idea

[fbartels]

@avatar1024 said in Why not make Cloudron fully open source again?:

but without update push

If I remember correctly, this is how it was before the two apps limit existed. You could install, but all updates where from the cli. It was no fun.

[jdaviescoates]

I'm going off topic, but re:

@timconsidine said in Why not make Cloudron fully open source again?:

Woke socialism

I find the the crazy culture wars we live in these strange times so bizarre when they lead to such terms being used in a derogatory way like this.

"Woke" just means "awake to the injustices of the world" or as Wikipedia puts it:

"alert to racial prejudice and discrimination".

and "socialism" basically just means "understands that concentrated private ownership - think about the ultra concentrated ownership of land, banks, media - isn't really good for anyone" (and e.g. The Spirit Level has shown very convincingly that inequality is bad for everyone, including the rich), or as Wikipedia puts it:

characterised by social ownership of the means of production, as opposed to private ownership....Social ownership can be public, community, collective, cooperative, or employee.

Note that it doesn't mean state ownership of everything (although, coupled with greatly modernised more participatory and deliberative democratic practices more suited to the 21st century - of which thankfully there are many good examples of all over the world - wrt to natural monopolies like water and rail etc, that would often make lots of sense)

And now in the UK we have the Conservative Government tweeting utterly bizarre things like this (which thankfully nearly everyone - including loads of actual scientists - is taking the piss out of):

https://twitter.com/Conservatives/status/1709207218027934071/quotes

[avatar1024]

@fbartels said in Why not make Cloudron fully open source again?:

It was no fun.

Agreed, but the change in license was no fun either...and in my view more harmful

[ruihildt]

@ryangorley said in Why not make Cloudron fully open source again?:

Directus made a similar move over to a BSL license a few months ago. I was really sympathetic to BSL licensing in principle

Also sympathetic on principle, but when the code is released to open source 3 years later, it's a kind of bad joke when you talk about a web platform with all dependencies, etc.

[LoudLemur]

I think Cloudron should be Free as in Freedom.

I have a few boring things to say, which I will add at the end, but this is what I think:

1. Business Model
   Creating a financially viable business model for a Free Software project has been a longstanding problem. In all the discussions I have seen, the most promising way a Free project can achieve this is by the project team being the best provider of code improvements. They can achieve this by for example staying current with the needs and requests of users and responding in a timely fashion with quality code.

A crowd-funding, goal / stretch-goal format for making improvements would hopefully sustain continual work on the project. CodeWeavers have been successful with a system where paying users gained the perk of being eligible to vote on the direction the coding focus should take. It is worth looking at how they manage it:
https://www.codeweavers.com/

Data visibility is very helpful for a system like that, where you can see a roadmap and options along the way, the flow of developer time, the use of resources etc. Apache eCharts could help, for example.

Another source of funding would be to have a "Corporation Suggested Contribution" in the download area. This could be scaled and set according to the size of the corporation, for example. If the relevant page were pitched in terms of corporate social responsibility, corporate citizenship, and had some sort of "establishing a relationship with the developers" perks, that might be enough to enable corporate IT departments to authorize the payment, perhaps in a tax deductible way.

Another path Cloudron might follow would be to take a policy that code would be made Free later, for example, during the third year after it was initially introduced.

Open Source?
Isn't Cloudron 'Open Source' already? Does it not satisfy Freedom 1, publishing the source code in a human readable way? Does Cloudron not follow an Open Source development model, where people can contribute code to, for example, add support for an additional application?

https://www.cloudron.io/opensource.html

There are some non-Free packages which Cloudron supports, and I believe these should be flagged as such, so that people can filter them. By Free Software Foundation standards, including non-Free packages is enough to categorize Cloudron as non-Free, in the same way that Debian GNU/Linux has been categorized as non-Free, due to its support for proprietary firmware.

[jdaviescoates]

@LoudLemur said in Why not make Cloudron fully open source again?:

Open Source?
Isn't Cloudron 'Open Source' already?

No.

The source is available and is developed in the open as you allude to, but it doesn't meet the definition of open source as per https://opensource.org/osd/

(nor the definition of free software as per https://www.gnu.org/philosophy/free-sw.html )

But, anyways, on the business model side of things, I personally don't see any reason why Cloudron would have to change anything if they were to fully open source their code / use a free software licence again.

Cloudron already has a successful business model! Basically: charging for timely updates and support.

To repeat some of the stuff I said in the OP

@jdaviescoates said in Why not make Cloudron fully open source again?:

@girish said in Cloudron no longer AGPL? (my emphasis added):

The technical reason is that the code base has subscription, appstore and sign up logic. It's unclear what the license should be if it requires the cloudron.io service to work. The non-technical reason is that we were spending too much time explaining why we call ourselves opensource and charge for it. To put an end to such conversations (many of them very hurtful), we just stopped calling ourselves opensource as as early as 2017. I don't know of an easy solution to this.

And in one of the threads on Mastodon, a Cloudron dev said (again, my emphasis added):

Cloudron is attempting to enable people with lesser technical knowledge to get apps running and most importantly updated, backed up and secured"

and:

most of our work goes into reliable, reproducible app updates

And later on in the same thread Cloudron devs go on to describe their desire to create:

a sustainable product with support

And:

We believe more into source available for trust and validation reasons bundled with a business model which is sustainable to ensure continuity for users and one which does not rely on external investment or other means to pay for dev. We have seen sandstorm failing, everyone looses out.
My personal opinion: Ideally we all have the luxury to develop all this for free, but sadly at least I don't. And we have tried patreon style.

So, to summarise, and correct me if I'm wrong @girish and @nebulon, but it would appear to me that the primary reason given for why Cloudron is not fully open source is simply because:

the business model is to sell subscriptions in order to fund ongoing development, updates and support.

Assuming I'm not wrong(?), this really confuses me, because I don't understand why Cloudron being fully open source would stop Cloudron from selling subscriptions for updates and support?

Indeed, selling subscriptions for updates and support is pretty much exactly the same business model as the first one-billion dollar (now nearly $4B) open-source company in the world, and one of the most successful open source companies of all time: RedHat:

Red Hat sells subscriptions for the support, training, and integration services that help customers in using their open-source software products. Customers pay one set price for unlimited access to services such as Red Hat Network (makes updates, patches, and bug fixes of packages included within Red Hat Linux and Red Hat Enterprise Linux available to subscribers) and up to 24/7 support.

This was also one of the points raised on Mastodon:

"Choosing a FOSS license does not impact your ability to have a subscription service."

It was also made previously on this forum too:

@gabrielcossette said in Cloudron no longer AGPL?:

It should be pretty simple for customers to understand, they are paying for a service of maintenance and support (indirectly funding the development of the core product). That is no different than let's say a WordPress maintenance service to have plugins/themes kept up-to-date by a company.

So, to rephrase my first question to @girish and @nebulon

What exactly is it about Cloudron and/or the AGPL that leads you to the conclusion that if Cloudron were fully AGPL licensed you would be unable to continue with your sustainable business model of selling subscriptions for updates and support?

I'm not really too bothered to be honest, but I've never actually seen any answer to that question, even though @nebulon was the first to respond with:

@nebulon said in Why not make Cloudron fully open source again?:

Thanks for your elaborate post, we will answer in more detail

I'd still like Cloudron to be fully open source again as

1. an insurance policy, in case something bad happens to Cloudron,
2. because it'd be very good for marketing, and
3. because I think some people who don't subscribe nor contribute due it's it current licence might begin to do so, and finally
4. because I don't think (m)any people would stop subscribing, that more would start, and because I'm yet hear any arguments about how it would damage the existing business model.

But in the meantime, I'm very happy for @staff to continue making Cloudron even better than it is rather than spending time answer my question

(i.e. What exactly is it about Cloudron and/or the AGPL that leads you to the conclusion that if Cloudron were fully AGPL licensed you would be unable to continue with your sustainable business model of selling subscriptions for updates and support?)

And it's already been said before, but perhaps one way to alleviate any fears @girish & @nebulon may have about copycat businesses setting up and undercutting their pricing (which is the only potentially real threat I can think of as it's happened to other open source projects) would be to adopt what people like https://wpmudev.com/ and https://wordpress.org/plugins/wordfence/ do i.e. charge for timely updates (which in effect is what Cloudron already does), and only release public open source updates after 6 months (as others have pointed out, 3 years would be way too long)

[scooke]

@jdaviescoates said in Why not make Cloudron fully open source again?:

why Cloudron being fully open source would stop Cloudron from selling subscriptions for updates and support?

This forum provides a hint why: Few would pay, but still come looking for help. So, the way around that is to firewall this forum. They could then possibly leave this forum as-is for whoever wants to run it openly, but then you'd end up with the mess that is the Yunohost "help" forum. Give it some time, and the good name of Cloudron gets tarnished, people stay away, contributions drop...

one of the most successful open source companies of all time: RedHat

Which is also, if my browsing tells me anything, one of the most deeply hated companies of all time! And it's an enterprise behemoth, not for folks like you and I. It'd be sad if Cloudron went that route.

Your contributions are always appreciated @jdaviescoates , let me add. I just think the number of the people who you think don't subscribe or contribute due to Cloudron's current licence (and thus who would pay if the licence changes) simply does not outweigh the masses who would flock to the type of OS you prefer and then clamor for Support, not get it, complain, and torpedo Cloudron's rep. Cloudron really has found a good balance (from what I can tell).

[bmann]

“Classic Open Source” needs to change because it’s been taken over by corporate free loading. I’m very much in support of Cloudron’s “source available” approach.

I actually totally agree with a “subscriber walled forum”. Communicating in forums uses scarce people time. Copying source code takes no time. Which is why I advocate for permissive source but gated “community” access.

And of course — licenses can evolve. For instance, the Big Time License is free to use for companies less than 20 people and/or less than $1MUSD in revenue. It’s not an open source license as defined by the OSI, but it’s a great “fair” license.

But no charge for code is still separate from subscription/ service fees!

[marcusquinn]

@bmann The forum has significant SEO value for generating awareness, I think that the openness of the community adds value, since anything that grows the user base, benefits all users as the development grows with it.

[bmann]

@marcusquinn my main point was that there is zero marginal cost to copying bits of code and there are infinite copies of the source code, and that all the expensive time is eg responding to Gitlab issues from non-paying subscribers, which uses scarce people time who only have so many hours in the day.

Whether it’s an effective conversion tool to paying subscribers is a separate issue.