Talk:SCO–Linux disputes

How to use this page
This page was created in an attempt to create more structured information about the various lawsuits that SCO is involved in. My whole idea is as follows:

One page with very brief information about all the lawsuits and other issues that are related to the lawsuits and SCO's campaign (this page). One page with a more detailed explaination for each lawsuit and possible the other issues involved, for example: SCO v. IBM, Red Hat v. SCO, SCO v. Novell, SCO v. AutoZone, SCO v. DaimlerChrysler. Please use these pages to add specific information about these cases and try to keep the main overview page as bare as possible.

If it is needed we could even add specific pages for a complete timeline of each lawsuit, for example: SCO v. IBM (timeline), Red Hat v. SCO (timeline), SCO v. Novell (timeline), SCO v. AutoZone (timeline), SCO v. DaimlerChrysler (timeline). A main less detailed timeline can be found here: SCO v. Linux (timeline).

Other issues that may require external pages are SCO and SGI, SCO and the GPL, SCOsource, Who is the owner of Unix, USL v. BSDi.

Perhaps SCO v. Linux (external resources) could be used to store a more complete reference of external resources that contain information about this subject.

I also found that some legal terms are not defined on Wikipedia. Perhaps we could also create pages that explain some of the terms used on these pages, for example: Declaratory judgement, Preliminary injunction, etc.. See Summary judgement for an example of how I think such a page would need to look like.


 * Niels Leenheer

Old information
The following text was removed from The SCO Group. This information still needs to be incorporated into this page and the sub-pages:

The company then initiated a complex reorganization plan described in this [http://contracts.corporate.findlaw.com/agreements/sco/caldera.mer.2000.08.01.html AGREEMENT AND PLAN OF REORGANIZATION], and was renamed the SCO Group. (The company is not related to the former Santa Cruz Operation, now called Tarantella, Inc., other than in its purchase of 2 of 3 business groups from the former SCO and 2002 composition of mostly SCO former employees.)

As a result, the SCO Group was sued for defamation by a number of parties including IBM, the German LinuxTag organisation and Linux vendors SuSE and Red Hat. In Germany and some other countries, the SCO Group accepted a court order to abstain from making claims against Linux, whereas the legal cases in the United States are still unresolved.

Today, the SCO Group outwardly seems to be having much financial difficulty. Some analysts claim that its lawsuit with IBM and its aggressive campaign against Linux stems from this difficulty. The SCO Group denies that it is attacking Linux, citing the fact that they produced their own OpenLinux distribution of Linux.

Documents
Loan from Canopy Group to Caldera

Quotes

 * "[O]bviously Linux owes its heritage to UNIX, but not its code. We would not, nor will not, make such a claim." - Darl McBride, as quoted in Linux Journal, August 28, 2002.
 * "We believe that Linux infringes on our UNIX intellectual property and other rights. We intend to aggressively protect and enforce these rights. Consistent with this effort, on March 7 (2003), we initiated legal action against IBM for alleged unfair competition and breach of contract with respect to our UNIX rights. This case is pending in Utah Federal District Court. ... For the reasons explained above, we have also announced the suspension of our own Linux-related activities until the issues surrounding Linux intellectual property and the attendant risks are better understood and properly resolved."

The name of this page
Niels -- I think we got started off on the wronge foot here, calling the page SCO v. Linux, and now with SCO v. SGI. The xxx v. yyy format refers to actual court cases, I believe. So far only the five mentioned cases are actual filings. (btw - thanks for your help with this subject.)


 * I don't think the xxx v. yyy format is used exclusively in court cases. The format does indicate a conflict of some sort, whether it be legal in the form of a lawsuit or otherwise. So I don't think the use of this format for the title of this page and the SGI page is a big problem. But if you have better titles for these two pages, I would be interested in hearing them. -- Niels


 * My only issue is using that specific format. It is very specific in a legal context.  It references an actual court case from somewhere and time.  Especially when used in a legal context as here, it is very confusing.  It leads to the expectation of a court case where there is none.  And this whole matter is so terrably confusing in the best of circumstances to begin with.  How about SCO verse Linux?  That may be enough to suggest conflict and not a court case.


 * I've change the title of the SGI page to SCO and SGI. Before changing the title of the main page, I would also like some feedback from other contributors. Does everybody agree with changing the title of this page and what would be the correct title of this page? Niels Leenheer 19:27, 2 Aug 2004 (UTC)


 * Niels, seems we two are the only ones working on this topic. After thinking a bit about it, I would suggest a title of "SCO-Linux Wars''.  This is to reflect that it's not just a legal conflict, but also has major chapters in FUD, PR and financial areas as well.

Please, no "Wars"
Calling it "war" is hyperbole. It's fine for a sensationalist headline in a newspaper, but I don't think that it is appropriate for a supposedly serious encyclopedia article. Please rename the page, e.g. to "SCO-Linux Controversy".

Note that you don't put spaces around a hyphen in ordinary English typography, and "the" is generally superfluous in an article title.

&mdash;Steven G. Johnson 14:14, Sep 28, 2004 (UTC)

I would have thought something like "SCO-Linux lawsuits" would fit this page better. It's mostly about what's happening in court as opposed to a "controversy" (what people think of one side or the other). --LeeHunter 20:52, 28 Sep 2004 (UTC)


 * A lawsuit, by definition, involves a controversy between at least two parties. In this case, the controversy extends well outside of the courtroom &mdash; to competing public-relations efforts and press releases, to disputed licensing programs, to questions about the degree of financial involvement by Microsoft and Sun.  Yes, the lawsuits are the centerpiece of all this, so if you feel strongly that it should be "SCO-Linux lawsuits" I won't argue further.  &mdash;Steven G. Johnson 17:34, Sep 29, 2004 (UTC)

Which abbreviations to use?
In order to avoid confusion of the reader I think it is important to determine which abbreviations we should use and then use them consistantly. I've made a little list of things that are not used consistantly right now. I've made my preference bold:


 * The SCO Group: SCO, SCOX, SCOG
 * SCO is the abbreviation The SCO Group uses themselves and it is also used in the names of the lawsuits.


 * Santa Cruz Operation: Santa Cruz Operation, Santa Cruz, SCO, OldSCO
 * I don't think this name should be used as an abbreviation in order to reduce the confusion. Futher, I think it would be wise to use a contruct like this the first time this name is used on a page: .... Santa Cruz Operation, currently operating under the name Tarantella, ....


 * System V Release 4: SVR4, SVr4, Svr4, SVR 4, SVr 4
 * The official name uses caps, so the abbreviation also


 * System V Release: SVRx, SVR
 * The same as above, only without a specific version number


 * Unix: UNIX, Unix
 * This is a difficult one. Most of the time the term Unix is used in these text, it is not in the context of a single product, so Unix seems appropriate. On the other hand, UNIX is the official trademark.
 * There was a mix of Unix and UNIX so I changed them all (except UnixWare) to UNIX. My reasoning was that it should match the UNIX page (where the capping issue is discussed). I actually prefer the look of 'Unix' but consistency is important too. --LeeHunter 22:59, 8 Aug 2004 (UTC)


 * UnixWare: UnixWare, UNIXWare, UW
 * I think UnixWare would be the only acceptible way to call this product. Just like the official trademark.

In general, I think it is important to use the full name for the first occurance of an abbreviation, with the abbriviation between parenthesis. For example: The SCO Group (SCO) is currently involved .... SCO has initiated a series....


 * These sound OK to me. My only hesitation is using SCO for the SCO Group, but you are correct about the current court cases reference.

Any comments?

Niels Leenheer 08:04, 4 Aug 2004 (UTC)

Edits
Removed information about share price. Seems like trivial and constantly changing information. It also has the taste of something included just to tweak SCO's nose.

Removed the following "Core Issues" section as it only repeated what was written earlier in the article (and the same info is repeated again later):
 * The SCO Groups basic claim was that certain intellectual properties (IP) that they own has is some manner made its way into Linux. They further claimed that this obligated users of Linux to aquire a license from SCO in order to legally run that operating system.  Thoughout the controversy that followed in both the public press and in the courts, several core questions have emerged and clear answers have not yet been arrived at.  The first one is specifically what intellectual property is at issue?  The second question is who actually owns what rights in the various elements of that intellectual property?  And the third question is where in the Linux source code base are any of these rights violated?

The following bit is garbled. I left it in because I have not idea what it means or what to do with it
 * Many of the UNIX Licensees took the license was to develop new and additional features for the core UNIX system and develop new products and services. Those new features are provided by computer code that was not included in the initially licensed as the SVRx code base. --LeeHunter 03:13, 7 Aug 2004 (UTC)

Remove the following section because it is too vague and POV. Also the section name (SCO and the GPL) has already been used:
 * During 2003 and 2004, The SCO Group repeatedly stated that they believe the GPL is unconstitutional. The open source community, including the creators of the GPL, the Free Software Foundation, responded fiercely to these claims and believe that SCO is making a fool of themselves by even suggesting that the GPL cannot be enforced because of this.

Also removed the following for POV reasons:
 * Many people, including many users of Linux, consider this to be a scam. To date, SCO has claimed certain companies have paid for the licenses. Two of them, Computer Associates and Leggett & Platt deny having purchased any such licenses, at least not having any intention to do so. Questar and EV1Servers, however, have admitted to purchasing the controversial licenses, angering many customers who continue to follow the story.

More links
--2mcm 05:18, 24 August 2005 (UTC)
 * 
 * 
 * 
 * 

A Summary?
Could we see a paragraph or two about the current state of the case ( which AFAIK SCO has 'lost' ) in the first 'screen' ? --2mcm 05:18, 24 August 2005 (UTC)

Accusations of Linux plagiarism
I found it rather strange that the weasel phrase "Some open-source advocates claim that" was inserted. It's not a matter of claiming or not claiming. According to the terms of the GPL, if you include code from a product that is licensed under the GPL, you are required to release your work under that same license. While the truth of the claims has yet to be established, the consequences should they be shown to be true stand pretty much certain. Jamyskis Whisper, Contribs 14:15, 17 January 2006 (UTC)

Misunderstanding
"Microsoft, at the time, had $550 million invested with BayStar."

This was a common misunderstanding at the time, coming from a BayStar statement about Microsoft usage of pipe investments in general. As you can see from the article linked to that claim, nothing of the claim remains (if it ever was in that article). —Preceding unsigned comment added by 193.216.110.111 (talk • contribs)

Current Event?
Given that these lawsuits are ongoing, should this page get a 'current event' tag? Is this too long of a current event to get such a tag? —Preceding unsigned comment added by Darkonc (talk • contribs)
 * I think the current event template is used on articles where information can change rapidly in the immediate future, which is not the case for this article. - Sikon 13:29, 4 September 2006 (UTC)

bewildering storm of claims?
should an encyclopedic entry ever refer to anything as bewildering? Perhaps a rephrase is in order here.

NpoV
After reading this article, I came away very against the SCO group. Can this article be made more neutral? 194.105.160.77 16:45, 15 March 2007 (UTC)


 * I just re-read the article after a number of months having not read it and while the article doesn't present SCOX in a very favorable light, that is a direct result of the events being described. You can certainly try to make the tone more neutral and might have a good deal of success doing that, but I don't think that the underlying developments in the court cases to date will allow an article that leaves the reader with a neutral feeling about the parties to the controversies.  -- Upholder 17:14, 15 March 2007 (UTC)


 * If this article was changed to read closer to actual reality, you would come away from it even more so against the SCO Group. For example, SCOG have a claim about "derivative works", and they relate that to "methods and concepts" from UNIX somehow not being allowed to be implemented in Linux. Yet there is a link to another Wikipedia page which describes "derivative works" in a legal sense as meaning something entirely different ... a work is legally a "derivative work" (despite SCOGs claims) only if it actually contains parts of an earlier work. http://en.wikipedia.org/wiki/Derivative_work In this case, that means that Linux must be shown to actually have "major, basic copyrighted aspects" from UNIX source code contained within it for SCOG to actually have a case. SCOG have utterly failed to find any part of UNIX code contained within Linux.

From the article: "SCO has also claimed in early stages of the litigation, that the GPL is invalid and non-binding although they have stopped taking that stance after realizing that by their own distribution of Linux code, they are liable for multiple copyright infringement instances unless they accept and respect the GPL." This paragraph in particular is an example of something that's NPOV. I don't think any facts need to be removed from it, but the phrase "after realizing that" (for example) strongly suggests the reader draw a certain conclusion from the article; it's better to just present the facts and be encyclopedic and let the reader draw their own conclusions. 63.163.61.3 20:39, 26 April 2007 (UTC)
 * That is not a NPOV. IBM entered a counterclaim saying that IBM contributions in Linux were IBM's copyrighted property, and they were licensed for distribution under the GPL. If SCOG repudiated the GPL, then SCOG were distributing IBM's copyrighted code without any license to do so. SCOG answered that counterclaim of IBM's in offical court papers by claiming that SCOG fully complied with the GPL, and had never repudiated it. Therefore, it is entirely acurate to characterize this sequence of events as follows: "SCO has also claimed in early stages of the litigation, that the GPL is invalid and non-binding although they have stopped taking that stance after realizing that by their own distribution of Linux code, they are liable for multiple copyright infringement instances unless they accept and respect the GPL."


 * That's not the only conclusions. They could have held the GPL was invalid and that they didn't commit copyright violations because the stuff was in the public domain, or that the GPL evidenced a license to use without cost but that its requirements upon the purported licensee weren't enforcable.  Or, that IBM didn't have the rights sufficient to sue anyways.  In any case, nothing stops a party from taking inconsistant positions.  You can argue that the GPL is invalid, that you complied with it, and sue for violations of it all at the same time.24.29.234.88 (talk) 05:25, 1 July 2009 (UTC)

corrected reference no.32
It was pointing at an obsolete page. Apparently the original website changed their content management engine. The corrected reference points at the original article again. —Preceding unsigned comment added by 60.52.82.203 (talk) 13:16, 19 September 2007 (UTC)

V6 UNIX
What is the status of the old V6 or V7 UNIX code, which was widely distributed by Bell Labs in the 1970s? I'm guessing it must be more or less public domain, since Bell Labs made no attempt to enforce a copyright of it. I recall in those days, there was a book by a professor Lions in Australia that EVERY unix programmer had. Lions did get into some trouble over that book, and was asked to stop printing it (thus the n-th generation xerox copies everyone had). DonPMitchell (talk) 04:05, 25 July 2008 (UTC)


 * One of the results of USL v. BSDi was that the judge expressed doubts on whether the copyright to the early Unix code could have been sustained (because they didn't properly claim copyright or register it), which was part of the thing that convinced USL to settle so quickly.--Prosfilaes (talk) 06:40, 28 December 2012 (UTC)

Just for the record, the V6 and V7 code was released by Caldera before the SCO legal cases begain, and is partly described in Ancient_UNIX. Tiger99 (talk) 15:06, 22 September 2010 (UTC)


 * Interestingly, since the courts have ruled that the copyrights to the Unix source code did not transfer to SCO, Caldera did not hold the copyrights and therefore could not release the code under a different license. This applies to all the open sourcing of Unix including the subsequent deal with Sun to release the SVR5 code used in OpenSolaris. Ronald Joe Record (talk) 19:38, 22 September 2010 (UTC)

Bot report : Found duplicate references !
In the last revision I edited, I found duplicate named references, i.e. references sharing the same name, but not having the same content. Please check them, as I am not able to fix them automatically :) DumZiBoT (talk) 22:01, 9 August 2008 (UTC)
 * "doc377" :
 * Memorandum order and decision, document 377 in case 2:04CV139DAK, the court order on Groklaw
 * MEMORANDUM DECISION AND ORDER Civil Case No. 2:04CV139DAK

Removing "Needs Updating" bot message
I think this article has been updated sufficiently since the bot flagged it; I'm going to remove the banner. GuiderBob (talk) 15:02, 17 January 2010 (UTC)

SCO/SGI
I've tagged as POV this section. Regardless of the merits of the claims of either party we have a list of reasons given conclusively "proving" a particular position. However, that position is not linked any reliable source presenting that interpretation and as such is inherently POV. Unless a source can be found that covers those points properly it needs a dramatic amount of trimming and refactoring. Crispmuncher (talk) 02:03, 21 November 2011 (UTC).

Protection for users of linux again the litigation
There is no mention of the insurance offered to users of Linux in this period. Here are some articles: -- PeterEastern (talk) 13:32, 5 January 2012 (UTC)
 * "Once More Unto the Breach: OSRM [Open Source Risk Management], Lloyds of London, and Open Source Insurance" Aug 2005
 * 'HP to Indemnify Linux Customers'2003
 * 'Novell Offers Liability Shield for SUSE Linux'
 * 'Red Hat to Protect Linux Customers' 2004
 * Open Source Risk Management still offer Open Source insurance.

External links modified
Hello fellow Wikipedians,

I have just added archive links to 3 one external links on SCO–Linux controversies. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:
 * Added archive https://web.archive.org/20050213234612/http://www.zdnet.com.au:80/insight/software/0,39023769,39116509,00.htm to http://www.zdnet.com.au/insight/software/0,39023769,39116509,00.htm
 * Added archive https://web.archive.org/20041009172817/http://www.caldera.com:80/scosource/letter_to_partners.html to http://www.caldera.com/scosource/letter_to_partners.html
 * Added archive https://web.archive.org/20080314051749/http://www.smallworks.com:80/archives/00000250.htm to http://www.smallworks.com/archives/00000250.htm

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

Cheers. —cyberbot II  Talk to my owner :Online 01:15, 9 September 2015 (UTC)

External links modified
Hello fellow Wikipedians,

I have just added archive links to 3 one external links on SCO/Linux controversies. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:
 * Added archive https://web.archive.org/20060429152726/http://www.caldera.com:80/scosource/letter_to_partners.html to http://www.caldera.com/scosource/letter_to_partners.html
 * Added archive https://web.archive.org/20091010163419/http://www.linux.org/news/sco/timeline.html to http://www.linux.org/news/sco/timeline.html
 * Added archive https://web.archive.org/20081013001529/http://news.zdnet.com/2100-3513_22-5811081.html to http://news.zdnet.com/2100-3513_22-5811081.html

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

Cheers.—cyberbot II  Talk to my owner :Online 10:41, 10 February 2016 (UTC)

The name of this article seems to be wrong
Given the fact that the company that started the court case was Caldera Linux (after buying parts from SCO and then renaming itself to SCO), I cannot see a SCO/Linux controversy but rather a Linux internal dispute. Schily (talk) 11:24, 10 February 2016 (UTC)


 * The court cases were filed by "THE SCO GROUP, INC., Plaintiff": e.g. MEMORANDUM DECISION AND ORDER Civil Case No. 2:04CV139DAK. That the company at some point used to be one of many Linux distributors and used to have a different name does not matter. At that time, they used the legal name "The SCO Group, Inc.", and owned the SCO trademark: File:SCO_Group_(logo).png. Therefore, the article name is sensible (and there are plenty of references to "SCO vs. Novell" - this is what the controversy was called, and the name the company used). It's not the "old SCO", so the article should not be called "OldSCO/Linux controversies", obviously. --Chire (talk) 10:26, 12 February 2016 (UTC)


 * That is a thoroughly disingenuous piece of an incorrect statement, followed by a biased and fallacious assertion. Chire has pointed out the obvious flaw in the first part, but to then use that to try and cast this issue into "a Linux internal dispute" is grossly biased invention on your part (Your partisan position within the Unix world is well known).
 * This is not the first time I have encountered you on Wikipedia and it is claimed by some that you are some sort of heroically notable programmer. So far though I'm just seeing outright trolling that is getting to the level of billygoats and bridges. Viam Ferream (talk) 11:49, 12 February 2016 (UTC)
 * Thank you! We now know where the trolls are. Schily (talk) 14:10, 12 February 2016 (UTC)
 * Indeed: Viam Ferream (talk) 14:41, 12 February 2016 (UTC)
 * And informed people know that http://sco.com is a domain owned by Xinuos, while the rights on the process are owned by something called "TSG" group... Schily (talk) 14:55, 12 February 2016 (UTC)
 * Yes, Xinuous now owns the SCO trademark which they got after SCO went bankrupt, so what? At the time when the cases were filed, the company used the name SCO, not Caldera. Xinuous never used the name "SCO" as their company name, only as part of their product names. The court cases are referred to as "SCO vs. Novell", "SCO vs. IBM", etc. because that are the names they were using back then. Sorry to break the news to you: some things change (ownership of the SCO trademark), some things lose relevance (e.g. SCCS lost to CVS lost to Subversion lost to Git, cdrecord, POSIX is constantly losing relevance as people focus on Linux and OSX specifics instead of a standard that nobody complies to), and some things fail to ever have substantial audience (e.g. pax, star, OpenSolaris). --Chire (talk) 15:56, 12 February 2016 (UTC)
 * Furthermore, the subject of their claims are "UNIX System V code" rights they had bought from the old SCO; not rights they obtained from their Caldera-Linux times. So by any means, it is not a Linux internal dispute, because it is about copyright of UNIX System V code. So please, cut back your anti-Linux-GNU evangelism. Let me repeat this to you: "SCO's claims are derived from several contracts that may have transferred UNIX System V Release 4 intellectual property assets." You supposedly are aware that "UNIX System V" is not Linux. --Chire (talk) 15:56, 12 February 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just added archive links to 1 one external link on SCO/Linux controversies. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:
 * Added archive http://web.archive.org/web/20041009172817/http://www.caldera.com:80/scosource/letter_to_partners.html to http://www.caldera.com/scosource/letter_to_partners.html

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.—cyberbot II  Talk to my owner :Online 23:43, 20 March 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 1 one external link on SCO/Linux controversies. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Corrected formatting/usage for http://perens.com/Articles/SCO/SCOSlideShow.html

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.—cyberbot II  Talk to my owner :Online 09:56, 14 April 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 3 one external links on SCO/Linux controversies. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20040806125142/http://www.novell.com:80/licensing/indemnity/legal.html to http://www.novell.com/licensing/indemnity/legal.html
 * Corrected formatting/usage for http://news.com.com/2100-1016-1007528.html
 * Added archive https://web.archive.org/web/20121023132946/http://www.thescogroup.com/ to http://www.thescogroup.com/

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.— InternetArchiveBot  (Report bug) 06:23, 11 November 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 4 external links on SCO/Linux controversies. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20071109190233/http://money.cnn.com/magazines/fortune/fortune_archive/2007/05/28/100033867/ to http://money.cnn.com/magazines/fortune/fortune_archive/2007/05/28/100033867/
 * Added archive https://web.archive.org/web/20081105224359/http://legalpad.blogs.fortune.cnn.com/2007/05/13/msft-linux-free-software-infringe-235-of-our-patents/ to http://legalpad.blogs.fortune.cnn.com/2007/05/13/msft-linux-free-software-infringe-235-of-our-patents/
 * Added archive https://web.archive.org/web/20060106163301/http://www.infoworld.com/article/03/08/08/31OPcringely_1.html to http://www.infoworld.com/article/03/08/08/31OPcringely_1.html
 * Added archive https://web.archive.org/web/20060825130902/http://ir.sco.com/ReleaseDetail.cfm?releaseid=109360 to http://ir.sco.com/ReleaseDetail.cfm?releaseid=109360

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 23:17, 15 December 2017 (UTC)

Requested move 9 April 2018

 * The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section. 

The result of the move request was: consensus to move the pages to SCO–Linux disputes and Timeline of SCO–Linux disputes, per the discussion below. Dekimasu よ! 17:35, 17 April 2018 (UTC)

– a few days ago these pages were moved by technical request to and,  each with a rationale beginning WP:SLASH / WP:SUBPAGE slashes should be avoided in article titles That seems to be correct about the inappropriateness of WP:SLASH/WP:SUBPAGE, but I have never before seen a page title with an emdash (as was done in these moves), so I have reverted both. This proposal uses the shorter endash. I am unsure whether this creates any ambiguity, so I am listing it for discussion rather than just doing WP:BOLD moves. Brown HairedGirl (talk) • (contribs) 13:35, 9 April 2018 (UTC)
 * SCO/Linux controversies → SCO–Linux controversies
 * Timeline of SCO/Linux controversies → Timeline of SCO–Linux controversies
 * Note category I came to this via WP:CFDS, where request was made to speedily move Category: SCO/Linux controversies to Category: SCO&mdash;Linux controversies (i.e. target using the emdash).  I opposed that speedy, but if this discussion reaches a consensus on a new title for SCO/Linux controversies, then the category should be speedily renamed to match per WP:C2D. -- Brown HairedGirl (talk) • (contribs) 13:43, 9 April 2018 (UTC)
 * Support endash per MOS. Opencooper (talk) 01:26, 10 April 2018 (UTC)
 * Support endash, but would humbly suggest SCO–Linux disputes as the target. It's mostly about disputes and litigations concerning copyrights, not so much about broader public controversy. No such user (talk) 11:59, 13 April 2018 (UTC)


 * Comment: Agree with No such user that  SCO–Linux disputes is probably better. It comes down to semantics.  Controversy and dispute are similar in meaning and  this  this was a legal dispute concerning facts. Controversy, is more a questioning of  beliefs concerning  non concrete ideology rather than  facts. So, I support 'Linux disputes' or even  Linux legal disputes. Aspro (talk) 14:06, 13 April 2018 (UTC)
 * Support either "SCO–Linux controversies" per nom or "SCO–Linux disputes" per No such user. Reasons listed by others above. Paintspot Infez (talk) 00:04, 15 April 2018 (UTC)
 * Comment as nominator, I think that @No such user's suggested "SCO–Linux disputes" is an improvement on "controversies". It better describes the cat's contents. -- Brown HairedGirl (talk) • (contribs) 02:48, 16 April 2018 (UTC)
 * Rename to whatever title does not contain a slash, since it was a speedy move under WP:SLASH, the easiest move is just to get rid of the slash by direct substitution. Though I agree that "disputes" makes a better title. -- 70.51.203.56 (talk) 15:01, 16 April 2018 (UTC)


 * The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.

Intro wording
All the article needs  now is the intro to be reworded. Think that: The SCO–Linux disputes were  a series of legal and public arguments between the software company SCO Group (SCO) and various Linux vendors and users would suffice. Notice present tense 'are' is replaced by  'were' (plural simple past tense indicative). Second paragraph is should be replaced by 'are'. Anyone agree along these lines? Aspro (talk) 18:16, 17 April 2018 (UTC)

Update, summary, current status?
Could someone who's been following these cases update this page, summarize and collate the information present, and also provide the current status? I'm asking because I followed a link from Berkeley_Packet_Filter, which right now states:


 * In August 2003, SCO Group publicly claimed that the Linux kernel was infringing Unix code which they owned. Programmers quickly discovered that one example they gave was the Berkeley Packet Filter, which in fact SCO never owned. SCO has not explained or acknowledged the mistake but the ongoing legal action may eventually force an answer.

This sounds like it was written 10+ years ago and not updated since --- but sadly so does this page. New information has been added, for sure, but the ,,big picture`` is missing. I'd be very happy if someone could take care of that. 178.11.76.218 (talk) 13:26, 3 January 2020 (UTC)