Inspired by the Welcome kit created by Remy DeCauseMaker (decause) which can be found here. Contains content from the original post.
If you are reading this, congratulations! Your project idea has now become an official Google Summer of Code project and you're all set to go. The aim of this welcome kit is to provide a basic overview of the Fedora project and make you familiar with the workflow of the Fedora Project. If you have any questions about this welcome kit, please feel free to ping skamath on #fedora-commops on Freenode or send me an e-mail @ [email protected]
The Google Summer of Code webapp has an official timeline which is followed by all the origanizations which can be found here. No exceptions will be made here and all the evaluations will happen as per the GSoC timeline. The dates are documented here for clarity.
| Date | Event/Milestone |
|---|---|
| March 20, 2017 - April 3, 2017 | Student Application Period |
| May 4, 2017 | Student Projects Announced |
| May 5 - 30, 2017 | Community Bonding Period |
| May 30, 2017 - August 21, 2017 | Coding Period |
| June 26 - 30, 2017 | First Evaluations (Part of coding period) |
| June 26 - 30, 2017 | Second Evaluations (Part of coding period) |
| August 21 - 29, 2017 | Code Submission & Mentor review |
| August 29, 2017 - September 5, 2017 | Mentors Submit Final Evaluations |
| September 6, 2017 | Final Results Announced |
Community bonding period is a very important part of the program and all the interns are expected to be in constant touch with the mentors and the community in understanding the workflow of the community. As Google community puts it, the community bonding period acts a bridge between an intern and the community.
As a Fedora GSoC student, you should be doing the following things during the community bonding period :
You are expected to send an introduction mail on the project/SIG mailing list with your basic information, your FAS account details, brief plan of action and anything else that you think is relevant. The mail should help the community better understand you as a person and the project you will be working on this summer.
List of relevant mailing lists :
| Title | Link |
|---|---|
| Fedora Development List | https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org |
| General Summer Coding List | https://lists.fedoraproject.org/admin/lists/summer-coding.lists.fedoraproject.org |
| Lists Directory (Browse all mailing lists) | https://lists.fedoraproject.org |
A developer blog is a crucial part of building your presence and personal brand, and communicating with the FOSS community. This will be the primary place you publish your weekly reports. If you already have a blog, you can use that for your development blog, just make sure that it follows the planet guidelines listed below here, and that your RSS feed you generate uses tags or categories to make sure all your content is relevant to the planet readers.
Quoting Planet Wiki, Planet Fedora is a distributed communication tool that many Fedora contributors rely on to keep a pulse on Fedora's community. Contributors connect their blogs to Planet Fedora to express to the Fedora community their thoughts and personality, and share what they are working on through blog posts.
Read more about Fedora planet and set up a blog here.
If you are not CLA+1, please wait until you get added to the
summer-codingFAS group. In the mean time, you can also join the FAS group of your SIG/Community if it exists.
Fedora uses IRC as a primary mode of communication. As a summer coding participant, you should be attending the community meetings regularly. This is an important step and will help you understand the community better. You can find the list of meetings on Fedocal.
If you are new to IRC, please read How to communicate using IRC on Fedora wiki.
If you are unsure on what meetings to attend, please contact your mentor.
You should use the community bonding period to understand the existing codebase and get familiar with the modules and functionalities. Stating the obvious, you should also be setting up all the tools and utilities required for the coding period.
Pagure is a light-weight git-centered forge where we do project coordination and collaboration in Fedora. We also use pagure as a ticket tracker and almost all the communities have a Pagure group where tickets are created as issues and discussed. You will be using Pagure to host code or contribute to existing projects while working on your project.
You should introduce yourself on your blog (after you're hooked up to the Fedora Planet) and let the Fedora community know who you are, what you've done, and what you are looking to accomplish this summer. Feel free to add any links to social media or other places you'd like to promote your online presence (within the planet guidelines.) You can also share a link to this introduction on the summer-coding mailing list as well.
You should do this so that you can fly the Fedora Flag, and so that you can protect your IP address when connecting on Freenode. See this wiki page for instructions - https://fedoraproject.org/wiki/FreenodeCloaks
Feel free to ask any questions to the mentor. Before asking, make sure you research on the topic by searching online. When in doubt, always contact the mentor on IRC/Mailing list. You can also ask your questions on the community IRC for faster and quality responses from various community members. Remember, we are here to help :)
Coding period guidelines to be added soon. This document is a work in progress.