"Session ID: HKG18-400K1 Session Name: HKG18-400K1 - Keynote: Kenneth Lee - “To define the rule -- why you should go open source” Speaker: Kenneth Lee Track: Keynote ★ Session Summary ★ This talk will explain why a commercial organization should join the open source development from the software architecture and commercial competition perspective. And it will also tell how a bad open source strategy will fail the original target. --------------------------------------------------- ★ Resources ★ Event Page: http://connect.linaro.org/resource/hkg18/hkg18-400k1/ Presentation: http://connect.linaro.org.s3.amazonaws.com/hkg18/presentations/hkg18-400k1.pdf Video: http://connect.linaro.org.s3.amazonaws.com/hkg18/videos/hkg18-400k1.mp4 --------------------------------------------------- ★ Event Details ★ Linaro Connect Hong Kong 2018 (HKG18) 19-23 March 2018 Regal Airport Hotel Hong Kong --------------------------------------------------- Keyword: Keynote 'http://www.linaro.org' 'http://connect.linaro.org' --------------------------------------------------- Follow us on Social Media https://www.facebook.com/LinaroOrg https://www.youtube.com/user/linaroorg?sub_confirmation=1 https://www.linkedin.com/company/1026961"

1. Why Do You Join Open Source Activity？
Kenneth Lee, Hisilicon

2. This presentation is about?
● Why are you here?
● How can you explain to your manager(s) you are here for
work, not for vacation
● How can you, and your organization, get benefit by joining
open source activity

3. The Speaker
Kenneth Lee
● 1998 Join OS Team, GSM Product,
Huawei
● 2002 Chief Designer of Quidview 2.0, a
LanSwitch/Router Management System
● 2005 Chief Architect for DOPRA Linux
Distribution
● 2012 Chief Software Architect for
Hisilicon ARM ICT SoC, Linaro TSC
Representative

4. Though
● Actually, I feel embarrassing introducing
myself…
○ It is part of basic Chinese Philosophy
■ Fact always go to the reversed direction of its
Name（反者道之动）
■ This is also the key point to support my view in this
presentation

5. 道可道，⾮非常道，名可名，⾮非常名
(route can be routed but not in its general way. Name can be named, but not in its general meaning)
Name
Name
Name
Name
Name
Name
Investigating the name and make it shining, the fact will be off the name
Investigating on fact can change the fact
the fact
Non- fact

6. Left vs. Right
Name
RightLeft
When people see a problem(Name), they try to solve it
by turn it left or right

7. On vs. Off
Name
RightLeft
On
Off
But what if you just turn the Name off?
Name is the problem. We should remove the problem by shutting down the name.
(But you cannot shutdown the name without shutting down the problem)

8. Now let’s see what architecture design is
● Architecture is to design and
maintain a logic chain which lead
us to our target
○ Design: make the logic chain
“reasonable” and “optimized”
○ Maintenance: make the logic node
“turn true” and refine the chain
according to the new situation
● But system engineering is only to
“make the fact happen”
● So your would be aware of system
engineering activity but not the
architecture activity

9. So you join open source activity to keep your architecture
logic chain stable
● You have bunches of private source code to keep it safe. And it won’t be if you cannot
ensure the development direction of the ecosystem that you reply on
● You don’t come to take the code, you can always take the code without joining it
● You don’t come to develop the code together with your competitors. You won’t be
trying hard in the case. And a source base without trying hard make no sense for you
to rely on.
● You don’t try to ask a community to fulfill your business requirement by giving them
some money. You should pay a out sourcing team to do so.
● You are not supposed to tell your internal team you bring benefit to them because
they can get it without your help.
● The only way that you can get benefit from a community is to bring (some of) your
internal development force to the open source community, so you main business will
be safe.

10. Why the standard organization’s way not works any further?
● Complexity: Code changed for no reason, it just works like that
Code Initiation
(Driven by Requirement)
Code Base Evolution
(Driven by Competition)
(Added for Performance, added function,
maintenance…)
Framework,
Connection
Function Function
Function Function
Framework,
Connection
Function Function
Function Function

11. Open Source Branch vs. Business Branch
Architecture Branch (Open Source)
Development Branch
Product Branches

12. Example: How ERP Strategy is made (1/2)
● Enterprise Reference Platform: A platform to help the
enterprise ecosystem to be compatible with each other
● It is not intended to create another distro
Common distros (such as
Debian, Fedora)
To support the latest
mainline

13. Example: How ERP Strategy is made (2/2)
● It does not compete with the ecosystem
○ It is not a “long term support” version, so it is not compete with any distribution
○ It is not a “landing project” for SoC, so it is not block your own landing team to
join
● It is attractive to the ecosystem
○ It is the only version that can support the latest feature and latest Linux kernel
for ARM server hardware (not behind the mainline for more than 2 revisions)
○ Any new feature can be merged to the next ERP version. But if the pusher
cannot hold it. It will be dropped in next release.
○ All Linaro common features will be developed and verified only on ERP. Linaro
and its members will all encourage their cooperators to develop and verified
new technology on ERP.

14. Conclusion: 圣⼈人⽆无私，所以成其私
● We work with open source community by helping it.
● We help it so we are compatible with it. So it belong to us.
● We take it without contributing to it. It becomes our
burden. It does not belong to us.

15. Thank You
#HKG18
HKG18 keynotes and videos on: connect.linaro.org
For further information: www.linaro.org