6 ms·

You have another option, keeping the GNU GPL as a license and avoiding this time-shift complexity: sell the binary, and offer the source only to those who buy t

You have another option, keeping the GNU GPL as a license and avoiding this time-shift complexity: sell the binary, and offer the source only to those who buy the binary -- don't make the source code public on github. It's not only possible but it's what sustained many GNU projects, until they were acquired by others. Nobody in the comments mentioned the most successful case: Cygnus Solutions had been developing the GNU Compiler Collection (GCC) for good money, all under the GNU GPL. Notably, they made a lot of cash from a deal with Sony to support the original Playstation in gcc. A good read about how they marketed Free Software on John Gilmore's pages: http://www.toad.com/gnu/cygnus/ http://www.toad.com/gnu/cygnus/

CiPHPerCoder 10y ago
People confuse Free Software to mean gratis rather than libre. It can be, but it doesn't have to be.
- dragonwriter 10y ago
  > People confuse Free Software to mean gratis rather than libre. It can be, but it doesn't have to be. It doesn't have to be initially, but once you redistribute it to others with the permission to redistribute it that defines Free Software, the probability that you end up competing with gratis derivatives of the same code base tends to unity over time. So, Free-for-a-price software really relies on a premium price charged to early users (often only the first user); IOW, its more like selling bespoke software development services than like selling other software licenses.
IshKebab 10y ago
That definitely would only work where you can get paid for customisation. GCC is probably the best case scenario. There aren't many megacorps that would pay you loads to customise a code search engine.
SamBam 10y ago
> offer the source only to those who buy the binary But don't the receivers of the source then have the same right to redistribute it without charging?
- randoramax 10y ago
  And why would they do that? Try know well that they get support and features from the author, they gain nothing from sharing something they paid for. There is no economic incentive
dragonwriter 10y ago
> sell the binary, and offer the source only to those who buy the binary -- don't make the source code public on github. The problem with that model in many software markets is that the proven value of the bazaar development model means that when you do that, eventually one of the purchasers of the binary is going to make the code public (because the GPL means they can), and once they do that, the cat's out of the bag, and people (both users and alternate service vendors) can roll their own binaries), commoditizing the software and reducing (likely, eliminating) your ability to charge for binaries rather than ancillary services like support and custom development.
- slgeorge 10y ago
  Selling the binary is difficult, which is why it's best to provide a "service" of a mix of things which also happens to include access to the binary. Then, you can refuse to provide future service if the end-user makes the code public. It's a bit sticky, because the GPL doesn't allow any constraint on distribution. However, the argument intellectually is that you're not stopping distribution you are merely refusing to deliver the "service" due to a breach of the service agreement - "I'm not stopping you distribute, I'm saying if you distribute then I won't be providing this separate service X". Here's a 2014 example from a RedHat APAC service agreement: "Distributing the Software or any portion of the Subscription Services to a third party or using any of the Subscription Services for the benefit of a third party is a material breach of the Agreement even though the open source licenses applicable to individual software packages may give you the right to distribute those packages (and this Appendix is not intended to interfere with your rights under those individual licenses)" Where: "Software” means Red Hat Enterprise Linux, JBoss Enterprise Middleware and other software programs branded by Red Hat, its Affiliates and/or third parties including all modifications, additions or further enhancements delivered by Red Hat. URL: http://jp.redhat.com/licenses/apac_enterprise_agreement_appendices_one_and_two_webversion_japan_20141111.pdf http://jp.redhat.com/licenses/apac_enterprise_agreement_appe...
blackorzar 10y ago
Add to this idea the Redhat-Centos rulebook: Make the project name and assets with trademarks (non GPL) so if the customer wants to distribute the code they need to rip off the trademarks (name and images) from the project.

CiPHPerCoder 10y ago

People confuse Free Software to mean gratis rather than libre. It can be, but it doesn't have to be.

dragonwriter 10y ago
> People confuse Free Software to mean gratis rather than libre. It can be, but it doesn't have to be. It doesn't have to be initially, but once you redistribute it to others with the permission to redistribute it that defines Free Software, the probability that you end up competing with gratis derivatives of the same code base tends to unity over time. So, Free-for-a-price software really relies on a premium price charged to early users (often only the first user); IOW, its more like selling bespoke software development services than like selling other software licenses.

IshKebab 10y ago

That definitely would only work where you can get paid for customisation. GCC is probably the best case scenario. There aren't many megacorps that would pay you loads to customise a code search engine.

SamBam 10y ago

> offer the source only to those who buy the binary But don't the receivers of the source then have the same right to redistribute it without charging?

randoramax 10y ago
And why would they do that? Try know well that they get support and features from the author, they gain nothing from sharing something they paid for. There is no economic incentive

dragonwriter 10y ago

> sell the binary, and offer the source only to those who buy the binary -- don't make the source code public on github. The problem with that model in many software markets is that the proven value of the bazaar development model means that when you do that, eventually one of the purchasers of the binary is going to make the code public (because the GPL means they can), and once they do that, the cat's out of the bag, and people (both users and alternate service vendors) can roll their own binaries), commoditizing the software and reducing (likely, eliminating) your ability to charge for binaries rather than ancillary services like support and custom development.

slgeorge 10y ago
Selling the binary is difficult, which is why it's best to provide a "service" of a mix of things which also happens to include access to the binary. Then, you can refuse to provide future service if the end-user makes the code public. It's a bit sticky, because the GPL doesn't allow any constraint on distribution. However, the argument intellectually is that you're not stopping distribution you are merely refusing to deliver the "service" due to a breach of the service agreement - "I'm not stopping you distribute, I'm saying if you distribute then I won't be providing this separate service X". Here's a 2014 example from a RedHat APAC service agreement: "Distributing the Software or any portion of the Subscription Services to a third party or using any of the Subscription Services for the benefit of a third party is a material breach of the Agreement even though the open source licenses applicable to individual software packages may give you the right to distribute those packages (and this Appendix is not intended to interfere with your rights under those individual licenses)" Where: "Software” means Red Hat Enterprise Linux, JBoss Enterprise Middleware and other software programs branded by Red Hat, its Affiliates and/or third parties including all modifications, additions or further enhancements delivered by Red Hat. URL: http://jp.redhat.com/licenses/apac_enterprise_agreement_appendices_one_and_two_webversion_japan_20141111.pdf http://jp.redhat.com/licenses/apac_enterprise_agreement_appe...

blackorzar 10y ago

Add to this idea the Redhat-Centos rulebook: Make the project name and assets with trademarks (non GPL) so if the customer wants to distribute the code they need to rip off the trademarks (name and images) from the project.