OpenSource in BB10 Jam

OpenSource in BB10 Jam

Transcript

1. All you need to know about Open Source… So you can use it in your BlackBerry 10 Apps DEV109 Eduardo Pelegri-Llopart Roberto Speranza May 1-3, 2012
2. You have played this game… 2
3. You have played this game… 3
4. You have played this game… 4
5. Agenda Ÿ  Introductions Ÿ  What is Open Source Ÿ  Open Source Projects Ÿ  Applications and App World Ÿ  Demo Ÿ  For more Information Ÿ  Q & A @pelegri– 5
6. Introductions 6 To the speakers, and to the Session
7. Intro: Eduardo & Roberto Eduardo: Sr Director, Open Source @pelegri „  Previously: Sun and Oracle „  IDEs, Java, GlassFish, Hudson (now Jenkins)… Roberto: Application Development Consultant, Dev Rel @RSSessantotto „  Previously: Software and Web Consultant „  Graphical UI, Web Design, 2D / 3D Graphics… @pelegri - 7
8. Intro: Eduardo & Roberto Eduardo: Sr Director, Open Source - @pelegri „  Previously: Sun and Oracle „  IDEs, Java, GlassFish, Hudson (now Jenkins)… Roberto: Application Development Consultant, Dev Rel „  Previously: Software and Web Consultant „  Graphical UI, Web Design, 2D / 3D Graphics… @pelegri - 8 None of us are Lawyers! If you need legal advice, Talk with a lawyer
9. Goals of this Session Ÿ  What is Open Source (OSS) Ÿ  How OSS Helps You Create Apps for App World Ÿ  Different Roles „  User of OSS Components „  Contributor to an OSS Project „  Lead of an OSS Project „  Research In Motion Ÿ  You may play multiple roles at the same time @pelegri - 9
10. Goals of this Session Ÿ  What is Open Source (OSS) Ÿ  How OSS Helps Create Apps for App World Ÿ  Understand Better How OSS Works Ÿ  Different Roles „  User of OSS Components „  Contributor to an OSS Project „  Lead of an OSS Project „  Research In Motion Ÿ  You may play multiple roles at the same time @pelegri - 10 User of OSS Components Contributor to an OSS Project Research in Motion
11. What is Open Source 11
12. What is Open Source? Ÿ  Strictly, just: “Source is available under an Open Source License” Ÿ  Reality is more complex and, in addition to license, your interaction with OSS depends on details like: „  Copyright + Governance + Trademarks + Tooling … @pelegri - 12
13. Promises of OSS Ÿ  Agile, Cost-Effective Development „  Reusable and Portable Components „  Availability of Expert Developers „  Applicability of Latest Tools „  Bug Fixes Incorporated Promptly Ÿ  Efficient Product Cycle „  Simpler Interaction w/ Customers, Partners „  Better Communication Across Groups „  Improved Adoption @pelegri - 13
14. Open Source Principles Ÿ  Copyright Ÿ  License Ÿ  Governance @pelegri – 14
15. Open Source Principles Ÿ  Copyright Ÿ  License Ÿ  Governance Ÿ  Trademarks @pelegri – 15
16. Open Source Principles Copyright – Who Owns the IP Ÿ  Copyright Owner can change license Ÿ  But you can fork! Ÿ  One or many Copyright owners Ÿ  Some OSS projects require Contribution Agreement Ÿ  Assert authorship of contributions / licenses patents Ÿ  Apache uses the ICLA and CCLA – RIM does too @pelegri – 16
17. Open Source Principles Copyright – Who Owns the IP License – What Can be done with the IP Ÿ  BSD, MIT – “Don’t sue me” Ÿ  ASL2 – Adds Patent Rights. Ÿ  GPL, GPLv2 – Viral, Original FSF licenses Ÿ  LGPLv2.1 – Limited/Lesser/Library Ÿ  GPLv3 – Strong patent rights and tool chain requirements @pelegri – 17
18. Open Source Principles Copyright – Who Owns the IP License – What Can be done with the IP Governance – How the IP changes Ÿ  Who and How on decisions of „  Features, Releases, Names, Access to Source Repositories… „  E.g. “Can I upstream my change?” Ÿ  Some Models „  BDFL - Benevolent Dictator For Life, Meritocracy, Corporate @pelegri – 18
19. Ÿ  Git/GitHub encourages forks/merge (rails >3K forks!) Governance,  Git  and  GitHub   @pelegri - 19 Repo Repo 1fork local repo 6merge 5push 2clone 3pull update 4merge This impacts project governance
20. Open Source Projects 20 Applying the OSS Principles Open Source Projects by RIM and for you
21. RIM using Open Source to help You Sep 29, 2010 Ÿ  Launched WebWorks Ÿ  1 repo at GitHub @pelegri – 21 May 2, 2012 Ÿ  56 repos at GitHub „  Samples, Tools, Runtimes… Ÿ  Participating in „  Webkit, Qt Project, Apache Cordova Ÿ  More Upstreaming of changes
22. Open Source Projects Ÿ  Samples - HTML5, NDK, TunnelTilt… Ÿ  HTML5 - WebWorks, Alice, bbUI.js, Apache Cordova, Webkit… Ÿ  Native – Cascades, GamePlay, Scoreloop, Qt… Ÿ  Tools – Ripple… Ÿ  Ports - Cocos2d-x, SDL… Ÿ  Frameworks - Alice, bbUI.js, GamePlay… Ÿ  Showcases - Quake3, DosBox… Ÿ  External Communities – Qt Project, Webkit, Apache Cordova @pelegri – 22
23. New this week Ÿ  New Samples: „  Cascades-Samples, Scoreloop-Samples „  PictureWall, jQuery-Mobile-Samples Ÿ  New Significant Updates „  bbUI.js, gameplay Ÿ  New Ports „  ZXing and CppUnit Ÿ  Ongoing development on many repos Ÿ  New Community Wiki 23 Big announcements at DevBlog.blackberry.com All updates at OpenBBNews.Wordpress.com
24. GitHub  and  RIM   Ÿ  Main Entry Points – via Pages „  blackberry.github.com – Dev that wants to Use a OSS component „  github.com/blackberry – Dev that wants to Contribute… Ÿ  Several Organizations Ÿ  Wikis, Issue Tracker, Milestones Ÿ  Some demos are hosted at GitHub! Ÿ  New Community Wiki (beta) @pelegri - 24
25. “Default” Structure of Projects Ÿ  License – ASL 2 Ÿ  Copyright – RIM „  Contribution Agreement Adapted from ASF’s Ÿ  Governance - RIM assigns the leader Ÿ  Repo hosted at github.com in BlackBerry Org Ÿ  Possibly extra staging repos + individual repos „  github.com/blackberry-webworks/Webworks-API-Docs @pelegri– 25
26. Samples Ÿ  Samples are Open Source „  Learn, Borrow, Enhance „  Contribute back – if you want! Ÿ  Samples out of the SDKs Ÿ  KB samples to GitHub „  Clear, well-known, licenses „  Easier to update „  Delivery Async of SDKs @pelegri– 26
27. Many Sample Repos Ÿ  WebWorks-Samples Ÿ  WebGL-Samples (tunneltilt) Ÿ  NDK-Samples Ÿ  Cascades-Samples Ÿ  Cascades-Community-Samples Ÿ  jQuery-Mobile-Samples Ÿ  Scoreloop-Samples Ÿ  Samples-for-Java Ÿ  Samples-for-AIR Ÿ  PictureWall Ÿ  BWS-Samples Ÿ  Gameplay @pelegri– 27 Linked from Micro-Sites Linked from Community Wiki Linked from Organization page
28. Micro-Sites, Repos, Wikis @pelegri - 28 developer.blackberry.com/native github.com/blackberry/gameplay blackberry.github.com blackberry.github.com/Community/
29. HTML5 Projects Ÿ  All WebWorks development is done at GitHub „  Runtimes „  Tools (Ripple) „  Frameworks / Libraries (Alice, bbUI.js) „  Documentation „  Future APIs „  Samples 29
30. HTML5 Projects - Non-RIM Led Ÿ  Apache Cordova „  Aligned with WebWorks Ÿ  Webkit.org „  TorchMobile early participant „  We are back in active participation Ÿ  jQuery Mobile, three.js… @pelegri - 30
31. HTML5 Projects Ÿ  Frameworks started as Samples: „  bbUI.js „  Alice 31 @pelegri – 31
32. Native Projects Ÿ  Many Samples „  NDK-Samples „  Scoreloop-Samples „  Cascades-Samples, Cascades-Community-Samples,… Ÿ  Gameplay Ÿ  Ported Components „  Upstreaming Ÿ  Showcases 32
33. Gameplay Ÿ  3-D cross-platform game platform for indie devs Ÿ  Release 1.2 adds Multi-Platform Support „  PlayBook 2.0 and BlackBerry 10 ready „  Apple iOS, Google Android „  Microsoft Windows „  Apple MacOS X Ÿ  Community Participation „  Yours Encouraged! 33
34. Ported Components Ÿ  Native C/C++ packages ported to PlayBook / BB10 Ÿ  Examples include „  Audio: OpenAL, ALUT, SDL, Ogg Vorbis „  Physics Engines: Box2D, Bullet Physics „  Game Engines: Cocos2D-X, gameplay „  General Purpose: Boost (almost there) „  Scripting: Lua, SpiderMonkey, Erlang, v8 „  Libraries: PCRE, TouchControlOverlay „  Computer Vision: OpenCV „  Others: CouchDB, GetOpt, JSON_parser, JsonCpp… 34
35. Upstreaming: Cocos2d-x @pelegri – 35
36. Showcases Ÿ  Some ports showcase the platform, or show how to port some features „  Quake3, OpenTTD, The Battle of Wesnoth, DosBox 36
37. Key External Participations Ÿ  HTML5 – Webkit.org Ÿ  HTML5 – Apache Cordova Ÿ  Native – Qt Project „  Ports to BlackBerry PlayBook and BB 10 devices „  General contributions to Community 37
38. BlackBerry Community Wiki Ÿ  New Initiative (beta) Ÿ  GitHub Pages Ÿ  Community Driven „  Participation Encouraged Ÿ  Pages point to “more info” Ÿ  Help us make it work for you! 38 http://blackberry.github.com/Community/
39. Some Examples: Ÿ  Wikipedia Client, NodeBeat, OpenCV, OpenFramework 39 Elsewhere… innovation happens elsewhere
40. Open Source and App World 40
41. App World Vendor Agreement Updated March, 29th, 2012 Section 10: Vendor Representations, Warranties and Covenants Vendor hereby represents, warrants and covenants to RIM that: (a)… (b)… (c)… 41 http://us.blackberry.com/legal/BlackBerry_App_World_Vendor_Agreement_032912cl.pdf Most relevant to us is section 10(k)
42. App World Vendor Agreement 10(k) (k) Applications shall not contain, or be derived in any manner (in whole or in part), from any software, including without limitation open source software, that would require that any RIM or third party proprietary software or information be: (i) disclosed or distributed in source code form; (ii) licensed for the purpose of permitting modifications or derivative works; (iii) reproduced and/or redistributed at no or minimal charge; (iv) permitted to be reverse engineered; or (v) used only for non-commercial purposes; 42 http://us.blackberry.com/legal/BlackBerry_App_World_Vendor_Agreement_032912cl.pdf
43. Multiple Terms Ÿ  Reminder: You must comply with the terms of both the Vendor Agreement and any applicable open source licenses. Ÿ  If the terms are incompatible, then the component with the conflicting license terms may not be used. 43
44. Open Source Licenses Ÿ  BSD, MIT, ASL2 (*) „  License needs to be “included”. Make it easy for users to find license from App „  ASL2 requires “NOTICE” file to be kept, if present Ÿ  (L)GPLv2, v2.1 (*) „  Sources of component need to be made available. Make it easy for users to find sources of application from App „  LGPL components have to be used as a library „  Requirements on these components using these licenses depend on context 44 (*) these are required but not necessarily sufficient
45. Best Practice Ÿ  Try to build license compliance into your application 45 45
46. Open Source Licenses Ÿ  BSD, MIT, ASL2 (*) „  License needs to be “included”. Make it easy for users to find license from App „  ASL2 requires “NOTICE” file to be kept, if present Ÿ  (L)GPLv2, v2.1 (*) „  Sources of component need to be made available. Make it easy for users to find sources of application from App „  LGPL components have to be used as a library „  Requirements on these components using these licenses depend on context 46 None of us are Lawyers! If you need legal advice, Talk with a lawyer
47. GitHub Demo Roberto Speranza 47
48. For More Information 48
49. Two Way Communications Ÿ  Links „  blackberry.github.com and github.com/blackberry „  OSS General Forum at supportforums.blackberry.com „  blackberry.github.com/Community/ - wiki Ÿ  Blogs: „  DevBlog.blackberry.com – official, covers all key events „  OpenBBNews.wordpress.com – Open Source Community news Ÿ  Twitter - @blackberrydev (@pelegri) Ÿ  And see you tomorrow at the Unconference! @pelegri - 49
50. THANK YOU DEV109 Eduardo Pelegri-Llopart Roberto Speranza May 1-3, 2012