1 |
Welcome to Gentoo's edition of the Google Summer of Code! We hope you've |
2 |
been in touch with your mentor and are already comfortable with the |
3 |
tools you need, so you can begin writing code today. |
4 |
|
5 |
The rest of this email contains general information to help you be more |
6 |
productive this summer; please read it completely and carefully so you |
7 |
don't miss anything critical. |
8 |
|
9 |
|
10 |
Communication |
11 |
============= |
12 |
|
13 |
It is *very important* that you are in constant touch with your mentor |
14 |
throughout the duration of the program; poor communication is one of the |
15 |
most frequent causes of failure. There are several channels of |
16 |
communication that Gentoo developers use, and we'll go through the most |
17 |
important of them: |
18 |
|
19 |
Mailing Lists |
20 |
------------- |
21 |
gentoo-dev is the list where technical discussions related to Gentoo but |
22 |
not suited for more specific lists takes place. We highly recommend you |
23 |
subscribe to this list and lurk for a while to get a feel of what kind |
24 |
of questions are asked on it. |
25 |
|
26 |
You should already be subscribed to the gentoo-soc mailing list, where |
27 |
you will receive important announcements related to the program. In |
28 |
addition to these two lists, your mentor might also want you to |
29 |
subscribe to another list, depending on your project. A complete listing |
30 |
of all our mailing lists, along with information on how you can |
31 |
subscribe to them is available on: |
32 |
http://www.gentoo.org/main/en/lists.xml |
33 |
|
34 |
The primary language of communication on most of our lists is English, |
35 |
but many of us are not native English speakers, so don't be ashamed of |
36 |
writing "bad English" although SMS text language is typically frowned |
37 |
upon ("u" instead of "you" for example). It is usually sufficient if you |
38 |
are able to communicate your idea and everyone understands what you are |
39 |
trying to say. Also, don't be afraid of asking "stupid questions" -- many |
40 |
of you are new to the world of open-source software, and we know that. |
41 |
We're here to help. |
42 |
|
43 |
When starting a new thread on a mailing list, send a new email to the |
44 |
list -- don't reply to an existing thread. Also, you are expected to send |
45 |
plain-text email, no HTML! Learn how to quote relevant portions when |
46 |
replying to a thread. This web page might help: |
47 |
http://www.netmeister.org/news/learn2quote.html |
48 |
|
49 |
IRC |
50 |
--- |
51 |
Most Gentoo developers hang out in several channels on the Freenode IRC |
52 |
channel. IRC is generally used for real-time conversations and is very |
53 |
useful when you want a quick reply. The starting point for you should be |
54 |
the #gentoo-soc channel; your mentor will tell you which other channels |
55 |
you are recommended to join. If you are new to IRC, this might help: |
56 |
http://www.irchelp.org/irchelp/irctutorial.html |
57 |
|
58 |
IRC is a highly informal environment, and we don't recommend you make |
59 |
important decisions there unless you've scheduled a meeting with your |
60 |
mentor to discuss them. Even if you do, we recommend you archive that |
61 |
decision by other means (a post to a list, blog post) since most IRC |
62 |
channels are not logged. Also, some developers don't use IRC at all but |
63 |
they may have something valuable to say. |
64 |
|
65 |
You should be available on IRC during your regular working hours. Our |
66 |
admins will want to be able to contact you there, and your mentors and |
67 |
other Gentoo developers and contributors may wish to do so as well. |
68 |
|
69 |
Bugzilla |
70 |
-------- |
71 |
Gentoo maintains a bug database at http://bugs.gentoo.org/ and you |
72 |
should sign up for an account there. Depending on your project, your |
73 |
mentor may expect you to file bugs and follow them. Whenever your |
74 |
project involves changes to code maintained by existing Gentoo |
75 |
developers, you will usually have to file a bug and follow it up. Your |
76 |
mentor will tell you whether or not you will be using Bugzilla, and if |
77 |
so, to what extent. |
78 |
|
79 |
Blogs |
80 |
----- |
81 |
Many developers use blogs to communicate with the community at large. We |
82 |
highly recommend, but do not require, that you read posts on Planet |
83 |
Gentoo (http://planet.gentoo.org/) and add the feed to your reader. We |
84 |
also highly recommend that you get a blog for yourself (if you don't |
85 |
already have one), and use it to write anything relevant to your project |
86 |
under a category such as "gsoc2013" or "gentoo." We will aggregate your |
87 |
blogs on our Planet for the entire Gentoo community to read. You can |
88 |
contact planet@g.o about getting a blog -- do mention that you are |
89 |
a GSoC student. |
90 |
|
91 |
|
92 |
Code Management |
93 |
=============== |
94 |
|
95 |
Gentoo prefers Git for code management. We expect you to |
96 |
maintain a repository containing your code on Gentoo infrastructure, |
97 |
unless you're working on an existing project that's already hosted |
98 |
elsewhere. |
99 |
|
100 |
You and your mentor should urgently contact Denis Dupeyron |
101 |
(calchan@g.o) about getting repositories set up or gaining |
102 |
access to existing repositories, if you haven't already done so. We |
103 |
expect you to start committing in the very first days of your project. |
104 |
|
105 |
|
106 |
Project Websites |
107 |
================ |
108 |
|
109 |
You must have a centralized, permanent location for information about |
110 |
you and your project that is hosted by Gentoo (unless you're working on |
111 |
an existing project hosted elsewhere). If you're working on an |
112 |
established codebase like Portage or Porthole, you can just use its |
113 |
existing infrastructure. Otherwise, the Gentoo wiki is generally your |
114 |
best bet. Please discuss it with your mentor |
115 |
|
116 |
|
117 |
Shell Access |
118 |
============ |
119 |
|
120 |
As a GSoC student with Gentoo, you get access to one of our shell |
121 |
servers. This is an ideal place to run an IRC client like irssi coupled |
122 |
with screen, so that you are always available on IRC and can reconnect |
123 |
from anywhere. Talk to your mentor about this, if you aren't already set |
124 |
up. |
125 |
|
126 |
|
127 |
Progress Reports |
128 |
================ |
129 |
|
130 |
We expect progress reports from each of you at least once a week. Feel |
131 |
free to report more often! At the top, provide a brief summary of your |
132 |
project (including links to resources like homepage and code) to remind |
133 |
anyone who hasn't followed it closely, and tell us whether it's on |
134 |
schedule, ahead of schedule, or behind schedule. Then tell us about your |
135 |
accomplishments, your problems, how you solved them, and your plans for |
136 |
the next week. |
137 |
|
138 |
Your mentors will tell you their preferred method of communication, but |
139 |
you must also post your weekly progress reports to the gentoo-soc |
140 |
mailing list. Make sure that you inform your mentor well in advance if |
141 |
you plan to be missing for *any* period of time (vacation, exams etc.). |
142 |
We understand that you may have a student life to attend to in parallel, |
143 |
but if you are missing for more than a week without reason, we will be |
144 |
forced to disqualify you from the program. |
145 |
|
146 |
Gentoo's GSoC admins may also require very short, occasional surveys to |
147 |
help us ensure you have a great time this summer. |
148 |
|
149 |
|
150 |
Questions |
151 |
========= |
152 |
|
153 |
Your mentor is the primary contact for any questions pertaining to the |
154 |
program, technical or not. However, it is possible that a mentor may be |
155 |
unreachable for sometime due to personal reasons or otherwise. It is |
156 |
*extremely* important that you immediately notify an organization |
157 |
administrator in the event that your mentor is unavailable for more than |
158 |
3 days. The administrator will immediately look into the issue and |
159 |
assign a new mentor, if required. Since all of us are from various |
160 |
cultures around the world, it is also possible that you and your mentor |
161 |
may not "get along" very well. Please do contact our organization |
162 |
administrators to discuss any such issues: |
163 |
|
164 |
Donnie Berkholz <dberkholz@g.o> |
165 |
Denis Dupeyron <calchan@g.o> |
166 |
|
167 |
As a final note, we want to remind you that this is the Summer of Code, |
168 |
and not the Summer of Project Research And Design or the Summer of |
169 |
Learning Your Programming Language And Tools. You should already have |
170 |
completed all the background work, so you can spend the whole summer |
171 |
writing code. |
172 |
|
173 |
We're looking forward to a great summer with all of you, and we hope |
174 |
that all your projects are successful. Please don't hesitate to use any |
175 |
of the mentioned communication channels if you have a question or doubt. |
176 |
|
177 |
Have a great summer! |