And we released a lot of
open source projects
from them
Slide 30
Slide 30 text
From back-end to
front-end
Slide 31
Slide 31 text
phprew, pux, gutscript
and so on…
Slide 32
Slide 32 text
My public contribution calendar was almost like this,
2013
and private repositories are not included.
Slide 33
Slide 33 text
Here is what I’ve learned.
And which should be helpful
for small projects to start.
Slide 34
Slide 34 text
專案
名稱
The name of a project should be easy to
remember
Slide 35
Slide 35 text
1. Short name
node.js, three.js, gearman, apache, nginx,
jQuery, bootstrap, gem, rails and so on…
Slide 36
Slide 36 text
2. Pronounceable
You don’t want a project named
“hjkdvbjkGUI” or something
Slide 37
Slide 37 text
3. Unique
Slide 38
Slide 38 text
4. Combining words or
making up new words
entirely
YouTube, Facebook, Myspace, GitHub
Slide 39
Slide 39 text
第⼀一
印象
First Impression
Slide 40
Slide 40 text
SYNOPSIS
Slide 41
Slide 41 text
Which I learned from CPAN - an
aged, fantastic site.
Slide 42
Slide 42 text
Synopsis is important
because…
Slide 43
Slide 43 text
It may include a workable
example to help others
run a basic program
Slide 44
Slide 44 text
No content
Slide 45
Slide 45 text
And of course, further
development :)
Slide 46
Slide 46 text
You firstly see the
synopsis of the API,
Slide 47
Slide 47 text
then read the tediously
long description
Slide 48
Slide 48 text
先看對⽅方正不正
再看是否進⼀一步交往
Slide 49
Slide 49 text
⾔言簡
意賅
Easy to understand
Slide 50
Slide 50 text
• Describe what’s the project doing, and what’s
the problem this project trying to solve.
• Details & mechanism later.
• Design & implementation doc for advanced
users.