• Introduction
• What is Google Summer of Code?
• Why Should I Apply?
• Am I Good Enough?
• Applying
• Making First Contact
• Choosing an Organization
• Finding the Right Project
• Writing a Proposal
• Being Turned Down
• Community Bonding Period
• How GSoC Works
• What Does Community Mean?
• Open Source Culture
• Communication Best Practices
• How to Get a Head Start
• Let the Coding Begin
• Working with Your Mentor
• Time Management for Students
• Evaluations
• Wrapping Up
• Getting Your Code Committed
• Staying Engaged with Your Community
• APPENDICES
• About This Manual
• History of GSoC
• Additional Resources
• Proposal Example 1
• Proposal Example 2
• Glossary
• Credits

Communication Best Practices  

One of the best things about GSoC is the group of individuals from diverse cultures and different open source organizations that participate each year. This also means that you cannot make any assumptions about communication. Specifically:

• Always read the Program Rules, FAQ and manual first! One of the best ways to destroy your reputation early is to repeatedly ask questions on IRC or the mailing list that are covered in a FAQ or other types of documentation.
• Don't expect instant answers. Remember you are working with volunteers.
• Avoid humor when communicating with the entire GSoC community. It does not translate well to large groups and is likely to be misconstrued by someone.
• Remember that other peoples' time is just as valuable as your own.  

How to Use a Mailing List

Every community uses mailing lists differently. It is extremely important that you spend some time understanding how to participate in a way that is acceptable to the community. Read the mailing list archives, observe for awhile first and be sure to inquire about and read any codes of conduct or guidelines before you post.

Some specific guidelines that should apply across communities:

• Follow the mailing list posting style. Do people top or bottom post? Follow the norm.
• Keep your posts on-topic. Avoid tangents and posting "I know this is off-topic but..." type posts. If you have any doubt, email the moderator before you post. 
• Don't cross-post to multiple lists. Communicating well on mailing lists means knowing where and when to post items, if you have any doubts regarding what is appropriate, ask the moderator.
• Never send community members unsolicited personal messages. Especially, if your content is along the lines of "the way you talk about code really turns me on." Inappropriate!
• If you are offended by a response or post, walk-away. Do not respond when you are angry.
• Avoid posting to the mailing list if you are significantly under the influence of anything that makes you behave out of your norm. Just like drunk-dialing is bad -- so is drunk emailing to your open source community mailing list.
• Avoid profanity.
• Don't post chain letters, marketing messages or other types of non-topical spam.
• Always check the archives before re-posting your message. Lots of mail clients don't send you duplicates of your mailing lists posts. Check the archives before you re-send!
• Always read the entire thread before replying. Seriously, read every message in a thread first!
• Don't use the mailing list as your own personal Google. Take the time to research the question first. Check the archives, search the project documentation first, Google it yourself.
• Don't begin or get involved in religious or political arguments.  
• Never proselytize on the mailing list. 
• Do your best to always assume the best of the poster. We all have bad days. Sometimes, a non-native speaker may appear to have an offensive "tone" in the post where no offense is meant.
• Avoid unintentional "tone" in your postings. If you have any doubt read your message out loud or have someone else read your message before you post.

Like a bullhorn 

When you post to the GSoC student list you are essentially using a bullhorn to broadcast your words to 7,000 people across time zones and international boundaries. Use your bullhorn wisely, or it might be ripped from your hands by an unruly and angry mob, or by a responsible moderator. 

How to Use IRC

Many projects use IRC for real-time conversations. Often these IRC conversations appear very casual. It is always best to assume formality if you have any doubts about who may be listening or participating in the conversation.

The Fedora Project has a great FAQ on how to use IRC. Read it!

http://fedoraproject.org/wiki/Fedora_Channel_FAQ

Some additional guidelines:

• Include your real name in your IRC signature information.
• Never private-message (pm) someone that you don't know without first asking if it is OK in the public channel.
• Read the topic before asking questions.
• Stay on-topic for the channel.
• Before asking questions in #gsoc - read the FAQ!