1 |
On 05/14/2010 11:04 PM, Donnie Berkholz wrote: |
2 |
> Welcome to Gentoo's edition of the Google Summer of Code, and |
3 |
> congratulations on your selection! We hope you're already in touch with |
4 |
> your mentor and getting comfortable with the tools you need, so you can |
5 |
> write code starting on day 1 of the summer. The rest of this email |
6 |
> contains general information to help you be more productive this summer. |
7 |
> |
8 |
> If you aren't already in touch with your mentors, this email should be |
9 |
> followed by another email from your primary mentor giving you more |
10 |
> specific details. This year, you'll be working on 1 of 19 projects. We |
11 |
> grew more than 100% from last year, when we had 7 projects, so we're |
12 |
> really excited about working with all of you this summer! |
13 |
> |
14 |
> I've included a list of all of the people you'll be working with this |
15 |
> summer, and their projects, at the end of this email. |
16 |
> |
17 |
> |
18 |
> Communicating |
19 |
> ============= |
20 |
> |
21 |
> The community bonding period has already begun, and the purpose is to |
22 |
> familiarize you with our general community practices. It is *very |
23 |
> important* that you are in constant touch with your mentor throughout |
24 |
> the duration of the program. There are several channels of communication |
25 |
> that Gentoo developers use, and we'll go through the most important of |
26 |
> them: |
27 |
> |
28 |
> Mailing Lists |
29 |
> ------------- |
30 |
> gentoo-dev is the list where technical discussions related to Gentoo not |
31 |
> suited for more specific lists takes place. We highly recommend you |
32 |
> subscribe to this list and lurk for a while to get a feel of what kind |
33 |
> of questions are asked on it. You should already be subscribed to the |
34 |
> gentoo-soc mailing list, where you will receive important announcements |
35 |
> related to the program. In addition to these two lists, your mentor |
36 |
> might also want you to subscribe to another list, depending on your |
37 |
> project. A complete listing of all our mailing lists, along with |
38 |
> information on how you can subscribe to them is available on: |
39 |
> http://www.gentoo.org/main/en/lists.xml |
40 |
> |
41 |
> The primary language of communication on most of our lists is English, |
42 |
> but a lot of us are not native English speakers, so don't be ashamed of |
43 |
> writing 'bad english'. It is usually sufficient if you are able to |
44 |
> communicate your idea and everyone understands what you are trying to |
45 |
> say. Also, don't be afraid of asking 'stupid questions' -- many of you |
46 |
> are new to the world of open-source software, and we are aware of that. |
47 |
> We're here to help. |
48 |
> |
49 |
> When starting a new thread on a mailing list, send a new email to the |
50 |
> list -- don't reply to an existing thread. Also, you are expected to |
51 |
> send plain-text email, no HTML! Learn how to quote relevant portions |
52 |
> when replying to a thread. This web page might help: |
53 |
> http://www.netmeister.org/news/learn2quote.html |
54 |
> |
55 |
> IRC |
56 |
> --- |
57 |
> The majority of Gentoo developers hang out in several channels on the |
58 |
> Freenode IRC channel. IRC is generally used for real-time conversations |
59 |
> and is very useful when you want a quick reply. The starting point for |
60 |
> you should be the #gentoo-soc channel; your mentor will tell you which |
61 |
> other channels you are recommended to join. If you are new to IRC, this |
62 |
> might help: http://www.irchelp.org/irchelp/irctutorial.html |
63 |
> |
64 |
> IRC is a highly informal environment, and we don't recommend you make |
65 |
> important decisions there unless you've scheduled a meeting with your |
66 |
> mentor to discuss them. Even if you do, we recommend you archive that |
67 |
> decision by other means (a post to a list, blog post) since most IRC |
68 |
> channels are not logged. Also, some developers don't use IRC at all but |
69 |
> they may have something valuable to say. |
70 |
> |
71 |
> Bugzilla |
72 |
> -------- |
73 |
> Gentoo maintains a bug database on: http://bugs.gentoo.org/. We |
74 |
> recommend you sign up for an account there. Depending on your project, |
75 |
> your mentor may expect you to file bugs and follow them. Whenever your |
76 |
> project involves changes to code maintained by existing Gentoo |
77 |
> developers, you will usually have to file a bug and follow it up. Your |
78 |
> mentor will tell you whether or not you will be using Bugzilla, and if |
79 |
> yes, to what extent. |
80 |
> |
81 |
> Blogs |
82 |
> ----- |
83 |
> Many developers use blogs to communicate with the community at large. We |
84 |
> recommend you read posts on Planet Gentoo (http://planet.gentoo.org/) |
85 |
> and add the feed to your reader. We also highly recommend that you get a |
86 |
> blog for yourself (if you already don't have one), and use it to write |
87 |
> anything relevant to your project under a category such as 'gsoc2010' or |
88 |
> 'gentoo'. We will aggregate your blogs on our Planet for the entire |
89 |
> Gentoo community to read. |
90 |
> |
91 |
> |
92 |
> Code Management |
93 |
> =============== |
94 |
> |
95 |
> Gentoo uses a mix of CVS, SVN and Git internally. We expect you to |
96 |
> maintain a repository containing your code on Gentoo infrastructure, |
97 |
> although you may choose to actively work on the code elsewhere (for |
98 |
> example, Github). One of the explicit aims of the Community Bonding |
99 |
> period is to get you up to speed with the version control system you |
100 |
> will be working with. Please contact your mentor for help *before* |
101 |
> signing up with a particular service. In some cases, you may be expected |
102 |
> to work on an existing repository -- contact your mentor for specifics. |
103 |
> |
104 |
> To have a repository set up, contact Robin Johnson (robbat2@g.o) |
105 |
> and send him a public SSH key, the repository type, and the repository |
106 |
> name. Your mentor can help you with this. |
107 |
> |
108 |
> |
109 |
> Project Websites |
110 |
> ================ |
111 |
> |
112 |
> We highly recommend having a centralized location for information about |
113 |
> you and your project, and Trac is an ideal way to do that. We are happy |
114 |
> to set up Trac instances for your project, so it has an online home |
115 |
> where people can go to learn more about it. This will provide you with a |
116 |
> homepage, a wiki, a timeline, and possibly integration with your source |
117 |
> code. |
118 |
> |
119 |
> To have Trac set up, contact Patrick Lauer (patrick@g.o) with |
120 |
> details about your project. The Trac instance should have the same name |
121 |
> as your repository, if possible. Discuss with your mentor whether Trac |
122 |
> is something you need. |
123 |
> |
124 |
> |
125 |
> Shell Access |
126 |
> ============ |
127 |
> |
128 |
> As a GSoC student with Gentoo, you get access to one of our shell |
129 |
> servers. This is an ideal place to run an IRC client like irssi coupled |
130 |
> with screen, so that you are always available on IRC and can reconnect |
131 |
> from anywhere. Contact Robin Johnson (robbat2@g.o) with your |
132 |
> public SSH key, and he will set you up with access. |
133 |
> |
134 |
> If you don't already have an SSH key, you can generate one like this: |
135 |
> `ssh-keygen -t dsa`. Be sure to set a passphrase on your key. The |
136 |
> 'id_dsa.pub' file is what you send to Robin. |
137 |
> |
138 |
> |
139 |
> Progress Reports |
140 |
> ================ |
141 |
> |
142 |
> We expect weekly progress reports from each of you, at the very least. |
143 |
> Feel free to report more often! Your mentor will tell you his preferred |
144 |
> method of communication, but you must also post your weekly progress |
145 |
> reports to the gentoo-soc mailing list, as well as on your blog for all |
146 |
> to see. Make sure that you inform your mentor well in advance if you |
147 |
> plan to be missing for a week or more (vacation, exams etc.). We |
148 |
> understand that you have a student life to attend to in parallel, but if |
149 |
> you are missing for more than a week without reason, we will be forced |
150 |
> to disqualify you from the program. |
151 |
> |
152 |
> |
153 |
> Questions |
154 |
> ========= |
155 |
> |
156 |
> Your mentor is the primary contact for any questions pertaining to the |
157 |
> program, technical or not. However, it is possible that a mentor may be |
158 |
> unreachable for sometime due to personal reasons or otherwise. It is |
159 |
> *extremely* important that you immediately notify our organization |
160 |
> administrators in the event that your mentor is unavailable for more |
161 |
> than 3 days. The administrator will immediately look into the issue and |
162 |
> assign a new mentor, if required. Since all of us are from various |
163 |
> cultures around the world, it is also possible that you and your mentor |
164 |
> may not "get along" very well. Please do contact our organization |
165 |
> administrators to discuss any such issues: |
166 |
> |
167 |
> Donnie Berkholz: dberkholz@g.o |
168 |
> Alec Warner (backup admin): antarus@g.o |
169 |
> |
170 |
> As a final note, we want to remind you that this is the Summer of Code, |
171 |
> and not the Summer of Project Research And Design or the Summer of |
172 |
> Learning Your Programming Language And Tools. Please make sure you've |
173 |
> got all the background work done by May 24 so you can spend the whole |
174 |
> summer writing code. |
175 |
> |
176 |
> We're looking forward to a great summer with all of you, and we hope |
177 |
> that all 19 projects are successful. Please don't hesitate to use any of |
178 |
> the mentioned communication channels if you have a question or doubt. |
179 |
> |
180 |
> Have a great summer! |
181 |
> |
182 |
|
183 |
Thank you for giving such detailed information to us! I really |
184 |
appreciate that Gentoo community provides us with a bunch of useful |
185 |
resources. |
186 |
I have questions about the Blogs and Progress reports. |
187 |
|
188 |
1. I didn't use blog before and I think it's time for me to get one as |
189 |
you suggested. Is it possible to create a blog at blogs.gentoo.org? |
190 |
|
191 |
2. When should we start reporting the progress of our projects? |
192 |
|
193 |
-- |
194 |
Best wishes, |
195 |
Mu Qiao |
196 |
GnuPG fingerprint: 92B1 B0C4 8D14 F8C4 EFA5 3ACC 30B3 0DE4 17B1 57E9 |