


Novell Goes Public with Microsoft Linux Deal 133
InfoWorldMike writes "On the back of defending the agreement this week, Novell did as promised and published details of its landmark November 2006 Linux partnership agreements with Microsoft. Linux advocates are expected to scour the documents for signs of how the agreement may affect Linux and whether anything in it will put Microsoft or Novell in potential violation of the upcoming version 3 of the GNU General Public license (GPL). The GPL is used in licensing many components of the Linux operating system. Open-source advocate Bruce Perens said he would be looking to see exactly what Novell was given through the deal and whether there is any requirement for the Linux vendor to defend Microsoft's patent claims. 'What I'm actually looking for is, to what extent was there a violation of faith?' he said."
Actual Patent Agreement (Score:5, Informative)
I am no lawyer (but I do read contracts from time to time, as a 'hobby'), but this is really an odd 'covenant'. The agreement appears to not state what products are actually covered by the patent covenant, in bizarre ways. For example, "Clone Products" are not covered, "Clone Products" being presumably things like Mono and OpenOffice (as they duplicate Microsoft APIs and products); yet all such products already designed at time of signing are exempt, i.e., they are covered. Yet, the following projects are not subject to the exemption: "Wine, OpenXchange, StarOffice and OpenOffice", i.e., they are not covered. So OpenOffice appears to not be covered.
Likewise Samba would presumably be a "Clone Product", and not covered as well, except by the exemption due to its existing at time of signing. Yet this might not cover additional functionality added later. It just isn't clear.
No actual products are named aside from the quote above, and even they are not stated as being covered or not (just not exempted by a particular subsection). So, reading this, I can't tell whether Novell customers are in fact covered or not, in any way. The assumption was always that the agreement did protect them from patent lawsuits. But that assumption may have been wrong.
Is the contract specifically designed to not mention any products, effectively letting it be ambiguous and perhaps of no legal use - that is, only effective for PR purposes?
Re:Actual Patent Agreement (Score:4, Informative)
Re:Actual Patent Agreement (Score:5, Informative)
Really? Care to give a citation for that claim? Some features of Xenix were merged into SVR4 around 1990, but that's hardly 20 years ago, and I don't recall any mention of royalties being paid to Microsoft for using SVR4 source code. Anyway, Xenix would have required Microsoft to strike some sort of licensing deal with AT&T in the first place, as they owned the source code that Xenix was based on. I'm not sure what point SCO (old-SCO that is) ended their relationship with MicroSoft, but that may have predated the merging of Xenix features into AT&T's codebase anyway.
Re:Actual Patent Agreement (Score:3, Informative)
Following the links from the article I ended up here [infoworld.com] which does explicitly state that Microsoft and Novell will collaborate to improve interoperability between Microsoft Office and OpenOffice, also between Microsoft Active Directory and Novell eDirectory.
Unfortunately all the links in that article to the SEC filings are 404s.
Re:No right to distribute (Score:4, Informative)
Re:Fair is Fair (Score:5, Informative)
Re:Actual Patent Agreement (Score:3, Informative)
Re:Actual Patent Agreement (Score:1, Informative)
Re:Mono is not Visual Studio (Score:1, Informative)
And obviously you don't have the slightest clue about what "clone" means in software world either. Something written from scratch to mimic something else is a clone.