How to join the LimeSurvey project team/ja

あなたが必要です！

LimeSurveyが素晴らしい製品だと思うなら、貢献してみませんか？

コードを書く必要はありません。テスター、翻訳者、サポーター、またはそのすべてになれます。歓迎します。または、ソースをちょっとハッキングして素晴らしい新機能を作ったり、このプロジェクトで将来の開発をしたいと思いませんか？私たちはあなたを愛しています！

LimeSurveyの開発者/翻訳者/チームメンバーになる方法

共通の要件

• チームプレイヤー、素敵で丁寧な人。
• 他のチームメンバーと頻繁にコミュニケーションをとってください。開発ミーティングに出席してください。IRCチャンネル（[1]）に参加して、何が起こっているか見てください。
• 考えを共有してください。一人で考えないで、あなたのアイデアを他のチームメンバーと話し合ってください。
• 現実の人生が最優先です。参加できないときはどのぐらいになるか知らせてください。
• 開発者はオープンソースプロジェクトに出たり入ったりします。これは極めて普通のことです。ただ、プロジェクトを離れる場合は、どこまで進んだのか、何をしたのか、やるべきことがまだあるかどうか、他の誰かがあなたの仕事を続けることができるよう教えてください。
• 毎週火曜日、ベルリン時間14:30に開催される開発者会議に参加してください。会議は、irc.freenode.orgでチャンネルは#limesurvey-teamです（パスワードはCarsten Schmitzに聞いてください）。

最初のステップ

If you agree to the above points please follow these steps:

1. Create a personal account on the limesurvey.org website here (if you don't have one): [2]
2. Create a personal account on gitHub here (if you don't have one): [3]
3. Make sure you subscribe to the limesurvey-developer mailing list at [4]. If you want to get notified of any changes in the development source code then subscribe to the limesurvey-git list too.
4. If you use a Windows System get the Git client SmartGit (there are others but we recommend this one) to access the source code gitHub. You can download it from [5]
5. Introduce yourself on the limesurvey-developer mailing list and provide the following information:
   1. A short resume (so we can see what your background is)
   2. Tell us why you would like to work in the LimeSurvey project ('I am bored to death!', 'I like your style...') (:wink:)
   3. Tell us in what area you would like to help (coding, patching, support etc.)
6. Carsten Schmitz will get back to you as soon as possible. He is a very nice guy and will give you an introduction and will provide more information on the next steps.
7. Visit the official LimeSurvey IRC Channel and SAY HELLO TO US!
   ([6])

Additional information for new developers

LimeSurvey contains a lot of old and mess code - but by now we strictly pay attention to coding guidelines which are very important.

Coding Guidelines and Generic Code Implementation will help you and any developers working on your code at a later time by easier understanding your code and making it more modular.

To ensure this quality we are mentoring new developers using the following steps:

1. At first we only assign small tasks to the new developer. What task is assigned will be decided together with the new developer.
2. The developer sends the code to the mentor for review.
3. If the mentor is satisfied with the code quality the developer may commit the code to the repository.
4. Rinse and repeat Step 1 to 3 until the mentor states that the new developer is ready to submit patches freely to the repository.

Additional information for new supporters

Giving support is a specialty since you are interacting with lots of different persons, friendly and not so friendly, strict or sloppy, eager or calm.

Therefore we have a special request to persons who give support in the channel or forums:

• Don't be caught by support burnout.  It's nearly impossible to answer every technical question that is asked in the forum. In many cases, the problem doesn't lie in the technical aspects of the question; cultural barriers may get in the way of communication, or it may be difficult to explain to a newbie just where to begin. When you try to answer every question, regardless of difficulty, you set yourself up for support burnout.
  Support burnout is nearly always accompanied by the feeling that you're losing control of your time, that the people you've set out to help are making unreasonable demands. The problem is that you're taking on too much responsibility; but it begins to appear instead that the problem is the end user who's asking for help.
  Different people react to support burnout in different ways. Some offer malicious advice, some insist that every question a newbie asks should be answered with a URL or by lists of manual references.
  Such arbitrary rule sets tend to grow longer over time, because they don't solve the real problem. You can't answer every question, and you shouldn't try. Be gentle, be courteous, be flexible and be as patient and helpful as you can - but let someone else try to answer questions that you find too frustrating. Don't try to be a superhuman support machine. Also leave room for user-to-user help. If you support every user and answer every question you do not necessarily boost the community thinking because too much activity takes away any other user motivation to help.