How to open source a project at Mega Corp (Geecon - May/2011)

64
How to open source internal software in a Mega-Corp Martijn Verburg (@karianna) (Full presentation slides will be made available on slideshare) Slide Design http://www.kerrykenneally.com 1 Friday, 13 May 2011

description

How to convince your stakeholders to open source a project at Mega Corp as well as how to get it started.

Transcript of How to open source a project at Mega Corp (Geecon - May/2011)

  • 1. How to open source internal software in a Mega-Corp Martijn Verburg (@karianna) (Full presentation slides will be made available on slideshare) Slide Design http://www.kerrykenneally.comFriday, 13 May 2011 1
  • 2. Introduction SpeakerFriday, 13 May 2011 2
  • 3. 3Friday, 13 May 2011 3
  • 4. Introduction Speaker Im a Java and open source software consultant mentor. Helps banks leverage those technologies for fun and profit! I work on several open source projects Recently Ikasan EIP http://www.ikasan.org & PCGen - http://pcgen.sf.net I Co-lead the London JUG and moderate on the Javaranch Writing The Well-Grounded Java Developer for Manning with Ben Evans. Shameless plug! Twitter: @kariannaFriday, 13 May 2011 4
  • 5. Introduction Thats no Moon.... We are not going to get through all of this!Friday, 13 May 2011 5
  • 6. Introduction Slides != Live Presentation The slides have a *lot* of material Buts thats so you can read while I tell you bed time stories Well actually its for the enterprise folks who need to convince their companies Ill be talking lots about use cases, in particular experiences with: Using open source software in investment banks Producing open source software from investment banks Some controversial open source projects out there today For those folks seeing this on slideshare See my Hollywood good looks and hear my sultry voice on Parleys.com 6Friday, 13 May 2011 6
  • 7. Introduction Areas to cover 1. Getting Started Part I 2. Convincing the Stakeholders 3. Getting Started Part II 4. Technical Infrastructure 5. Social and Political infrastructure 6. Money 7. Communications 8. Packaging, Releasing and Daily Development 9. Managing Volunteers 10. Licensing, Patents and CopyrightFriday, 13 May 2011 7
  • 8. Getting Started Part I - Benefits of open sourcing $Friday, 13 May 2011 8
  • 9. Getting Started Part I - Benefits of open sourcing Image courtesy of Catan HD iPhoneFriday, 13 May 2011 9
  • 10. Getting Started Part I - Benefits of open sourcing Public Relations I couldnt find a cool image Friday, 13 May 2011 10
  • 11. Getting Started Part I - Benefits of open source 10,000 eyes on the technical content Explaining/Documenting for outsiders improves quality More users == more rigorous testing! Participation in a vibrant community Its fun again Developing software is a social activityFriday, 13 May 2011 11
  • 12. Getting Started Part I - Benefits of open source Cultural Change Banks are often held back by their IT Are startups? (But surely banks have more resources!) The rest of the world is doing: mobile, cloud, agile, lean, dynamic languages, continuous deliveryFriday, 13 May 2011 12
  • 13. Getting Started Part I Choosing an appropriate project Key indicators that can help you identify the right project: Plumbing Not a core competency No intrinsic IP value Ikasan EIP The Middleware platform Middleware is plumbing Software development is not a core competency of the bank Software had no IP value (that the bank wanted to trade on)Friday, 13 May 2011 13
  • 14. Convincing the Stakeholders Who are they?Friday, 13 May 2011 14
  • 15. Convincing the Stakeholders Legal Legal: Questions 1. What license to use? 2. What liability do we have? 3. Uh oh, we dont even have a policy on using open source, what now? Legal: Answers 1. That depends! There are plenty of business/corporate friendly licenses. There is legal precedence in this area 2. That depends on the law of the land Typically none, unless its overruled by common law 3. Then you are vulnerable to lawsuits Get a policy in place immediately!Friday, 13 May 2011 15
  • 16. Convincing the Stakeholders Information Security Information Security: Questions 1. Will our data be in the public domain? 2. Are any of our systems made vulnerable? 3. How is authentication/authorisation applied? 4. Open source must surely mean less secure? Information Security: Answers 1. Not unless your staff upload sensitive information (same as now) 2. Not if you host the project externally as recommended 3. According to project policy Typically everything is reviewed before being committed 4. Fallacy Think Linux vs. MS Windows Security through obscurity is not security at allFriday, 13 May 2011 16
  • 17. Convincing the Stakeholders Infrastructure Infrastructure: Questions 1. What access do internal staff require? Infrastructure: Answers 1. Typically they need secure access to external hosting providers, e.g.: HTTPS SCP SSH Plus HTTP access to some social/communication sitesFriday, 13 May 2011 17
  • 18. Convincing the Stakeholders IT Management Head of IT: Questions 1. Does it affect productivity? 2. Does this mean free help? 3. Whats the cost? 4. Quality Control? Head of IT: Answers 1. Initially yes! But then community takes over 2. Yes! But you get out what you put in 3. Legal is often the biggest up front cost On the IT side, it can be set-up for