We all love open source software and open culture, and of course we all want to contribute to and leverage the power of open source in our work. However when it comes to working in a startup, openness is often sacrificed to give way to work efficiency and business logic. In this talk I will talk about some of my experience(and failures) to be open source, and how our company is trying to be open by default without too much efficiency overhead. https://hkoscon.org/2020/topics/open-default-trying-run-startup-open-source-culture-mind

1. William Chong
Trying to run a startup with open source
culture in mind
@likecoin

2. - William Chong
- (former) Game Developer
- Fullstack developer of LikeCoin
- Mainly contributes to crypto
and web related oss project,
e.g. Metamask, Nuxt.js, lunie

3. - Hong Kong based startup
- Public blockchain for content
monetization, attribution and
distribution
- Media partners include Standnews,
Matters, HKcnews, Inmediahk
- 69,000+ Likers, 247,000+ contents by
9,600+ creators on 1000+ media
@June
https://like.co/

4. https://commits.top/hong_kong.html

5. - “公司 d code open source 同放上 github”
should be a more common practice
- Not only opening source code, but open in
culture and workflow.

6. - what we did to be open
- how we minimize extra overhead
- what trouble we encountered

7. - Making every single work or tool we use is
open, without considering trade off
- Suggesting any silver bullets solution

8. - Internet product startup
- Crowdfunding projects
- Blockchain/crypto projects
(requires extra trust from your users)

10. -
- Gain trust
- Gain loyalty (IKEA effect)
- Get feedback from fans
-
- Get technical feedback
- Open source contribution
- User, developer and employer brand
JONO HEY, SKETCHPLANATIONS, CC BY NC

11. - Customers / user community
- Technical and developer community
- Also Internally!
- Like technical debt, transforming from closed to
open is costly
- Your community might surprise you

12. One day when I was
committing
LICENSE.md...

13. - Community update & sharing
- Public internal knowledge sharing
- Community participation
- DAO - Decentralized Autonomous
Organization
- Open repository
- Gitcoin bounties
- Open API
- Documentation and code samples
- Hackathons

14. - Keep community
updated
- Allow basis for
community participation
- Let people know you are
still alive!

15. - Zoom for weekly meeting,
why not make it public?
- Statistic graph and work log
for progress synchronization,
why not make it public?
- 第一次參加LikeCoin 星期一週
會感受

16. - Timezone
- Language
- Privacy
- Be careful with
your mouth!
- Zoom is bad! How
about Jitsi?

17. - Internal knowledge
sharing is interesting
to external too
- Content marketing /
brand building
Simple sharing on Github Action

18. - Engage in conversation
with your community
- Slack / discord / telegram
or other online
community
- We have #likecoin on
Matters
- Governance system of
LikeCoin chain

20. - Not all comments will be supportive, some will be
skeptical, some will be antagonistic
- A good chance to clarify concepts, understand
common misconception, and what the concerns of
community are
- Affected by how well did you update your community

21. - LikeCoin ecosystem is not
governed solely by
LikeCoin Foundation, but a
group of validators
- Validators are public,
assigned according to
amount of LIKE delegated
by users
- They have power to
propose and vote on the
future of the ecosystem

22. - Proposal
- Discussion
- Actual voting

23. - Open Source repository allows
user to read, understand and
contribute your code
- Forced good software
engineering practice like
decouple and proper git
message usage
- Open standard allow other
parties to join: ISCN

24. - We use GitHub
- Use public Issue tracker
for internal issue report,
allow a unified flow for
bug reporting
- Use Github Project or
Trello board to manage
issues

25. - Don’t leak your secret, consider
GitGuardian to monitor secret
leak (GCP has built in detector)
- Timezone and communication
overhead on issues, be async
- Management and triage overhead
- Make sure you have a good linter,
tests and CI system to avoid
unneeded time spent on
reviewing minor code changes.

26. - https://gitcoin.co/explorer
Example

27. - Modern web/app development
uses front/backend separation
pattern
- So your probably have
Restful/GraphQL API ready
anyway…
- Why not open your API using
open OAuth 2.0 standard?

28. - When designing your API, use JWT for
authentication token
- Try to classify your API into different
scope and permissions
- Build a OAuth 2.0 authentication server
and authentication flow
- Tada! You now have an open API
- Write your API documentation properly,
we use Postman for develop -> testing
-> documentation cycle

29. - Designing proper OAuth scope
and developer console is hard
- Reviewing sensitive scope is
time consuming human process
- Be careful not to make another
Cambridge Analytica
- Security audit
https://blog.yorkxin.org/2013/09/30/oauth2-imple
mentation-differences-among-famous-sites.html
Yu-Cheng Chuang’s Blog

30. - We use Postman and documentor for API
develop cycle
- Sample codes are committed for future
reference. We also use codepen &
codesandbox.
- User guide and developer
documentation are written in Gitbook, PR
can be made to the repo for correction
- Translation would be possible in future
using Github integration tool
LikeCoin API Sharing

31. - https://matters.news/@likecoin/%E8%AE%9A%E5%AE%A2%E6%9D%BE-likerthon-2020-lik
e-coin-%E7%8B%82%E6%83%B3%E6%9B%B2%E5%BE%8C%E7%BA%8C-bafyreiemfrqhcn6cy3gny6o
v6rv2lxiccr7cuh2keeyrx5qtja62p545tm

32. - This is just our experience, there may be many
better ideas.
- Ideas might not fit 100% to you, but do begin
somewhere and try to be open!
- Many of our methods are made possible via
blockchain. Blockchain is not only about fintech,
join LikeCoin in slack, telegram and facebook to
know more!

33. Day 2 (2020-06-13)
10:00 am
Hall B
https://hkoscon.org/2020/topics/
decentralized-content-registry-e
xpanding-ipfs-functionality-cosm
os-based-blockchain

34. Liker Land
WordPress
Facebook
Telegram
Twitter
Matters
Github