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. Emerging Threat to Patent Reforms at the USPTO

    Our plan of returning to coverage of US patent affairs in the wake of powerful lobbies that pursue patent maximalism



  2. You Know That the Unitary Patent (UPC) is in Huge Peril When Its Biggest Fans Admit It's Unlikely to Happen Even Next Year

    The tactics of Team UPC turn ugly as they personally target anyone who stands in their way, even a professor/judge who is courageous enough to state the obvious



  3. More Than Six Human Casualties Under Battistelli at the EPO, But the Human Toll Can Become a Lot Worse

    The bigger or much broader picture detailing the high cost of autocracy and mental torture at the EPO, where lives are ruined not only when these are ended and some key buildings pose severe threat to a lot of workers



  4. EPO's Elodie Bergot Calls Staff Suicide Just 'Passing Away', Pretends to Care

    How the EPO continues to mislead if not lie to staff, even when staff commits suicide -- a growing problem for Team Battistelli, whom some insiders hold accountable for these deaths



  5. The Administrative Tribunal of ILO Will Deliver EPO Judgments in Six Days

    Despite its old age (nearly a century), ILO's tradition when it comes to enforcing the law is anything but sterling, yet one can hope that it will stop its unproductive cat-and-mouse game with the EPO, where compliance is rare and actual judgments (not deferrals/referrals) are even rarer



  6. Links 21/6/2017: Red Hat's Numbers Are Up, New Debian Being Studied

    Links for the day



  7. Another Suicide Reported at the EPO While the Paid-for Media Focuses on 'European Inventor Award' Charade

    Puff pieces for Benoît Battistelli published aplenty while the European media refuses to deal with the reality -- not paid-for illusions -- at the European Patent Office



  8. Links 20/6/2017: Chuwi Lapbook, Linux 4.12 RC6, Mesa 17.1.3

    Links for the day



  9. At the European Inventor Award Ceremony Benoît Battistelli Lied to a Lot of Scientists and “Media Partners” About the UPC

    The Liar in Chief, Benoît Battistelli, still lives in a fantasy world or simply lies intentionally, which would be worse



  10. Contact Details for the EPO's Administrative Council Delegations

    List of Heads of Delegation and their E-mail addresses (used to be public information before Benoît Battistelli's oppressive regime or coup)



  11. Don't Forget to Vote for EPO Strike This Week (Thursday)

    A reminder that there's a vote on a strike at the European Patent Office later this week, giving an opportunity to rebut the "vocal minority" myth which Benoît Battistelli likes to spread



  12. European Patent Office (EPO) Whistleblowing Guidelines: Motivation and Impact of Leaks

    Advice on when to leak and what to leak for the desired effect, which is reformatory (though transparency and accountability)



  13. Links 18/6/2017: New Debian Release, Catchup With a Lot of News

    Links for the day



  14. Appalling Press Coverage Regarding the Unitary Patent (UPC)

    How the media has lied (and keeps lying) about the UPC, which the European public neither needs nor wants, putting aside serious constitutional issues that are associated with the UPC



  15. The Writings on the Wall at the European Patent Office: Number of Directors May Soon Decline From 150 to Just 65-70

    Battistelli is seizing more direct and indirect control over the European Patent Office (EPO), which is supposed to eject him with a proposal for replacement already formally prepared for publication



  16. European Patent Office (EPO) Whistleblowing Guidelines

    The first part of a series which offers tips for sending us material/evidence, specifically from the European Patent Office (EPO)



  17. General Consultative Committee of the EPO Warns About Battistelli's Plans

    The General Consultative Committee (GCC) issues a long document (176 pages) which explains to the overseer of the Office how internal rule changes make things even worse



  18. Links 16/6/2017: New Atom Release, Firefox 55 Beta

    Links for the day



  19. Leaked: European Patent Office Still Uses Microsoft Windows XP... in 2017

    The EPO continues to rely on inherently insecure (by design) platforms and Mr. Kraft, Battistelli's CIO, bragged that the actions of the Office "prevented any damage to the EPO and its reputation"



  20. Unitary Patent (UPC) Will Start “Real Soon” Now... Said Team UPC For So Many Years

    The Unitary Patent or Unified Patent Court Agreement (UPCA) is going nowhere fast, but those who spent time and money promoting it for self gain continue to lie to the press with overly optimistic predictions, unrealistic timelines, and Kool-Aid about the supposed 'benefits' of the Unified Patent Court (UPC)



  21. EPO Management Wastes Millions of Euros on a Silly, Gratuitous, Self-Serving Festival While EPO Staff is Planning Another Strike

    Unrest at the European Patent Office (EPO) is growing again, with plans of a strike resulting in a formal vote for a strike next week



  22. Links 15/6/2017: Mir 0.26.3, FreeNAS 11.0

    Links for the day



  23. Software Patents in Europe Are Still Promoted by the EPO, Even in Defiance of the Ban

    The European Patent Office continues to ignore the directive on the patentability of computer-implemented inventions, which had software patents disallowed with an overwhelming majority of 648 to 14 votes at the European Parliament



  24. Leaked: Job Advertisement for Removing Battistelli From the European Patent Office

    In spite of rumours that Benoît Battistelli would pursue elongation of his term, in clear defiance of the rules (again), paperwork is being put forth to replace him



  25. Links 14/6/2017: New BlackArch Linux ISO and Q4OS 1.8.6, Orion

    Links for the day



  26. Even UPC Proponents, Paid by the EPO's PR Firm, Admit That UPC May Never Happen

    Speculations are being floated regarding the cause of the impasse, which is going to result in a very long period of uncertainty and possibly the collapse of the Unified Patent Court (UPC) as it was envisioned by Michel Barnier, Benoît Battistelli and other opportunists



  27. Caricature: Balance of Justice at the European Patent Office

    Balance of justice under Battistelli's regime isn't quite what the Office wants the public and the Dutch authorities to believe



  28. Links 13/6/2017: Alpha Litebox Comes With GNU/Linux, Warning to Munich About Windows

    Links for the day



  29. A Massive Proponent of UPC, CIPA, Enters IP Kat, as Readers Call Out Stacked UPC 'Panels'

    On matters of patents, IP Kat continues moving to the right (patent maximalism, acceptance of Battistelli’s regime, UPC bubble and so on) and commentary to the contrary is not being accepted



  30. In Spite of Censorship by IP Kat, Issues Associated With UPC Had Become Apparent, Even Before Germany Halted Ratification

    IP Kat is allegedly still censoring comments whilst at the same time delivering promotional UPC puff pieces, notably but not only composed by Bristows staff, without even stating vested interests (disclosure of bias/agenda)


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