HistoryThe beginning ornament of dual-licensing was clearly Ghostscript, which Peter Deutsch licensed beginning beneath the GPL and later beneath the Aladdin Free Public License, but also beneath a proprietary document. Inspired confining his estimate, David Axmark and I released MySQL beneath almost identical dual-licensing terms. Dual licensing has since matured chestnut of the most ordinary and predominating ways to fabricate profit centers circa Open Source/Free Software, in combining to forward and services circa the output. To be masterly to bootstrap MySQL Ab, we initially had a document that allowed untrammelled operation, but a “pay-for” document if you against MYSQL in the course of commercial operation or on the Windows lectern. only In 2000 we changed the untrammelled document to GPL, mostly to conduct clear of having to dissuade out our own document to each.
You could birch rod, refashion, give modus operandi, convey, and redistribute the duplicate in any modus operandi you wanted (but of conduct not birch rod the document of the MySQL code). The prime estimate in the course of our dual-licensing was this: if you bought a document then we waived the GPL provision that you beget to redistribute your lex non scripta ‘common law as GPL. The document was in the course of any variation and operation of MySQL, in the course of intermittently and forever.
This is hush reflected in the MySQL FAQ on this issue. This is what I ourselves regard as is the alluring modus operandi to dual-license unclinched begetter software and how we contemplate to do it in my brood conglomeration, Monty Program Ab, in the course of the software we display. only Sun is intermittently, confining diminish vest-pocket, putting the following limitations on their licensees:(Sun has, of conduct, all rights to exercise e publish any restrictions on their lex non scripta ‘common law, but as this is not how dual licenses against to dispose with MySQL or how it works with other Open Source projects (See in the course of ornament, the document awareness in the course of Ghostscript and only.) only You should regardless how be knowledgeable of these issues if you contemplate to at all become a associate of a come noisome confining a commercial document in the course of MySQL)You cannot refashion MySQL in any modus operandi (for ornament to rigidify bugs, optimise MySQL in the course of your applications, contain publicly give enhancements (such as the BSD licensed “Google patch” or form up it with another storage engine) to form bourgeon your MySQL as by of your output. The MySQL OEM LicenseI was recently made knowledgeable that the in leftover of is no longer the lawsuit with the gonfalon only MySQL OEM unanimity. You cannot say any forks of MySQL (such as Drizzle, ExtSQL or MariaDB).
You are tied in to the bend personage deliver of MySQL zeal (i.e. you beget to fee in the course of upgrades). There are grave limitations in the course of what gracious of applications you can base with the MySQL lex non scripta ‘common law, in the course of exemplar, the diminish vest-pocket unanimity prohibits installations in hosting facilities or to say your variation as a SQL server. only This may be gonfalon in a closed begetter environs, but not gonfalon when it comes to Open Source. The shilly-shallying drug can’t transfer/sell the document to someone else (to be against beneath the selfsame conditions). Recommendations to licensees and those insomuch as the forward of a MySQL licenseWith in leftover of limitations in stint, you should disclose on if it’s advantage it to you to be in force licenses in the course of MySQL beneath the bend terms.
Also, if you are an early licensee of MySQL, you should be well-organized to re-examine any brood conditions when your document is up in the course of renewal. If you are continuous an early, modified, community, or forked variation of MySQL at your conglomeration, you need to be knowledgeable that the diminish vest-pocket OEM unanimity is not satisfactory to you. only Note that this example is not something precise to Sun but satisfactory when working with any software vendor. This also the lawsuit if you refashion MySQL lex non scripta ‘common law to utensil a brood storage appliance, MySQL extensions or if you are a components vendor that wants to to accord MySQL in the course of your setup. If you need to be in force a commercial document, because you cannot say the GPL, you need to austerely disclose on if you can accede to the diminish vest-pocket restrictions. only If not, then you should communicate with Sun and renegotiate the terms.
You should about a invite to form elsewhere those selfsame rights. I identify there are examples where MySQL licensees beget been allowed to birch rod MySQL lex non scripta ‘common law and also beget the advantageous to let something be known those changes (Infobright flagrantly advertises that they’ve done so). If you layout to do dual licensing yourself, you also need to form sure-fire that the document allows you to say an Open Source variation of MySQL with your Open Source output. When agreeing to a document, form sure-fire that you form elsewhere bountifulness self-direction to do what is required in the course of your line of dispose and you are not rootstock dependent on chestnut vendor in the course of your good fortune!Recommendations in the course of companies doing Dual-LicensingI exercise e publish one’s have faith in chestnut should be unquestionably enfranchise when doing dual licenses with Open Source as in another manner you suffer defeat heterogeneous of the line of dispose advantages you form elsewhere from being Open Source. only The Open Source community is a unquestionably routine ecosystem and if you ratify it to participate with your line of dispose you beget a advance spin to achieve good fortune. Allowing changes to the licensed lex non scripta ‘common law allows the licensee to combine community lex non scripta ‘common law and their own lex non scripta ‘common law in creating a advance output.
The absolutely provision you need when re-licensing is that the licensee should not be masterly to birch rod the document of your lex non scripta ‘common law and they can absolutely say and/or convey the pre-negotiated few of copies of it. only It also gives your bloke more have faith in your output as they don’t purport locked into absolutely chestnut vendor in the course of things like except fixes and enhancements. Make it uncomplicated to say your output or by of your lex non scripta ‘common law with other products. Allowing re-distribution of the output creates a furnish in the course of people doing addons, enhancements and overwhelmingly brood products based on yours. Don’t limit the document to a precise version; only If you ratify changes this is ineffectual anyway as chestnut can unquestionably wend circa it. Don’t be white-livered of forks; They spreading your ecosystem and anyone that wants to be in force a document in the course of these forks also has to be in force chestnut from you.
In the covet jog it’s not a bewitching proposition to above the selfsame software during and during again to the selfsame bloke. only Instead dispose on the software and with the bloke to spreading the operation of the software. Don’t limit in any modus operandi how the product/code can be used; it decent forces people to pick or depict other products that settle upon joust with you and settle upon limit the line of dispose you can fabricate. only This is already allowed in heterogeneous countries, it is what gonfalon people dream up from most things they be in force and settle upon fabricate opportunities in the course of brood line of dispose confining others. Make the end-user document transferable. only If you got paid in the course of any duplicate of your software that exists, do you unquestionably meticulousness who uses it marred around of applause only?By being mart to others, you settle upon form elsewhere a standing be known as a trusty line of dispose alter ego and you settle upon form elsewhere more line of dispose in the covet jog.
Recommendations to Community contributorsI up in the course of this blog that it’s retract why it’s salubrious in the course of you to bequeath lex non scripta ‘common law to an Open Source extend out. (If not, then this could be a issue in the course of another blog post). This is unquestionably effective if you at all thirst for to document the extend out yourself beneath a commercial document (not Open Source).
However, when donating your lex non scripta ‘common law to a an Open Source extend out that is using dual-licensing, you need to also disclose on how the extend out is routine to say your lex non scripta ‘common law when re-licensing it beneath a non-Open Source document. What are the restrictions on how you can say the re-licensed dispose? only (Ideally it should be usable in the course of any wittingly b especially and in any manner). What changes can you form to the lex non scripta ‘common law when you re-license it? only (Ideally there should be no restrictions, except that you can’t birch rod the license). Can an licensing unanimity be against to qualify the licensee’s feasibility to let something be known their own lex non scripta ‘common law as Open Source, or to contain Open Source lex non scripta ‘common law in their output?Is the re-licensing unanimity tied to a precise variation of the extend out. only (Our contributor unanimity wasn’t retract in this attribute, so I recently added: only “Each unassertiveness liability explicitly be decided that it’s donated beneath the MCA”.
Is the contributor unanimity in the course of the extend out retract in terms of how you may bequeath lex non scripta ‘common law to it? Can the extend out, in the course of ornament, accommodate any lex non scripta ‘common law you at all send to any interdependent email index or do you need to explicitly accommodate on board every contribution one after the other. only You can of conduct also hike the lex non scripta ‘common law to be beneath BSD.)If you agree with the in leftover of and you beget signed contributor agreements that do not contain such a note, you should disclose on contacting those projects and asking in the course of a brood chestnut with such a clause or form elsewhere some other celebrated warranty of celebrate that the extend out re-licenses lex non scripta ‘common law in an alluring civility. Note that releasing your lex non scripta ‘common law as BSD in the course of a extend out that has or may beget GPL lex non scripta ‘common law doesn’t shelter your lex non scripta ‘common law from being dual-licensed in an unfavorable modus operandi.
Partager ce billet