Hacker culture and OSS (Open Source Software) are discussed. Why they are so important. Building a hacker centric culture in Rakuten.

1. Hiro Yoshioka, Technical Managing Officer,!
Rakuten, Inc.!
Using Open Source at an
Internet Company and
Hacker Culture!

2. 2
Agenda
• Using OSS at Rakuten and
Hacker Culture

3. 3
https://twitter.com/yukihiro_matz/status/620418684708786176

4. 4
Software is eating the world
• http://www.wsj.com/articles/
SB100014240531119034809045
76512250915629460
• Why Software is Eating the World
Marc Andreessen
August 20, 2011
• 世界はソフトウェアでできている

5. 5
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)

6. 6
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

7. 7
ネットを支えるオープンソー
ス、ソフトウェアの進化 角
川インターネット講座、０２
http://kci-salon.jp/books/02/
第４章 ハッカー精神とは何か
プログラマーに求められる素養
と思考方法

8. 8
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)

9. 9
Who are we?

10. 10
Rakuten in Japan

11. 11

12. 12

13. 13
Rakuten Eagles is No. 1 on 2013
http://event.rakuten.co.jp/campaign/eagles/group/

14. 14
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

15. 15
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

16. 16
Hacker Culture, Common Value
• Computers can change your life for the better
• rough consensus and working code
• http://www.ietf.org/tao.html
• It is much easier to apologize than it is to get
permission. By Grace Hopper
• If it's a good idea, go ahead and do it.
許可を求めるな謝罪せよ
http://d.hatena.ne.jp/hyoshiok/20110205/p1

17. 17
http://blogs-images.forbes.com/jasonoberholtzer/files/
2011/06/Talent_traffic.gif

18. 18
Hacker-centric Culture
• Software Development in Internet Age
• Hire good programmers
• Good programmers want to work with
good programmers at hacker centric
culture
• Build good work place
• Good programmers make good services

19. 19
The Hacker Way (Facebook)
IPO 2012
• Code wins arguments
• Done is better than perfect
• Continuous Improvement and Iteration
• Open and Meritocratic
• Hackathon – demo or die
• Bootcamp
• http://www.wired.com/business/2012/02/zuck-
letter/

20. 20
Hacker-centric Culture
• Why do we need it?
• Common Good
• Competitiveness
• Best practice

21. 21
Hacker-centric Culture
• Why do we need it for me?
• It is fun.
• Reasons
• Common good (make better world)
• Competitiveness (win a competition)
• Best practice (increase productivity)

22. 22
How do we foster it?
• Corporate culture is developed by implicit and
explicit way
• Only insiders know it

23. 23
The Hacker Way
• Hackathon
• Demo or Die
• Pizza and Beer

24. 24
Web 2.0
• Software products vs Internet Services
• http://oreilly.com/web2/archive/what-is-
web-20.html 9/30/2005
http://en.wikipedia.org/wiki/File:Web_2.0_Map.svg

25. 25
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

26. 26
Open Source
• History
– Public domain
– Proprietary Software
– Free Software,
• GNU, 1983,
• GNU General Public License, 1989
– Netscape opened source code,
1998
– Open Source software

27. 27
Open Source license
• Open Source Definition
– right to use, modify, redistribute
• http://opensource.org/osd

28. 28
Open Source license
• copyleft
– require same license to derivative
works
– GNU General Public License, AGPL
• permissive
– don’t require same license
– MIT, Apache, BSD

29. 29
Top 20 Licenses (2012)
http://www.blackducksoftware.com/resources/data/top-20-
licenses

30. 30
Why OSS
• Innovation
– collaboration with community
• Flexibility
– freedom from vendor lock in
• Quality
– fixing bugs, enhancements

31. 31
Why do we need OSS license?
• Collaboration model
– Cathedral and Bazaar
• Eric Raymond, 1997
• http://www.catb.org/esr/writings/
cathedral-bazaar/
• Ban Free riders
– The Tragedy of the Commons

32. 32
Bazaar
• Software Development Model
• Engagement
– Users become Developers
• Develop by Community
– individual vs. organization
– volunteers
http://en.wikipedia.org/wiki/File:Laad_Bazaar.jpg

33. 33
Most of github hosted projects did
not have any license.
http://www.blackducksoftware.com/resources/infographics/deep-license-data

34. 34
How can we choose it?
http://choosealicense.com

35. 35
copyleft vs permissive
Source License 2008 2011 2012
Black Duck GNU GPL 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%
http://www.youtube.com/watch?v=o82QmitU4XE
OSCON 2013, Eileen Evans, "Licensing Models and
Building an Open Source Community"
Projects are increasingly using permissive licenses.

36. 36
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)
committers
charisma
contributors
casual users
Matz
Yugui
Linus
Greg K Hartman
http://commons.wikimedia.org/
wiki/File%3AGreg_Kroah-
Hartman_lks08.jpg

37. 37
Linux
• Commits 596K+
• contributors 14K+
• lines of code 18M+
• License GPL v2
• https://www.openhub.net/p/linux
• (as of 07/16/2015)

38. 38
Ruby
• commits 39K+
• contributors 99
• lines of code 987K+
• license GPL v2+, Ruby
• https://www.openhub.net/p/ruby
• (as of 07/16/2015)

39. 39
Contributions to recent open source
projects
License Project Year
Started
Number
of
Commits
Number of
Contributors
Lines of
Code
Apache 2.0 OpenStack 2010 62K+
/129K+
1,043
/2,556
0.8 milioons+
/2.0 millions+
Apache 2.0 CloudStack 2010 17K+
/25K+
184
/312
1.7 millions+
/1.5 millions+
GPLv3 Eucalyptus 2009 72K+
/88K+
70
/120
1.3 millions+
/1.5 millions+
http://www.youtube.com/watch?v=o82QmitU4XE
OSCON 2013, Eileen Evans, "Licensing Models and
Building an Open Source Community"
(as of May 2013/Dec 2014)
http://www.ohloh.net/p/openstack
http://www.ohloh.net/p/CloudStack
http://www.ohloh.net/p/eucalyptus

40. 40
Open source and Bazaar
• Open source software （OSS）
– software license
• Bazaar
– Software development model
– global distributed collaborative work

41. 41
OSS at Rakuten
• OSS is everywhere
– Manual for collaborating with OSS
community
– OSS training
• Homegrown applications
– ROMA (Distributed KVS)
– LeoFS (File System)

42. 42
https://rakutentech.github.io/

43. 43
Open source
• Open information, it evolves
• Patents, Copyright

44. 44
• Open source, patents, copyright,
• The architecture is different but
purpose is the same
• Making the world better

45. 45
Open Innovation
• The technology at outside
– collaboration is important
• Innovation at outside
– vs NIH (Not Invented Here)
• Community
– fun

46. 46
IT Seminar Calendar of Japan
http://eventdots.jp/events/calendar
more than 600 meetings/month

47. 47
In Japan
• Engineers at Web companies
• IT study sessions, workshops,
meetups
• Sharing common value

48. 48
Conferences in Japan
http://ll.jus.or.jp/2014/
http://phpcon.php.gr.jp/w/2014/
http://yapcasia.org/2014/
https://pycon.jp/2014/
http://nodefest.jp/2014/
http://rubykaigi.org/2014
http://gocon.connpass.com/event/9748/

49. 49
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), Go Conference

50. 50
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

51. 51
Rakuten Technology Conference 2015
November 21, 2015
Rakuten Crimson House, Futagotamagawa, Tokyo
http://tech.rakuten.co.jp/

52. 52
Open Innovation
• Open Source community =
Engine of open innovation

53. 53
• The future is already here — it's
just not very evenly distributed.
by William Gibson

54. 54
• Be Hacker.
• Make the world a better place.

55. 55
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