The document discusses strategies for embracing open source communities as an individual or organization. It provides advice tailored to different roles such as product managers, engineers, operators, and students. The overall message is that participating in open source communities provides benefits like access to user feedback, skill development, and opportunities for collaboration. It encourages contributing code, documentation, and other forms of feedback to communities.

1. Embrace Upstream!
Embrace Community!
Embrace a better life!
Rico Lin, Heat PTL@OpenStack , @EasyStack

2. Open Infra

3. Product

4. You're Here Because...

5. A Common Case

6. Upstream
RockyQueens
Product plan
Downstream
PikeNewton

7. Upstream
RockyQueens
Downstream
PikeNewton
Product plan

8. Upstream
Production
RockyQueens
Product plan
Downstream
PikeNewton

9. Upstream
Production
c2
RockyQueens
Product plan
Downstream
PikeNewton

10. Upstream
Production
c1
c2
RockyQueens
Product plan
Downstream
PikeNewton

11. Upstream
Production
c1
c2 c3
RockyQueens
Product plan
Downstream
PikeNewton

12. Upstream
Production
c1
c2 c3
RockyQueens
Product plan
Downstream
PikeNewton

13. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
Downstream
PikeNewton

14. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
Downstream
PikeNewton

15. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
Downstream
PikeNewton

16. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
Downstream
c7
PikeNewton

17. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c5
Downstream
c7
PikeNewton

18. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c5
Downstream
c8c7
PikeNewton

19. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c6c5
Downstream
c8c7
PikeNewton

20. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c6c5
Downstream
c8c7
PikeNewton

21. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c6c5
c10
Downstream
c8c7
PikeNewton

22. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c6c5
c10
Downstream
c9
c8c7
PikeNewton

23. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c6c5
c10
Downstream
c9
c8c7
User feedback
PikeNewton

24. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c6c5
c10
Downstream
c9
c8c7
User feedback
PikeNewton

25. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c6c5
c10
Downstream
c9
c8c7
User feedback
PikeNewton
c11

26. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c6c5
c10
Downstream
c9
c8c7
User feedback
PikeNewton
c11

27. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c6c5
c10
Downstream
c9
c8c7
User feedback
PikeNewton
c11

28. Upstream
Production
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c6c5
c10
Downstream
c9
c8c7
User feedback
PikeNewton
c11

29. Upstream
Production
Downstream
c1
c4c2 c3
RockyQueens
Product plan
User feedback
c6c5
c10
c9
c8c7
User feedback
PikeNewton
c11
FAILED!!

30. And You Feel...

31. You Need a Strategy!!!

32. Define Strategy

33. link
孫子兵法：始計篇

34. Your Enterprise Community
There are Feedins and There are Feedbacks

35. Your Enterprise Community
That's ECOSYSTEM

36. When Two Forces Can Accelerate Each Other,
That's (More than) the Definition of
PERPETUAL MOTION

37. How to Win?

38. Upstream
SteinRocky
Product plan

39. Upstream
Downstream
SteinRocky
Product plan

40. Upstream
Check & Gate
Downstream
SteinRocky
Product plan

41. Upstream
Check & Gate
Downstream
c1 SteinRocky
Product plan

42. Upstream
Check & Gate
Downstream
c1
c2
SteinRocky
Product plan

43. Upstream
Check & Gate
Downstream
c1
c2 c3
SteinRocky
Product plan

44. Upstream
Check & Gate
Downstream
c1
c2 c3
SteinRocky
Feedin
&
Contribute
Product plan

45. Upstream
Check & Gate
Production
Downstream
c1
c2 c3
SteinRocky
Feedin
&
Contribute
Product plan

46. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan

47. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan

48. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback

49. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback

50. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c5

51. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5

52. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5

53. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5
c7

54. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5
c8c7

55. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5 c9
c8c7

56. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5
c10c8c7
c9

57. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5
c10
c9
c8c7
User feedback

58. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5
c10
c9
c8c7
User feedback

59. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5
c10
c9
c8c7
Product plan
User feedback

60. Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5
c10
c9
c8c7
pull &
Integrate
test
Product plan
User feedback

61. Join PTG
Propose
spec & bug
Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5
c10
c9
c8c7
pull &
Integrate
test
Product plan
User feedback

62. Join PTG
Propose
spec & bug
Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5
c10
c9
c8c7
pull &
Integrate
test
Product plan
Upstream
Feedback
User feedback

63. Join PTG
Propose
spec & bug
Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5
c10
c9
c8c7
pull &
Integrate
test
c11
Product plan
Upstream
Feedback
User feedback

64. Join PTG
Propose
spec & bug
Upstream
Check & Gate
Production
Downstream
c1
c4c2 c3
SteinRocky
Feedin
&
Contribute
Product plan
User feedback
c6c5
c10
c9
c8c7
pull &
Integrate
test
c11 c12
Product plan
Upstream
Feedback
User feedback
Success!!

65. That's for product
Let's talk about
people

66. What Can I Do?

67. Where I Can Start?

68. Who Can I Talk To?

69. You Only Live Once...

70. Embrace You Life

71. Make It Matters

72. Remember
Whoever Give You A -1
They're Trying To Help You

73. Something more...

74. I'm a Product
Take from community:
• A comparing place, the ring
Common Questions:
• I don't care about community when I'm a product.
• Product and Open Source project are two conflict concept
Actions or Keep in mind:
• Integration happens fast, the request always urgent, there is
room for done the third step first, but if you never go back
ASAP to fill up the first and second step, you not actually
doing anything
• User experience alway matters, that's the rule
• Upstream is not a product (even it's production ready)
• Aware about the licence
• good product sells itself, but people always is the root
• Don't waste opportunities to new things, but don't go
rush
• Don't mess up with your structure, it will crush.
• Make your strategy, execute it, and adjust your strategy
nicely.

75. I'm Enterprise owner (CXO)
Take from community:
• Good reputation
• More chances to make buessness deal
• Making spec as you needed
Common Questions:
• How's that gonna make renvenue?
• Why should I feedback? Why me?
• This just some works for my engineer, not me!
Actions:
• Allow people to join community
• Control the quality
• Join The Enterprise owner cercle
• Control quantity of spend
• Speak to other owners
• Support local events, and partners and let it support you

76. I'm a Manager
Take from community:
• A stage for manager to present with customers in front of
other potential customers.
• Protential customers in marketing place
Common Questions:
• None of my client stay in the area where community events
were hosted
• I simply needs the product released ASAP, why should I care
others
Actions:
• Help operators and developers learn about user’s needs
• Support Technical team to build CI/CD and works for
community
• Let customers feel they’re part of this ecosystem, not just
your master. Let them join User survey, give presentations
with you to binding each other
• Do marketing place like you do in front of customers
• go talk to developers

77. I'm a Technical Leader
Take from community:
• Place to push the skill of developers/ops
• Knew what other companies been doing and where are the
dead end or pain point
• Control the developing flow of an open source
Common Questions:
• To send developers in, gonna leave them un-control
• I can't control the community
• How's that going to serve our products
• We shouldn't share the secret of our business
Actions:
• Build CI/CD for your products (I mean real CI/CD)
• Make developers/ops do meaningful contribution
• Partially reveal/release your technical power. Keep the core
knowledge as your wish.
• Adopt changes, experiment integration and survey
• Allow developer have time to share and do documentation
• Observe How's a staff doing in Community and Products

78. I'm a Engineer
Take from community:
• Better develop skill
• Good developer experiences on real world issues
• Work with global team
• Prevent bad decision for development
Common Questions:
• Where I can trace these code?
• I don't feel I can do what I want in that project team
Actions:
• There's always test for your code
• Bring discussion to community
• Don't try to reinvent stuff unless you can prove with tests
• Allow rooms as buffer from product to community, but make
it as small as possible
• Go deep
• Go talk to others
• Really join community, fix real issues, join discussions,
provide ideas, do review, speak, and speak loud!

79. I'm an Operator( or MIS)
Take from community:
• Observe other people's experiences
• Go bother the best you know
• Make them work for your integration
Common Questions:
• I'm operate my own system, what's that have to do with
community?
• From ops point of view, it's really not clear what is what
• I hard a lot of `This is another team's issue`, not ours
Actions:
• Be a devops
• Provide feedback
• go talk to developers
• ducument matters

80. I'm an Intern/Student
Take from community:
• Learn from the best
• No binding for you in community
Common Questions:
• I'm just a student
• I'm still wondering what I want
Actions:
• Learn English
• Learn the spirit of Open Source
• Learn less than two programing languages
• Treat you self as a serious role
• Go talk to everyone
• Stay with Open Source Community

81. The next OpenStack Summit
(OpenInfra)
See You In Berlin
CITYCUBE, NOV 13-15, 2018

82. The next OpenStack Summit
(OpenInfra)
See You In Berlin
CITYCUBE, NOV 13-15, 2018

83. The next OpenStack Summit
(OpenInfra)
See You In Berlin
CITYCUBE, NOV 13-15, 2018

84. slide references
ref1, ref2, ref3, ref4, ref5, ref6, ref7, ref8, ref9, ref10, ref11, ref12, ref13, ref14, ref15