Gentoo Archives: gentoo-soc

From: Anant Narayanan <anant@g.o>
To: gentoo-soc@l.g.o
Subject: [gentoo-soc] Welcome GSoC Students!
Date: Tue, 22 Apr 2008 18:04:13
1 Welcome to Gentoo's edition of the Google Summer of Code, and
2 congratulations on your selection! To get you started, here's some
3 general information. This email should be followed by another email
4 from your mentor giving you more specific details. This year, you'll
5 be working on 1 of 6 projects:
7 Using Gentoo, Seed Linux and Catalyst to provide easy access to a
8 Beowulf Clustering/HPC environment to everyday users
9 by Eric Thibodeau
10 mentored by Donnie Berkholz (dberkholz@g.o)
11 Eric and Donnie are going to be working on making the process of
12 creating and maintaining Beowulf clustering solutions based on Gentoo
13 easier for end-users and system administrators. This will ultimately
14 help in building machines for applications such as high performance
15 and scientific computing.
17 Automate it All
18 by Nirbheek Chauhan
19 mentored by Stephen Anthony Klimaszewski (steev@g.o)
20 Nirbheek is going to create a new web application that would enable
21 Gentoo developers to utilize remote machines for queuing "jobs", where
22 "jobs" are simply a sequence of steps that can be defined by the
23 developers. The results will then be sent back to them when they are
24 completed. Some of the use cases for such a system are: checking for
25 breakage on new versions of a package, verifying dependencies of a
26 package and arch testing.
28 Implement OpenPAM compatible modules for Linux
29 by Serafeim Mellos
30 mentored by Diego Pettenò (flameeyes@g.o)
31 Serafeim is going to write a set of PAM modules (specifically
32 pam_unix, pam_securetty, pam_shells, pam_wheel, pam_nologin and
33 others, if time permits) using the OpenPAM library. This would enable
34 users to choose between OpenPAM and the existing Linux-PAM
35 implementations and offer greater flexibility, in the true spirit of
36 Gentoo.
38 GNAP Love (embedded framework enhancements)
39 by Vít Vomáčko
40 mentored by Andrey Falko (andrey@××××××.net)
41 Vit is going to be improving the general state of Gentoo/GNAP this
42 summer. Some of the tasks he hopes to complete are: supporting more
43 platforms, make it easier for developers to write extensions, unionfs
44 and live upgrade support, catalyst related bug fixes and changes,
45 among others.
47 Setting Beacon Afloat
48 by Nandeep Mali
49 mentored by Anant Narayanan (anant@g.o)
50 Nandeep is going to revisit the GuideXML editor "Beacon", and add a
51 bunch of features such as collaborative editing, UI spruce-ups, easier
52 deployment and rewrites of certain parts of the backend. His ultimate
53 goal is to make Beacon a really competitive alternative for developers
54 and users to write and collaborate on GuideXML documents.
56 revdep-rebuild reimplementation
57 by Carl Lucian Poston
58 mentored by Marius Mauch (genone@g.o)
59 Carl is going to be re-implementing the revdep-rebuild utility. He's
60 planing on using the set framework and linkage information in
61 portage-2.2 to improve on revdep-rebuild's current behavior. At the
62 end of the project, the tool will model a system's dependencies as a
63 dependency graph and resolve all dynamic linker errors by repairing
64 broken libraries and packages.
66 Communicating
67 The community bonding period begins now and the purpose is to
68 familiarize you with our general community practices. It is *very
69 important* that you are in constant touch with your mentor throughout
70 the duration of the program. There are several channels of
71 communication that Gentoo developers use, and we'll go through the
72 most important of them:
74 - Mailing Lists: gentoo-dev is the list where technical discussions
75 related to Gentoo not suited for more specific lists takes place. We
76 highly recommend you subscribe to this list and lurk for a while to
77 get a feel of what kind of questions are asked on it. We would also
78 like you to subscribe to the gentoo-soc mailing list in order to
79 receive important announcements related to the program. In addition to
80 these two lists, your mentor might also want you to subscribe to
81 another list, depending on your project. A complete listing of all our
82 mailing lists, along with information on how you can subscribe to them
83 is available on:
85 The primary language of communication on most of our lists is
86 English, but a lot of us are not native English speakers, so don't be
87 ashamed of writing 'bad english'. It is usually sufficient if you are
88 able to communicate your idea and everyone understands what you are
89 trying to say. Also, don't be afraid of asking 'stupid questions', a
90 lot of you are new to the world of open source software, and we are
91 aware of that. We're here to help.
93 When starting a new thread on a mailing list, send a new email to the
94 list - don't reply to an existing thread. Also, you are expected to
95 send plain text email, no HTML! Learn how to quote relevant portions
96 when replying to a thread. This web page might help:
98 - IRC: A lot of Gentoo developers hang out in several channels on the
99 Freenode IRC channel. IRC is generally used for real-time
100 conversations and is very useful when you want a quick reply. The
101 starting point for you should be the #gentoo-soc channel; your mentor
102 will tell you which other channels you are recommended to join. If you
103 are new to IRC, this might help:
105 We would like to point out that IRC is a highly informal environment,
106 and we don't recommend you make important decisions there; unless
107 you've scheduled a meeting with your mentor to discuss them. Even if
108 you do, we recommend you archive that decision by other means (a post
109 to a list, blog post) since most IRC channels are not logged. Also,
110 some developers don't use IRC at all but they may have something
111 valuable to say.
113 - Bugzilla: Gentoo maintains a bug database on: http://
114 We recommend you sign up for an account there.
115 Depending on your project, your mentor may expect you to file bugs and
116 follow them. Whenever your project involves changes to code maintained
117 by existing Gentoo developers, you will usually have to file a bug and
118 follow it up. Your mentor will tell you whether or not you will be
119 using Bugzilla, and if yes, to what extent.
121 - Blogs: A lot of developers use blogs to communicate with the
122 community at large. We recommend you read posts on Planet Gentoo (
123 ) and add the feed to your reader. We also highly recommend that you
124 get a blog for yourself (if you already don't have one), and use it to
125 write anything relevant to your project under a category such as
126 'soc08' or 'gentoo'. We will be aggregating your blogs on our Planet
127 for the entire Gentoo community to read.
129 Code Management
130 - Gentoo uses a mix of CVS, SVN and Git internally. We recommend you
131 use an external code hosting service to help manage your code. Some of
132 the popular ones are:,
133 (CVS/SVN) and (Git). One of the explicit aims of
134 the Community Bonding period is to get you upto speed with the version
135 control system you will be working with. Please contact your mentor
136 for help *before* signing up with a particular service. In some cases,
137 you may be expected to work on an existing repository - again -
138 contact your mentor for specifics.
140 Progress Reports
141 - We will be expecting weekly progress reports from each of you at
142 the very least. Feel free to report more often! Your mentor will tell
143 you his preferred method of communication, but you must also post your
144 weekly progress reports to the gentoo-soc mailing list, as well as on
145 your blog for all to see. Make sure that you inform your mentor well
146 in advance if you plan to be missing for a week or more (vacation,
147 exams etc.) We understand that you have a student life to attend to in
148 parallel, but if you are missing for more than a week without reason,
149 we will be forced to disqualify you from the program.
151 Questions
152 - Your mentor is the primary contact for any questions pertaining to
153 the program, technical or not. However, it is possible that a mentor
154 may be unreachable for sometime due to personal reasons or otherwise.
155 It is *extremely* important that you immediately notify our
156 organization administrators in the event that your mentor is
157 unavailable for more than 3 days. The administrator will immediately
158 look into the issue and assign a new mentor, if required. Since all of
159 us are from various cultures around the world, it is also possible
160 that you and your mentor may not "get along" very well. Please do
161 contact our organization administrators to discuss any such issues:
163 Alec Warner: antarus@g.o
164 Grant Goodyear: g2boojum@g.o
165 Joshua Jackson: tsunam@g.o
167 We're looking forward to a great summer with all of you, and hope that
168 all 6 projects are successful. Please don't hesitate to use any of the
169 mentioned communication channels if you have a question or doubt.
171 All the best!
172 --
173 The GSoC Mentors and Admins for Gentoo
174 Summer of Code 2008--
175 gentoo-soc@l.g.o mailing list


Subject Author
Re: [gentoo-soc] Welcome GSoC Students! Nirbheek Chauhan <nirbheek.chauhan@×××××.com>
Re: [gentoo-soc] Welcome GSoC Students! Marius Mauch <google-soc@××××××.de>