Language Selection

English French German Italian Portuguese Spanish

From Microsoft: C# and CLI under the Community Promise

Filed under
Microsoft

First the big news: Microsoft will be applying the Community Promise patent licensing to both C# and the CLI.

The announcement was done by Peter Galli at Microsoft over at Port25 and it states:

I have some good news to announce: Microsoft will be applying the Community Promise to the ECMA 334 and ECMA 335 specs.

ECMA 334 specifies the form and establishes the interpretation of programs written in the C# programming language, while the ECMA 335 standard defines the Common Language Infrastructure (CLI) in which applications written in multiple high-level languages can be executed in different system environments without the need to rewrite those applications to take into consideration the unique characteristics of those environments.

"The Community Promise is an excellent vehicle and, in this situation, ensures the best balance of interoperability and flexibility for developers," Scott Guthrie, the Corporate Vice President for the .Net Developer Platform, told me July 6.
It is important to note that, under the Community Promise, anyone can freely implement these specifications with their technology, code, and solutions.

You do not need to sign a license agreement, or otherwise communicate to Microsoft how you will implement the specifications.

rest here




Also: Microsoft has something called a community promise?

Promises, promises

theopensourcerer.com: Microsoft made an interesting announcement, they are promising not to sue people for using Mono. Jolly good of them really, it is nice not being sued.

Lets just assume for the moment that this promise means what they say it means (forgetting about the partial implementations exclusion and the fact that the promise needed to be made in the first place) and it makes Mono totally safe to use now, even in countries with broken patent laws. I still won’t be using Mono.

Rest Here

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Octa-core Cortex-A53 hacker SBC sells for $60

FriendlyARM’s $60, open spec “NanoPC-T3” SBC runs Android or Linux on an octa-core Cortex-A53 SoC packed with wireless and media interfaces, plus 8GB eMMC. The over-caffeinated board builders at Guangzhou, China-based FriendlyARM have shipped their highest-end hacker board yet. The NanoPC-T3 is almost identical to the NanoPC-T2 board, but swaps out the quad-core, Cortex-A9 Samsung S5P4418 SoC for a layout-compatible S5P6818 with eight Cortex-A53 cores that can be clocked dynamically from 400MHz to 1.4GHz. Last month, FriendlyARM’ unveiled an $11, quad-core NanoPi M1 single board computer with similarly open source hardware and Android and Linux software. Read more

today's leftovers

Linux and Graphics

Security Leftovers

  • Cockpit 0.104
    Cockpit is the modern Linux admin interface. There’s a new release every week. Here are the highlights from this weeks 0.104 release.
  • FFmpeg 3.0.2 "Einstein" Multimedia Framework Released with Updated Components
    Today, April 28, 2016, the development team behind the popular FFmpeg open-source and cross-platform multimedia framework has released the second maintenance release in the stable FFmpeg 3.0 "Einstein" series. FFmpeg 3.0 was a massive release announced in mid-February, which brought in numerous existing changes, including support for decoding and encoding Common Encryption (CENC) MP4 files, support for decoding DXV streams, as well as support for decoding Screenpresso SPV1 streams.
  • Using bubblewrap in xdg-app
    At the core of xdg-app is a small helper binary that uses Linux features like namespaces to set up sandbox for the application. The main difference between this helper and a full-blown container system is that it runs entirely as the user. It does not require root privileges, and can never allow you to get access to things you would not otherwise have.
  • Build System Fallbacks
    If you are using Builder from git (such as via jhbuild) or from the gnome-builder-3-20 branch (what will become 3.20.4) you can use Builder with the fallback build system. This is essentially our “NULL” build system and has been around forever. But today, these branches learned something so stupidly obvious I’m ashamed I didn’t do it 6 months ago when implementing Build Configurations.
  • Node.js version 6 is now available