Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: gdb ml <gdb@sourceware.org>
Subject: google summer of code
Date: Thu, 26 Feb 2009 14:25:00 -0000	[thread overview]
Message-ID: <1235658320.5890.18.camel@localhost.localdomain> (raw)

Hi,

I was wondering whether we want to participate in the Google Summer of
Code. The application period for mentoring organizations is from March 9
until March 13th, so now is a good time to decide if it will be
beneficial for us.

I think two benefits that we get from the program are: 1. possibility of
attracting new gdb developers and 2. a helping hand for features we want
to develop.

There are some disadvantages too. From what I read, the main problem is
that mentoring a student takes some time and effort. From the GSoC
Mentors Wiki:

"However talented the students are who you may select, they will require
significant attention from your developers, so release schedules and the
desire of your community to be supportive are important considerations.

Many organizations have found great rewards in mentoring, but most agree
that they underestimated the amount of time that mentoring requires.

As a potential administrator you should also consider that you will be
responsible for getting reports and forms in to the GSoC website on
time. You should make sure that your potential mentors realize that they
will need to take time to evaluate students at the mid and final points
of the 12 week period.

Failure to meet the reporting requirements or mentoring requirements of
GSoC is a serious infraction, and reflects poorly on your organization.
If you have a big release coming out during the summer that will require
all hands, you may wish to reconsider applying."

We have some ideas for projects that a student could implement in:

http://sourceware.org/gdb/wiki/ProjectIdeas

Some that may be worth considering for this:

1. Help with Python scripting support;
2. Help with reversible debugging (not sure if teawater and Michael need
a helping hand there);
3. Support pipes in the run command (this may be too small for a GSoC);
4. Support tracepoints in gdbserver.

There may be some wishlist bugs in the bugzilla that we could lump
together with 3. to keep someone busy for the summer...

Some pointers about the GSoC:

Main page: http://code.google.com/soc/
FAQ: http://code.google.com/opensource/gsoc/2009/faqs.html
Mentors Wiki: http://gsoc-wiki.osuosl.org/index.php/Main_Page

-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


             reply	other threads:[~2009-02-26 14:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 14:25 Thiago Jung Bauermann [this message]
2009-02-26 17:34 ` Joel Brobecker
2009-02-26 21:55   ` Thiago Jung Bauermann
2009-02-26 23:35     ` Joel Brobecker
2009-02-26 18:18 ` Tom Tromey
2009-02-27  2:27 ` teawater
2009-03-08  6:27   ` Thiago Jung Bauermann
2009-03-08  6:52     ` teawater
2009-02-27  8:41 ` Oğuz Kayral
2009-03-05  6:05   ` Thiago Jung Bauermann
2015-02-16 17:14 Google Summer of Code Joel Sherrill
2015-02-16 18:36 ` Jose E. Marchesi
2015-02-16 20:04   ` Joel Sherrill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1235658320.5890.18.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox