An update was just posted up on the Enyo blog clarifying some of the rumors about the team leaving to go to Google. The statement mentions that some of the ‘key members’ of the team have left the company, but the ‘majority of the engineering and leadership team remains’.
Earlier today a report from Chris Ziegler at The Verge had stated that the Enyo team would leave HP and go to Google. The story was later updated to say that the entire team wouldn’t be leaving, although Matt McNulty and people responsible for ‘99% of the code’ would be among them.
F**k it, we'll do it live!
Our biggest ever edition of TNW Conference is fast approaching! Join 10,000 tech leaders this May in Amsterdam.
The team post goes on to say that the team is “thrilled with the traction Enyo has gained to date,” and will be continuing development of the project.
The post continues:
The core of Enyo 2 is solid. We’re hearing great things from developers about the performance improvements in the last release, and we have another release on the way. After that, we’ll focus 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.
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 know. And of course, all are welcome to contribute to the code by making GitHub pull requests.
Our door is open; if you have any concerns, feel free to voice them in the Enyo forums. We’re always listening and will do our best to address your questions. We’ll also be out in person at next week’s O’Reilly Fluent Conference in San Francisco, and at HP Discover in Las Vegas the following week — we’d love to see you there.
Enyo is the HTML5-based app framework that WebOS devices like the TouchPad used as the basis for many apps.
HP announced at an all-hands meeting back in December that it would be keeping the webOS division but will submit much of its code to the open-source community. HP also said that it would continue to contribute to Enyo, the application framework for webOS.
Conjectures were made at the time of the original report that the Enyo team might contribute significantly to the Chrome app framework or Android. This very well still might occur, as it’s not clear how many engineers have left.