from the versionctl⠀-alt⠀-del dept.
[Update 20180604 @ 14:00 UTC: Acquisition confirmed. Microsoft is paying $7.5 billion in stock. Coverage at Microsoft, Security Week, The Register, and The Verge. Also, see the Microsoft blog post. --martyb]
Microsoft has reportedly acquired GitHub, and could announce the deal as early as Monday. Bloomberg reports that the software giant has agreed to acquire GitHub, and that the company chose Microsoft partly because of CEO Satya Nadella. Business Insider first reported that Microsoft had been in talks with GitHub recently.
Time to move off GitHub?
Previously: Microsoft Holds Acquisition Talks with Github
An AC also submitted Bloomberg's article.
Microsoft held talks in the past few weeks to acquire software developer platform GitHub, Business Insider reports.
One person familiar with the discussions between the companies told CNBC that they had been considering a joint marketing partnership valued around $35 million, and that those discussions had progressed to a possible investment or outright acquisition. It is unclear whether talks are still ongoing, but this person said that GitHub's price for a full acquisition was more than Microsoft currently wanted to pay.
GitHub was last valued at $2 billion in its last funding round 2015, but the price tag for an acquisition could be $5 billion or more, based on a price that was floated last year.
A Google executive has admitted the search giant lost out on buying GitHub. Speaking at a Fortune Magazine event yesterday, Diane Greene Google's head of cloud made an interesting admission. "I wouldn't have minded buying them, but it's OK," said Greene, Bloomberg reports.
Previous rumors suggest Google was also trying to acquire GitHub, alongside Microsoft's bids. GitHub founder Chris Wanstrath reportedly chose Microsoft because of his relationship with CEO Satya Nadella. GitHub is a large code repository that has become very popular with developers and companies to host projects, documentation, and code. Apple, Amazon, Facebook, Google, and many other big tech companies use GitHub. There are 85 million repositories hosted on GitHub, and 28 million developers contribute to them.
In its fifth year of life, some promising development of a Playstation 4 emulator has emerged thanks to its mostly standard PC architecture and abundant FOSS projects to draw from. From wololo.net:
Orbital is the combination of three separate projects which together allow us to boot into PS4 kernels. Those being:
orbital-bios, orbital-grub and the most important part: orbital-qemu. A summary of these would be that orbital-bios is a SeaBIOS fork to add support to the PS4 quirks (no VGA, no ISA bus, etc.). This is needed because the PS4 is not really a PC. orbital-grub simply forks GRUB and adds a modified freebsd bootloader to add support for Orbis kernels, since they include custom sections written by Sony and orbital-qemu is a QEMU fork that adds support for PS4 hardware: Aeolia (USB, Ethernet, etc. etc.) and Liverpool (GPU and Audio).
It seems they were able to translate the graphics stack to run on top of Vulcan fairly well, but this system currently requires a physical DualShock 4 connected to the host with USB passthrough. Further, it can only work with decrypted firmwares made available via previously known exploits on physical consoles.
The Free Software Foundation (FSF) has published five of the white papers it funded regarding questions about Microsoft Copilot. After Microsoft acquired GitHub, it set up a machine learning system to cull through its archive of software, called Copilot. The approach chosen and even the basic activity raises many questions starting with those of licensing.
Microsoft GitHub's announcement of an AI-driven Service as a Software Substitute (SaaSS) program called Copilot -- which uses machine learning to autocomplete code for developers as they write software -- immediately raised serious questions for the free software movement and our ability to safeguard user and developer freedom. We felt these questions needed to be addressed, as a variety of serious implications were foreseen for the free software community and developers who use GitHub. These inquiries -- and others possibly yet to be discovered -- needed to be reviewed in depth.
In our call for papers, we set forth several areas of interest. Most of these areas centered around copyright law, questions of ownership for AI-generated code, and legal impacts for GitHub authors who use a GNU or other copyleft license(s) for their works. We are pleased to announce the community-provided research into these areas, and much more.
First, we want to thank everyone who participated by sending in their papers. We received a healthy response of twenty-two papers from members of the community. The papers weighed-in on the multiple areas of interest we had indicated in our announcement. Using an anonymous review process, we concluded there were five papers that would be best suited to inform the community and foster critical conversations to help guide our actions in the search for solutions.