YAPC::Asia Tokyo 2015 day 0

1. How to Create/Improve
OSS Product and Its Community
YAPC::Asia 2015 (2015/08/16)
Satoshi Tagomori (@tagomoris)

2. Satoshi "Moris" Tagomori
(@tagomoris)
Fluentd, Norikra, MessagePack-Ruby,...
CPAN: Net::Hadoop::WebHDFS, Woothee, Norikra::Client, ...
Docker logging driver for Fluentd (docker v1.8)
Treasure Data, Inc.

3. We are hiring!

4. DataWe

5. Qualify: Sep 26,27 (online)
Final: Oct 31 (Hikarie)

6. How to create/improve OSS
product and its community
• What the OSS product is for?
• What programming language the product is written in?
• How do we versioning about the product?
• What (natural) language we use around the product?
• How can we create the community around the product?
• Famous developer people problem
• The way to live as a OSS developer

7. All OSS products needs:
More users
More use-cases
More contributions

8. What the OSS Product Is For?
• OSS version of internal product?
• OSS native?
• Internal use + alpha?
• Internal use primary, Global use secondary?
• Global use primary, Internal use secondary?
• Global use primary (and nothing else)?

9. What the OSS Product Is For?
(2)
• What depends on "What the OSS Product Is For?"
• Core developer selection
• How to accept contribution
• How to maintain that software

10. What the OSS Product Is For?
(3)
• Goods to create/improve community
• Open developer team
• Open steps for contribution
• Support from a company

11. What Programming Language
the Product Is Written in?
• Perl? Ruby? Python? PHP? JavaScript? Java? Scala?
Clojure? C? C++? Golang? Objective-C? Erlang?
Haskell? ...
• Once you wrote it in Perl, Scala people don't take a
glance on it. (strongly biased :P) (community side issue)
• Data processing world is dominated by JVM (runtime
side issue)

12. How Do We Versioning about
the Product?
• Versioning says that:
• it's unstable or not
• it's still under development or not
• it's still under maintenance or not
• Unstable version requires a lot "Air Reading"
• Miyagawa's 0.99 product is safe! (really?)

13. What (Natural) Language We
Use Around the Product?
• English! English! English!
• Almost all things around the product should be done in
English:
• Code/Commit comments
• Issues, Pull-requests, Mailing lists
• Software design sheets / its drafts

15. What (Natural) Language We
Use Around the Product?
• What important is to express:
"We DON'T exclude you."
by using English

16. pictures of beers or
something else
break...

17. How to create/improve OSS
product and its community
• What the OSS product is for?
• What programming language the product is written in?
• How do we versioning about the product?
• What (natural) language we use around the product?
• How can we create the community around the product?
• Famous developer people problem
• The way to live as a OSS developer

18. How Can We Create the
Community around the Product?
• Create/Maintain good software
• Be open for contribution
• Show it's stable and still under maintenance
• Communicate with people all over the world in English

19. How Can We Create the Community
around the Product?
(2)
• One more thing: Pluggable/module architecture
• Apache httpd, Nginx, Linux kernel, ...
• Emacs, Vim, Eclipse, IntelliJ IDEA (and many IDEs), ...
• Plagger, Fluentd, ...
• Pluggable architecture makes user community to be
developer community!

20. Famous Developer Problem
• Some OSS products seems to become famous easily!
• especially from famous developers....
• DON'T mind it!
• There's many reason which we can't know
• Good looking point
• Existing (but unknown) use cases

21. The Way to Live
as a OSS developer
• We can't create a super product at first
• Anyone can't create a super product without
continuous improvement

22. The Way to Live as a OSS developer
Do it, and keep doing it.
Thank you!