From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JoMqj-0002bA-5M for garchives@archives.gentoo.org; Tue, 22 Apr 2008 18:04:13 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4BAFEE02FB; Tue, 22 Apr 2008 18:04:12 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id E4145E02FB for ; Tue, 22 Apr 2008 18:04:11 +0000 (UTC) Received: from [220.224.109.155] (unknown [220.224.109.155]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 62D3C66DFB for ; Tue, 22 Apr 2008 18:04:05 +0000 (UTC) Message-Id: <47DF82F7-A0F5-4425-812B-D3F3ED0222F7@gentoo.org> From: Anant Narayanan To: gentoo-soc@lists.gentoo.org Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-soc@lists.gentoo.org Reply-to: gentoo-soc@lists.gentoo.org Mime-Version: 1.0 (Apple Message framework v919.2) Subject: [gentoo-soc] Welcome GSoC Students! Date: Tue, 22 Apr 2008 23:33:56 +0530 X-Mailer: Apple Mail (2.919.2) X-Archives-Salt: 7680e24a-c6e3-4ed4-a2e1-d748d93769f9 X-Archives-Hash: ce0c5c0e6e902f9191146c6152961644 Welcome to Gentoo's edition of the Google Summer of Code, and =20 congratulations on your selection! To get you started, here's some =20 general information. This email should be followed by another email =20 from your mentor giving you more specific details. This year, you'll =20 be working on 1 of 6 projects: Using Gentoo, Seed Linux and Catalyst to provide easy access to a =20 Beowulf Clustering/HPC environment to everyday users by Eric Thibodeau mentored by Donnie Berkholz (dberkholz@gentoo.org) Eric and Donnie are going to be working on making the process of =20 creating and maintaining Beowulf clustering solutions based on Gentoo =20= easier for end-users and system administrators. This will ultimately =20 help in building machines for applications such as high performance =20 and scientific computing. Automate it All by Nirbheek Chauhan mentored by Stephen Anthony Klimaszewski (steev@gentoo.org) Nirbheek is going to create a new web application that would enable =20 Gentoo developers to utilize remote machines for queuing "jobs", where =20= "jobs" are simply a sequence of steps that can be defined by the =20 developers. The results will then be sent back to them when they are =20 completed. Some of the use cases for such a system are: checking for =20 breakage on new versions of a package, verifying dependencies of a =20 package and arch testing. Implement OpenPAM compatible modules for Linux by Serafeim Mellos mentored by Diego Petten=C3=B2 (flameeyes@gentoo.org) Serafeim is going to write a set of PAM modules (specifically =20 pam_unix, pam_securetty, pam_shells, pam_wheel, pam_nologin and =20 others, if time permits) using the OpenPAM library. This would enable =20= users to choose between OpenPAM and the existing Linux-PAM =20 implementations and offer greater flexibility, in the true spirit of =20 Gentoo. GNAP Love (embedded framework enhancements) by V=C3=ADt Vom=C3=A1=C4=8Dko mentored by Andrey Falko (andrey@afalko.net) Vit is going to be improving the general state of Gentoo/GNAP this =20 summer. Some of the tasks he hopes to complete are: supporting more =20 platforms, make it easier for developers to write extensions, unionfs =20= and live upgrade support, catalyst related bug fixes and changes, =20 among others. Setting Beacon Afloat by Nandeep Mali mentored by Anant Narayanan (anant@gentoo.org) Nandeep is going to revisit the GuideXML editor "Beacon", and add a =20 bunch of features such as collaborative editing, UI spruce-ups, easier =20= deployment and rewrites of certain parts of the backend. His ultimate =20= goal is to make Beacon a really competitive alternative for developers =20= and users to write and collaborate on GuideXML documents. revdep-rebuild reimplementation by Carl Lucian Poston mentored by Marius Mauch (genone@gentoo.org) Carl is going to be re-implementing the revdep-rebuild utility. He's =20 planing on using the set framework and linkage information in =20 portage-2.2 to improve on revdep-rebuild's current behavior. At the =20 end of the project, the tool will model a system's dependencies as a =20 dependency graph and resolve all dynamic linker errors by repairing =20 broken libraries and packages. Communicating The community bonding period begins now and the purpose is to =20= familiarize you with our general community practices. It is *very =20 important* that you are in constant touch with your mentor throughout =20= the duration of the program. There are several channels of =20 communication that Gentoo developers use, and we'll go through the =20 most important of them: - Mailing Lists: gentoo-dev is the list where technical = discussions =20 related to Gentoo not suited for more specific lists takes place. We =20 highly recommend you subscribe to this list and lurk for a while to =20 get a feel of what kind of questions are asked on it. We would also =20 like you to subscribe to the gentoo-soc mailing list in order to =20 receive important announcements related to the program. In addition to =20= these two lists, your mentor might also want you to subscribe to =20 another list, depending on your project. A complete listing of all our =20= mailing lists, along with information on how you can subscribe to them =20= is available on: http://www.gentoo.org/main/en/lists.xml The primary language of communication on most of our lists is =20= English, but a lot of us are not native English speakers, so don't be =20= ashamed of writing 'bad english'. It is usually sufficient if you are =20= able to communicate your idea and everyone understands what you are =20 trying to say. Also, don't be afraid of asking 'stupid questions', a =20 lot of you are new to the world of open source software, and we are =20 aware of that. We're here to help. When starting a new thread on a mailing list, send a new email = to the =20 list - don't reply to an existing thread. Also, you are expected to =20 send plain text email, no HTML! Learn how to quote relevant portions =20 when replying to a thread. This web page might help: = http://www.netmeister.org/news/learn2quote.html - IRC: A lot of Gentoo developers hang out in several channels = on the =20 Freenode IRC channel. IRC is generally used for real-time =20 conversations and is very useful when you want a quick reply. The =20 starting point for you should be the #gentoo-soc channel; your mentor =20= will tell you which other channels you are recommended to join. If you =20= are new to IRC, this might = help:http://www.irchelp.org/irchelp/irctutorial.html We would like to point out that IRC is a highly informal = environment, =20 and we don't recommend you make important decisions there; unless =20 you've scheduled a meeting with your mentor to discuss them. Even if =20 you do, we recommend you archive that decision by other means (a post =20= to a list, blog post) since most IRC channels are not logged. Also, =20 some developers don't use IRC at all but they may have something =20 valuable to say. - Bugzilla: Gentoo maintains a bug database on: http://=20 bugs.gentoo.org/. We recommend you sign up for an account there. =20 Depending on your project, your mentor may expect you to file bugs and =20= follow them. Whenever your project involves changes to code maintained =20= by existing Gentoo developers, you will usually have to file a bug and =20= follow it up. Your mentor will tell you whether or not you will be =20 using Bugzilla, and if yes, to what extent. - Blogs: A lot of developers use blogs to communicate with the =20= community at large. We recommend you read posts on Planet Gentoo = (http://planet.gentoo.org/=20 ) and add the feed to your reader. We also highly recommend that you =20 get a blog for yourself (if you already don't have one), and use it to =20= write anything relevant to your project under a category such as =20 'soc08' or 'gentoo'. We will be aggregating your blogs on our Planet =20 for the entire Gentoo community to read. Code Management - Gentoo uses a mix of CVS, SVN and Git internally. We recommend = you =20 use an external code hosting service to help manage your code. Some of =20= the popular ones are: http://code.google.com/hosting/(SVN), = http://sourceforge.net/=20 (CVS/SVN) and http://repo.or.cz/ (Git). One of the explicit aims of =20= the Community Bonding period is to get you upto speed with the version =20= control system you will be working with. Please contact your mentor =20 for help *before* signing up with a particular service. In some cases, =20= you may be expected to work on an existing repository - again - =20 contact your mentor for specifics. Progress Reports - We will be expecting weekly progress reports from each of you = at =20 the very least. Feel free to report more often! Your mentor will tell =20= you his preferred method of communication, but you must also post your =20= weekly progress reports to the gentoo-soc mailing list, as well as on =20= your blog for all to see. Make sure that you inform your mentor well =20 in advance if you plan to be missing for a week or more (vacation, =20 exams etc.) We understand that you have a student life to attend to in =20= parallel, but if you are missing for more than a week without reason, =20= we will be forced to disqualify you from the program. Questions - Your mentor is the primary contact for any questions = pertaining to =20 the program, technical or not. However, it is possible that a mentor =20 may be unreachable for sometime due to personal reasons or otherwise. =20= It is *extremely* important that you immediately notify our =20 organization administrators in the event that your mentor is =20 unavailable for more than 3 days. The administrator will immediately =20 look into the issue and assign a new mentor, if required. Since all of =20= us are from various cultures around the world, it is also possible =20 that you and your mentor may not "get along" very well. Please do =20 contact our organization administrators to discuss any such issues: Alec Warner: antarus@gentoo.org Grant Goodyear: g2boojum@gentoo.org Joshua Jackson: tsunam@gentoo.org We're looking forward to a great summer with all of you, and hope that =20= all 6 projects are successful. Please don't hesitate to use any of the =20= mentioned communication channels if you have a question or doubt. All the best! -- The GSoC Mentors and Admins for Gentoo Summer of Code 2008= -- gentoo-soc@lists.gentoo.org mailing list