Switch branches/tags
Nothing to show
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


Code party(コード懇親会)


RubyData Tokyo Meetupの後はデータサイエンス関連のRubyのコードを書きながら懇親しましょう!


This is not a typical party. For familiar party, participants enjoy drinking and talking. At the code party, We will enjoy together while programing. It is an good opportunity to exchange directly with other Rubyists. Let's develop together and have fun!


Because it is not a typical party, there may be people saying "Although it seems to be fun, I can not tell whether I will participate or not because I care about what it will become." So, in order to be able to imagine the contents of this code party, we have summarized some similar events, not doing things and doing things.


If you have anything else you want to know please ask with the issue. It is the same way as usual development! Because it's a code party!

他にも知りたいことがある人は issue で質問してください。普段の開発と同じやり方です!だって、これはコード懇親会ですから!

Similar contents(似ている内容)

The content of the code party is similar to "Sprint". In Python's event, We often see "Sprint". For example, there are Development Sprints of PyCon 2018 in Cleveland, Ohio. Both Sprint and code party write code, but Sprint focuses on developing it, Code Party focuses on writing code and enjoying it.

コード懇親会の内容は「スプリント」と似ています。Pythonのイベントでは「スプリント」をよくみかけます。たとえば、PyCon JP 2017 in Tokyo のスプリントがありました。 スプリントもコード懇親会もコードを書きますが、スプリントは開発することにより注力し、コード懇親会は懇親することに注力します。

The content of the code party is somewhat similar to "Hackathon". Both of them write the code, but there are the following differences.

  • Hackathon may be held for a long time, but the code party ends in the same amount of time (2 hours) as a typical party.
  • In Hackathon, we may review development results, but never review at code party.


  • ハッカソンは長時間開催されることがあるが、コード懇親会はよくある懇親会と同じくらいの時間(2時間)で終わる
  • ハッカソンでは開発成果を審査することがあるが、コード懇親会は決して審査しない

What you do not do(やらないこと)

The concept of code party is "If you are writing code fun even alone, it is fun to interact through code!" Therefore, at the code party, we will not "enrich with the usual way of writing code". For example, we do not prepare the following planning. (It is free for participants to do spontaneously with each other.)

  • Code Golf
  • Mob Programming


  • コードゴルフ
  • モブプログラミング

What you do(やること)

Participants write code as usual as a code party. To do so, proceed as follows.


  1. Create a group for each product

    • Example: mxnet.rb, PyCall, Apache Arrow, Red Data Tools, Red Chainer, Cumo, XND, rubyplot, Menoh-Ruby, Numo and so on.
    • What kind of group you can do depends on the participants (If you do not have it yet, make it new)
    • Desks and chairs are gathered for each group
      • To make code easy to write
    • Preparing N displays for each group
      • In order to make it easy to share PC screen
    • White board prepared for each group
      • For easier discussion


    • 例:mxnet.rb、PyCall、Apache Arrow、Red Data Tools、Red Chainer、Cumo、XND、rubyplot、Menoh-Ruby、Numoなど
    • どんなグループができるかは参加者次第(まだなかったら新しく作る)
    • グループごとに机とイスがまとまっている
      • コードを書きやすくするため
    • 各グループにn個のディスプレイを用意
      • PCの画面を共有しやすくするため
    • 各グループにホワイトボードを用意
      • 相談しやすくするため
  2. Participants join somewhere in the group

    • Group can be changed freely later, so feel free to decide
    • You can decide which group you want to join in advance, whichever you decide not to decide
    • You can talk to which group you would like to join on the day


    • グループはあとから自由に変更できるので気軽に決めてよい
    • 事前にどのグループに入りたいかは決めてきても決めてこなくてもどちらでもよい
    • 当日どのグループに入るのがよさそうか相談できる
  3. Interacting while writing the code together in the group

    • Main content (less than 2 hours)
    • Example: Consultation on development offline with people who are constantly developing together online
    • Example: Consultation as to the author of gem that I normally use talks about where it is better to participate in development
    • Move to other group
    • Make it easier to understand what other groups are there
      • Example: Group map is prepared on the whiteboard
    • Food and drink prepared at the venue


    • メインコンテンツ(2時間弱)
    • 例:オンラインで一緒に開発している人とオフラインで開発の相談
    • 例:普段使っているgemの作者にどこから開発に参加するのがよさそうか相談して開発に参加
    • 他のグループに移動可能
    • 会場には他にどのようなグループがあるかわかりやすくなる仕組みを用意
      • 例:ホワイトボードにグループマップを用意
    • 会場には飲食物を用意
  4. Submit a questionnaire

    • Submit the pull request on how the code party is in the end
      • Since it is a code party, submit a questionnaire as usual!
    • Refer to feedback for the submission method


    • 最後にこの会がどうだったかをプルリクエストで提出
      • コード懇親会なので、アンケートの提出もいつものように!
    • 提出方法はfeedbackを参照