[gentoo-soc] Welcome GSoC Students!

[gentoo-soc] Welcome GSoC Students!

[Anant Narayanan]

Welcome to Gentoo's edition of the Google Summer of Code, and  
congratulations on your selection! To get you started, here's some  
general information. This email should be followed by another email  
from your mentor giving you more specific details. This year, you'll  
be working on 1 of 6 projects:

Using Gentoo, Seed Linux and Catalyst to provide easy access to a  
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  
creating and maintaining Beowulf clustering solutions based on Gentoo  
easier for end-users and system administrators. This will ultimately  
help in building machines for applications such as high performance  
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  
Gentoo developers to utilize remote machines for queuing "jobs", where  
"jobs" are simply a sequence of steps that can be defined by the  
developers. The results will then be sent back to them when they are  
completed. Some of the use cases for such a system are: checking for  
breakage on new versions of a package, verifying dependencies of a  
package and arch testing.

Implement OpenPAM compatible modules for Linux
	by Serafeim Mellos
	mentored by Diego Pettenò (flameeyes@gentoo.org)
Serafeim is going to write a set of PAM modules (specifically  
pam_unix, pam_securetty, pam_shells, pam_wheel, pam_nologin and  
others, if time permits) using the OpenPAM library. This would enable  
users to choose between OpenPAM and the existing Linux-PAM  
implementations and offer greater flexibility, in the true spirit of  
Gentoo.

GNAP Love (embedded framework enhancements)
	by Vít Vomáčko
	mentored by Andrey Falko (andrey@afalko.net)
Vit is going to be improving the general state of Gentoo/GNAP this  
summer. Some of the tasks he hopes to complete are: supporting more  
platforms, make it easier for developers to write extensions, unionfs  
and live upgrade support, catalyst related bug fixes and changes,  
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  
bunch of features such as collaborative editing, UI spruce-ups, easier  
deployment and rewrites of certain parts of the backend. His ultimate  
goal is to make Beacon a really competitive alternative for developers  
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  
planing on using the set framework and linkage information in  
portage-2.2 to improve on revdep-rebuild's current behavior. At the  
end of the project, the tool will model a system's dependencies as a  
dependency graph and resolve all dynamic linker errors by repairing  
broken libraries and packages.

Communicating
	The community bonding period begins now and the purpose is to  
familiarize you with our general community practices. It is *very  
important* that you are in constant touch with your mentor throughout  
the duration of the program. There are several channels of  
communication that Gentoo developers use, and we'll go through the  
most important of them:

	- Mailing Lists: gentoo-dev is the list where technical discussions  
related to Gentoo not suited for more specific lists takes place. We  
highly recommend you subscribe to this list and lurk for a while to  
get a feel of what kind of questions are asked on it. We would also  
like you to subscribe to the gentoo-soc mailing list in order to  
receive important announcements related to the program. In addition to  
these two lists, your mentor might also want you to subscribe to  
another list, depending on your project. A complete listing of all our  
mailing lists, along with information on how you can subscribe to them  
is available on: http://www.gentoo.org/main/en/lists.xml

	The primary language of communication on most of our lists is  
English, but a lot of us are not native English speakers, so don't be  
ashamed of writing 'bad english'. It is usually sufficient if you are  
able to communicate your idea and everyone understands what you are  
trying to say. Also, don't be afraid of asking 'stupid questions', a  
lot of you are new to the world of open source software, and we are  
aware of that. We're here to help.

	When starting a new thread on a mailing list, send a new email to the  
list - don't reply to an existing thread. Also, you are expected to  
send plain text email, no HTML! Learn how to quote relevant portions  
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  
Freenode IRC channel. IRC is generally used for real-time  
conversations and is very useful when you want a quick reply. The  
starting point for you should be the #gentoo-soc channel; your mentor  
will tell you which other channels you are recommended to join. If you  
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,  
and we don't recommend you make important decisions there; unless  
you've scheduled a meeting with your mentor to discuss them. Even if  
you do, we recommend you archive that decision by other means (a post  
to a list, blog post) since most IRC channels are not logged. Also,  
some developers don't use IRC at all but they may have something  
valuable to say.

	- Bugzilla: Gentoo maintains a bug database on: http:// 
bugs.gentoo.org/. We recommend you sign up for an account there.  
Depending on your project, your mentor may expect you to file bugs and  
follow them. Whenever your project involves changes to code maintained  
by existing Gentoo developers, you will usually have to file a bug and  
follow it up. Your mentor will tell you whether or not you will be  
using Bugzilla, and if yes, to what extent.

	- Blogs: A lot of developers use blogs to communicate with the  
community at large. We recommend you read posts on Planet Gentoo (http://planet.gentoo.org/ 
) and add the feed to your reader. We also highly recommend that you  
get a blog for yourself (if you already don't have one), and use it to  
write anything relevant to your project under a category such as  
'soc08' or 'gentoo'. We will be aggregating your blogs on our Planet  
for the entire Gentoo community to read.

Code Management
	- Gentoo uses a mix of CVS, SVN and Git internally. We recommend you  
use an external code hosting service to help manage your code. Some of  
the popular ones are: http://code.google.com/hosting/(SVN), http://sourceforge.net/ 
  (CVS/SVN) and http://repo.or.cz/ (Git). One of the explicit aims of  
the Community Bonding period is to get you upto speed with the version  
control system you will be working with. Please contact your mentor  
for help *before* signing up with a particular service. In some cases,  
you may be expected to work on an existing repository - again -  
contact your mentor for specifics.

Progress Reports
	- We will be expecting weekly progress reports from each of you at  
the very least. Feel free to report more often! Your mentor will tell  
you his preferred method of communication, but you must also post your  
weekly progress reports to the gentoo-soc mailing list, as well as on  
your blog for all to see. Make sure that you inform your mentor well  
in advance if you plan to be missing for a week or more (vacation,  
exams etc.) We understand that you have a student life to attend to in  
parallel, but if you are missing for more than a week without reason,  
we will be forced to disqualify you from the program.

Questions
	- Your mentor is the primary contact for any questions pertaining to  
the program, technical or not. However, it is possible that a mentor  
may be unreachable for sometime due to personal reasons or otherwise.  
It is *extremely* important that you immediately notify our  
organization administrators in the event that your mentor is  
unavailable for more than 3 days. The administrator will immediately  
look into the issue and assign a new mentor, if required. Since all of  
us are from various cultures around the world, it is also possible  
that you and your mentor may not "get along" very well. Please do  
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  
all 6 projects are successful. Please don't hesitate to use any of the  
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

Re: [gentoo-soc] Welcome GSoC Students!

[Nirbheek Chauhan]

On Tue, Apr 22, 2008 at 11:33 PM, Anant Narayanan <anant@gentoo.org> wrote:
[snip an awesome project]

>  Automate it All
>         by Nirbheek Chauhan

It's "Automate it All"! =P
The quotes are important. =)

[snip other awesome projects]

[snip some great advice]


>         - Blogs: A lot of developers use blogs to communicate with the
> community at large. We recommend you read posts on Planet Gentoo
> (http://planet.gentoo.org/) and add the feed to your reader. We also highly
> recommend that you get a blog for yourself (if you already don't have one),
> and use it to write anything relevant to your project under a category such
> as 'soc08' or 'gentoo'. We will be aggregating your blogs on our Planet for
> the entire Gentoo community to read.

Besides planet gentoo, there's also http://planet-soc.com -- the
official GSoC planet :)

>
>  Code Management
>         - Gentoo uses a mix of CVS, SVN and Git internally. We recommend you
> use an external code hosting service to help manage your code. Some of the
> popular ones are: http://code.google.com/hosting/(SVN),
> http://sourceforge.net/ (CVS/SVN) and http://repo.or.cz/ (Git).

Using external code hosting services makes keeping track of all the
Gentoo projects painful at the very least. Some people will use
code.google, others sf, launchpad, etc etc and one has to run around
between all these websites to access the projects.

So to make things easier for the students, mentors, and those who are
interested in the code, Redmine has been setup at
http://soc.gentooexperimental.org/ (hosting courtesy bonsakitten) for
Gentoo SoC project management.

Redmine was chosen over Trac for the following reasons:

1. Hosting multiple projects is trivial with Redmine compared to Trac
2. Redmine is *simple*.
3. Redmine doesn't provide inbuilt source code management, and instead
can "watch" any repository you want. This makes managing projects
which already have an exisiting repostory (such as portage for the
revdep-rebuild project) very easily
4. Redmine provides a wiki, a forum, a bug tracker, release cycle,
calendar for planning, fancy charts for stats, and will provide a
mailing list in a future release.

Redmine can manage bzr, svn, cvs, git, darcs, and mercurial repositories

bzr, svn, and git repository management will be provided on the same
server for projects that need it.

>  One of the
> explicit aims of the Community Bonding period is to get you upto speed with
> the version control system you will be working with. Please contact your
> mentor for help *before* signing up with a particular service. In some
> cases, you may be expected to work on an existing repository - again -
> contact your mentor for specifics.

[snip more great advice]

>
>         Alec Warner: antarus@gentoo.org
>         Grant Goodyear: g2boojum@gentoo.org
>         Joshua Jackson: tsunam@gentoo.org

What do the powers that be have to say about soc.ge.o? Can we have it
as the official project management place for Gentoo SoC projects? :-)

If so, Anant might want to add this to the GSoC section in this month's GMN ;-)


-- 
~Nirbheek Chauhan
-- 
gentoo-soc@lists.gentoo.org mailing list

Re: [gentoo-soc] Welcome GSoC Students!

[Alec Warner]

grr, sent as wrong sender again...

On Wed, Apr 23, 2008 at 1:57 PM, Alec Warner <antarus@scriptkitty.com> wrote:
> On Wed, Apr 23, 2008 at 9:58 AM, Nirbheek Chauhan
>  <nirbheek.chauhan@gmail.com> wrote:
>  > On Tue, Apr 22, 2008 at 11:33 PM, Anant Narayanan <anant@gentoo.org> wrote:
>  >  [snip an awesome project]
>  >
>  >
>  >  >  Automate it All
>  >  >         by Nirbheek Chauhan
>  >
>  >  It's "Automate it All"! =P
>  >  The quotes are important. =)
>  >
>  >  [snip other awesome projects]
>  >
>  >  [snip some great advice]
>  >
>  >
>  >
>  >  >         - Blogs: A lot of developers use blogs to communicate with the
>  >  > community at large. We recommend you read posts on Planet Gentoo
>  >  > (http://planet.gentoo.org/) and add the feed to your reader. We also highly
>  >  > recommend that you get a blog for yourself (if you already don't have one),
>  >  > and use it to write anything relevant to your project under a category such
>  >  > as 'soc08' or 'gentoo'. We will be aggregating your blogs on our Planet for
>  >  > the entire Gentoo community to read.
>  >
>  >  Besides planet gentoo, there's also http://planet-soc.com -- the
>  >  official GSoC planet :)
>
>  I encourage you to sign up for both.  You can contant
>  planet@gentoo.org for us and I'm sure planet-soc has some signup
>  somewhere (the le' awesome webchick is running it).
>
>
>  >
>  >
>  >  >
>  >  >  Code Management
>  >  >         - Gentoo uses a mix of CVS, SVN and Git internally. We recommend you
>  >  > use an external code hosting service to help manage your code. Some of the
>  >  > popular ones are: http://code.google.com/hosting/(SVN),
>  >  > http://sourceforge.net/ (CVS/SVN) and http://repo.or.cz/ (Git).
>  >
>  >  Using external code hosting services makes keeping track of all the
>  >  Gentoo projects painful at the very least. Some people will use
>  >  code.google, others sf, launchpad, etc etc and one has to run around
>  >  between all these websites to access the projects.
>
>  Painful at the very least eh?  I disagree ;)
>
>  I expect students to use whatever hosting service they choose provided
>  it is up enough (ie hosting it on your workstation at home is probably
>  not good enough).
>
>  I expect students to post a URL to their code somewhere so people can
>  find it easily (maybe we can update the soc webpage...).
>
>  You may want to visit the 'official' unofficial soc wiki as well:
>
>  13:54 <@antarus|work> !wiki
>  13:54 <+socinfo> "wiki" is located at http://socwiki.natulte.net/ . For
>                  accepted SoC students only, see the student list for access
>                  information!
>
>
>  >
>  >  So to make things easier for the students, mentors, and those who are
>  >  interested in the code, Redmine has been setup at
>  >  http://soc.gentooexperimental.org/ (hosting courtesy bonsakitten) for
>  >  Gentoo SoC project management.
>  >
>  >  Redmine was chosen over Trac for the following reasons:
>  >
>  >  1. Hosting multiple projects is trivial with Redmine compared to Trac
>  >  2. Redmine is *simple*.
>  >  3. Redmine doesn't provide inbuilt source code management, and instead
>  >  can "watch" any repository you want. This makes managing projects
>  >  which already have an exisiting repostory (such as portage for the
>  >  revdep-rebuild project) very easily
>  >  4. Redmine provides a wiki, a forum, a bug tracker, release cycle,
>  >  calendar for planning, fancy charts for stats, and will provide a
>  >  mailing list in a future release.
>  >
>  >  Redmine can manage bzr, svn, cvs, git, darcs, and mercurial repositories
>  >
>  >  bzr, svn, and git repository management will be provided on the same
>  >  server for projects that need it.
>  >
>
>  Thanks go to Patrick and Co. for getting this set up.  I want to
>  stress again that while it is utterly awesome that it is offered, you
>  don't have to use it.
>
>
>  >
>  >  >  One of the
>  >  > explicit aims of the Community Bonding period is to get you upto speed with
>  >  > the version control system you will be working with. Please contact your
>  >  > mentor for help *before* signing up with a particular service. In some
>  >  > cases, you may be expected to work on an existing repository - again -
>  >  > contact your mentor for specifics.
>  >
>  >  [snip more great advice]
>  >
>  >
>  >  >
>  >  >         Alec Warner: antarus@gentoo.org
>  >  >         Grant Goodyear: g2boojum@gentoo.org
>  >  >         Joshua Jackson: tsunam@gentoo.org
>  >
>  >  What do the powers that be have to say about soc.ge.o? Can we have it
>  >  as the official project management place for Gentoo SoC projects? :-)
>
>  I don't think an 'official' place is necessary but feel free to try to
>  convince me otherwise.
>
>  -Alec
>
>
>
>  >
>  >  If so, Anant might want to add this to the GSoC section in this month's GMN ;-)
>  >
>  >
>  >  --
>  >  ~Nirbheek Chauhan
>  >  --
>  >
>  >
>  > gentoo-soc@lists.gentoo.org mailing list
>  >
>  >
>
-- 
gentoo-soc@lists.gentoo.org mailing list

Re: [gentoo-soc] Welcome GSoC Students!

[Nirbheek Chauhan]

On Thu, Apr 24, 2008 at 2:27 AM, Alec Warner <antarus@gentoo.org> wrote:
> grr, sent as wrong sender again...
>
>  On Wed, Apr 23, 2008 at 1:57 PM, Alec Warner <antarus@scriptkitty.com> wrote:
>
> > On Wed, Apr 23, 2008 at 9:58 AM, Nirbheek Chauhan
>  >  <nirbheek.chauhan@gmail.com> wrote:
>  >  >  Besides planet gentoo, there's also http://planet-soc.com -- the
>  >  >  official GSoC planet :)
>  >
>  >  I encourage you to sign up for both.  You can contant
>  >  planet@gentoo.org for us and I'm sure planet-soc has some signup
>  >  somewhere (the le' awesome webchick is running it).

That's what I meant -- I was recommending other people to sign up for
that as well


>  >  >  Using external code hosting services makes keeping track of all the
>  >  >  Gentoo projects painful at the very least. Some people will use
>  >  >  code.google, others sf, launchpad, etc etc and one has to run around
>  >  >  between all these websites to access the projects.
>  >
>  >  Painful at the very least eh?  I disagree ;)
>  >
>  >  I expect students to use whatever hosting service they choose provided
>  >  it is up enough (ie hosting it on your workstation at home is probably
>  >  not good enough).

Hosting for source code, sure, anywhere. But I don't expect people to
setup their own Trac ;)

>  >
>  >  I expect students to post a URL to their code somewhere so people can
>  >  find it easily (maybe we can update the soc webpage...).

That was what drove me to getting this setup -- say I want to find
2007's SoC projects;  I google for "gentoo 2007 soc projects", I get
several blogs (about them, not of them), and a link to
http://www.gentoo.org/proj/en/userrel/soc/archives/2007.xml which
doesn't link to any code.

At this point, I've effectively hit a dead end in my search.

I think there should be one single place where you can be *guaranteed*
to *either* find all the projects, *or* find links to where they are
actually hosted. What I suggest is the following:

1. People be given the option to use soc.ge.o(redmine) for their work
2. Redmine doesn't provide inbuilt SCM, so they can host their source
code anywhere (soc.ge.o if they want)
3. If they don't want to use soc.ge.o/Redmine at all, they can just
create a dummy project on soc.ge.o which has a link in the project
summary to the place where the actual development is taking place.

This will:
a) Give people the freedom to host the work wherever they want
b) Provide a place where either the projects, or pointers to them can
be found with ease
c) The advantage of using Redmine over gentoo.org/*/soc/ is that it
can "plug into" a remote repository to show the code, generate
statistics and such

[snip]

>  >
>  >  Thanks go to Patrick and Co. for getting this set up.  I want to
>  >  stress again that while it is utterly awesome that it is offered, you
>  >  don't have to use it.

Don't use it, just list your project there :)


>  >  >  What do the powers that be have to say about soc.ge.o? Can we have it
>  >  >  as the official project management place for Gentoo SoC projects? :-)
>  >
>  >  I don't think an 'official' place is necessary but feel free to try to
>  >  convince me otherwise.

Convinced yet? ;-)


-- 
~Nirbheek Chauhan
-- 
gentoo-soc@lists.gentoo.org mailing list

Re: [gentoo-soc] Welcome GSoC Students!

[Marius Mauch]

On Tue, 22 Apr 2008 23:33:56 +0530
Anant Narayanan <anant@gentoo.org> wrote:

> Welcome to Gentoo's edition of the Google Summer of Code, and  
> congratulations on your selection! To get you started, here's some  
> general information. This email should be followed by another email  
> from your mentor giving you more specific details.

Ok, took me a bit longer than expected to get around to writing this
mail, hope that's no problem for you.
> Communicating

> 	The community bonding period begins now and the purpose is
> to familiarize you with our general community practices. It is *very  
> important* that you are in constant touch with your mentor
> throughout the duration of the program. There are several channels
> of communication that Gentoo developers use, and we'll go through
> the most important of them:
> 
> 	- Mailing Lists: gentoo-dev is the list where technical
> discussions related to Gentoo not suited for more specific lists
> takes place. We highly recommend you subscribe to this list and lurk
> for a while to get a feel of what kind of questions are asked on it.
> We would also like you to subscribe to the gentoo-soc mailing list in
> order to receive important announcements related to the program. In
> addition to these two lists, your mentor might also want you to
> subscribe to another list, depending on your project. A complete
> listing of all our mailing lists, along with information on how you
> can subscribe to them is available on:
> http://www.gentoo.org/main/en/lists.xml

For mailing lists, I'd strongly suggest you subscribe at least to
gentoo-dev, gentoo-dev-announce (to stay in touch with the general
dev community), gentoo-portage-dev (for questions regarding your
project) and gentoo-soc (for SoC related stuff). Except for gentoo-dev
they all don't have a lot of traffic, so it should require a lot of
time to follow them.

> 	- IRC: A lot of Gentoo developers hang out in several
> channels on the Freenode IRC channel. IRC is generally used for
> real-time conversations and is very useful when you want a quick
> reply. The starting point for you should be the #gentoo-soc channel;
> your mentor will tell you which other channels you are recommended to
> join.

I've seen that you already hang out in #gentoo-portage, and that's
generally also the first place if yo have any portage (or gentoolkit)
related questions. Eventually you might also look into #gentoo-dev
(moderated, let me know if you want voice in there) or #gentoo-dev-help
for ebuild or other Gentoo related questions.
Of course you can also contact me via /msg at any time.
Note that I'm often not watching my IRC client when online, so it can
take some time before you get a reply. When it's important I suggest
you also send an email, or (if it's a more generic question) ask around
on one of the IRC channels/mailing lists. As said before, I'm located
in the CEST timezone (UTC+2), though that doesn't mean much for my IRC
availability. The best time to catch me is probably between 16:00 and
22:00 UTC, but that's no guarantee (also I sometimes won't be on IRC
for a couple of days, but I'll still read email).

> 	- Bugzilla: Gentoo maintains a bug database on: http:// 
> bugs.gentoo.org/. We recommend you sign up for an account there.  
> Depending on your project, your mentor may expect you to file bugs
> and follow them. Whenever your project involves changes to code
> maintained by existing Gentoo developers, you will usually have to
> file a bug and follow it up. Your mentor will tell you whether or not
> you will be using Bugzilla, and if yes, to what extent.

While you don't have to file bugs to get your code "in", I'd suggest
that you take a close look at existing bugs regarding revdep-rebuild to
get a feeling for the problems it has. You might also want to watch the
tools-portage@gentoo.org and/or dev-portage@gentoo.org aliases in
bugzilla to get a feeling about how development is going on (that's
going to be a lot of traffic however).

> Code Management
> 	- Gentoo uses a mix of CVS, SVN and Git internally. We
> recommend you use an external code hosting service to help manage
> your code. Some of the popular ones are:
> http://code.google.com/hosting/(SVN), http://sourceforge.net/
> (CVS/SVN) and http://repo.or.cz/ (Git). One of the explicit aims of
> the Community Bonding period is to get you upto speed with the
> version control system you will be working with. Please contact your
> mentor for help *before* signing up with a particular service. In
> some cases, you may be expected to work on an existing repository -
> again - contact your mentor for specifics.

I don't really care what system or service you're going to use, as long
as it has a simple way for me to see the code (best via webinterface so
I can take a look even when not at my dev system). You're not going to
work in the portage repository for several (administrative) reasons, so
you'll have to track it via anonsvn.gentoo.org.
At the end of the project I'll expect some kind of patch that applies
against a specified (not too old) revision of the portage repository,
but that's not something to worry about now.

> Progress Reports
> 	- We will be expecting weekly progress reports from each of
> you at the very least. Feel free to report more often! Your mentor
> will tell you his preferred method of communication, but you must
> also post your weekly progress reports to the gentoo-soc mailing
> list, as well as on your blog for all to see. Make sure that you
> inform your mentor well in advance if you plan to be missing for a
> week or more (vacation, exams etc.)

For progress reports, it's sufficient if you CC me on the report to
the gentoo-soc list (I'm subscribed to the list, but a CC makes it
easier to find things later). I suggest you stick to a specific day of
the week for your progress reports, but it's no big deal if the
interval between reports varies a bit. Just if you haven't made any
reports for two weeks in a row without notification I'll start to worry.

Now for some advice regarding the early phase of your project:
- The first thing you have to do is to become very familiar with the
underlying problem as there are a lot of details there to understand. A
good starting point is the ld.so manpage to understand how the linker
works, also check bugzilla and the forums for some common problems
with revdep-rebuild. If you want to you could also take a look at the
new FEATURES=preserve-libs functionality in portage-2.2 for some code
that has a related purpose to your project, but for that you'll have to
actually dig into nasty portage code (and the current code will soon be
rewritten due to a number of conceptual problems).
- Actually read and understand revdep-rebuild (and eventually its
clones). One of the main problems you'll have to deal with are the
numerours details, corner cases and exceptions implemented there. Might
be worth to write a little spec about revdep-rebuild before you really
start coding (would also make evaluations a bit easier for me ;)
- Understand the portage subsystems you're going to use. That includes
the PackageSet interface as well as certain parts of the
portage.dbapi.vartree module (in particular the LibraryPackageMap
class, though I'm currently replacing that with a new LinkageMap class,
so you might want to wait a bit on that)

Other than that I suggest that we come together for a meeting on IRC
sometime during the next two weeks to come up with a roadmap until the
mid-term evaulations and discuss any questions you (or I) still have.
Let me know when you think would be a good time (I'm quite flexible as
long as it's between 16:00 and 0:00 UTC).

Oh, and welcome to Gentoo :)

Marius

-- 
Marius Mauch <google-soc@genone.de>
-- 
gentoo-soc@lists.gentoo.org mailing list

Re: [gentoo-soc] Welcome GSoC Students!

[Marius Mauch]

Note to self: always change the recipients before writing a longer mail.

-- 
Marius Mauch <google-soc@genone.de>
-- 
gentoo-soc@lists.gentoo.org mailing list

[gentoo-soc] Welcome, GSoC students!

[Donnie Berkholz]

Welcome to Gentoo's edition of the Google Summer of Code, and 
congratulations on your selection! We hope you're already in touch with 
your mentor and getting comfortable with the tools you need, so you can 
write code starting on day 1 of the summer. The rest of this email 
contains general information to help you be more productive this summer.

If you aren't already in touch with your mentors, this email should be 
followed by another email from your primary mentor giving you more 
specific details. This year, you'll be working on 1 of 19 projects. We 
grew more than 100% from last year, when we had 7 projects, so we're 
really excited about working with all of you this summer!

I've included a list of all of the people you'll be working with this 
summer, and their projects, at the end of this email.


Communicating
=============

The community bonding period has already begun, and the purpose is to 
familiarize you with our general community practices. It is *very 
important* that you are in constant touch with your mentor throughout 
the duration of the program. There are several channels of communication 
that Gentoo developers use, and we'll go through the most important of 
them:

Mailing Lists
-------------
gentoo-dev is the list where technical discussions related to Gentoo not
suited for more specific lists takes place. We highly recommend you
subscribe to this list and lurk for a while to get a feel of what kind
of questions are asked on it. You should already be subscribed to the
gentoo-soc mailing list, where you will receive important announcements
related to the program. In addition to these two lists, your mentor
might also want you to subscribe to another list, depending on your
project. A complete listing of all our mailing lists, along with
information on how you can subscribe to them is available on:
http://www.gentoo.org/main/en/lists.xml

The primary language of communication on most of our lists is English,
but a lot of us are not native English speakers, so don't be ashamed of
writing 'bad english'. It is usually sufficient if you are able to
communicate your idea and everyone understands what you are trying to
say. Also, don't be afraid of asking 'stupid questions' -- many of you
are new to the world of open-source software, and we are aware of that.
We're here to help.

When starting a new thread on a mailing list, send a new email to the
list -- don't reply to an existing thread. Also, you are expected to
send plain-text email, no HTML! Learn how to quote relevant portions
when replying to a thread. This web page might help:
http://www.netmeister.org/news/learn2quote.html

IRC
---
The majority of Gentoo developers hang out in several channels on the
Freenode IRC channel. IRC is generally used for real-time conversations
and is very useful when you want a quick reply. The starting point for
you should be the #gentoo-soc channel; your mentor will tell you which
other channels you are recommended to join. If you are new to IRC, this
might help: http://www.irchelp.org/irchelp/irctutorial.html

IRC is a highly informal environment, and we don't recommend you make
important decisions there unless you've scheduled a meeting with your
mentor to discuss them. Even if you do, we recommend you archive that
decision by other means (a post to a list, blog post) since most IRC
channels are not logged. Also, some developers don't use IRC at all but
they may have something valuable to say.

Bugzilla
--------
Gentoo maintains a bug database on: http://bugs.gentoo.org/. We
recommend you sign up for an account there. Depending on your project,
your mentor may expect you to file bugs and follow them. Whenever your
project involves changes to code maintained by existing Gentoo
developers, you will usually have to file a bug and follow it up. Your
mentor will tell you whether or not you will be using Bugzilla, and if
yes, to what extent.

Blogs
-----
Many developers use blogs to communicate with the community at large. We
recommend you read posts on Planet Gentoo (http://planet.gentoo.org/)
and add the feed to your reader. We also highly recommend that you get a
blog for yourself (if you already don't have one), and use it to write
anything relevant to your project under a category such as 'gsoc2010' or
'gentoo'. We will aggregate your blogs on our Planet for the entire
Gentoo community to read.


Code Management
===============

Gentoo uses a mix of CVS, SVN and Git internally. We expect you to
maintain a repository containing your code on Gentoo infrastructure,
although you may choose to actively work on the code elsewhere (for
example, Github). One of the explicit aims of the Community Bonding
period is to get you up to speed with the version control system you
will be working with. Please contact your mentor for help *before*
signing up with a particular service. In some cases, you may be expected
to work on an existing repository -- contact your mentor for specifics.

To have a repository set up, contact Robin Johnson (robbat2@gentoo.org)
and send him a public SSH key, the repository type, and the repository
name. Your mentor can help you with this.


Project Websites
================

We highly recommend having a centralized location for information about
you and your project, and Trac is an ideal way to do that. We are happy
to set up Trac instances for your project, so it has an online home
where people can go to learn more about it. This will provide you with a
homepage, a wiki, a timeline, and possibly integration with your source
code.

To have Trac set up, contact Patrick Lauer (patrick@gentoo.org) with
details about your project. The Trac instance should have the same name
as your repository, if possible. Discuss with your mentor whether Trac
is something you need.


Shell Access
============

As a GSoC student with Gentoo, you get access to one of our shell
servers. This is an ideal place to run an IRC client like irssi coupled
with screen, so that you are always available on IRC and can reconnect
from anywhere. Contact Robin Johnson (robbat2@gentoo.org) with your
public SSH key, and he will set you up with access.

If you don't already have an SSH key, you can generate one like this:
`ssh-keygen -t dsa`. Be sure to set a passphrase on your key. The
'id_dsa.pub' file is what you send to Robin.


Progress Reports
================

We expect weekly progress reports from each of you, at the very least.
Feel free to report more often! Your mentor will tell you his preferred
method of communication, but you must also post your weekly progress
reports to the gentoo-soc mailing list, as well as on your blog for all
to see. Make sure that you inform your mentor well in advance if you
plan to be missing for a week or more (vacation, exams etc.). We
understand that you have a student life to attend to in parallel, but if
you are missing for more than a week without reason, we will be forced
to disqualify you from the program.


Questions
=========

Your mentor is the primary contact for any questions pertaining to the
program, technical or not. However, it is possible that a mentor may be
unreachable for sometime due to personal reasons or otherwise. It is
*extremely* important that you immediately notify our organization
administrators in the event that your mentor is unavailable for more
than 3 days. The administrator will immediately look into the issue and
assign a new mentor, if required. Since all of us are from various
cultures around the world, it is also possible that you and your mentor
may not "get along" very well. Please do contact our organization
administrators to discuss any such issues:

        Donnie Berkholz: dberkholz@gentoo.org
        Alec Warner (backup admin): antarus@gentoo.org

As a final note, we want to remind you that this is the Summer of Code, 
and not the Summer of Project Research And Design or the Summer of 
Learning Your Programming Language And Tools. Please make sure you've 
got all the background work done by May 24 so you can spend the whole 
summer writing code.

We're looking forward to a great summer with all of you, and we hope
that all 19 projects are successful. Please don't hesitate to use any of
the mentioned communication channels if you have a question or doubt.

Have a great summer!

-- 
Thanks,
Donnie

Donnie Berkholz
Admin, Summer of Code
Gentoo Linux
Blog: http://dberkholz.wordpress.com



Here's the list of this summer's projects. Your primary mentor is first, 
and if you have secondary mentors, they're later in the list:

Improve NetworkManager integration with Gentoo
  Student: Mu Qiao
  Mentors: Robert Piasek, Arun Raghavan, Nirbheek Chauhan

Rewrite of g-pypi ebuild conversion tool
  Student: Domen Kozar
  Mentors: Jesus Rivero, Brian Harring

Ventoo - Visual Configure file editor
  Student: Christopher Harvey
  Mentor: Luis Araujo, Jesus Rivero

Improve the Octave/Matlab support.
  Student: Rafael Goncalves Martins
  Mentors: Denis Dupeyron, Sébastien Fabbro

Project Grumpy
  Student: Priit Laes
  Mentors: Mart Raudsepp, Brian Harring

Port the new distro-neutral initrd framework, Dracut, to Gentoo
  Student: Amadeusz Zolnowski
  Mentors: Lance Albertson, Eric Thibodeau

Porting Portage and its tools to DragonFly BSD.
  Student: Naohiro Aota
  Mentors: Patrick Lauer, Javier Villavicencio

Multiple Repository Support in sys-apps/portage
  Student: Otavio Pontes
  Mentors: Alec Warner, Zachary Medico, Brian Harring

Revive Kuroo
  Student: Detlev Casanova
  Mentor: Brian Dolbec

Help Gentoo Council and Recruiters by providing web based applications
  Student: Joachim Bartosik
  Mentors: Alex Legler, Petteri Raty

Gentoo-x86 QA Website
  Student: John-Patrik Nilsson
  Mentors: Brian Harring, Mart Raudsepp

"IDFetch" (Intelligent Distfile Fetcher)
  Student: Kostyantyn Ovechko
  Mentor: Robin Johnson

Portage/ebuild ability to use file-based capabilities rather than setuid
  Student: Constanze Hausner
  Mentors: Diego Elio Pettenò, Zachary Medico

Bash Programmatic and AST access
  Student: Nathan Eloe
  Mentors: Petteri Raty, Brian Harring

webapp-config rewrite
  Student: Andreas Nuesslein
  Mentor: Benedikt Boehm

Decreasing Gentoo boot time using Upstart
  Student: Oliver Schinagl
  Mentors: Steev Klimaszewski, Robin Johnson

G-CRAN
  Student: Auke Booij
  Mentor: Sébastien Fabbro

The Gentoo Council Web Application
  Student: Wei Xie
  Mentors: Hans de Graaff, Petteri Raty

G-PEAR
  Student: Wiktor W Brodlo
  Mentors: Steve Dibb, Anant Narayanan

Re: [gentoo-soc] Welcome, GSoC students!

[Mu Qiao]

[-- Attachment #1: Type: text/plain, Size: 9408 bytes --]

On 05/14/2010 11:04 PM, Donnie Berkholz wrote:
> Welcome to Gentoo's edition of the Google Summer of Code, and 
> congratulations on your selection! We hope you're already in touch with 
> your mentor and getting comfortable with the tools you need, so you can 
> write code starting on day 1 of the summer. The rest of this email 
> contains general information to help you be more productive this summer.
> 
> If you aren't already in touch with your mentors, this email should be 
> followed by another email from your primary mentor giving you more 
> specific details. This year, you'll be working on 1 of 19 projects. We 
> grew more than 100% from last year, when we had 7 projects, so we're 
> really excited about working with all of you this summer!
> 
> I've included a list of all of the people you'll be working with this 
> summer, and their projects, at the end of this email.
> 
> 
> Communicating
> =============
> 
> The community bonding period has already begun, and the purpose is to 
> familiarize you with our general community practices. It is *very 
> important* that you are in constant touch with your mentor throughout 
> the duration of the program. There are several channels of communication 
> that Gentoo developers use, and we'll go through the most important of 
> them:
> 
> Mailing Lists
> -------------
> gentoo-dev is the list where technical discussions related to Gentoo not
> suited for more specific lists takes place. We highly recommend you
> subscribe to this list and lurk for a while to get a feel of what kind
> of questions are asked on it. You should already be subscribed to the
> gentoo-soc mailing list, where you will receive important announcements
> related to the program. In addition to these two lists, your mentor
> might also want you to subscribe to another list, depending on your
> project. A complete listing of all our mailing lists, along with
> information on how you can subscribe to them is available on:
> http://www.gentoo.org/main/en/lists.xml
> 
> The primary language of communication on most of our lists is English,
> but a lot of us are not native English speakers, so don't be ashamed of
> writing 'bad english'. It is usually sufficient if you are able to
> communicate your idea and everyone understands what you are trying to
> say. Also, don't be afraid of asking 'stupid questions' -- many of you
> are new to the world of open-source software, and we are aware of that.
> We're here to help.
> 
> When starting a new thread on a mailing list, send a new email to the
> list -- don't reply to an existing thread. Also, you are expected to
> send plain-text email, no HTML! Learn how to quote relevant portions
> when replying to a thread. This web page might help:
> http://www.netmeister.org/news/learn2quote.html
> 
> IRC
> ---
> The majority of Gentoo developers hang out in several channels on the
> Freenode IRC channel. IRC is generally used for real-time conversations
> and is very useful when you want a quick reply. The starting point for
> you should be the #gentoo-soc channel; your mentor will tell you which
> other channels you are recommended to join. If you are new to IRC, this
> might help: http://www.irchelp.org/irchelp/irctutorial.html
> 
> IRC is a highly informal environment, and we don't recommend you make
> important decisions there unless you've scheduled a meeting with your
> mentor to discuss them. Even if you do, we recommend you archive that
> decision by other means (a post to a list, blog post) since most IRC
> channels are not logged. Also, some developers don't use IRC at all but
> they may have something valuable to say.
> 
> Bugzilla
> --------
> Gentoo maintains a bug database on: http://bugs.gentoo.org/. We
> recommend you sign up for an account there. Depending on your project,
> your mentor may expect you to file bugs and follow them. Whenever your
> project involves changes to code maintained by existing Gentoo
> developers, you will usually have to file a bug and follow it up. Your
> mentor will tell you whether or not you will be using Bugzilla, and if
> yes, to what extent.
> 
> Blogs
> -----
> Many developers use blogs to communicate with the community at large. We
> recommend you read posts on Planet Gentoo (http://planet.gentoo.org/)
> and add the feed to your reader. We also highly recommend that you get a
> blog for yourself (if you already don't have one), and use it to write
> anything relevant to your project under a category such as 'gsoc2010' or
> 'gentoo'. We will aggregate your blogs on our Planet for the entire
> Gentoo community to read.
> 
> 
> Code Management
> ===============
> 
> Gentoo uses a mix of CVS, SVN and Git internally. We expect you to
> maintain a repository containing your code on Gentoo infrastructure,
> although you may choose to actively work on the code elsewhere (for
> example, Github). One of the explicit aims of the Community Bonding
> period is to get you up to speed with the version control system you
> will be working with. Please contact your mentor for help *before*
> signing up with a particular service. In some cases, you may be expected
> to work on an existing repository -- contact your mentor for specifics.
> 
> To have a repository set up, contact Robin Johnson (robbat2@gentoo.org)
> and send him a public SSH key, the repository type, and the repository
> name. Your mentor can help you with this.
> 
> 
> Project Websites
> ================
> 
> We highly recommend having a centralized location for information about
> you and your project, and Trac is an ideal way to do that. We are happy
> to set up Trac instances for your project, so it has an online home
> where people can go to learn more about it. This will provide you with a
> homepage, a wiki, a timeline, and possibly integration with your source
> code.
> 
> To have Trac set up, contact Patrick Lauer (patrick@gentoo.org) with
> details about your project. The Trac instance should have the same name
> as your repository, if possible. Discuss with your mentor whether Trac
> is something you need.
> 
> 
> Shell Access
> ============
> 
> As a GSoC student with Gentoo, you get access to one of our shell
> servers. This is an ideal place to run an IRC client like irssi coupled
> with screen, so that you are always available on IRC and can reconnect
> from anywhere. Contact Robin Johnson (robbat2@gentoo.org) with your
> public SSH key, and he will set you up with access.
> 
> If you don't already have an SSH key, you can generate one like this:
> `ssh-keygen -t dsa`. Be sure to set a passphrase on your key. The
> 'id_dsa.pub' file is what you send to Robin.
> 
> 
> Progress Reports
> ================
> 
> We expect weekly progress reports from each of you, at the very least.
> Feel free to report more often! Your mentor will tell you his preferred
> method of communication, but you must also post your weekly progress
> reports to the gentoo-soc mailing list, as well as on your blog for all
> to see. Make sure that you inform your mentor well in advance if you
> plan to be missing for a week or more (vacation, exams etc.). We
> understand that you have a student life to attend to in parallel, but if
> you are missing for more than a week without reason, we will be forced
> to disqualify you from the program.
> 
> 
> Questions
> =========
> 
> Your mentor is the primary contact for any questions pertaining to the
> program, technical or not. However, it is possible that a mentor may be
> unreachable for sometime due to personal reasons or otherwise. It is
> *extremely* important that you immediately notify our organization
> administrators in the event that your mentor is unavailable for more
> than 3 days. The administrator will immediately look into the issue and
> assign a new mentor, if required. Since all of us are from various
> cultures around the world, it is also possible that you and your mentor
> may not "get along" very well. Please do contact our organization
> administrators to discuss any such issues:
> 
>         Donnie Berkholz: dberkholz@gentoo.org
>         Alec Warner (backup admin): antarus@gentoo.org
> 
> As a final note, we want to remind you that this is the Summer of Code, 
> and not the Summer of Project Research And Design or the Summer of 
> Learning Your Programming Language And Tools. Please make sure you've 
> got all the background work done by May 24 so you can spend the whole 
> summer writing code.
> 
> We're looking forward to a great summer with all of you, and we hope
> that all 19 projects are successful. Please don't hesitate to use any of
> the mentioned communication channels if you have a question or doubt.
> 
> Have a great summer!
> 

Thank you for giving such detailed information to us! I really
appreciate that Gentoo community provides us with a bunch of useful
resources.
I have questions about the Blogs and Progress reports.

1. I didn't use blog before and I think it's time for me to get one as
you suggested. Is it possible to create a blog at blogs.gentoo.org?

2. When should we start reporting the progress of our projects?

-- 
Best wishes,
Mu Qiao
GnuPG fingerprint: 92B1 B0C4 8D14 F8C4 EFA5  3ACC 30B3 0DE4 17B1 57E9


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]

Re: [gentoo-soc] Welcome, GSoC students!

[Domen Kožar]

[-- Attachment #1: Type: text/plain, Size: 726 bytes --]

Greetings to community from my side! Indeed nice overview for us
students and congratulations to Gentoo for it's growth:)

@Mu Qiao I was thinking to send email each Monday, starting in two days
with weekly report #0 

I am going to take this opportunity to help students with their
projects, with Continuous Integration tool called Hudson (for g-pypi2
the project is already located at http://hudson.fubar.si/job/g-pypi2/ ).

In other words, if you want your code to be tested after each
commit/push (and maybe some reports generated, together with
documentation), one can send me email with desired username and project
name. I will help you setup workflow and explain how everything works.


Cheers, Domen

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-soc] Welcome, GSoC students!

[Petteri Räty]

[-- Attachment #1: Type: text/plain, Size: 1679 bytes --]

On 05/14/2010 06:04 PM, Donnie Berkholz wrote:

> 
> 
> Project Websites
> ================
> 
> We highly recommend having a centralized location for information about
> you and your project, and Trac is an ideal way to do that. We are happy
> to set up Trac instances for your project, so it has an online home
> where people can go to learn more about it. This will provide you with a
> homepage, a wiki, a timeline, and possibly integration with your source
> code.
> 

For my own projects I have Agilefant running:
http://www.agilefant.org/
Agilefant supports multiple products so anyone else who wants to use it
for their GSoC project, email me GPG signed and I'll email you back
credentials encrypted with that key.

> 
> 
> Progress Reports
> ================
> 
> We expect weekly progress reports from each of you, at the very least.
> Feel free to report more often! Your mentor will tell you his preferred
> method of communication, but you must also post your weekly progress
> reports to the gentoo-soc mailing list, as well as on your blog for all
> to see. Make sure that you inform your mentor well in advance if you
> plan to be missing for a week or more (vacation, exams etc.). We
> understand that you have a student life to attend to in parallel, but if
> you are missing for more than a week without reason, we will be forced
> to disqualify you from the program.
> 

I require daily scrum emails from all my students. Feel free to take any
other points from documentation I have available at:
http://docs.google.com/leaf?id=0B_ck8Y9ixNtFNjI2NmJkMzAtN2UzZS00ODEwLThhYzUtY2FiOTdhZGViYjE3&hl=en

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

Re: [gentoo-soc] Welcome, GSoC students!

[Donnie Berkholz]

On 15:07 Sat 15 May     , Mu Qiao wrote:
> On 05/14/2010 11:04 PM, Donnie Berkholz wrote:
> > Blogs
> > -----
> > Many developers use blogs to communicate with the community at 
> > large. We recommend you read posts on Planet Gentoo 
> > (http://planet.gentoo.org/) and add the feed to your reader. We also 
> > highly recommend that you get a blog for yourself (if you already 
> > don't have one), and use it to write anything relevant to your 
> > project under a category such as 'gsoc2010' or 'gentoo'. We will 
> > aggregate your blogs on our Planet for the entire Gentoo community 
> > to read.
> 
> Thank you for giving such detailed information to us! I really 
> appreciate that Gentoo community provides us with a bunch of useful 
> resources. I have questions about the Blogs and Progress reports.

Great, thanks for asking! While we're at it, this is a good time to 
briefly mention one aspect of email etiquette. Take a look at how I 
quoted only the parts that are relevant to my reply, instead of the 
whole thing, and how I write my reply immediately after each part. This 
makes it a lot easier for people to follow the details.

> 1. I didn't use blog before and I think it's time for me to get one as
> you suggested. Is it possible to create a blog at blogs.gentoo.org?

We aren't hosting new blogs; you might want to set one up at 
wordpress.com or one of the many other blog-hosting sites. What we'll do 
is pull your content into a collection with all the other GSoC students, 
and probably a second feed shared with Gentoo developers, so that people 
who want to read about what's happening in Gentoo can follow your work.

Once you get a blog set up, you can file a bug to add your blog to our 
aggregator (Planet). The bug will get assigned to planet@gentoo.org — 
because I don't think you have privileges to assign bugs to specific 
people, you might want to ask your mentor to file it to speed things up.

> 2. When should we start reporting the progress of our projects?

No later than the end of the first week of coding. If you're already 
making progress, we'd love to hear from you!

-- 
Thanks,
Donnie

Donnie Berkholz
Admin, Summer of Code
Gentoo Linux
Blog: http://dberkholz.wordpress.com

Re: [gentoo-soc] Welcome, GSoC students!

[Donnie Berkholz]

On 19:17 Sun 16 May     , Petteri Räty wrote:
> For my own projects I have Agilefant running: 
> http://www.agilefant.org/
> 
> Agilefant supports multiple products so anyone else who wants to use 
> it for their GSoC project, email me GPG signed and I'll email you back 
> credentials encrypted with that key.

Petteri,

Could you briefly explain why anyone would want to use this, and what 
benefits it provides? Some students have asked me.

-- 
Thanks,
Donnie

Donnie Berkholz
Admin, Summer of Code
Gentoo Linux
Blog: http://dberkholz.wordpress.com

Re: [gentoo-soc] Welcome, GSoC students!

[Petteri Räty]

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

On 05/18/2010 06:28 PM, Donnie Berkholz wrote:
> On 19:17 Sun 16 May     , Petteri Räty wrote:
>> For my own projects I have Agilefant running: 
>> http://www.agilefant.org/
>>
>> Agilefant supports multiple products so anyone else who wants to use 
>> it for their GSoC project, email me GPG signed and I'll email you back 
>> credentials encrypted with that key.
> 
> Petteri,
> 
> Could you briefly explain why anyone would want to use this, and what 
> benefits it provides? Some students have asked me.
> 

There's a demo available here:
http://demo.agilefant.org/

It's a backlog management tool. You need a backlog if you want to do
something like Scrum. It can be used for personal project management but
biggest benefits come if the student is not acting as a project owner.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

Re: [gentoo-soc] Welcome, GSoC students!

[Nathan Eloe]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On May 15, 2010, at 4:45 AM, Domen Kožar wrote:

> Greetings to community from my side! Indeed nice overview for us
> students and congratulations to Gentoo for it's growth:)
> 
> @Mu Qiao I was thinking to send email each Monday, starting in two days
> with weekly report #0 
> 
> I am going to take this opportunity to help students with their
> projects, with Continuous Integration tool called Hudson (for g-pypi2
> the project is already located at http://hudson.fubar.si/job/g-pypi2/ ).
> 
> In other words, if you want your code to be tested after each
> commit/push (and maybe some reports generated, together with
> documentation), one can send me email with desired username and project
> name. I will help you setup workflow and explain how everything works.
> 
> 
> Cheers, Domen

Hello Domen
I'm interested in using Hudson for my project.  Thank you for offering such a powerful tool for development.

Project Name: libbash
Username: powerofazure

Once again, thank you for making such a tool easily available to us.

Nathan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)

iEYEARECAAYFAkv30ZwACgkQFpoRlVgtqKYauQCfaX/gtgH2+ETD0PG1/muz4plY
9IwAoJoyNQ/pOEZHbp/uYPq8QHOAeBaW
=r23I
-----END PGP SIGNATURE-----

Re: [gentoo-soc] Welcome, GSoC students!

[Christopher Harvey]

On 05/14/10 11:04, Donnie Berkholz wrote:
> 
> Project Websites
> ================
> 
> We highly recommend having a centralized location for information about
> you and your project, and Trac is an ideal way to do that. We are happy
> to set up Trac instances for your project, so it has an online home
> where people can go to learn more about it. This will provide you with a
> homepage, a wiki, a timeline, and possibly integration with your source
> code.
> 
> To have Trac set up, contact Patrick Lauer (patrick@gentoo.org) with
> details about your project. The Trac instance should have the same name
> as your repository, if possible. Discuss with your mentor whether Trac
> is something you need.
> 
I understand (from some conversations on IRC) that it is preferred that
websites go on gentoo infra. My project is a user application, and
exists only in vcs atm. It needs a website. I'd create one myself (as
others have done) but I thought I'd run it by this channel first. Is
there a place for students to host html? If not I don't mind hosting it
until gentoo finds a place. It is still a minor project after all.

-- 
My GnuPGP key at:
www.basementcode.com/public_key.txt

Re: [gentoo-soc] Welcome, GSoC students!

[Robin H. Johnson]

[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]

On Sat, May 22, 2010 at 02:05:18PM -0400, Christopher Harvey wrote:
> I understand (from some conversations on IRC) that it is preferred that
> websites go on gentoo infra. My project is a user application, and
> exists only in vcs atm. It needs a website. I'd create one myself (as
> others have done) but I thought I'd run it by this channel first. Is
> there a place for students to host html? If not I don't mind hosting it
> until gentoo finds a place. It is still a minor project after all.
For while you're students, you can create an public_html in your homedir
on the shell server, and access it as follows:
http://soc.dev.gentoo.org/~${USERNAME}/
eg:
http://soc.dev.gentoo.org/~robbat2/

Beyond that, if you have it in a repo of it's own, we can easily deploy
it elsewhere in Gentoo later in summer.
eg:
http://devmanual.gentoo.org/

However, depending on the level of integration with Gentoo, I would
suggest you focus on writing the content (plain text or Python's ReST)
and contact the documentation team to see about getting it on the main
www.gentoo.org website.

I haven't got the shell-server activated for GuideXML serving presently,
but I can if there is a demand for it.

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 330 bytes --]

Re: [gentoo-soc] Welcome, GSoC students!

[Luis Araujo]

On 05/24/2010 05:17 PM, Robin H. Johnson wrote:
> On Sat, May 22, 2010 at 02:05:18PM -0400, Christopher Harvey wrote:
>    
>> I understand (from some conversations on IRC) that it is preferred that
>> websites go on gentoo infra. My project is a user application, and
>> exists only in vcs atm. It needs a website. I'd create one myself (as
>> others have done) but I thought I'd run it by this channel first. Is
>> there a place for students to host html? If not I don't mind hosting it
>> until gentoo finds a place. It is still a minor project after all.
>>      
> For while you're students, you can create an public_html in your homedir
> on the shell server, and access it as follows:
> http://soc.dev.gentoo.org/~${USERNAME}/
> eg:
> http://soc.dev.gentoo.org/~robbat2/
>
> Beyond that, if you have it in a repo of it's own, we can easily deploy
> it elsewhere in Gentoo later in summer.
> eg:
> http://devmanual.gentoo.org/
>
> However, depending on the level of integration with Gentoo, I would
> suggest you focus on writing the content (plain text or Python's ReST)
> and contact the documentation team to see about getting it on the main
> www.gentoo.org website.
>
> I haven't got the shell-server activated for GuideXML serving presently,
> but I can if there is a demand for it.
>
>    
Hi Christopher,

Feel free to upload your web site design when you can , I am looking 
forward to it :)

Regards,

[gentoo-soc] Welcome, GSoC students!

[Donnie Berkholz]

[-- Attachment #1: Type: text/plain, Size: 11240 bytes --]

Welcome to Gentoo’s edition of the Google Summer of Code, and 
congratulations on your selection! We hope you’re already in touch with 
your mentor and getting comfortable with the tools you need, so you can 
write code starting on day 1 of the summer.

The rest of this email contains general information to help you be more 
productive this summer; please read it completely and carefully so you 
don’t miss anything critical.

If you aren’t already in touch with your mentors, this email should be 
followed by another email from your primary mentor giving you more 
specific details. This year, you’ll be working on 1 of 15 projects. 
We’re really excited about working with all of you this summer!

I included a list of all of the people you’ll be working with this
summer, and their projects, at the end of this email.


Communication
=============

The community-bonding period has already begun. Its purpose is to 
familiarize you with our general community practices and allow you to 
complete your project design so you can start coding by May 23.

It is *very important* that you are in constant touch with your mentor 
throughout the duration of the program; poor communication is one of the 
most frequent causes of failure. There are several channels of 
communication that Gentoo developers use, and we’ll go through the most 
important of them:

Mailing Lists
-------------
gentoo-dev is the list where technical discussions related to Gentoo but 
not suited for more specific lists takes place. We highly recommend you 
subscribe to this list and lurk for a while to get a feel of what kind 
of questions are asked on it.

You should already be subscribed to the gentoo-soc mailing list, where 
you will receive important announcements related to the program. In 
addition to these two lists, your mentor might also want you to 
subscribe to another list, depending on your project. A complete listing 
of all our mailing lists, along with information on how you can 
subscribe to them is available on: 
http://www.gentoo.org/main/en/lists.xml

The primary language of communication on most of our lists is English,
but many of us are not native English speakers, so don’t be ashamed of
writing “bad English” although SMS text language is typically frowned
upon (“u” instead of “you” for example). It is usually sufficient if you
are able to communicate your idea and everyone understands what you are
trying to say. Also, don’t be afraid of asking “stupid questions” — many
of you are new to the world of open-source software, and we know that.
We’re here to help.

When starting a new thread on a mailing list, send a new email to the
list — don’t reply to an existing thread. Also, you are expected to
send plain-text email, no HTML! Learn how to quote relevant portions
when replying to a thread. This web page might help:
http://www.netmeister.org/news/learn2quote.html

IRC
---
Most Gentoo developers hang out in several channels on the Freenode IRC 
channel. IRC is generally used for real-time conversations and is very 
useful when you want a quick reply. The starting point for you should be 
the #gentoo-soc channel; your mentor will tell you which other channels 
you are recommended to join. If you are new to IRC, this might help: 
http://www.irchelp.org/irchelp/irctutorial.html

IRC is a highly informal environment, and we don’t recommend you make
important decisions there unless you’ve scheduled a meeting with your
mentor to discuss them. Even if you do, we recommend you archive that
decision by other means (a post to a list, blog post) since most IRC
channels are not logged. Also, some developers don’t use IRC at all but
they may have something valuable to say.

Bugzilla
--------
Gentoo maintains a bug database at http://bugs.gentoo.org/ and you should 
sign up for an account there. Depending on your project, your mentor may 
expect you to file bugs and follow them. Whenever your project involves 
changes to code maintained by existing Gentoo developers, you will 
usually have to file a bug and follow it up. Your mentor will tell you 
whether or not you will be using Bugzilla, and if so, to what extent.

Blogs
-----
Many developers use blogs to communicate with the community at large. We 
highly recommend, but do not require, that you read posts on Planet 
Gentoo (http://planet.gentoo.org/) and add the feed to your reader. We 
also highly recommend that you get a blog for yourself (if you don’t 
already have one), and use it to write anything relevant to your project 
under a category such as “gsoc2011” or “gentoo.” We will aggregate your 
blogs on our Planet for the entire Gentoo community to read.


Code Management
===============

Gentoo uses a mix of Git, SVN, and CVS internally. We expect you to 
maintain a repository containing your code on Gentoo infrastructure. One 
of the explicit aims of the community-bonding period is to get you up to 
speed with the version-control system you will be working with. In some 
cases, you may be expected to work on an existing repository — contact 
your mentor for specifics.

To have a repository set up, contact Robin Johnson (robbat2@gentoo.org)
and send him a public SSH key, the repository type, and the repository
name. Your mentor can help you with this.


Project Websites
================

You must have a centralized, permanent location for information about 
you and your project that is hosted by Gentoo. If you're working on an 
established codebase like Portage or Porthole, you can just use its 
existing infrastructure. Otherwise, Trac is an ideal way to fulfill this 
requirement.

We are happy to set up Trac instances for your project, so it has an 
online home where people can go to learn more about it. This will 
provide you with a homepage, a wiki, a timeline, and possibly 
integration with your source code.

To have Trac set up, contact Robin Johnson (robbat2@gentoo.org) with 
details about your project. The Trac instance should have the same name 
as your repository, if possible. Discuss with your mentor whether Trac 
is something you need.


Shell Access
============

As a GSoC student with Gentoo, you get access to one of our shell
servers. This is an ideal place to run an IRC client like irssi coupled
with screen, so that you are always available on IRC and can reconnect
from anywhere. Contact Robin Johnson (robbat2@gentoo.org) with your
public SSH key, and he will set you up with access.

If you don’t already have an SSH key, you can generate one like this:
`ssh-keygen -t dsa`. Be sure to set a passphrase on your key. The
“id_dsa.pub” file is what you send to Robin.


Progress Reports
================

We expect progress reports from each of you at least once a week. Feel 
free to report more often! At the top, provide a brief summary of your 
project to remind anyone who hasn’t followed it closely and tell us 
whether it's on schedule, ahead of schedule, or behind schedule. Then 
tell us about your accomplishments, your problems, how you solved them, 
and your plans for the next week.

Your mentors will tell you their preferred method of communication, but 
you must also post your weekly progress reports to the gentoo-soc 
mailing list, as well as on your blog for all to see. Make sure that you 
inform your mentor well in advance if you plan to be missing for a week 
or more (vacation, exams etc.). We understand that you have a student 
life to attend to in parallel, but if you are missing for more than a 
week without reason, we will be forced to disqualify you from the 
program.

Gentoo's GSoC admins will also require very short surveys on a regular 
basis to help us ensure you have a great time this summer.


Questions
=========

Your mentor is the primary contact for any questions pertaining to the
program, technical or not. However, it is possible that a mentor may be
unreachable for sometime due to personal reasons or otherwise. It is
*extremely* important that you immediately notify our organization
administrators in the event that your mentor is unavailable for more
than 3 days. The administrator will immediately look into the issue and
assign a new mentor, if required. Since all of us are from various
cultures around the world, it is also possible that you and your mentor
may not “get along” very well. Please do contact our organization
administrators to discuss any such issues:

    Primary admin
        Donnie Berkholz: dberkholz@gentoo.org

    Backup admins
        Alec Warner: antarus@gentoo.org
        Leslie Hawthorn: lh@gentoo.org
        Grant Goodyear: g2boojum@gentoo.org

As a final note, we want to remind you that this is the Summer of Code, 
and not the Summer of Project Research And Design or the Summer of 
Learning Your Programming Language And Tools. Please make sure to 
complete all the background work by May 23, so you can spend the whole 
summer writing code.

We’re looking forward to a great summer with all of you, and we hope
that all 15 projects are successful. Please don’t hesitate to use any of
the mentioned communication channels if you have a question or doubt.

Have a great summer!

--
Thanks,
Donnie

Donnie Berkholz
Admin, Summer of Code
Gentoo Linux and X.Org
Blog: http://dberkholz.com



Projects
========
(Primary mentor listed first, backup mentors and co-mentors later)


libbash runtime
    Student: Mu Qiao
    Mentors: Petteri Räty
Client-server model for reporting and querying package statistics
    Student: Vikraman Choudhury
    Mentors: Alec Warner, Chris Harvey
Gentoo/Java IDE Integration
    Student: Kyle Pan
    Mentors: Serkan Kaba
Django CMS replacement for the www.gentoo.org website
    Student: Theo Chatzimichos
    Mentors: Matthew Summers, Robin Johnson
Apache Maven Integration for Gentoo EBuilds
    Student: Kasun Gajasinghe
    Mentors: Mathieu Le Marec - Pasquet, Serkan Kaba
Distfile patching support
    Student: Rafael Goncalves Martins
    Mentors: Robin Johnson, Denis Dupeyron
PMS compliance test suite
    Student: Michał Górny
    Mentors: Denis Dupeyron, Sébastien Fabbro
Gentoaster - freshly cooked Gentoo VM images, on demand
    Student: Liam McLoughlin
    Mentors: Ole Markus, Tim Harder
Rework Porthole to use the portage API
    Student: Detlev Casanova
    Mentors: Brian Dolbec
Automated benchmark suite for numerical libraries in Gentoo
    Student: Andrea Arteaga
    Mentors: Sébastien Fabbro
Glentoo
    Student: Robert Seaton
    Mentors: Anant Narayanan, Luca Barbato
Auto dependency builder
    Student: Alexander Bersenev
    Mentors: Marien Zwart
Provide Gentoo 11 LiveDVDs with Anaconda installer
    Student: Wiktor Brodlo
    Mentors: Denis Dupeyron, Luca Barbato
Help Gentoo Council by providing web based applications
    Student: Joachim Bartosik
    Mentors: Petteri Räty, Luca Barbato
Ebuild generator
    Student: Sebastian Parborg
    Mentors: Constanze Hausner, Donnie Berkholz

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-soc] Welcome, GSoC students!

[Donnie Berkholz]

[-- Attachment #1: Type: text/plain, Size: 8657 bytes --]

Welcome to Gentoo’s edition of the Google Summer of Code! We hope you’ve 
been in touch with your mentor and are already comfortable with the 
tools you need, so you're writing code today rather than doing setup 
work.

The rest of this email contains general information to help you be more 
productive this summer; please read it completely and carefully so you 
don’t miss anything critical.

This year, you’ll be working on 1 of 9 projects 
<http://www.google-melange.com/gsoc/org/google/gsoc2012/gentoo>. We’re 
really excited about working with all of you this summer!


Communication
=============

It is *very important* that you are in constant touch with your mentor 
throughout the duration of the program; poor communication is one of the 
most frequent causes of failure. There are several channels of 
communication that Gentoo developers use, and we’ll go through the most 
important of them:

Mailing Lists
-------------
gentoo-dev is the list where technical discussions related to Gentoo but 
not suited for more specific lists takes place. We highly recommend you 
subscribe to this list and lurk for a while to get a feel of what kind 
of questions are asked on it.

You should already be subscribed to the gentoo-soc mailing list, where 
you will receive important announcements related to the program. In 
addition to these two lists, your mentor might also want you to 
subscribe to another list, depending on your project. A complete listing 
of all our mailing lists, along with information on how you can 
subscribe to them is available on: 
http://www.gentoo.org/main/en/lists.xml

The primary language of communication on most of our lists is English, 
but many of us are not native English speakers, so don’t be ashamed of 
writing “bad English” although SMS text language is typically frowned 
upon (“u” instead of “you” for example). It is usually sufficient if you 
are able to communicate your idea and everyone understands what you are 
trying to say. Also, don’t be afraid of asking “stupid questions” — many 
of you are new to the world of open-source software, and we know that. 
We’re here to help.

When starting a new thread on a mailing list, send a new email to the 
list — don’t reply to an existing thread. Also, you are expected to send 
plain-text email, no HTML! Learn how to quote relevant portions when 
replying to a thread. This web page might help: 
http://www.netmeister.org/news/learn2quote.html

IRC
---
Most Gentoo developers hang out in several channels on the Freenode IRC 
channel. IRC is generally used for real-time conversations and is very 
useful when you want a quick reply. The starting point for you should be 
the #gentoo-soc channel; your mentor will tell you which other channels 
you are recommended to join. If you are new to IRC, this might help: 
http://www.irchelp.org/irchelp/irctutorial.html

IRC is a highly informal environment, and we don’t recommend you make 
important decisions there unless you’ve scheduled a meeting with your 
mentor to discuss them. Even if you do, we recommend you archive that 
decision by other means (a post to a list, blog post) since most IRC 
channels are not logged. Also, some developers don’t use IRC at all but 
they may have something valuable to say.

You should be available on IRC during your regular working hours.

Bugzilla
--------
Gentoo maintains a bug database at http://bugs.gentoo.org/ and you 
should sign up for an account there. Depending on your project, your 
mentor may expect you to file bugs and follow them. Whenever your 
project involves changes to code maintained by existing Gentoo 
developers, you will usually have to file a bug and follow it up. Your 
mentor will tell you whether or not you will be using Bugzilla, and if 
so, to what extent.

Blogs
-----
Many developers use blogs to communicate with the community at large. We 
highly recommend, but do not require, that you read posts on Planet 
Gentoo (http://planet.gentoo.org/) and add the feed to your reader. We 
also highly recommend that you get a blog for yourself (if you don’t 
already have one), and use it to write anything relevant to your project 
under a category such as “gsoc2011” or “gentoo.” We will aggregate your 
blogs on our Planet for the entire Gentoo community to read.


Code Management
===============

Gentoo uses a mix of Git, SVN, and CVS internally. We expect you to 
maintain a repository containing your code on Gentoo infrastructure, 
unless you're working on an existing project that's already hosted 
elsewhere.

Robin Johnson (robbat2@gentoo.org) has already sent out details to your 
mentors about getting repositories set up, so we don't need to go into 
that here. Contact your mentor if you need more details.


Project Websites
================

You must have a centralized, permanent location for information about 
you and your project that is hosted by Gentoo (unless you're working on 
an existing project hosted elsewhere). If you're working on an 
established codebase like Portage or Porthole, you can just use its 
existing infrastructure. Otherwise, Trac is an ideal way to fulfill this 
requirement.

We are happy to set up Trac instances for your project, so it has an
online home where people can go to learn more about it. This will
provide you with a homepage, a wiki, a timeline, and possibly
integration with your source code.

To have Trac set up, contact Robin Johnson (robbat2@gentoo.org) with
details about your project. The Trac instance should have the same name
as your repository, if possible. Discuss with your mentor whether Trac
is something you need.


Shell Access
============

As a GSoC student with Gentoo, you get access to one of our shell 
servers. This is an ideal place to run an IRC client like irssi coupled 
with screen, so that you are always available on IRC and can reconnect 
from anywhere. Talk to your mentor about this, if you aren't already set 
up.


Progress Reports
================

We expect progress reports from each of you at least once a week. Feel 
free to report more often! At the top, provide a brief summary of your 
project to remind anyone who hasn’t followed it closely and tell us 
whether it's on schedule, ahead of schedule, or behind schedule. Then 
tell us about your accomplishments, your problems, how you solved them, 
and your plans for the next week.

Your mentors will tell you their preferred method of communication, but 
you must also post your weekly progress reports to the gentoo-soc 
mailing list. Make sure that you inform your mentor well in advance if 
you plan to be missing for a week or more (vacation, exams etc.). We 
understand that you have a student life to attend to in parallel, but if 
you are missing for more than a week without reason, we will be forced 
to disqualify you from the program.

Gentoo's GSoC admins will also require very short, occasional surveys to 
help us ensure you have a great time this summer.


Questions
=========

Your mentor is the primary contact for any questions pertaining to the 
program, technical or not. However, it is possible that a mentor may be 
unreachable for sometime due to personal reasons or otherwise. It is 
*extremely* important that you immediately notify an organization 
administrator in the event that your mentor is unavailable for more than 
3 days. The administrator will immediately look into the issue and 
assign a new mentor, if required. Since all of us are from various 
cultures around the world, it is also possible that you and your mentor 
may not “get along” very well. Please do contact our organization 
administrators to discuss any such issues:

    Primary admin: Donnie Berkholz <dberkholz@gentoo.org>
    Backup admin: Leslie Hawthorn <lh@gentoo.org>

As a final note, we want to remind you that this is the Summer of Code, 
and not the Summer of Project Research And Design or the Summer of 
Learning Your Programming Language And Tools. You should already have 
completed all the background work, so you can spend the whole summer 
writing code.

We’re looking forward to a great summer with all of you, and we hope 
that all your projects are successful. Please don’t hesitate to use any 
of the mentioned communication channels if you have a question or doubt.

Have a great summer!

--
Thanks,
Donnie

Donnie Berkholz
Admin, Summer of Code
Gentoo Linux
Blog: http://dberkholz.com

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]