Constellation Insights

Google introduces 'zero-touch' enterprise deployment for Android devices: It's going to be easier and more secure to roll out enterprise Android devices, with Google's introduction of "zero-touch enrollment" capabilities.

Under the program, companies that purchase Android devices can use EMM (enterprise mobility management) software to automatically apply configurations and policies the first time a user turns the device on. Supported EMMs include VMWare AirWatch, BlackBerry, MobileIron, IBM and GSuite.

Initially, the feature is available only on Google's Pixel phone when purchased through Verizon. Google is working with Samsung, Huawei, Sony, LG and other device makers to add zero-touch; Sony's Xperia XZ1 and XZ1 Compact will be among the first additional devices to get it. Google is also working with a variety of other carriers besides Verizon.

POV: This is certainly a desirable feature given how much it can cut down on device management and end-user support tasks. It also has security benefits, since the devices won't ever be used in an un-managed state.

However, this is also an instance where Google is playing catch-up for a change, as Apple has offered similar capabilities through its Device Enrollment Program, as has Samsung with its Knox Mobile Enrollment service. It's nonetheless a welcome addition to Google's mobile enterprise capabilities with real benefits for customers.

Red Hat updates, expands its 'patent promise': In 2002, Red Hat issued a decree saying it would not enforce its patents against free and open-source software. Fifteen years later, the company has released a new version of the Patent Promise, one it says substantially extends the original's scope. Here's how Red Hat explains the decision, from an FAQ:

We issued the first Patent Promise 15 years ago. Since then, both Red Hat and open source have changed considerably, and some aspects of the Promise became outdated. Open source is what Red Hat does, and open innovation plays an increasingly important role in technology and beyond. Our expanded Patent Promise recognizes and is designed to protect open innovation.

The new Promise is substantially clearer and broader than its predecessor. While the old Promise covered approximately 35 percent of open source software, the new version will cover more than 99 percent. It applies to all software meeting the free software or open source definitions of the Free Software Foundation or the Open Source Initiative and listed by the FSF or OSI.

Both the original and new promise covered the entirety of Red Hat's patents. But the company today has more than 2,000 patents, compared to just a handful at the time of the first promise.

Both the new Promise and the original Promise covered all Red Hat’s patents. It’s worth noting that at the time of the original Promise, Red Hat had only a few patents, while now it has more than 2000.

POV: As a company based on open source software, Red Hat's pledge seems like a natural step. It doesn't appear that it provides any protection to companies from patent lawsuits brought by non-practicing entities—otherwise known as patent trolls—but clearly puts a flag in the ground stating that Red Hat is a trusted partner to companies looking to innovate with open-source software.

IBM open-sources Websphere Liberty for agile app development: Big Blue has open-sourced the code for Websphere Liberty, the ligher-weight version of its flagship Java application server. IBM's Ian Robinson explains why in a blog post:

We created Liberty five years ago to enable developers to easily and quickly create applications using agile and dev/ops principles. It has been an incredibly successful and popular transformation for WebSphere and now is the time to take it to the next level by moving the essential Liberty code base into the open.

This week IBM launched the Open Liberty project and moved our Liberty development effort to it. The code is available in GitHub under the Eclipse Public License V1, and our ongoing development for WebSphere Liberty will be based on this project. Open Liberty is focused on creating a runtime to support Java microservices that can be frequently updated and easily moved between different cloud environments.

At any time, developers can move up to the commercial versions of WebSphere Liberty, adding dedicated technical support and more advanced capabilities. Because Open Liberty and WebSphere Liberty are built on the same codebase this transition is seamless, so there’s no need to modify your applications.

POV: IBM is also open-sourcing its IBM J9 virtual machine implementation, which along with Open Liberty provides a full, IBM-approved Java stack.

While Open Liberty is easier to set up and manage, gets more frequent updates, and offers more deployment options than the full-blown WebSphere, it isn't as feature-rich. There are also many existing applications that would be difficult or not possible to move to Open Liberty due to feature gaps.

IBM is betting that moving Open Liberty to an open-source model will attract community support and subsequently more development resources and market traction around the code base. It's far from an unprecedented move, but still stands as another example of where open source wins, notes Constellation VP and principal analyst Holger Mueller.

"While IBM knows how to partner and work with open source, customers have to keep a watchful eye on vendors not just punting the code over," Mueller says. "I'm not saying that is the case here, but with all the struggles at IBM it's a potential risk to consider."