GPL and BSD

In summary
The free market isn't free because ideas can't be freely implemented due to lack of UnlimitedBandwidth, patents, copyright and the GPL restriction from Stallman's Free software foundation(Restricted software foundation). What CNN refers to as the 'free market' is the 'rigged market', large corporations bribe the senate and congress to make copyright and patent laws forbidding the free market.

HackPatents the designs on Wind energy, communications etc. and sell using a fronting company, one can't go to jail for civil debt in South-Africa as per a constitutional court ruling. Since the empowerment partner as the CEO of the fronting company has no assets to begin with, he has nothing to lose. This is a significant loophole to exploit in South-Africa to bypass patents. Corporations is being equivocated with capitalism. Large corporations use their monopoly powers to prevent the free market from operating with HackPatents. Through deception by NBC (controlled by corporate GE) the corporatism is equated with capitalism, much like Richard Stallman(RMS) Newspeaks a restriction(GPL) into a freedom(BSD). GE owns the patents on Wind energy, enabling them to sell wind turbines at any price, by deceiving the public to vote for the Democrats to solve a problem that doesn't exist Global warming, BatteryTech, they legislate their own laws to benefit corporate GE.

Restrictions such as copyright and patents (patent royalties) leads to unintended consequences because powerful actors corrupt the good intentions. Companies are paying their own shell companies which they own through indirection "royalties" and deducting this from tax. The GPL restriction from the copyright holder is being used to emulate the effect of patents.(GPL_and_BSD). Employing the Linux GPL copyright holders allows Google, Oracle and Redhat to practice selective communism: communism is the centralization of ideas and the regulation of their implementation. (SCO unix couldn't figure this out.) http://www.fsf.org communist RMS wants to worlds governments to sign over all copyright to him personally so he can live out his atheist fantasy of telling everybody what to do. RMS, Torvalds and Eric Raymond have deceived coders to hand sign over the copyright on key algorithmic abstractions such as 'Mount' to Redhat. Because they wanted to promote themselves, they lied about the fact that open source is not public domain nor Equality source. Key linux copyright holders were given pre-IPO stock options and became employees of Redhat etc.

The GPL license on the gcc compiler applies only to the licensees(slaves) and not to Richard Stallman himself. With Equality source the public domain is emulated. Linus Torvalds assures us his GPL licensing as a copyright holder is based on exchange: you release your code, and Torvalds in exchange will give more code back. But this is not an obligation on his part as licensor, many GPL copyright holders license their code in closed source projects for remuneration without anybody knowing about it. Google, Redhat and IBM's editorial shills on wikipedia are twisting the legally defined dichotomy between public domain(free) and copyright(proprietary) as determined by the courts by refusing that this factual information be included in their "open source" and "Free software" articles. All information is either proprietary or public domain: only a copyright holder can license code as GPL, BSD, Microsoft EULA or coo-coo-clock license.

Redhat emulates the effect of being sole copyright holder of Linux GPL because they employ the copyright holding coders. In addition under copyright law Redhat and its employees are considered a single entity. The extension of the Unix operating system must be done on an Equality source basis, the same way English language is public domain. It is the ecosystem that allows commercial and non-commercial ideas to be implemented, preventing wannabee atheist dictators such as RMS telling everybody what to do and think. IBM, Redhat, Google and other "corporate sponsors" of the Linux kernel programmers(Cox, Torvalds), employ these very same programmers and copyright holders. Google's Android system uses Linux code without releasing back such modifications(GPL_and_BSD). These companies are employing the copyright holders to Linux GPL as an assault weapon to attack their competitors, it isn't being used to expand the code base primarily. US constitutional restrictions preventing spying by domestic agencies on citizens are circumvented by contracting the spying on Google accounts to the UK spy agencies, any restriction or forced behavior can be subverted by indirection.

The Creative commons license non-commercial is but another means of emulating the effect of a patent, in addition nobody knows what exactly defines 'commmercial'.

Confused? You should be, SCO Unix couldn't figure it out. They correctly asserted that you can't make money by giving everything away for free. What they could not grasp is that by using Churches thesis the illusion that Equality source is created under GPL by the effective copyright holders IBM, Google, Redhat, RMS and Torvalds employing the copyright holders who have commit rights to the Linux kernel tree. Instead if SCO had been advised by the same smart lawyers(Eben Moglen who explained to IBM and Google how to harness the enthusiasm of millions of GPL'd deceived using the weasel terms like "open source", they might have been a Redhat themselves.

Proprietary

 * http://en.wikipedia.org/wiki/Proprietary_software "....Proprietary software or closed source software is computer software licensed under exclusive legal right of the copyright holder with the intent that the licensee is given the right to use the software only under certain conditions, and restricted from other uses, such as modification, sharing, studying, redistribution, or reverse engineering.[1][2] Usually the source code of proprietary software is not made available.

Complementary terms include free software,[2][3] licensed by the owner under more permissive terms, and public domain software, which is not subject to copyright and can be used for any purpose. Proponents of free and open source software use proprietary or non-free to describe software that is not free or open source.[4][5]  ..."

GPL and BSD thought experiment
Imagine as a thought experiment that all the source code in the world is handed over to Google as sole copyright proprietor under the BSD license. This means that everybody has access to the same code under the BSD license, with the exception of Google who as copyright holder can license such code under a different license(fruitcake license for example) to other parties without having to even make this public. Now imagine the same the code is instead vested in Stallman under the GPL license as sole copyright holder: what power would this give an atheist to enforce his will on the world? Communism is the centralization of ideas, this is not bad of course if you happen to be the person on whom it is centralized. It's the freemarket for IBM, Redhat, Google employing the GPL copyright holders and communism for the rest of us.

Gpl newspeak, http://www.gnu.org/licenses/why-assign.html all code contributors to FSF are obliged to sign over their copyright to RMS. Imagine the implication if Richard Stallman could have all copyright of everything assigned to him personally. He would then be able to target Christians and Israel by discouraging manufacturers from providing them with hardware that of necessity will use such copyrighted code. It is a false premise that some fair dispenser of GPL justice by a Robocop walks around enforcing the terms of the GPL on an equality basis: GPL enforcement is arbitrary by the copyright holder, and such license does not apply to the copyright holder such as FSF.

The Linux (GPL) copyright holders employed by Google, IBM and Redhat allows these employers to dictate the behavior of those that don't employ the majority of them such as Nvidia and the hacker brewing the next Facebook in his garage. By employing the Linux copyright holders Google was able to create the Android operating system and not release back the code modifications because the GPL restriction only applies to the licensees and not the copyright masters, whom Google effectively control by their monthly pay check. Therefore the Linux code base can only be implemented in such a way as dictated by the Linux copyright employers, such as Redhat litigating against a hacker for incorporating the Linux "mount"(GPL2) command in order to destroy his business, yet allow another party to use "mount" in closed source projects after paying Redhat lots of money because the GPL restriction in MySQL, Mount etc. does not apply to Oracle and Redhat the copyright holders. GPL allows Oracle, Google and Redhat to use highly motivated slave labor who are confusing their access to the source with Equality source like *implementation* of the source. Having merely access to the source code is like somebody who thinks that having access to Solar energy patents is the same as implementing the ideas.

There is no company listed on an exchange that could possibly be a commercial viability if they were to publish all their ideas. Of necessity a start-up or hacker will incorporate GPL code to facilitate his products or business without publishing everything. GPL allows copyright holders such as Google and Redhat to practice selective communism. Communism is the centralization of ideas and the regulation of their implementation. Socialism is the centralization of the means of production. The distinction between these two concepts is fuzzy today because we are in the information age, it differs from its more dichotomous meaning during the times of Lenin and Stalin. Today with advances in robotics anything can be produced decentralized, this is being prevented with copyright emulating the effect of [[patents] and outright patents of course. Centralizing ideas in the hands of copyright holders such as Redhat, Google and IBM enables them to use indirection and prevent decentralized manufacturing.

Using Microsoft as a lightning rod for hacker discontent, Eben Moglen and RMS have deceived coders to sterilize vast swaths of algorithmic abstractions such as mount, ping, tracert, ncurses into copyright holders, which in turn are employed by Google, IBM, Redhat, Oracle etc. allowing them to prevent the implementation of unsanctioned code by competitors to these monopolies using Churches thesis. Prof.Moglen is on the same level as a trade unionist socialist wanting "job creation" - http://lwn.net/Articles/434318/. There are over 67 software licenses and thousands of "job creators", fabricating different incantations of copyright restrictions on the populace - the legal profession creating jobs for themselves. BSD Equality source limits the scope for money making litigation by the legal profession.

GPL imposes restrictions on what you can and can't do with code, in such a way that the restriction only applies to the non-copyright holders and not for example Oracle, the copyright holder of MySql. This enables Google, IBM, Redhat to 'Embrace, Extend, Extinguish' any would be competitor by either incorporating him as their indentured servant working for a monthly salary for them or ruining him financially with bogus copyright lawsuits.


 * By employing the coders who locked up algorithmic abstractions in the Linux GPL code base, as influenced by Linus Torvalds, RMS and Eric Raymond, Google, IBM, Redhat are emulating the effect of a software patent because they have gained effective control of the algorithms using indirection.

Redhat's employment of the Linux copyright holders allows them to litigate against any company or garage hacker making money out of Linux by forcing them to reveal all their code, while not imposing such litigated restriction on those who pay them lots of money to them or become their indentured servant.


 * http://www.freebsd.org/doc/en_US.ISO8859-1/articles/bsdl-gpl/article.html#GPL-ADVANTAGES
 * http://slashdot.org/story/99/06/23/1313224/FeatureGPL-vs-BSD
 * http://www.shlomifish.org/philosophy/computers/open-source/gpl-bsd-and-suckerism/
 * http://www.freebsdnews.net/2008/07/18/bsd-license-vs-gpl-license/
 * http://slashdot.org/~Chemisor/journal/143017
 * http://news.slashdot.org/story/08/07/08/1832255/Linguistic-Problems-of-GPL-Advocacy
 * http://www.freebsd.org/cgi/getmsg.cgi?fetch=506636+517178+/usr/local/www/db/text/1999/freebsd-hackers/19991003.freebsd-hackers
 * http://www.linuxjournal.com/article/5935 Explains how BSD allows ideas to remain free.
 * http://www.shlomifish.org/philosophy/computers/open-source/gpl-bsd-and-suckerism/ Arguments as why BSD must be used and not GPL

GPL adovates have missed one of the key points that makes the BSD license do so much good for the world. The BSD license, by allowing people to use its code in commerical products, promotes commercial products following open standards.

The classic example is TCP/IP. There are a lot of commercial products out there using the Berkeley TCP/IP stack, and one of the big reasons for that is that it's cheaper than developing their own protocol stack or even buying one. The value we see from this is the network effect; that a device communicates using the Berkeley TCP/IP stack rather than Novell's IPX stack or Microsoft's networking stack benefits all of us, because we can much more easily communicate with it (even, perhaps, in ways that the author did not intend). Open standards are even more important to freedom for computer users than open source. (Having source code and patents documenting an idea is nice, but it's not much good if it doesn't permit you to inter operate with other platforms out there or implement the idea itself. Linux is popular because it talks to other computers.) Therefore, I'd say that the Berkeley license has done more than any other license to bring us to the state today where we have a lot of freedom in our computing choices. Freedom means the freedom not to share an idea based on derivative ideas. A company is free to tweak the TCP/IP protocol in a commercial product without having to release the derived code, with GPL they would be forced to release any derivation.

The VLC project copyright holders relicensed their GPL code as LGPL, in order to allow the widespread adoption of VLC by companies who are not going to release their code as GPL or BSD etc. But because the copyright was not vested in a single or few authors but in *everybody* who contributed code, each of them had to be contacted and had to give permission. In the http://www.fsf.org incessant cult-like repetition of 'free software' they don't point out to programmers to be careful as to who will eventually own the copyright. This is deliberate because once to many programmers have copyright under say GPL3 or GPL then just one or a few copyright holders could prevent the majority from relicensing to something more sensible such as BSD or LGPL.

There is not a single idea held by anyone that isn't somehow a derivative of another idea by somebody else. GPL advocates expect to be recognized for 'their' ideas, ideas which are most probably somebody else's who didn't seek recognition. GPL doesn't allow a user the freedom to do with the code whatever he wishes, but like copyright and patents restricts its usage. A restriction isn't freedom, restricting the implementation of ideas leads to Unintended_consequences, such as the inability to commercialize an idea.

If the TCP/IP was released under GPL it would have prevented Microsoft from adopting it. Forcing Microsoft to use their proprietary protocol by forbidding them to use TCP/IP out of spitefulness could have established the Microsoft networking stack as a de-facto standard like their Office suite is a standard, with catastrophic consequences for society as a whole. Many GPL advocates are over-estimating their own importance and the importance of the code they contribute. They have an undue desire for recognition on trivialities - Parkinson's Law of Triviality, also known as bikeshedding or the bicycle shed example. GPL is a restriction placed on the licensee by the copyright holder, with such restriction not applying to the licensor. Freedom means that a person has the right not to share his derived ideas, with GPL thousands of developers are forced to share their ideas with the copyright holder like http://www.fsf.org, who in turn get corrupted by "corporate sponsors" to only enforce the GPL restriction against the competitors of powerful companies who have carved up the economy between themselves. Linux Torvalds for example recently received a "reward" by fronting organization for these corporate sponsors, a bribe for somebody who presents himself as a messianic figure handing out his autograph, to encourage Torvalds to do as they please(this needs citations, Torvalds prevents Stallman from forcing GPL3 on the Linux kernel because GPL suites corporations who employ the Linux kernel developers, thus buying themselves immunity from GPL enforcement, while corrupting the FSF to engage in arbitrary GPL enforcement against their competitors.)

GPL license is like the restriction on derived ideas we have with HackPatents, patents documents the idea, but doesn't allow its implementation without permission.

Open source or Equality source ?
"Open source" and RMS "free software" are not public domain. http://www.linuxtoday.com/developer/1999062802310NWSM Nowhere does Raymond make the distinction between public domain and proprietary code. BSD, MSFT closed, GPL, GPL3 etc. is defined as proprietary code by copyright law. There is no such thing as "open source" or "free software" in terms of copyright law, these terms are weasel-worded lies. The proprietors are free to call their master/slave relationship anything they want such as "I am little teapot licence", "free softwware licence" or "open source license", because copyright law allows them to do such. Any code acceptance by the FSF to their GCC compiler is done by the contributor signing over his copyright to the FSF. FSF remains the sole copyright holder. The copyright holders(there can be any number) of code under say GPL3 can licence such code in closed source(meaningless term?) projects without anybody knowing about it. Oracle for example are using the MySQL code base in their commercial products because they bought the copyright and do not have to publish their code as dictated by the GPL license, because the GPL license only applies to the licensees and not to Oracle, the sole copyright holder.

All code in terms of copyright law is either proprietary or public domain, a fact that Eben Moglen from http://www.fsf.org tries his best to conceal. Only proprietary code can be licensed as GPL, BSD and Microsoft closed license or any other license by a proprietary copyright holder: GPL code is defined as proprietary code by copyright law, RMS is legally and factually incorrect to assert the converse. BSD clause-3 is an attempt by a proprietor to emulate public domain while avoiding liability for code implementation and prevent public domain code winding up as GPL code.

RMS makes the distinction between "custom software" and "proprietory software" which is meaningless. Copyright law only defines something as public domain or proprietory.

Copyrigh on gcc compiler
http://www.fsf.org as the copyright holder of gcc must practice their freedom speech: why don't the fsf.org make lets say 10,000 coders fellow copyright holders?

The GPL license on the gcc compiler applies only to the licensees(slaves) and not to Richard Stallman himself or Linus Torvalds(masters). Eric s. Raymond regrets his initial support for GPL(this needs citations). Torvalds and RMS views open source code as philosophy, or pragmatic methodology where they as copyright holders of such open source code licenses(GPL) the code too thousands of code restrictees who must provide back their innovations to them, innovations they in turn can license in closed source projects but not allowing the restricted licensees to have the same rights as they have, since the GPL licensees working for free aren't the copyright holders. Using Newspeak they have deceived GPL coders into mistaking open source with Equality source: the terms under which the open source code is made open doesn't apply to the copyright holder, with Equality source the public domain is emulated. Linus Torvalds assures us his GPL licensing as a copyright holder is based on exchange: you release your code, and Torvalds in exchange will give more code back. But this is not an obligation on his part as licensor, many GPL copyright holders license their code in closed source projects for remuneration without anybody knowing about it.

The wikipedia commercial software, http://en.wikipedia.org/wiki/Proprietary_software , http://en.wikipedia.org/wiki/Free_software and http://en.wikipedia.org/wiki/Open_source obfuscations attempts to twist the legally defined dichotomy between public domain(free) and copyright(proprietary) as laid down by the courts. Every shred of information is either proprietary(restricted) or public domain(free, Equality source), which the Wikipedia articles don't make clear.

Redhat as single legal entity
Redhat is sole copyright holder of their distribution because they employ coders with such coders not becoming associate copyright holders because under copyright law Redhat and its employees are considered a single entity. The Linux kernel itself has thousands of copyright holders, while Redhat figured out a scheme whereby the can leverage GPL code but still maintain copyright (not sure about this, it needs further research). IBM, Redhat, Google and other "corporate sponsors" of the Linux kernel programmers, employ these very same programmers and copyright holders. They have come to an agreement that between them no GPL enforcement will take place, Google's Android system uses Linux code without releasing back such modifications.

Confused? You should be, SCO Unix couldn't figure it out. They correctly asserted that you can't make money by giving everything away for free. What they could not grasp is that by using Churches thesis the illusion that Equality source is created under GPL.

RMS wishes that if only the governments of the world would copyright the alphabet and sign over the copyright to him, then he as global idea atheist dictator will show us how communism is really supposed to work.

RMS ,Torvalds and FSF have deceived both GPL and BSD proponents. For some reason even http://www.freebsd.org seems either unable or unwilling to clarify the difference between copyright and public domain. MSFT bought the TCP/IP stack from the BSD copyright holders for $10mil. They did this to avoid having to give credit to the copyright holders as specified in the BSD license. If they used the TCP/IP stack as dictated by the license, then no payment to the owners of the BSD copyright would have been needed. The same type of exemption could have been made if TCP/IP was under GPL by the copyright holders. Both BSD and GPL proponents don't understand this legal fact in terms of copyright law.(Must all the copyright holders give permission?)

GPL is proprietary software
GPL is a copyright proprietary license; without an author who owns the copyright it is meaningless. An owner of the copyright must be established in order to make the copyright enforceable and license under which he licenses the code. The only alternative to this under copyright law is the public domain which is emulated with Equality source and not open source. All licensing such as GPL, BSD etc. is subject to copyright law. Proprietary is the characteristic of a proprietor, by having the exclusive legal right, or exclusive title to something, an owner. Proprietary software is owned software, the owner of the code can license his master/slave relationship under the following terms: Whether the licensing terms are meaninful or meaningless is irrelevent because copyright law allows the master to license as he wishes.
 * I'm a little teapot license
 * GPL
 * BSD
 * coo-coo-clock license

The FSF owns gcc through their copyright on the gcc compiler, they have retained exclusive legal rights to gcc. Red Hat is the copyright holder of Gluster and Oracle bought the copyright to MySql. Red Hat, Oracle and FSF as licensors of their proprietary software licensed their code to the licensee under the GPL license, the GPL restrictions only apply to the licensees and not the copyright holder. GPL regulates the behavior of software in a master/slave relationship, much like Microsoft regulates their users. Richard Stallman, FSF and Linux Torvalds in presenting themselves as messianic figures, have deceived GPL coders into believing that they are not in a master/slave licensor/licensee relationship with the copyright holder.

As proprietors of MySql, Gluster and GCC they can initiate arbitrary legal action against companies while not targeting others. All derived code that the licensees provide back to Oracle(licensor) can be used by Oracle in closed source projects. FSF as copyright holder of gcc revoked the GPL license for the more restrictive GPL3, forcing BSD unix forks to adopt the Clang compiler and get rid of all GPL code.

In a semantic smoke and mirrors exercise FSF have convinced the public that if code is under the GPL license then the licensor and licensee can use the code under the same terms. GPL only places an obligation on the licensee, not the licensor. Thus Red hat will litigate against anyone using its Gluster code in violation of the GPL as it sees fit while releasing closed source code to anyone as it sees fit. FSF and RSM usage of proprietary and free confuses this point. There are basically only two concepts: Proprietary and Public domain. The omission in the GPL propagandizing at http://www.gnu.org and http://www.fsf.org on the utilization of GCC as opposed to the Clang compiler is that FSF retains the copyright, which establishes them in a dominant position over the users(GPL licensees). This is not what freedom and equality means.

BSD license was created to prevent liability litigation over code released to the public domain(http://en.wikipedia.org/wiki/Public_domain_software). Most countries are subject to the http://en.wikipedia.org/wiki/Berne_Convention which defines that something is either proprietary or in the public domain. Only proprietary code can be released under a license such as BSD and GPL. This allowed for example the Pixhawk code licensed under BSD to relicensed under LGPL when they merged with the http://www.diydrones.com project. RMS can't redefine the legal concept of Proprietary as the opposite of Public domain by using the terms free(GPL) and permissively free(BSD): something is either proprietary or public domain(free). What Stallman refers to as freedom under GPL is actually dictated behavior of the licensee by the licensor - http://onlamp.com/onlamp/2005/06/30/esr_interview.html
 * (Pending: BSD clause-3 seems to release copyright to public domain and thus once BSD it can't be relicensed to some other code ...don't know will get back to this...)


 * ...Linux Format UK - December 2012 ..p.61.... the code is effectively held in common.....  All are free to read, study and share it. As such, it's impossible for workers to be locked in by those above them in the class system, since at any time they can choose to put the means of production, the code to use for their own ends....

The code is held in common by which licensor and how many copyright(licensors) holders are there? Copyright law doesn't restrict the number of copyright holders. In the quote the "...held in common ..." it isn't made clear as to who these "commoners" are: they are the copyright holders, establishing a master/slave relationship with licensees using GPL, which by definition means they are above the licensees of GPL. Companies can't as the licensee of Red hat's Gluster(GPL) produce a product under their own terms, while Red hat can use their derived code under any terms such as releasing derived code under a closed product and not releasing the derived ideas back to the company again.

Redhat code acceptance policy
I am not sure, but as I understand it if the Redhat GPL proprietor(owner) accepts code into their project by a person that is not an employee, then that person automatically obtains copyright. Redhat and it's employees are considered a single legal entity under copyright law. Redhat will never allow therefore a non-employee to contribute code or only under a contract of not obtain shared copyright. Thus you have to become a paid slave of them,not able to run your business in order to commit back improvements. This is an important omission that RMS and Linus Torvalds makes when handing out their autographs. Therefore the entire code sharing experience that is supposed to take place in theory under GPL on an Equality source footing can by the copyright holder be dictated to be in a master/slave relationship.

Copyright law allows the licensor to license the code under any number of licenses and to instigate arbitrary legal action or no legal action against any licensee: this is not what "freedom" is supposed to be. Freedom is only works released under the http://en.wikipedia.org/wiki/Public_domain_software. Only a copyright holder can release something as http://en.wikipedia.org/wiki/Copyleft and revoke such license. Copyleft is a form of licensing that is used to maintain copyright conditions for the licensor while delegating reduced rights to the licensee while making the licensee believe he has the same rights, much like the pigs in Animal Farm thought they had equal rights.

(Pending: Socialism is the centralized means of production, Communism is the centralization of ideas or allowed behavior/ideas. Redhat would ideally want to have all copyright on all of Linux, this would enable them to use slave labor working for free while under the delusion that as licensees of GPL they are on an equal standing with the licensor. )


 * http://www.gnu.org/philosophy/free-sw.html .... ...Free software” means software that respects users' freedom and community. Roughly, the users have the freedom to run, copy, distribute, study, change and improve the software. With these freedoms, the users (both individually and collectively) control the program and what it does for them....

Redhat on Linux in the Firescount UAV
Redhat stated p.53 Linux format magazine Dec.2012: ".....It's kind of funny to see people say ".Ooh, Linux is in the Firescout". It's going to force cataclysmic changes in the GPL No! It's not a cataclysmic event, it's a contract...."

The "contract" he refers is the contract that copyright holders of Linux made with the US government. While the licensees of GPLm, not being copyright holders of Linux are in no position to do this. (...this section needs more citations and alternative views.....). It should be obvious that the military can't release their detailed software designs on the Firescout as the GPL dictates, but because the GPL doesn't apply to the Linux copyright holders(licensors) they made an exemption after being paid lots of money. The unfairness in this is that the GPL users of Linux Busybox can't pull the same stunt: where is their freedom to use Linux in violation of GPL. Why is the US government exempted but not Sony by the Busybox copyright holders? Vast swaths of the Linux kernel developers are employed by major companies such as Redhat and Google. As employees who have to eat at the end of the month, those Linux copyright holders not providing their permission to have GPL violated by strong actors have a very good incentive not to deny it either. Therefore by employing the copyright holders of Linux or paying their Linus Torvalds salary as an independent maintainer of Linux, Redhat is able to leverage Linux code in closed systems such as government military software, where the derivative work can't for obvious reasons be made public.

Church's Thesis
This process of subverting the original ideals of RMS that everybody will be 'free' and have equal terms access is known as Church's Thesis(http://www.softpanorama.org/Copyright/License_archive/gpl.shtml#GPL%20and%20Corba). RMS and the RIAA are on opposite sides of the freedom debate, but they do share one common enemy "Church's Thesis" http://cs.fit.edu/~ryan/glossary.html.


 * A direct result of Church's Thesis is that no matter what you're trying to do, there's always a way to do it with one more level of indirection, or one more after that, or one more after that, or .... There's always a way to cheat *any* system you have in place, so unless you're willing to take draconian measures that will make a lot of legitamate uses illegal, you'll just have to accept it.

An example of Church's thesis are pyramid investment schemes indirection by selling nutritional products as a cover for financial fraud. The actual goods themselves could have been purchased much cheaper or are purchased not because the consumer actually wants the product but because more people will be recruted into the scheme.

Redhat provides the US government with Linux services as the copyright holder(master), in a way that you as GPL(slave) licensee can't. They use legal tricks as the copyright holder to prevent the GPL deceived from providing the same services, they are an example of Church's Thesis: leverage the work of GPL licensees to make money in closed products, while making the licensee think(using the incessant chanting of 'freedom') they are on the same equality standing as the licensor.

Alphabet under public domain not copyright
Pending: alphabet is under public domain. Ideally RMS and the FSF would like the letter @e@ to be under copyright held by the FSF. IF the FSF holds the copyright to the gcc compiler then why not give them the copyright on the entire alphatbet? Then literally everything we do and say could be involved in FSF "platinum member corporate sponsored" litigation. It would allow the FSF to become a global idea superpower, able to target those their "corporate sponsors want targeted".

GPL and cloud computing
http://www.softpanorama.org/Copyright/License_archive/gpl.shtml#GPL%20and%20Fair%20use The GPL does NOT prevent corporate interests from exploiting your work with no remuneration to you. For example, if I can arrange my money-making scheme so that all your GPL'ed code is running on my server somewhere, and the clients are just accessing it over the web, guess what? I'm making money from your code, and I don't have to give it to anyone.

Clint/server approaches can take a lot of the bite out of GPL. Look at TiVo. They are certainly benefiting greatly from Linux, but the guts of their stuff runs as an application, and so does not have to be GPL'ed. They take the regular Linux kernel, make a few mods (which they GPL), and then use it to run their proprietary application. And then there is component-based computing: COM on the Windows side, and CORBA everywhere else. GPL, which is fundamentally based on a dying model of how computer programs work, provides basically no protection then.

RMS uses 'freedom as metaphor for 'behavior'
RMS uses freedom as a metaphor for behavior or dictated behavior. His FSF holds the copyright on the GCC compiler. The GPL doesn't change the ownership of a snippet of code. It only changes the terms under which others can use that code. The original author still retains the copyright to do whatever the he wants with his code. The original author, who is the copy(right|left holder, can do whatever he pleases, including putting it into a proprietary system. Nobody ELSE can do that unless provided permission by the GPL proprietor. Oracle bought the mysql copyright, this allows them to take all GPL forks of mysql and release the innovations under their own proprietary databases.

The original author can release the same code under multiple licenses.He could license it under all 67 licenses currently available. Lets presume an irrational actor from say Iran pinches off $4bil in oil funds and employs 10000 coders all being promised that the code will be released as BSD, but because Iran is the copyright holder they instead release it under lets say 1200 licenses, thus sterilizing the code because it would tie up companies in endless litigation with the copyright holder.

Google is openly violating the GPL clause of Linux with its Android system by not releasing code back. If an injunction is obtained against Google, the only way they would be allowed to re-use Linux once they comply is all the hundreds of copyright holders on Linux give their permission: they will never all give such permission.

Stallman as GCC copyright holder wants the licensees to engage in a certain behavior. If such behavior meets his moral code he calls it freedom. Coders should only have the 'freedom' to engage in behavior as sanctioned by Stallman. Thus he Newspeaks 'restriction' into 'freedom'.

Both patents and copyright allows the licensor to license an idea to the licensee with specific terms that lays down the "behaviour" of the licensee. Under GPL which applies only to the licensee the behavior required of the licensee is to release all derivative works back to the licensor.

PENDING: Nobody can legally define what a derivative work is to begin with.

Since my behavior is outlined by the licensor I do not have the freedom to behave in a manner outside the terms of the copyright holder of GCC or a patent holder. RMS pulled an Orwellian Jedi doublethink mind trick by restricting my behavior to his moral code and deceived the wider Linux community to say that behaving in the manner he wants is Freedom.

RMS deceived coders to say: Restriction is freedom! Much like the animals in animal farm chanted Slavery is freedom!. He pandered to communist resentment and people's desire to eliminate all class differences.

Lets be very clear about this: A restriction isn't a freedom. If there is any restriction about how one is allowed to develop an idea then it is George Orwell Newspeak to call such restriction a freedom.

GPL allows people with resentments to ensnare the rest of the world with it. They resent Steve Job's and Bill Gates being billionares. In this state of resentment they want to use the GPL for assured mutual destruction, like is happening with with environmental destruction of forests because 2000 idea restricting HackPatents are making patented commercial StirlingEngines unavailable to Africans.

Ogg Vorbis and theora under BSD in an attempt to get Microsoft to adopt the standard so that windows and linux can play the same files. Instead we have the defacto mp3 and Mpeg-4 standard under license restrictions. GPL proponents don't understand that if Linux can't communicate with Windows at all, then Linux will become utterly irrelevant. GPL prevents microsoft from adopting Linux code, thus preventing communication between them, establishing Windows as a de facto standard for applications.

Opensource newspeak
Opensource is a form of newspeak to obfuscate that it actually mirrors the effect of a patent: access to the source code is provided by the copyright holder such as Redhat, but one is restricted in how it can be implemented - HackPatents. Redhat implements the code released back by the licensees in their own closed solutions. It is deceitful to call a restriction on the licensee a freedom. GPL advocates must sort out their terminology and use properly defined terms to reflect what they mean as defined in dictionary's. A licensor / licensee relationship isn't "freedom", it is a master/slave relationship.


 * (Pending: If the US government releases GPL code then nobody can implement closed solutions of it? What scheme is Redhat upto for them to leverage government code in closed solutions, while nobody else can)


 * http://en.wikipedia.org/wiki/BSD_license BSD licenses are a family of permissive free software licenses. The original license was used for the Berkeley Software Distribution (BSD), a Unix-like operating system after which it is named.

GPL is labeled free software while BSD is labeled permissive free which is Orwell Newspeak obfuscation. Something isn't eiher free or permissively free it is either restricted or free.


 * .... wishing to publish BSD-licensed software which relies upon separate programs using the more-restrictive GNU GPL....

Note the more-restrictive(GPL) from the article as opposed to permissive free. GPL is uses free and more-restrictive interchangeably. Restrictions leads to unintended consequences. Ideally there should be no restrictions on any idea whatsoever, no copyright ect. We would now have had a cheap cure for cancer available had it not been for the unintended consequences of idea restricting patents, GPL and copyright. Microsoft, Apple and GE are working the system, what has to change is the law. BSD developers and Stallman(GPL) agree that all copyright and patents must be disbanded. Since this isn't going to happen BSD takes the pragmatic view by realizing that commercial companies will provide code back since it is in their commercial interest to have a global pool of developer knowledge by people. GPL communism tries to take out its frustrations with the legal system on Microsoft, leading to http://en.wikipedia.org/wiki/Unintended_consequences
 * More recently, the law of unintended consequences has come to be used as an adage or idiomatic warning that an intervention in a complex system tends to create unanticipated and often undesirable outcomes.[7][8][9][10] Akin to Murphy's law, it is commonly used as a wry or humorous warning against the hubristic belief that humans can fully control the world around them.

Communists tried to regulate every facet of human interaction, restricting the freedoms of people and ideas. https://www.youtube.com/watch?v=ZemhXvN2stE&NR=1&feature=endscreen states that Stallman started the free software movement, this is incorrect as the MIT BSD like license was available before his GPL restriction as an answer to copyright restriction. GPL forces users to provide code back to a government agency who released it as GPL, without the government agency having to release code back to the developers but still able to use the code internally and derive benefits from extending the code, since government agencies and corporations are considered a single legal entity or person by law. This defeats the whole expectation of GPL coders that entities would be forced to release modifications back to them or they wouldn't be able to use their ideas.

Theo
http://undeadly.org/cgi?action=article&sid=20070901041657
 * GPL fans said the great problem we would face is that companies would take our BSD code, modify it, and not give back. Nope—the great problem we face is that people would wrap the GPL around our code, and lock us out in the same way that these supposed companies would lock us out. Just like the Linux community, we have many companies giving us code back, all the time. But once the code is GPL'd, we cannot get it back.

Thingiverse.com
You can give users the right to use the work under CC. However when you upload anything to thingverse you also licence it to them under this license:


 * http://www.thingiverse.com/legal "3.2 License. You hereby grant, and you represent and warrant that you have the right to grant, to Company and its affiliates and partners, an irrevocable, nonexclusive, royalty-free and fully paid, worldwide license to reproduce, distribute, publicly display and perform, prepare derivative works of, incorporate into other works, and otherwise use your User Content, and to grant sublicenses of the foregoing, solely for the purposes of including your User Content in the Site and Services. You agree to irrevocably waive (and cause to be waived) any claims and assertions of moral rights or attribution with respect to your User Content."

This means that Thingiverse can allow others to use your ideas under a different license then the one you thought you gave, because Thingiverse becomes joint copyright holder over your ideas. The uploaders to thingiverse are under the illusion that they are the sole copyright holders. The FSF newspeaky 'opensource' makes this distinction difficult to discern.

products
Ironport, isilon, ncircle, netapp, netscaler, juniper, sandvine, pallisade, avid, nokia, vxworks, thomson, panasas, symmetricon

GPL and Google: the fine print
Many GPL advocates are actually communists with the view that there shouldn't be any class differences and that nobody must make money of their ideas without them getting a cut.

Google is using GPL code internally, generating wealth with it and not releasing their code modifications. A communist using the GPL to fight the corprotism(which he confuses with the free market) don't understand that he is in anycase not deriving direct financial benefit. Many communists have spent months of their lives behind GPL code, which was then used by Google, without Google paying them a cent.

Thus rather use the BSD license and at least formalize what is taking place in reality. GPL is a form of communism that will not allow any idea to be commercialized. As a commercial company there must be derived ideas that Google can't release to the public domain. One can't expect a company to invest Billions of dollars in hardware to release a product and release detailed exact descriptions of what they did. Imagine that all commercial companies be forced to release their internal trade secrets and suppliers, it would prevent people from investing in the first place. http://www.stallman.org/ logic is that Sasol must provide a DVD containing detailed blueprints on its implementation of the http://en.wikipedia.org/wiki/Fischer%E2%80%93Tropsch_process petrol production process. Since this isn't going to happen like it isn't going to happen that Vodacom will suddenly allow free access to its 900Mhz spectrum we need to be realistic and rather implement the BSD pragmatic approach - http://sasecurity.wikia.com/wiki/GPL_and_BSD#Help_Vodacom_rather

BSD encourages but doesn't force companies to release back their derived ideas. Apple has done many code releases back to http://www.freebsd.org and many of the core BSD developers work for Apple. GPL advocates and anybody else were free to buy Apple stock and share in the companies wealth. Yahoo releases back code to the postgresql BSD, keeping their in-house modifications current with the main SQL fork, allowing them to employ postgreSQL developers for proprietary coding. For Yahoo, Google, Sasol etc. to have a business case they must be able to use algorithmic abstractions documented by others, without publishing such modifications.

GPL thus penalizes those trying to sell electronic products using such GPL code, while Sasol uses GPL code internally to sell petrol, but Sasol can't be sued for selling an end product. In both cases an end product is being sold, in both cases GPL code is used to provide such product, yet only the electronic product is actually able to be targeted in litigation.

Telecom firms I explained under Crime and Bandwidth solution are legal firms with an antenna on their roof engaging in Rent seeking, recycling math algorithms on FpGa devices. GPL,Copyright and HackPatents holders and coders also are rent seekers, expecting money each time their ideas are used. This has resulted in an Aristocracy lording over indentured slaves, who don't have the money like Apple, IBM to patent ideas and aren't being allowed to setup their own businesses using patentend ideas.

This has partially resulted in 25% of world GDP being concentrated in the hands of 200 companies. This is not a failure of capitalism or the freemarket but Newspeak obfuscation by the powerful mind control entities CNN, Fox news. etc. who don't want the public to understand this. The solution to this isn't more restrictions on ideas and their implementation, which is what the GPL license is.

GPL fragmented the Unix base
GPL splintered the BSD freebsd Unix base(Ubuntu, Red hat etc), thousands of sharp minds are wasting their time building a better bike-shed, not able to incorporate the superior file management system under BSD(nuclear power plant). Red Hat used clever legal tricks to in effect leverage the work done by developers under GPL but not release back these innovations. They have made it clear to their paying clients that there will be some form of retribution if they release code to others. Red Hat worked out a scheme whereby they are making money of GPL code but not giving back some of these modifications. (this need citations, I have lost the article and will cite it once found again)

http://linuxfonts.narod.ru/why.linux.is.not.ready.for.the.desktop.current.html provides a list of Nvidia driver issues. The complexity of Linux is scaling out of control due to a fragmented developer base and design flaws. BSD is more centralized.


 * Problems stemming from the vast number of Linux distributions: No unified configuration system for computer settings, devices and system services. E.g. distro A sets up networking using these utilities, outputting certain settings residing in certain file system locations, distro B sets up everything differently. This creates confusion for users.


 * Due to unstable Linux and constantly changing kernel APIs/ABIs Linux is ineffective for companies which cannot push their drivers upstream into the kernel for various reasons like their closedness (NVIDIA, ATI, Broadcom, etc.), or inability to control development or co-develop (VirtualBox/Oracle, VMWare/Workstation, etc.), or licensing issues (4Front Technologies/OSS).


 * "...There should be no reason why you can't take the last release that AMD made for that HD3200 and have it run perfectly on the latest distro and the fact that you stand here and admit that it doesn't work just shows what is wrong with linux in a nutshell...."

Too many devs tinkering with drivers, kernel and low level internals with not thinking through the effect this has on backwards compatibility. Backwards compatibility is required, because most software companies aren't going to pay a team of devs to constantly rebuild their products to cope with fragmented changes.

Shuttleworth could have done like Google did with Android and fork the thing away from the devs so that real stability and BSD style central management could be brought to bare instead of the cat herding we have now, but it was not to be.

Linux has beautiful UIs, and tons of software, but retailers won't touch the product if installing it on a system and 6 months later its broken its own drivers because decentralized dev's changed low level system files and disabled the retailer's customer WiFi or sound...(Add Pulse section later)

Gluster New speak
http://community.gluster.org/q/why-did-gluster-choose-gnu-gpl-agpl-instead-of-bsd-license/
 * http://en.wikipedia.org/wiki/Newspeak

''...BSD license allows proprietary derivatives and forks of Gluster software. GNU GPL and AGPL defends software freedom better than BSD license. We would like to ensure enhancements to Gluster software to be contributed back to the community....''

Gluster not allowing their ideas to be used elsewhere without documenting such derived ideas is a restriction and specifically not a freedom. They are owned by Red-hat. Redhat is a corporate entity that retains the copyright on Gluster, there is no community held copyright on Gluster.

Copyright holder forks Tcpreplay into GPL
Aaron Turner the copyright proprietor of Tcpreplay was the only person with the legal power to make a GPL license in addition to his existing BSD license. Only the copyright holder can do this, but this did not allow him to revoke the BSD, he merely forked the development away from the BSD branch, which could still continue to be used by developers. In his http://synfin.net/sock_stream/technology/code/tcpreplay/why-tcpreplay-went-gpl article the usual point of how this will guarantee our freedoms under equality terms is given. What he did not mention is that the GPL restriction can be revoked for those using his GPL fork after paying him lots of money, because the GPL restriction does not apply to the proprietor. If something has a proprietor, then in terms of copyright law it isn't free(public domain).

What is the premise?
http://www.amazon.com/Zero-Marginal-Cost-Society-Collaborative/product-reviews/1137278463/ref=cm_cr_dp_see_all_btm?ie=UTF8&showViewpoints=1&sortBy=bySubmissionDateDescending
 * ".....JR cackles with Leninist glee (@8-9) as he describes how the significance of the Internet dawned on neoclassical economists Larry Summers and Brad DeLong. They suggested in a 2001 article that when you can make new copies of "information goods" for next-to-nothing (near-zero MPC), you can't make a profit in perfect competition -- so maybe monopolies are necessary to encourage innovation. Don't you see the irony? The capitalists base their theory on perfect competition, but now they're backtracking! DeLong and Summers "are hopelessly trapped" (@8). But it gets worse, because according to the capitalists' own neoclassical theory, "A near zero marginal cost society is the optimally efficient state for promoting the general welfare and represents the ultimate triumph of capitalism. Its moment of triumph, however, also marks its inescapable passage from the world stage." (@9) Mmmuwahahahaha, in a manner of speaking. (Why Leninist? because Marx thought a commodity-based economy occurred only in capitalism, but the Bolsheviks based their economy on commodities; see the Socialist Party of Great Britain's online article by Richard Montague, "Marx and Lenin's views contrasted.")..."

...They suggested in a 2001 article that when you can make new copies of "information goods" for next-to-nothing (near-zero MPC), you can't make a profit in perfect competition -- so maybe monopolies are necessary to encourage innovation..... By using http://sasecurity.wikia.com/wiki/GPL_and_BSD#Church.27s_Thesis a de facto monopoly over algorithms was established by employing the GPL copyright license holders of Linux by Google, Apple, IBM, Red hat etc.

later
http://www.catb.org/~esr/writings/cathedral-bazaar/

Apple issues
Steve Jobs stated ....... Apples makes the best notebooks on the planet .... Which is true, but what he failed to mention is that this is because Apple patented key technologies that doesn't allow other hardware vendors to reproduce similar products. The solution is to disband HackPatents and copyright, not add additional patent like restrictions with the GPL license. We must not fight restrictions like HackPatents with an incantation of the same restriction - GPL.

k
section on SSL allowing windows and linux to talk to one another.

Help Vodacom rather
The cell companies are running a rent seeking scam. There are various responses to this:

1) Distributed denial of service attack by sprinkling thousands of FpGa devices with the 3G protocol stack in peoples gardens. This could lead to a severe backlash and is a resentful, angry option like GPL allows angry communists to live out their classless society fantasy, leading to unintended consequences. Any large scale uncontrollable attack on the cell masts could lead to cell companies paying enough bribes to both the ANC and DA to change the constitution to provide Icasa with real powers and completely shut down all wireless networks: be careful what you wish for. Trying to destroy the commercial viability of cell companies could backfire badly.

2) The pragmatic option, grasping the reality of the situation and adapting to it. Try and see the situation from Vodacom's perspective and reduce their cost of doing business by allowing them to install for free mini-cell towers(femto cells) on your roof and even interlinking them using the opensource Ronja FreeSpaceOptics.

By reducing Vodacom's cost of doing business and forming a partnership between communities everybody benefits, enabling Vodacom to reduce their prices and still make a profit and not enabling them to demonize freedom loving people who will use the spectrum on 700,600,400Mhz etc. Since their business is so entrenched in 900Mhz no unauthorized usage of this spectrum must take place: we will not extend the same principle to 400Mhz - Unlimited bandwidth

Their present cost structure involves setting up expensive large towers, they have to raise their prices to recoup their costs and provide a return on investment. The GPL communist mindset would object and say that this isn't fair, sure life isn't fair, GPL supporters wants to wait for a classless fair society before allowing their ideas to be used. We have a limited lifespan on this earth, by the time 'fairness' arrives all of those reading this will be long dead.

GPL newspeak
http://en.wikipedia.org/wiki/Free_software


 * Free software, software libre or libre software is software that can be used, studied, and modified without restriction, and that can be copied and redistributed in modified or unmodified form either without restriction, or with restrictions that only ensure that further recipients have the same rights under which it was obtained and that manufacturers of consumer products incorporating free software provide the software as source code.

pending merge with issue on derived works by lawyer and programmer under the UNIX secion.

BTS
http://wush.net/trac/rangepublic enBTS is distributed in two forms:

1. The public ("P") release. The public release is distributed under AGPLv3 with copyrights assigned to the  Free Software Foundation. The public release is a subset of the commercial release intended for experimentation, education, evaluation and proof-of-concept projects.

2. The commercial ("C") release. The commercial release is installed in Range Networks products under a mix of GPL and non-GPL licenses. Range Networks also offers a customer portal for commercial customers where source code is available for the GPL components of the OpenBTS installation. The "C" release provides additional features for security, scalability, expanded capacity and the operation of multi-BTS networks. The "C" release is intended for users
 * who need to provide cellular service in industrial, government or commercial applications,
 * whose intellectual property policies or business models are incompatible with A/GPLv3 or
 * who require commercial support, network monitoring or other professional services.

See how clever this is by the copyright holder BTS? They make FSF a joint copyright holder who will hunt down and destroy anybody who "violates" AGPLv3. Meaning you can only like an employee of GE work on BTS but not make money off it and unlike the employee of GE not even get paid. On the other hand if you pay lots of money to copyright holder BTS you can develop and use the code as dictated by BTS without anybody even having to know about it. The same of course for AGPLv3, after paying Moglen some big bucks he can allow you to take the free labor of others and use it in your own commercial products without anybody even knowing about it. Because the obligation to release derived works as dictated by the GPL can arbitrarily waved for people who pay the copyright holder lots of money. The restrictions of the GPL does not apply to the copyright holder.

Links
http://www.itworld.com/storage/295325/red-hats-new-patent-troll-weapon-gpl-violation


 * Red Hat has taken a unique step in defending itself from a patent infringement claim from Twin Peaks Software: a counterclaim that Twin Peaks is in copyright violation on mount, the file management app that is licensed under the GPLv2. Not only is Red Hat seeking GPL compliance, it's also going after Twin Peaks for damages and is seeking an injunction on Twin Peaks' own roduct sales. mount, the document goes on to emphasize is licensed under the GPLv2, and can be freely used and distributed as long as the terms of the GPL are met - specifically, if you make a change to mount's code and distribute those changes, you have to make those changes freely available under the GPL so others can take advantage of the innovation. Red Hat has been the copyright holder of Mount - 2.10m beginning in May 2000 and of Mount 2.12a since March of 2004.

Having copyright on mount is like having copyright on the alphabet, the tools of our language should not be under any restrictions. Redhat can also use their defensive weapon offensively by extorting concessions out of others not targeting them in patent trolling for sole purpose of shutting down a competitor, thus emulating the effect of a patent. This is not what GPL proponents had in mind, their restriction was being used in unintended ways as per Church's thesis.
 * Bitlaw us an euro patent treaties
 * Jeremy Rifkin
 * BSD mailing list
 * Nvidia linux drivers
 * Eben Moglen
 * http://www.roughlydrafted.com/RD/Home/3FA34DA6-CD7A-44C1-9D8A-4AB90106BB4D.html tcp in bsd
 * http://fsfe.org/campaigns/gplv3/barcelona-rms-transcript#q11-banning-bad-use Tivoisation
 * http://slashdot.org/story/01/06/20/1249203/Bill-Gates-Says-GPL-Is-Like-Pac-Man  pack-man
 * http://news.slashdot.org/story/00/05/01/1052216/thus-spake-stallman
 * https://fitnessfortheoccasion.wordpress.com/2007/06/07/anti-gpl-crowd-doesnt-get-it/
 * http://compgroups.net/comp.os.linux.misc/licensing-question-public-domain-to-gpl/575077
 * http://archive09.linux.com/feature/30273
 * https://cyberpolitics.wordpress.com/category/lecture-notes/
 * http://www.wired.com/opinion/2013/09/why-free-software-is-more-important-now-than-ever-before/ Stallman on freedom, does not say a word about the copyright holder and makes and legally meaningless distinction between proprietary and commercial. Something is either proprietary or public domain.
 * http://www.bcgreen.com/comments/2005/communism.html Communism issue. The author failed to note that by employing GPL copyright holders Red Hat becomes the de-facto copyright holder.
 * https://www.youtube.com/watch?v=uFMMXRoSxnA interview with stalmann on rtnews  7min extreme capitalism . Stallman confuses corprotism with free market.
 * http://www.softwarefreedom.org/resources/2007/gpl-non-gpl-collaboration.html
 * http://en.wikipedia.org/wiki/Fork_%28software_development%29 "...In proprietary software, the copyright is usually held by the employing entity, not by the individual software developers. Proprietary code is thus more commonly forked when the owner needs to develop two or more versions, such as a windowed version and a command line version, or versions for differing operating systems, such as a word processor for IBM PC compatible machines and Macintosh computers. Generally, such internal forks will concentrate on having the same look, feel, data format, and behavior between platforms so that a user familiar with one can also be productive or share documents generated on the other. This is almost always an economic decision to generate a greater market share and thus pay back the associated extra development costs created by the fork. ..."