Using oss and hacker culture at an internet company at osc/tokyo 2014/03/01
•
3 gostaram•3,064 visualizações
Using OSS and Hacker Culture at Rakuten. OSC/Tokyo 2014 Spring #osc14tk https://www.youtube.com/watch?v=BJD9eb-dLV4
Recomendados
Recomendados
Mais conteúdo relacionado
Destaque
Destaque (20)
Semelhante a Using oss and hacker culture at an internet company at osc/tokyo 2014/03/01
Semelhante a Using oss and hacker culture at an internet company at osc/tokyo 2014/03/01 (20)
Mais de Hiro Yoshioka
Mais de Hiro Yoshioka (20)
Último
Último (20)
Using oss and hacker culture at an internet company at osc/tokyo 2014/03/01
- 1. Using Open Source and Hacker Culture at an Internet Company.! OSC Tokyo 2014/Spring! Hiro Yoshioka, Technical Managing Officer,! Rakuten, Inc.!
- 2. Agenda • Using OSS at Rakuten and Hacker Culture 2
- 3. whoami Name: Hiro Yoshioka Title: Technical Managing Officer Company: Rakuten, Inc 2009 – present My mission: Empower Our Engineers, Build hacker centric culture Twitter: @hyoshiok http://d.hatena.ne.jp/hyoshiok (Diary in Japanese) http://someday-join-us.blogspot.jp/ (in English) 3
- 4. whoami Name: Hiro Yoshioka 2009-present, Rakuten 2000-2008, Miracle Linux, CTO 2002-2003, OSDL board member 1994-2000, Oracle 1984-1994, DEC 1984 Keio University (MS) I have one patch to Linux Kernel J x86: cache pollution aware patch 2006/6/23, 2.6.18 http://git.kernel.org/cgit/linux/kernel/git/torvalds/ linux.git/commit/? id=c22ce143d15eb288543fe9873e1c5ac1c01b69a1 4
- 5. Who are we? l Rakuten, Inc. l Internet services company l Founded : Feb. 7th 1997, Tokyo, Japan l The first service: Rakuten Ichiba (shopping mall) 5
- 8. Rakuten Eagles is No. 1 http://event.rakuten.co.jp/campaign/eagles/group/ 8
- 9. Open Source • History – Public domain – Proprietary Software – Free Software, • GNU, 1983, • GNU General Public License, 1989 – Netscape opened source code, 1998 – Open Source software 9
- 10. Free Software license • Free Software – right to use, modify, redistribute • copyleft – require same license to derivative works • permissive – don’t require same license 10
- 11. Free Software license • copyleft – GNU General Public License, AGPL • permissive – MIT, Apache, BSD 11
- 12. Why OSS • Innovation – collaboration with community • Flexibility/Agility – freedom from vendor lock in • Quality – fixing bugs, enhancements • cf. Free of Charge 12
- 13. Top 20 Licenses (2012) http://www.blackducksoftware.com/resources/data/top-20licenses 13
- 14. Most of github hosted projects did not have any license. http://www.blackducksoftware.com/resources/infographics/deep-license-data 14
- 15. How can we choose it? http://choosealicense.com 15
- 16. Why do we need OSS license? • Collaboration model • Ban Free riders – The Tragedy of the Commons 16
- 17. Top 20 Licenses (2012) http://www.blackducksoftware.com/resources/data/top-20licenses 17
- 18. copyleft vs permissive Source License 2008 2011 2012 70% 56.9% 53.2% Permissive N/A 25.6% 32.3% FLOSS Mole GNU GPL 70.8% 62.8% 62.8% Permissive 10.9% 13.4% 13.7% Google Code GNU GPL N/A 54.7% 52.7% Permissive N/A 38.0% 37.1% Black Duck GNU GPL Projects are increasingly using permissive licenses. http://www.youtube.com/watch?v=o82QmitU4XE OSCON 2013, Eileen Evans, "Licensing Models and Building an Open Source Community" 18
- 19. OSS Community • Typical OSS community – Charisma, top programmers (e.g., Matsumoto san (Ruby), Linus Torvalds (Linux)) – Committers (top notch programmers who have the right to add/modify the OSS) – Contributors (programmers who submit bug fixes, new proposals, patches) – Casual users (report bugs, ask questions, etc) charisma Matz committers Yugui contributors casual users Linus Greg K Hartman http://commons.wikimedia.org/ wiki/File%3AGreg_KroahHartman_lks08.jpg 19
- 20. Linux • • • • • commits 459K+ contributors 11K+ lines of code 16M+ License GPL v2 http://www.ohloh.net/p/linux 20
- 21. Ruby • • • • • commits 32K+ contributors 90 lines of code 946K+ license GPL v2+, Ruby http://www.ohloh.net/p/ruby 21
- 22. Contributions to recent open source projects (as of May 2013) License Project Year Started Number Number of Lines of of Contributors Code Commits Apache 2.0 OpenStack 2010 62,000+ 1,043 874,625+ Apache 2.0 CloudStack 2010 17,000+ 184 1.7 million+ GPLv3 Eucalyptus 72,000+ 70 1.3 millions http://www.ohloh.net/p/openstack http://www.ohloh.net/p/CloudStack http://www.ohloh.net/p/eucalyptus 2009 http://www.youtube.com/watch?v=o82QmitU4XE OSCON 2013, Eileen Evans, "Licensing Models and Building an Open Source Community" 22
- 23. Open source and Bazaar • Open source software （OSS） – software license • Bazaar – Software development model – global distributed collaborative work 23
- 24. Hacker Ethics • • • • • • Sharing Openness Decentraization Free access to computers World improvement Levy, Steven. (1984, 2001). Hackers: Heroes of the Computer Revolution (updated edition). Penguin. http://www.gutenberg.org/ebooks/729 24
- 25. Hacker Ethics • Access to computers—and anything which might teach you something about the way the world works—should be unlimited and total. Always yield to the Hands-On Imperative! • All information should be free • Mistrust authority – promote decentralization • Hackers should be judged by their hacking, not criteria such as degrees, age, race, sex, or position • You can create art and beauty on a computer • Computers can change your life for the better 25
- 26. Hacker Culture, Common Value • Computers can change your life for the better • rough consensus and working code • http://www.ietf.org/tao.html • It’s better to ask forgiveness than permission. • If it's a good idea, go ahead and do it. It is much easier to apologize than it is to get permission. By Grace Hopper 26
- 27. The Hacker Way (Facebook) IPO 2012 • • • • • • Code wins arguments Continuous Improvement and Iteration Open and Meritocratic Hackathon Bootcamp http://www.wired.com/business/2012/02/zuckletter/ 27
- 28. Web 2.0 • Software products vs Internet Services • http://oreilly.com/web2/archive/what-isweb-20.html 9/30/2005 http://en.wikipedia.org/wiki/File:Web_2.0_Map.svg 28
- 29. Netscape vs Google • A native web application, never sold or packaged, but delivered as a service • None of the trappings of the old software industry are present. • No scheduled software releases, just continuous improvement. • No licensing or sale, just usage. • No porting to different platforms, …, just a massively scalable collection of commodity PCs running OSS operating systems plus homegrown applications and utilities that no one outside the company ever gets to see. http://oreilly.com/web2/archive/what-is-web-20.html 29
- 30. Why OSS at Rakuten • Innovation – collaboration with community – hacker centric culture • Flexibility/Agility – freedom from vendor lock in • Quality – fixing bugs, enhancements • cf. Free of Charge 30
- 31. Maturity of OSS usage • • • • Find Use Participate Innovate/Build Community 31
- 32. OSS at Rakuten • OSS is everywhere – Manual for collaborating with OSS community – OSS training • Homegrown applications – ROMA (Distributed KVS) – LeoFS (File System) 32
- 33. OSS compliance • Risk of copyright infringement – Smartphone applications – e-book reader applications – client applications (javascript) – AGPL 33
- 34. Open source • Open information, it evolves • Patents, Copyright 34
- 35. • Open source, patents, copyright, • The architecture is different but purpose is the same • Making the world better 35
- 36. Open Innovation • The technology at outside – collaboration is important • Innovation at outside – vs NIH (Not Invented Here) • Community – fun 36
- 37. Why do we need OSS license? • Collaboration model • Ban Free riders – The Tragedy of the Commons 37
- 38. IT Seminar Calendar of Japan http://bit.ly/QmRFiS more than 300 meetings/month 38
- 40. Conference • • • • • • Running by volunteers Inexpensive, e.g., 5000 yen/day ($50/day) Numbers attendees; more than 100 - 1000 Sharing technical knowledge and networking Beer Bash or Drinking Party (optional) Examples, LL event, PHP Conference, YAPC (Yet another perl conference), RubyKaigi, Tokyo Node Gakuen (Javascript) 40
- 41. cf. Commercial Conference • • • • • • Running by corporation Expensive, e.g., $300-$500/day Numbers attendees; more than 1000 Sharing technical knowledge and networking Party (optional) Examples, OSCON $2045 (5 days), http://www.oscon.com/oscon2013 41
- 42. In Japan • Engineers at Web companies • IT study groups, workshops, meetups • Sharing common value 42
- 43. Open Innovation • Open Source community = Engine of open innovation 43
- 44. • Be Hacker. • Make the world a better place. 44
- 45. reference • License – http://www.slideshare.net/YutakaKachi/20110211 – http://handsout.jp/slide/1009 • Bazaar model – Producing OSS http://producingoss.com/ja/ – Cathedral and Bazaar http://cruel.org/freeware/cathedral.html • Open Innovation – http://books.rakuten.co.jp/rb/5913864/ – http://www8.cao.go.jp/cstp/tyousakai/seisaku/ haihu07/sanko1.pdf 45