EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

10.15.09

Jeremy Allison Recommends Passing Mono Software to Basket of Proprietary Software

Posted in GNU/Linux, Marketing, Microsoft, Mono, Novell, Patents, Samba at 5:14 pm by Dr. Roy Schestowitz

Jeremy Allison

Summary: Jeremy Allison from the Samba team argues that Mono and applications that depend on Mono should be put in “restricted” repositories

Jeremy Allison comes from Novell and so does Mono, which was acquired by the company along with Ximian. But as our interview with Allison shows, this man who worked for Novell (on Samba) was brave enough to make his voice heard and finally move to Google. He protested against the patent deal with Microsoft. Just as a reminder and a little bit of background, Novell issues have not been resolved yet*.

“A few days ago we also wrote about Git#, which is part of the trend of making GNU/Linux building blocks more closely tied to Microsoft APIs and/or programming languages.”Novell’s Banshee has a new release but little is said about the fact that the software uses parts of Mono that Microsoft explicitly excluded from its Community Promise, which means that the software is only “safe” for Novell customers to use.

A few days ago we also wrote about Git#, which is part of the trend of making GNU/Linux building blocks more closely tied to Microsoft APIs and/or programming languages. Here is some newer coverage of Git# from a source that typically promotes a lot of Microsoft tools.

GNU/Linux expert, distribution developer, and author Chris Smart has just added this to evidence that “Mono is a [Microsoft] trap.”

Still aren’t convinced that Mono is a trap which ultimately only benefits Microsoft?

Take a look at this “Highly Confidential” document from Microsoft (from Comes vs Microsoft case) entitled “Effective Evangelism” and decide for yourself. It exposes Microsoft’s game plan for dominating the market with their platforms (which we already know, but some choose to ignore).

To quote a memorable (and not out-of-date) quote from Microsoft President Bob Muglia: “There is a substantive effort in open source to bring such an implementation of .Net to market, known as Mono and being driven by Novell, and one of the attributes of the agreement we made with Novell is that the intellectual property associated with that is available to Novell customers.

Next, this brings us to Jeremy Allison’s latest good columns where he politely approaches one problem with Mono.

But the problem is that Mono is dangerous for Free Software. The heart of the matter is, as usual, software patents. Microsoft have patents on the technology inside .NET, and since the Tom Tom lawsuit, Microsoft have shown they are not averse to attacking Free Software using patent infringement claims. Microsoft have tried to allay some fears by putting the .NET specification under their “Microsoft Community Promise” which you can read here:

http://www.microsoft.com/interop/cp/default.mspx

Miguel hailed this a the solution to all the patent problems with Mono. But this promise is simply not good enough to base a language environment implementation upon. After all, if the rug is pulled out from under that implementation by the threat of patent infringement you don’t just lose the implementation itself, you lose all the programs that depend upon it. That’s a really dangerous situation for Free Software programs to be in. The Free Software Foundation wrote a good analysis of the problems with this promise here:

http://www.fsf.org/news/2009-07-mscp-mono

But my basic issue with the Microsoft Community Promise is that Miguel doesn’t have to depend on it like everyone else does. Miguel’s employer, Novell, has a patent agreement with Microsoft that exempts Mono users from Microsoft patent aggression, so long as you get Mono from Novell.

The emphasis above is not ours. Allison knew about the Novell deal and also saw it from the inside ahead of journalists. Allison also proposes a solution:

Microsoft isn’t playing games any more by merely threatening to assert patents. Real lawsuits have now occurred and the gloves are off against Free Software. Moving Mono and its applications to the “restricted” repositories is now just plain common sense.

That would include applications like Tomboy and F-Spot.

“Mono is a problem for many reasons, the main of which is the fact that it promotes Microsoft, the company which attacks Free software more than many other companies combined.”There are many comments on this new article (lots more to come), which include: “Nasty stuff! In the meantime, RedHat keeps a strong leadership in the server, and I am starting to move my desktops to purely Qt/KDE installs (to avoid any Mono contamination).

Why is Novell doing this to itself? Or is it doing it for Microsoft? Mono is a problem for many reasons, the main of which is the fact that it promotes Microsoft, the company which attacks Free software more than many other companies combined. Mono puts Microsoft in control of developers (as in “developers developers developers developers”) and on top of this there are software patents to tighten the grip.

Imitation is rarely the path to winning (or just winning over developers). In order to recruit new support for Free(dom) software, one needs to offer something unique; experience suggests that Mono failed to attract even Visual Studio people.

In Novell’s headquarters, what’s debated at the moment are issues of marketing, not necessarily freedom. A longtime apologist of the Novell/Microsoft relationship elaborates on this subject.
_____
*This Web site’s goal remains to put pressure on Novell — using its customers — and to rectify its commitment to its suppliers, the Free software world which includes not just developers but also other companies (development peers), enthusiastic users, and people who spread the software. The main issue with the deal is a combination of software patents and an obligation from Novell to do all sorts of things which advance Microsoft’s own ecosystem. SUSE intervention was attempted as means of alleviating or annulling the deal. Attempts were made in the past to do so through negotiation and many people who were using SUSE got involved, myself included. Novell argued that the deal with Microsoft was “irrevocable”, so there was little left to do but to protest through explanation of the consequences and have Novell regret the path that it chose.

Share this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

2 Comments

  1. Yuhong Bao said,

    October 15, 2009 at 9:00 pm

    Gravatar

    “Microsoft have patents on the technology inside .NET, and since the Tom Tom lawsuit, Microsoft have shown they are not averse to attacking Free Software using patent infringement claims. ”
    Yep, now you see why the news on tridge’s second version of the VFAT patent workaround patch that was buried in the hype about MS’s Hyper-V Linux kernel code “donation” was so important.

    Roy Schestowitz Reply:

    Indeed, I wrote about the impact of TomTom on Mono right here and also mentioned your post about VFAT several days ago.

What Else is New


  1. Links 22/5/2019: Mesa 19.0.5, Huawei and GNU/Linux, Curl 7.65.0, End of Antergos, Tails 3.14, ownCloud Server 10.2, Firefox 67.0

    Links for the day



  2. Quality of Patents is Going Down the Drain and Courts Have Certainly Noticed

    Uncertainty or lack of confidence in the patent system has reached appalling levels because heads of patent offices are just striving to grant as many patents as possible, irrespective of the underlying law



  3. EUIPO and EPO Abuses Growingly Inseparable

    'Musical chairs' at CEIPI and the EPO/EUIPO (Battistelli, Archambeau, Campinos) as well as joint reports never fail to reveal the extent to which EPO abuses are spreading



  4. Links 21/5/2019: China's GAFAM Exit, DragonFlyBSD 5.4.3

    Links for the day



  5. Links 20/5/2019: Linux 5.2 RC1, LibreOffice 6.3 Alpha, DXVK 1.2.1, Bison 3.4 Released

    Links for the day



  6. South Korea's Government Will Show If Microsoft Loves Linux or Just Attacks It Very Viciously Like It Did in Munich

    Microsoft's hatred of all things GNU/Linux is always put to the test when someone 'dares' use it outside Microsoft's control and cash cows (e.g. Azure and Vista 10/WSL); will Microsoft combat its longstanding urge to corrupt or oust officials with the courage to say "no" to Microsoft?



  7. Links 19/5/2019: KDE Applications 19.04.1 in FlatHub and GNU/Linux Adoption

    Links for the day



  8. The War on Patent Quality

    A look at the EPO's reluctance to admit errors and resistance to the EPC, which is its very founding document



  9. Watchtroll, Composed by Patent Trolls, Calls the American Patent System “Corrupt”

    Another very fine piece from Watchtroll comes from very fine patent trolls who cheer for Donald Trump as if he's the one who tackles corruption rather than spreading it



  10. Unified Patent Court Won't Happen Just Because the Litigation Microcosm Wants It

    Unified Patent Court (UPC) hopefuls are quote-mining and cherry-picking to manufacture the false impression that the UPC is just around the corner when in reality the UPC is pretty much dead (but not buried yet)



  11. Links 17/5/2019: South Korea's GNU/Linux Pivot, Linux 5.1.3

    Links for the day



  12. Q2 Midterm Weather Forecast for EPOnia, Part 4: Happy Birthday to the Kötter Group?

    This year the Kötter Group commemorates the 85th anniversary of its existence. But is it really a cause for celebration or would a less self-congratulatory approach be more fitting? And does it create the risk that a routine tendering exercise at the EPO will turn into Operation Charlie Foxtrot?



  13. Links 16/5/2019: Cockpit 194, VMware Acquires Bitnami, Another Wine Announcement and Krita 4.2.0 Beta

    Links for the day



  14. The EPO's Key Function -- Like the UPC's Vision -- Has Virtually Collapsed

    The EPO no longer issues good patents and staff is extremely unhappy; but the Office tries to create an alternate (false) reality and issues intentionally misleading statements



  15. Stanford's NPE Litigation Database Makes a Nice Addition in the Fight Against Software Patent Trolls

    As the United States of America becomes less trolls- and software patents-friendly (often conflated with plaintiff (un)friendliness) it's important to have accurate data which documents the numbers and motivates better policy; The NPE (troll) Litigation Database is a move towards that and it's free to access/use



  16. Q2 Midterm Weather Forecast for EPOnia, Part 3: “Ein kritikwürdiges Unternehmen”

    A brief account of some further controversies in which the Kötter Group has been involved and its strained relations with German trade unions such as Verdi



  17. EPO Had a Leakage Problem and Privacy of Stakeholders Was Compromised, Affecting at Least 100 Cases

    The confidentiality principle was compromised at the EPO and stakeholders weren't told about it (there was a coverup)



  18. Links 15/5/2019: More Linux Patches and More Known Intel Bugs

    Links for the day



  19. False Hope for Patent Maximalists and Litigation Zealots

    Patent litigation predators in the United States, along with Team UPC in Europe, are trying to manufacture optimistic predictions; a quick and rather shallow critical analysis reveals their lies and distortions



  20. The Race to the Bottom of Patent Quality at the EPO

    The EPO has become more like a rubber-stamper than a patent office — a fact that worries senior staff who witnessed this gradual and troublesome transition (from quality to raw quantity)



  21. Q2 Midterm Weather Forecast for EPOnia, Part 2: Meet the Kötters

    An introduction to the Kötter Group, the private security conglomerate which is lined up for the award of a juicy EUR 30 million contract for the provision of security services at the EPO



  22. Links 14/5/2019: Red Hat Satellite 6.5, NVIDIA 430.14 Linux Driver and New Security Bug (MDS)

    Links for the day



  23. Links 14/5/2019: GNU/Linux in Kerala, DXVK 1.2, KDE Frameworks 5.58.0 Released

    Links for the day



  24. Q2 Midterm Weather Forecast for EPOnia, Part 1: Urgent Shitstorm Alert

    Experts at the European Patent Office's (EPO) weather observation station have just issued an urgent alert warning about a major shitstorm looming on the horizon



  25. Patents That Were Gleefully Granted by the EPO Continue to Perish in Courts

    The decreasing quality of granted European Patents already becomes a growing problem if not a crisis of uncertainty



  26. Links 13/5/2019: ExTiX 19.5 and GNU Radio Conference 2019

    Links for the day



  27. The Microsoft Guide to the Open Source Galaxy

    Thou shalt not...



  28. Microsoft Would Kill the Goose for Money

    Microsoft is just 'monetising' Open Source by using it as 'bait' for Microsoft's proprietary software; those who we might expect to antagonise this have effectively been bribed by Microsoft



  29. Links 13/5/2019: Nanonote 1.2.0, OpenMandriva Lx 4.0 RC, and GNUnet 0.11.4

    Links for the day



  30. Professionally Incompetent EPO Management

    The EPO remains an awful employer, with top-level management largely responsible for the loss of talent and even money


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts