Did I miss something where Commandbox is no longer an open source free project in the latest version? Are we about to need to CentOS this thing?! lol

CommandBox Pro will licensed: https://www.ortussolutions.com/products/commandbox-pro

@Patrick @mjclemente Where on earth did you read anything like that?

But Dick's question was is COmmandbox v6 a free version AKA never said the word "Pro" in his statement; so is that implying that v6 and on are only under the "Pro" realm?

He referred to multi-site which is a Pro feature

lol - all good - it just sounded like there was a change with v6, based on the question

I didn't clarify that in his thread since it seemed he already understood the pro/multi-site differentiation

Ahh so if someone wanted to make those features and request PR's to the open source version then there wouldnt be any Ortus pushback to protect the "Pro" model??

Technically, you can buy a pro license now with COmmandBox 5. In fact, we have customers already

This sounds like smoke and mirrors to buy a license that isnt necessary then?

We're doing some nominal checks via ForgeBox to ensure you paid, but currently aren't spending a lot of effort to enforce it. We trust people not to rip us off, and if they do they can sleep with that at night

You just said all the features are available in the free open source version

No, I said the CODE is there

For example, if the multi-site feature is in the CODE on the free version then why do I need to buy a license to do more than X sites?

then why do I need to buy a license to do more than X sites?

Because it would be illegal 🙂

What license does Commandbox reside under? Guess need to read

There's a little thing called a EULA which is a legally binding agreement you enter into when you install software

So Commandbox = NOT OPEN SOURCE then correct?

no, I honestly don't know where you're getting this from, lol

yea I want to read more, what is the license it is under?

LGPL, and we'll modify our EULA according to clarify what additional licensing agreement the new features will fall under

So I can technically fork it, make these features if I wanted and redistribute it as boxxyboxbox if I hypothetically wanted to

Well first off, that would be a dick move, but we'll make sure we clarify in the 6 license so that's not possible 🙂

You're in luck Patrick - boxxyboxbox.com is available

I wasn't planning on changing the license in 6, but just clarifying what features will require additional licensing from Ortus. If you're serious about trying to rip it off, then maybe we'll need to move part of the new code to a different repo so it can have a different license

Not that I would I would actually fork it, I appreciate the community; it just comes off very corporate move vs community/open source when it has such a vast use in the community then gets converted into a Corporate locked down tool to generate $ and the community was dependent on VS a true open source community like Linux for example.

Well, I just said that no features in CommadnBox 5 are being removed or "locked down" so I'm not sure why you would claim that

I am just wanting a crystal clear picture of what this is; I have no intention of forking etc...but it was coming off very smoke and mirrors to buy a license etc

We're not "going back" on anything that's currently open source, we're adding value to our products under a commercial license

Corporate is corporate and open source is open source; I get it, just never noticed it that way until actual licensing and restrictions came into play. It has always been conceived as Open Source I would say by most of the community. Also, I dont even see a EULA on 5.x anywhere.

That's right, we've never limited any features until now in the core. We've put them into modules. Multi-site is very much tied into how servers work in the core, so making a "multi-site" module would be a pain and would actually make it even harder for everyone to use it for free on development.

I like the product, but in the end Ortus can do what they like, and the community can do what it likes. Dont like Licenses, then go with Lucee.

Well, I need to figure out how we'll handle our licensing before we release anyway. A lot of open source software with commercial features use a dual license approach. Couchbase is an example of this.

Firstly, I know nothing about software licensing so I won't comment on that. Secondly, we all benefit from the Open Source efforts of others and some of us contribute in anyway that we can, however small, but people need to eat and have shelter so they need compensation for some of their efforts. I have, personally, bought and upgraded an ACF licence in the past, most, if not all, of the books that have been produced by this community and am a Patreon of both Ortus and Lucee. I have been lucky and enjoyed a successful career in the world of CFML so I'm happy to pay to support others who support us. Finally, I have been eagerly awaiting the release of CommandBox Pro, especially its multi-site abilities but I'm finding the pricing model hard to justify. I have recommended the CommandBox Service Manager to several clients that has resulted in at least 15 sales and it has been seen as good value. So there is a market for enhanced CommandBox features. My issue is that too many other products and services have been bundled into the product that could have been made optional and this has inflated the price beyond what will be seen as good value.

If you have any questions about the Pro licensing, I certainly recommend reaching out to Ortus. While I'm the main developer, the pricing model has been work on by our internal marketing team and I'm sure they'd value any feedback.

Not to throw a monkey wrench in your statement, but that is what Canonical does. (Makers of Ubuntu) It is open-source, but support beyond public forums comes at a cost.