I am working on the commercial offshoot of Freebasic. Some main command names and little structure would be different. And there would be inbuilt GUI support.
It would have it's own IDE, tutorials, help file, etc.
But I'm I legally allowed to do so?
Commercial Offshot permission
-
counting_pine
- Site Admin
- Posts: 6323
- Joined: Jul 05, 2005 17:32
- Location: Manchester, Lancs
It is my understanding that the license permits you to make changes to the compiler/libraries - as long as your changes are released under a compatible license; and to charge money for distributing copies of FB or a derivative - although you cannot restrict those people from redistributing it to others.
If you make an IDE that doesn't statically link to the compiler then you can release/sell it under whatever license you want.
I would say though, that if you release your program under the FreeBASIC name but change the language so that programs written for your version no longer work in the original FreeBASIC, then that could hurt FreeBASIC users.
If you make an IDE that doesn't statically link to the compiler then you can release/sell it under whatever license you want.
I would say though, that if you release your program under the FreeBASIC name but change the language so that programs written for your version no longer work in the original FreeBASIC, then that could hurt FreeBASIC users.
-
leodescal
- Posts: 165
- Joined: Oct 16, 2009 14:44
- Location: Jodhpur, Rajputana, Empire of Aryavart
- Contact:
I wouldn't release it under name free basic. But with a new name. I.E. 'Royal Basic'.
98% of Free Basic programs wouldn't run on it. And 99.9999999999999999999999999999999999999% of Royal Basic programs wouldn't run on FreeBasic.
I'm adding many new thing like better structure, command name, etc. So why must I allow it's open distribution?
If I am changing the name and source, then wouldn't I get a new copyright?
98% of Free Basic programs wouldn't run on it. And 99.9999999999999999999999999999999999999% of Royal Basic programs wouldn't run on FreeBasic.
I'm adding many new thing like better structure, command name, etc. So why must I allow it's open distribution?
If I am changing the name and source, then wouldn't I get a new copyright?
-
Lachie Dazdarian
- Posts: 2338
- Joined: May 31, 2005 9:59
- Location: Croatia
- Contact:
The compiler is under the terms of GPL and its rtl and gfx under LGPL. It means, if you use the compilers sourcecode and change it, it's called 'derivative work'. For GPL this means, you have to publish the code under the terms of GPL and for LGPL it has to be LGPL or GPL.
Actually, you can't take the fbc and make a closed source new compiler out of its source, or we'll sue you.^^
Actually, you can't take the fbc and make a closed source new compiler out of its source, or we'll sue you.^^
Because the license requires you to do so.leodescal wrote: I'm adding many new thing like better structure, command name, etc. So why must I allow it's open distribution?
From the file GPL.txt:
If you are not going to respect this license... why should anybody respect yours?
if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
Sometimes, a software can have more than one license (it's called dual licensing): i.e. an open source version, available for free, and another version that can be used in closed source projects (that's what you need); so, maybe you could ask V1ctor (the original FreeBasic author) if he can give you a special license to use freebasic source code inside a proprietary compiler: but I doubt that such a license would be available for free; you'd have to pay for it, I believe.
My hint is: if you want to build a FreeBasic-derived compiler, release it with the source code, under GPL license: you can still sell cd-roms, provide support for a fee, ask for donations.
Forget about closing the source code.
And read this guide:
http://www.damnsmalllinux.org/income-guide/
because open source based business model is really different from copyright-based model.
I would say
you have to be careful not to be seen to abuse the hard work the creators of FreeBASIC have put into the open source project
Few Pointers
If you want your product to A sell and B have any a decent number of users then you have to consider making it compatible to some extent with other versions of basic
To deliberately make your basic incompatible with others is a big mistake
(unless u have some uber duber plan that can be executed to perfection)
another way to commercialize free basic is to polish up the system, eg excellent IDE , tutorials everything in one box cd+book
In this scenario You don't charge for Freebasic , it comes free on the cd. But you can charge for the Book, box & any IDE you create
Example a teachers pack with student guide that comes with multiple cds that contain the free , freebasic code + video tutirials , clasroom guides , general programming guide.
Customers would be willing to pay for such a product if by buying it it reduces the headstrain and makes life easy for them....why else would they shell out $ ?
If you make few bucks out of it then it wont hurt to send a few bucks in the creators direction. It would also boost the number of users of freebasic in the world.
Creating and selling Quality Help + Quality IDE is morally ok.
While there is nothing to physically stop you nicking all the source code and creating a new branch, if you start specifically charging for that new branch which contains masses of open source code things get morally tricky fast.
It is also prolly true that 50% of all commercial ever written code is stolen to a greater or lesser extent , ask Gates & S.Jobs R.I.P for details.
But i think it is wise to keep enemies to a minimum
The world would benefit from a mass market release of FreeBasicPRO or something very similar to it. A great deal of money could be made and a great deal of utility could be given to the world in the process.
If your project is perceived as a hit and run code grab with nada feeding back into the ecosystem then you will get a negative response from the community.
I am interested in expanding the Freebasic ecosystem. If done right FreebasicPro , (a polished variant of freebasic) could make a big positive contribution to the opensource freebasic community
I would be interested in getting involved in a commercial variant of freebasic but only so long as it didn't stamp all over the goodwill of the freebasic community and all who have contributed to it
It is perfectly viable, moral & feasible to have a dual ecosystem
open source freebasic , just doing its thang as it always has
and FreebasicPRO , a highly polished variant that enhances the ecosytem
IBM clone hardware , and pirated copies of windows and dos gave the world a single compatible hw/sw architecture....something of great value.
Once open source adds a small commercial wing to its ecosystem it can dominate.
" Intelligence acting without goodwill is apt to be evil
Goodwill acting without intelligence is apt to be impotent"
The full power and utility of open source cannot ever be released and conquer the world unless at least 1 branch of its ecosystem is softly commercialized in 'harmony' with its open source core
The commercial branch has to be of world class standard , or the whole thing will be a waste of time money and effort for all involved....forget about pocket money commercialization, you have to intend to win & be the winner by simply being the best value & utility on the market.
The grave marked second place is many miles deep !
I use freebasic because it is as good as and perhaps better than many commercial versions of basic......and its free !.....it only scores 4 outa 10 , but for the price i paid ( some hassle ) it was a fair purchase
I would happily pay $10 to $50 for FreebasicPro
Features like 1 click installation , Compatibility with all versions of windows, 64 bit futureproofing , #1 codebank & tutorials, interactive tutorials, established community etc is why i would shell out
Warning
Any commercial version of Basic , wether it be FreebasicPro or Royal basic has to consistently score 8+ or its dead in the water
150 Versions of Basic Listed
http://www.nicholson.com/rhn/basic/names.basic.txt
Few Pointers
If you want your product to A sell and B have any a decent number of users then you have to consider making it compatible to some extent with other versions of basic
To deliberately make your basic incompatible with others is a big mistake
(unless u have some uber duber plan that can be executed to perfection)
another way to commercialize free basic is to polish up the system, eg excellent IDE , tutorials everything in one box cd+book
In this scenario You don't charge for Freebasic , it comes free on the cd. But you can charge for the Book, box & any IDE you create
Example a teachers pack with student guide that comes with multiple cds that contain the free , freebasic code + video tutirials , clasroom guides , general programming guide.
Customers would be willing to pay for such a product if by buying it it reduces the headstrain and makes life easy for them....why else would they shell out $ ?
If you make few bucks out of it then it wont hurt to send a few bucks in the creators direction. It would also boost the number of users of freebasic in the world.
Creating and selling Quality Help + Quality IDE is morally ok.
While there is nothing to physically stop you nicking all the source code and creating a new branch, if you start specifically charging for that new branch which contains masses of open source code things get morally tricky fast.
It is also prolly true that 50% of all commercial ever written code is stolen to a greater or lesser extent , ask Gates & S.Jobs R.I.P for details.
But i think it is wise to keep enemies to a minimum
The world would benefit from a mass market release of FreeBasicPRO or something very similar to it. A great deal of money could be made and a great deal of utility could be given to the world in the process.
If your project is perceived as a hit and run code grab with nada feeding back into the ecosystem then you will get a negative response from the community.
I am interested in expanding the Freebasic ecosystem. If done right FreebasicPro , (a polished variant of freebasic) could make a big positive contribution to the opensource freebasic community
I would be interested in getting involved in a commercial variant of freebasic but only so long as it didn't stamp all over the goodwill of the freebasic community and all who have contributed to it
It is perfectly viable, moral & feasible to have a dual ecosystem
open source freebasic , just doing its thang as it always has
and FreebasicPRO , a highly polished variant that enhances the ecosytem
IBM clone hardware , and pirated copies of windows and dos gave the world a single compatible hw/sw architecture....something of great value.
Once open source adds a small commercial wing to its ecosystem it can dominate.
" Intelligence acting without goodwill is apt to be evil
Goodwill acting without intelligence is apt to be impotent"
The full power and utility of open source cannot ever be released and conquer the world unless at least 1 branch of its ecosystem is softly commercialized in 'harmony' with its open source core
The commercial branch has to be of world class standard , or the whole thing will be a waste of time money and effort for all involved....forget about pocket money commercialization, you have to intend to win & be the winner by simply being the best value & utility on the market.
The grave marked second place is many miles deep !
I use freebasic because it is as good as and perhaps better than many commercial versions of basic......and its free !.....it only scores 4 outa 10 , but for the price i paid ( some hassle ) it was a fair purchase
I would happily pay $10 to $50 for FreebasicPro
Features like 1 click installation , Compatibility with all versions of windows, 64 bit futureproofing , #1 codebank & tutorials, interactive tutorials, established community etc is why i would shell out
Warning
Any commercial version of Basic , wether it be FreebasicPro or Royal basic has to consistently score 8+ or its dead in the water
150 Versions of Basic Listed
http://www.nicholson.com/rhn/basic/names.basic.txt
-
vladimir777
- Posts: 94
- Joined: Aug 19, 2011 18:28
99.9999999999999999999999999999999999999% of Royal Basic programs wouldn't run on FreeBasic.
=======================
If this is true then go DO IT! I am giving you permission. Just insert a line
in every file:
Permited by Vladimir777
If you dont do it then prepare to talk to my lawyer!
=======================
I like 99.99999999 stuff
Also I like name: Royal
c:>RBC myroyalprogram.rbc
sounds great
==========================================
He is joking! A couple months ago he was asking very basic questions like how to read text file etc
==========================================
There is a company selling support for pascal-lazarus devlopment:
http://www.lazarussupport.com/
=======================
If this is true then go DO IT! I am giving you permission. Just insert a line
in every file:
Permited by Vladimir777
If you dont do it then prepare to talk to my lawyer!
=======================
I like 99.99999999 stuff
Also I like name: Royal
c:>RBC myroyalprogram.rbc
sounds great
==========================================
He is joking! A couple months ago he was asking very basic questions like how to read text file etc
==========================================
There is a company selling support for pascal-lazarus devlopment:
http://www.lazarussupport.com/
You can easily write a book about programming in FreeBASIC and take cash for it.
FreeBASIC is not a registered trademark, so you could probably take some money for t-shirts (at least the value of the t-shirt+work+shipping).
If you zip the compiler with other programms, you can take cash for the other programms, but not for fb itself and you have to provide a gpl copy with fb. If you link the fbc in any way, it would be a derivative work and you have to provide the source, but - you can sell a disc with this open source pakage and take money for support. Until v1c forbid it, you could do this even with plain fb as long as it stays open source. As the author of FreeBASIC, he can prohibit it without problem or just give you the freedom.
For tutorials etc. it's like with books. You are the author and you can do what you want...
FreeBASIC is not a registered trademark, so you could probably take some money for t-shirts (at least the value of the t-shirt+work+shipping).
If you zip the compiler with other programms, you can take cash for the other programms, but not for fb itself and you have to provide a gpl copy with fb. If you link the fbc in any way, it would be a derivative work and you have to provide the source, but - you can sell a disc with this open source pakage and take money for support. Until v1c forbid it, you could do this even with plain fb as long as it stays open source. As the author of FreeBASIC, he can prohibit it without problem or just give you the freedom.
For tutorials etc. it's like with books. You are the author and you can do what you want...