《One Hat》.pdf

One Hat, Two Hats How to Handle Open Source and Work Ken Walker @kwalker What prompted this talk? My last job was so secretive… easy … § IBM’s J9 JVM Lead for Embedded and Mobile platforms § Phones were secret § Car in-dash systems were secret § Black Game Consoles with Blu-ray… secret § Blog posts? Not so much to talk about § Open Source? In the later stages yes, but not for 10 years Along came Orion! § IBM Eclipse Developers working on new Web platform § Initial Eclipse contribution January 2011 § I joined the team in the Fall of 2011 § My goal was to grow the team, the community and IBM adoption § Orion didn’t match IBMs standard Eclipse process § Adopted a more aggressive release cycle of 3 times per year Everything was going smoothly § Why? We didn’t really have any key IBM adopters thru 2012 § Some teams were utilizing the Orion stand-alone editor component § That gave the developers free reign, open source deployments only to OrionHub § Team still split between Eclipse and Orion duties § But progress was being made 2013 - Things started to change § Hacked together integration demos earlier in 2012 changed some minds § Add the reality that IBM teams eager to push tooling to the web § Starting in February IBM wanted a complete solution by a June IBM Conference § Early beta of IBM JazzHub (now IBM DevOps Services) delivered § Other IBM teams on-boarding even including Rational web tools for Cobol § Other Open Source contributors SAP, HP and Pivotal getting involved § The IBM Orion team started growing to meet demand The CDD Phase - or Conference Driven Development § The start of the dark times… where feelings of “conflict” would start § These IBM Conferences did not necessarily align with Orion deadlines Pulse Innovate Impact Innovate Impact BlueMix GA 2013