After a report from The Verge gripped the Internet on Friday, announcing that HP's webOS Enyo team was migrating to Google, HP's Enyo team responded with a blog post to clarify the matter.
On Thursday, May 24, The Verge reported that Google would soon be regrouping the HP team behind the creation of Enyo, the HTML5-based application framework for WebOS. AllThingsD followed with a more detailed report, saying that Google did not poach the entire team, but recruited about half a dozen, including project chief Matt McNulty.
A May 25 blog post on the Enyo Web site aims to clarify such news reports. According to the post, most of the team remains in place, development of Enyo will continue, and the Enyo team is actually expanding. The Verge later updated its report as well, adding that Mat McNulty was indeed heading to Google, along with other members "responsible for 99 percent of the code."
"We'd like to clarify some of the news reports you may have read today about Enyo," started the May 25 blog post. "It's true that some key members of the Enyo team have left the company, but the majority of the engineering and leadership team remains. We want to reassure you that we're thrilled with the traction Enyo has gained to date and are redoubling our efforts to continue development, working closely with the community."
The post continues to assure that Enyo 2's core is solid, and developers are pleased with the performance improvements in the last release. The team also noted they have another release on the way. In addition, future plans include focusing on expanding the Onyx widget set. "We've enlisted the support of the developer relations engineers you know and love to help out as we work on growing the team," reads the post.
"That's right, we're growing. As we said earlier this month, we're hiring - not just to replace the engineers who have left, but to increase the size of the team going forward. If you would like to contribute to the success of Enyo (and get paid for it) please let us now. And of course, all are welcome to contribute to the code by making GitHub pull requests."
The blog post concludes by confirming the team's attendance at next week's O'Reilly Conference in San Francisco, and the following week at HP Discover in Las Vegas.