Gentoo Archives: gentoo-soc

From: Donnie Berkholz <dberkholz@g.o>
To: gentoo-soc@l.g.o
Subject: [gentoo-soc] Welcome, GSoC students!
Date: Fri, 14 May 2010 15:05:02
Message-Id: 20100514150444.GA5355@comet.mayo.edu
1 Welcome to Gentoo's edition of the Google Summer of Code, and
2 congratulations on your selection! We hope you're already in touch with
3 your mentor and getting comfortable with the tools you need, so you can
4 write code starting on day 1 of the summer. The rest of this email
5 contains general information to help you be more productive this summer.
6
7 If you aren't already in touch with your mentors, this email should be
8 followed by another email from your primary mentor giving you more
9 specific details. This year, you'll be working on 1 of 19 projects. We
10 grew more than 100% from last year, when we had 7 projects, so we're
11 really excited about working with all of you this summer!
12
13 I've included a list of all of the people you'll be working with this
14 summer, and their projects, at the end of this email.
15
16
17 Communicating
18 =============
19
20 The community bonding period has already begun, and the purpose is to
21 familiarize you with our general community practices. It is *very
22 important* that you are in constant touch with your mentor throughout
23 the duration of the program. There are several channels of communication
24 that Gentoo developers use, and we'll go through the most important of
25 them:
26
27 Mailing Lists
28 -------------
29 gentoo-dev is the list where technical discussions related to Gentoo not
30 suited for more specific lists takes place. We highly recommend you
31 subscribe to this list and lurk for a while to get a feel of what kind
32 of questions are asked on it. You should already be subscribed to the
33 gentoo-soc mailing list, where you will receive important announcements
34 related to the program. In addition to these two lists, your mentor
35 might also want you to subscribe to another list, depending on your
36 project. A complete listing of all our mailing lists, along with
37 information on how you can subscribe to them is available on:
38 http://www.gentoo.org/main/en/lists.xml
39
40 The primary language of communication on most of our lists is English,
41 but a lot of us are not native English speakers, so don't be ashamed of
42 writing 'bad english'. It is usually sufficient if you are able to
43 communicate your idea and everyone understands what you are trying to
44 say. Also, don't be afraid of asking 'stupid questions' -- many of you
45 are new to the world of open-source software, and we are aware of that.
46 We're here to help.
47
48 When starting a new thread on a mailing list, send a new email to the
49 list -- don't reply to an existing thread. Also, you are expected to
50 send plain-text email, no HTML! Learn how to quote relevant portions
51 when replying to a thread. This web page might help:
52 http://www.netmeister.org/news/learn2quote.html
53
54 IRC
55 ---
56 The majority of Gentoo developers hang out in several channels on the
57 Freenode IRC channel. IRC is generally used for real-time conversations
58 and is very useful when you want a quick reply. The starting point for
59 you should be the #gentoo-soc channel; your mentor will tell you which
60 other channels you are recommended to join. If you are new to IRC, this
61 might help: http://www.irchelp.org/irchelp/irctutorial.html
62
63 IRC is a highly informal environment, and we don't recommend you make
64 important decisions there unless you've scheduled a meeting with your
65 mentor to discuss them. Even if you do, we recommend you archive that
66 decision by other means (a post to a list, blog post) since most IRC
67 channels are not logged. Also, some developers don't use IRC at all but
68 they may have something valuable to say.
69
70 Bugzilla
71 --------
72 Gentoo maintains a bug database on: http://bugs.gentoo.org/. We
73 recommend you sign up for an account there. Depending on your project,
74 your mentor may expect you to file bugs and follow them. Whenever your
75 project involves changes to code maintained by existing Gentoo
76 developers, you will usually have to file a bug and follow it up. Your
77 mentor will tell you whether or not you will be using Bugzilla, and if
78 yes, to what extent.
79
80 Blogs
81 -----
82 Many developers use blogs to communicate with the community at large. We
83 recommend you read posts on Planet Gentoo (http://planet.gentoo.org/)
84 and add the feed to your reader. We also highly recommend that you get a
85 blog for yourself (if you already don't have one), and use it to write
86 anything relevant to your project under a category such as 'gsoc2010' or
87 'gentoo'. We will aggregate your blogs on our Planet for the entire
88 Gentoo community to read.
89
90
91 Code Management
92 ===============
93
94 Gentoo uses a mix of CVS, SVN and Git internally. We expect you to
95 maintain a repository containing your code on Gentoo infrastructure,
96 although you may choose to actively work on the code elsewhere (for
97 example, Github). One of the explicit aims of the Community Bonding
98 period is to get you up to speed with the version control system you
99 will be working with. Please contact your mentor for help *before*
100 signing up with a particular service. In some cases, you may be expected
101 to work on an existing repository -- contact your mentor for specifics.
102
103 To have a repository set up, contact Robin Johnson (robbat2@g.o)
104 and send him a public SSH key, the repository type, and the repository
105 name. Your mentor can help you with this.
106
107
108 Project Websites
109 ================
110
111 We highly recommend having a centralized location for information about
112 you and your project, and Trac is an ideal way to do that. We are happy
113 to set up Trac instances for your project, so it has an online home
114 where people can go to learn more about it. This will provide you with a
115 homepage, a wiki, a timeline, and possibly integration with your source
116 code.
117
118 To have Trac set up, contact Patrick Lauer (patrick@g.o) with
119 details about your project. The Trac instance should have the same name
120 as your repository, if possible. Discuss with your mentor whether Trac
121 is something you need.
122
123
124 Shell Access
125 ============
126
127 As a GSoC student with Gentoo, you get access to one of our shell
128 servers. This is an ideal place to run an IRC client like irssi coupled
129 with screen, so that you are always available on IRC and can reconnect
130 from anywhere. Contact Robin Johnson (robbat2@g.o) with your
131 public SSH key, and he will set you up with access.
132
133 If you don't already have an SSH key, you can generate one like this:
134 `ssh-keygen -t dsa`. Be sure to set a passphrase on your key. The
135 'id_dsa.pub' file is what you send to Robin.
136
137
138 Progress Reports
139 ================
140
141 We expect weekly progress reports from each of you, at the very least.
142 Feel free to report more often! Your mentor will tell you his preferred
143 method of communication, but you must also post your weekly progress
144 reports to the gentoo-soc mailing list, as well as on your blog for all
145 to see. Make sure that you inform your mentor well in advance if you
146 plan to be missing for a week or more (vacation, exams etc.). We
147 understand that you have a student life to attend to in parallel, but if
148 you are missing for more than a week without reason, we will be forced
149 to disqualify you from the program.
150
151
152 Questions
153 =========
154
155 Your mentor is the primary contact for any questions pertaining to the
156 program, technical or not. However, it is possible that a mentor may be
157 unreachable for sometime due to personal reasons or otherwise. It is
158 *extremely* important that you immediately notify our organization
159 administrators in the event that your mentor is unavailable for more
160 than 3 days. The administrator will immediately look into the issue and
161 assign a new mentor, if required. Since all of us are from various
162 cultures around the world, it is also possible that you and your mentor
163 may not "get along" very well. Please do contact our organization
164 administrators to discuss any such issues:
165
166 Donnie Berkholz: dberkholz@g.o
167 Alec Warner (backup admin): antarus@g.o
168
169 As a final note, we want to remind you that this is the Summer of Code,
170 and not the Summer of Project Research And Design or the Summer of
171 Learning Your Programming Language And Tools. Please make sure you've
172 got all the background work done by May 24 so you can spend the whole
173 summer writing code.
174
175 We're looking forward to a great summer with all of you, and we hope
176 that all 19 projects are successful. Please don't hesitate to use any of
177 the mentioned communication channels if you have a question or doubt.
178
179 Have a great summer!
180
181 --
182 Thanks,
183 Donnie
184
185 Donnie Berkholz
186 Admin, Summer of Code
187 Gentoo Linux
188 Blog: http://dberkholz.wordpress.com
189
190
191
192 Here's the list of this summer's projects. Your primary mentor is first,
193 and if you have secondary mentors, they're later in the list:
194
195 Improve NetworkManager integration with Gentoo
196 Student: Mu Qiao
197 Mentors: Robert Piasek, Arun Raghavan, Nirbheek Chauhan
198
199 Rewrite of g-pypi ebuild conversion tool
200 Student: Domen Kozar
201 Mentors: Jesus Rivero, Brian Harring
202
203 Ventoo - Visual Configure file editor
204 Student: Christopher Harvey
205 Mentor: Luis Araujo, Jesus Rivero
206
207 Improve the Octave/Matlab support.
208 Student: Rafael Goncalves Martins
209 Mentors: Denis Dupeyron, Sébastien Fabbro
210
211 Project Grumpy
212 Student: Priit Laes
213 Mentors: Mart Raudsepp, Brian Harring
214
215 Port the new distro-neutral initrd framework, Dracut, to Gentoo
216 Student: Amadeusz Zolnowski
217 Mentors: Lance Albertson, Eric Thibodeau
218
219 Porting Portage and its tools to DragonFly BSD.
220 Student: Naohiro Aota
221 Mentors: Patrick Lauer, Javier Villavicencio
222
223 Multiple Repository Support in sys-apps/portage
224 Student: Otavio Pontes
225 Mentors: Alec Warner, Zachary Medico, Brian Harring
226
227 Revive Kuroo
228 Student: Detlev Casanova
229 Mentor: Brian Dolbec
230
231 Help Gentoo Council and Recruiters by providing web based applications
232 Student: Joachim Bartosik
233 Mentors: Alex Legler, Petteri Raty
234
235 Gentoo-x86 QA Website
236 Student: John-Patrik Nilsson
237 Mentors: Brian Harring, Mart Raudsepp
238
239 "IDFetch" (Intelligent Distfile Fetcher)
240 Student: Kostyantyn Ovechko
241 Mentor: Robin Johnson
242
243 Portage/ebuild ability to use file-based capabilities rather than setuid
244 Student: Constanze Hausner
245 Mentors: Diego Elio Pettenò, Zachary Medico
246
247 Bash Programmatic and AST access
248 Student: Nathan Eloe
249 Mentors: Petteri Raty, Brian Harring
250
251 webapp-config rewrite
252 Student: Andreas Nuesslein
253 Mentor: Benedikt Boehm
254
255 Decreasing Gentoo boot time using Upstart
256 Student: Oliver Schinagl
257 Mentors: Steev Klimaszewski, Robin Johnson
258
259 G-CRAN
260 Student: Auke Booij
261 Mentor: Sébastien Fabbro
262
263 The Gentoo Council Web Application
264 Student: Wei Xie
265 Mentors: Hans de Graaff, Petteri Raty
266
267 G-PEAR
268 Student: Wiktor W Brodlo
269 Mentors: Steve Dibb, Anant Narayanan

Replies

Subject Author
Re: [gentoo-soc] Welcome, GSoC students! Mu Qiao <qiaomuf@×××××.com>
Re: [gentoo-soc] Welcome, GSoC students! "Petteri Räty" <betelgeuse@g.o>
[gentoo-soc] Git repository for libbash "Petteri Räty" <betelgeuse@g.o>
Re: [gentoo-soc] Welcome, GSoC students! Christopher Harvey <chris@××××××××××××.com>