Microsoft, through the Windows blog, announced Project MU, an adaptation of the EDK II TianoCores project to Unified Extensible Firmware Interface (UEFI) making it open source, being leveraged by the company on Surface devices and newer versions of Hyper -V. The news was announced at 40 minutes of the second half of 2018, on December 19th more precisely.
MS began to implement the Project MU with the latest versions of Windows, thus having better scalability for the final product. According to the company, the move will benefit Servers, IoT, PC or anyone who wanted to use Project MU.
The statement also said that it is not a side project, mirror, clone or anything like that, and that it will be used in top-tier Microsoft products and kept to continue and allow its products to flow.
They also set primary goals for a first phase, which are:
– Actively share the tool code to solicit feedback and attract collaborating partners, as with any open source project;
– Promote, evangelize and support a shift in industry towards a more collaborative environment so that we can all build and maintain lower cost, higher quality products;
Which Microsoft is this?
Two interesting points made in the ad, they want to facilitate and standardize implementation for partners and thus break down some barriers. Which translated into the following statement:
Project Mu also attempts to address the complex business relationships and legal challenges facing our partners today. To build most products, proprietary closed code assets are usually required as well as standard open code codes. The distributed compilation system and the design of multiple repositories allow product teams to keep the code separate and connected to their original source while respecting legal and business limits.
And the other point was:
Today's open source projects, while extremely valuable, are very resource intensive to interact with. This friction can drive large companies away from the industry, avoiding public interaction, thus diminishing the overall value of the community. The modern era of open source projects has incorporated new tools and procedures to lessen this friction and our goal to leverage these tools. GitHub provides problem tracking, pull requests, gate builds, web-based code reviews, tracked / required, and CI / CD (continuous builds and tests). We believe that by leveraging and extending this automation and workflow, we can reduce friction and provide a safe place for all employees to work.
In addition, Microsoft comments on the desire to bring Firmware-as-a-Service (FaaS) into the Open Source world and bring some features, such as the ones they listed:
– A code structure and development process optimized for firmware as a service;
– an onscreen keyboard;
– Secure management of UEFI configurations;
Enhanced security by removing unnecessary legacy code, a practice known as attack surface reduction;
– High performance startup;
– Modern examples of BIOS menu;
– Numerous tests and tools for analyzing and optimizing UEFI quality, etc.
This is going to be great for those who have notebooks or desktops where manufacturers have their custom boot and some standard hindrances or compatibility with Linux don't bring it to the platform, but with Project MU this could be tweaked and let It should be a barrier to the open use of the system that the user wants in a simpler and more efficient way, as it would be standardized.
If you want to know more about the ad and the project, you can visit the Microsoft blog and the Project MU website.
I hope you, until next time and a big hug.
See an error or would you like to add any suggestions to this article? Collaborate, click here.