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

12.18.09

Microsoft Gave Moonlight “Blessings” in 2007

Posted in FSF, GNOME, GNU/Linux, Microsoft, Mono, Novell, Patents at 6:10 am by Dr. Roy Schestowitz

“Every line of code that is written to our standards is a small victory; every line of code that is written to any other standard, is a small defeat.”

James Plamondon, Microsoft Technical Evangelist. From Exhibit 3096; Comes v. Microsoft litigation [PDF]

Summary: Analysis and deconstruction of the latest Moonlight PR; more about Mono and the GNU/GNOME kerkuffle

SOME people have begun responding to news regarding Moonlight. The following article uses an amusing headline which says that “Moonlight 2.0 Gets Microsoft’s Blessing”

Considering the fact that it’s a Microsoft project as much as it is a Novell project (the Novell/Microsoft Web site calls it "Microsoft Moonlight"), why would it need any additional “blessings”? Microsoft has blessed the project since its inception.

In 2006, Novell and Microsoft (NASDAQ: MSFT) entered into a joint patent and interoperability agreement, giving Novell users the OK to use open source technologies on which the software giant has said it may have intellectual property claims.

As a result of today’s expansion of that deal, Moonlight users will enjoy protection under the patent covenant regardless of whether they’re using Novell’s (NASDAQ: NOVL) Linux distro or another distributor’s.

Here is how Miguel de Icaza put it:

Culturally, we started on two opposite ends of the software licensing spectrum. The covenant not to sue that was issued for Moonlight 1 and 2 covered every user that used Moonlight, but only as long as the user obtained Moonlight from Novell. This is a model similar to how Flash is distributed: there is a well-known location where you get your plugin.

The open source world does not work that way though. In the open source world, the idea is to release source code and have distributions play the role of editors and curators and distribute their own versions of the software.

Microsoft’s intention was to expand the reach of Silverlight, but the original covenant was not a good cultural fit. We worked with the team at Microsoft (Brian Goldfarb and Bob Muglia’s teams) to make sure that the covenant would cover the other Linux distributions.

Microsoft’s intention is still “to expand the reach of Silverlight,” which it totally controls, unlike HTML for example. The biggest issue — as we have argued for years — is one of control. Patents are another issue, but not the main one. Moonlight (like Mono) gives Microsoft the sceptre and crown with which to rule and watch over FOSS developers. If they use Microsoft as their reference, then it not only helps Microsoft’s fight against Web standards but also against LAMP and Java, among a lot of other software. It’s mono-culture.

The Source (same author as Mono-Nono) has responded to the above announcement and made some predictions.

Here are my predictions, based on the last similar situation when Mono fell under the “promise” from Microsoft:

1. The new covenant will not be as comprehensive as Mr. de Icaza states. I do think he isn’t overselling this one near as much as the last one, which I think points to a lesson learned.
2. Team Mono will rail on and on about how this is a win for them and should “silence the critics”, never noting the incovenient fact that they promoted Moonlight just as hard without the “proper” coverage, and there are still remaining issues.
3. There will still be at least 3 obvious problems with the “Covenant” and a half-dozen subtle and complicated problems.

Our reader Oiaohm says that “the Moonlight agreement still sucks. It expires September 1, 2011.”

In other news, one reader told us that Storm OS is adding Mono software that falls outside the Microsoft Community Promise and thus makes it sensitive to Microsoft’s threats and lawsuits (both deterrents).

Here is something I’ve been working on for a little while, getting Mono to work properly. Properly = with dbus so you actually runs some apps with it. Banshee, F-Spot, Gnome-do and Monodevelop appear to be working with very few changes

According to Microsoft’s own words (no speculation), this is trouble. Longtime proponents of Mono (like Ryan Paul and others who still give it coverage) should pay more attention to the issues and bring light to them. The latest episode from Linux Outlaws (recommended show) is titled “Reverse Mono Trojan Horse”

Another proponent of Mono, Thom Holwerda (mentioned a few days ago in the same context), writes a little more about GNOME and GNU [1, 2, 3]. So does Bruce Byfield (whose words we unfortunately misinterpreted the other day, so we sincerely apologise to him). The latest from Byfield is a good writeup which concludes with:

Staying within the GNU Project may have very little practical effect on GNOME. However, making any formal decision under these circumstances might. At the very least, any vote might be delayed six months so that people have a chance to consider the idea on its merits and not on the emotions stored up over the last six months.

Genuine critics of GNU do exist (Lasse Havelund for example), but some of the more proactive and vocal critics appear to be doing this for other reasons. Someone quoting Upton Sinclair says that “It’s hard get a man to understand something, when he’s being paid not to understand it.”

“It’s probably better to keep funding and decision-making separate. Decide who gets to make decisions based on merit, not money.”
      –MinceR
He adds: “perfectly nails all these corporate swine trying to defame RMS and ruin Free Software.”

Our reader Brandon says: “some idiot keeps going around saying FSF accepts corporate funding as well, however GNOME is set up in a way where if you fund them via businesses, you get onto the “advisory board” which makes suggestions to the executives. this is exactly like the congress – lobbying connection – whereas, in other projects such as Apache, they will take your funding but won’t let you dictate [anything]. Apache has funding from MSFT, but they’ve publicly said that doesn’t mean crap because they still make all the decisions. GNOME on the other hand, with the advisory board at least has to listen to these suggestions. They don’t have to act upon them, but they gotta listen still.”

“It’s probably better to keep funding and decision-making separate. Decide who gets to make decisions based on merit, not money,” says MinceR in response.

Brandon adds: “I can’t find an equivalent in FSF for a corporately paid subsection which gets to tell board members suggestions based on them paying tens of thousands of dollars. I don’t mind if an organization takes funding, but funding/decisions should be separate. The “advisory board” is just a euphemism for “lobbying board”, I can’t see how its different. They pay tens of thousands of dollars, and get to make suggestions. Lobbyists pay congresspeople tens of thousands of dollars, and get to make suggestions.”

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

What Else is New


  1. [ES] Con la UPC Muerta por el Resto del Termino de Battistelli, No Hay Razón para que la EPO o el Consejo Administrativo Sigan Manteniéndolo Más

    Pensamientos acerca de lo que pasará al líderazgo de la EPO después de ‘Brexit’ (salida Británica de la EU), lo que sevéramente socava el proyecto más grande de Battistelli el que usaba habituálmente para justificar sus increíbles abusos



  2. [ES] El Caradura Benoît Battistelli Debería Renunciar a Luz de la Filtrada Nueva Decisión en Su Vendeta en Contra de un Juez que se Atrevió a Decir la Verdad (Actualizado)

    Benoît Battistelli continúa quebrando las propias reglas de la EPO, no sólo las leyes naciónales, como una nueva decisión ayuda a revelar



  3. [ES] Cada Vez Más Parece Que Battistelli está Escondiéndo ‘Evidencia’ Falsa y/o Ilegalmente Obtenda de la Unidad Investigativa de la EPO

    El porqué creemos que Benoît Battistelli está cada vez mas desesperado de esconder operaciónes ilícitas de reunir ´evidencia´ lo que eventuálment lo puso a él mismo — no al acusado — en una situación catastrófica situacion que lo puede forzar (esperamos) a us renuncia



  4. Links 28/6/2016: Vista 10 Updategate, OpenMandriva 3.0 Beta 2

    Links for the day



  5. Links 27/6/2016: Linux 4.7 RC 5, OpenMandriva Lx 3.0 Beta 2

    Links for the day



  6. From Alleged Organised Crime to Vice-President of the European Patent Office (EPO)

    Željko Topić's situation in Croatia illuminated by means of recent documents from the authorities



  7. Battistelli May Still be on the Way Out as Pressure Grows in Germany, UPC in Shambles

    Pressure on Battistelli is growing even from within circles that are traditionally protective of him and a long letter is sent to Dr. Christoph Ernst, who some believe will replace Battistelli



  8. Caricature: European Patent Office (EPO) Under Battistelli

    The latest caricature about the state of the European Patent Office (EPO)



  9. Techrights (Almost) at 10: From Software Patents to Novell and to Present Focus on EPO

    A short story about how and why we ended up writing so much about the European Patent Office (EPO) and the impact beyond Europe



  10. Patents Roundup: Bad Quality (USPTO), Bad Analysis (India), Bad Microsoft, Bad Actors (Trolls), Bad Scope (Software Patents), and the Ugly

    A mishmash of news about patents, mostly regarding the United States, and what can be deduced at the moment



  11. Links 26/6/2016: IceCat 38.8.0, Wine 1.9.13

    Links for the day



  12. With UPC Dead for Battistelli's Entire Remaining Term, No Reason for the EPO or the Administrative Council to Keep Battistelli Around

    Thoughts about what happens to the EPO's leadership after 'Brexit' (British exit from the EU), which severely undermines Battistelli's biggest project that he habitually used to justify his incredible abuses



  13. Links 24/6/2016: Xen Project 4.7, Cinnamon 3.0.6

    Links for the day



  14. Benoît Battistelli Should Resign in Light of New Leak of Decision in His Vendetta Against Truth-Telling Judge (Updated)

    Benoît Battistelli continues to break the EPO's own rules, not just national laws, as a new decision helps reveal



  15. Fake Patents on Software From Fake Australian 'Inventor' of Bitcoin and the Globally-Contagious Nature of EPO Patent Scope

    News from Australia regarding software patents that should not be granted and how patent lawyers from Australia rely on European patent law (EPO and UK-IPO) for guidance on patent scope



  16. Patent Lawyers Love (and Amplify) Halo and Enfish, Omit or Dismiss Cuozzo and Alice

    By misinterpreting the current situation with respect to software patents and misusing terms like "innovation" patent lawyers and others in the patent microcosm hope to convince the public (or potential clients) that nothing in effect has changed and software patents are all fine and dandy



  17. Looks Increasingly Plausible That Battistelli is Covering up Bogus and/or Illegally-Obtained 'Evidence' From the EPO's Investigative Unit

    Why we believe that Benoît Battistelli is growingly desperate to hide evidence of rogue evidence-collecting operations which eventually landed himself -- not the accused -- in a catastrophic situation that can force his resignation



  18. As Decision on the UK's EU Status Looms, EPO Deep in a Crisis of Patent Quality

    Chaotic situation at the EPO and potential changes in the UK cause a great deal of debate about the UPC, which threatens to put the whole or Europe at the mercy of patent trolls from abroad



  19. Another Demonstration by European Patent Office (EPO) Staff on Same Day as Administrative Council's Meeting

    SUEPO (staff union of the EPO) continues to organise staff actions against extraordinary injustice by Benoît Battistelli and his flunkies whom he gave top positions at the EPO



  20. Links 23/6/2016: Red Hat Results, Randa Stories

    Links for the day



  21. Interview With FOSSForce/All Things Free Tech

    New interview with Robin "Roblimo" Miller on behalf of FOSSForce



  22. Links 22/6/2016: PulseAudio 9.0, GNOME 3.21.3 Released

    Links for the day



  23. IP Europe's UPC Lobbying and the EPO Connection

    The loose but seemingly ever-growing connections between AstroTurfing groups like IP Europe (pretending to represent SMEs) and EPO staff which is lobbying-centric



  24. EPO “Recruitment of Brits is Down by 80%”

    Letter says that “recruitment of Brits is down by 80%” and "the EPO lost 7% of UK staff in one year"



  25. The Conspiracy of Patent Lawyers for UPC and Battistelli's Role in Preparing by Firing People

    The parasitic firms that lobby for the UPC and actually create it -- firms like those that pass money to Battistelli's EPO -- are doing exactly the opposite of what Europe needs



  26. Patent Lawyers, Having Lost Much of the Battle for Software Patents in the US, Resort to Harmful Measures and Spin

    A quick glance at how patent lawyers and their lobbyists/advocates have reacted to the latest decision from the US Supreme Court (Justice Breyer)



  27. Links 21/6/2016: Fedora 24 and Point Linux MATE 3.2 Officially Released

    Links for the day



  28. Supreme Court on Cuozzo v Lee Another Major Loss for Software Patents in the United States

    Much-anticipated decision on the Cuozzo v Lee case (at the highest possible level) serves to defend the appeal boards which are eliminating software patents by the thousands



  29. As Alice Turns Two, Bilski Blog Says 36,000 (Software) Patent Applications Have Been Rejected Thanks to It

    A look back at the legacy of Alice v CLS Bank and how it contributed to the demise of software patents in the United States, the birthplace of software patents



  30. EPO Self-Censorship by IP Kat or Just Censorship of Opinions That IP Kat Does Not Share/Accept (Updated)

    ree speech when it's needed the most (EPO scandals) needs to be respected; or why IP Kat shoots itself in the foot and helps the EPO's management by 'sanitising' comments


CoPilotCo

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

CoPilotCo

Recent Posts