Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb ml <gdb@sourceware.org>
Subject: Re: google summer of code
Date: Thu, 26 Feb 2009 21:55:00 -0000	[thread overview]
Message-ID: <1235685320.5890.38.camel@localhost.localdomain> (raw)
In-Reply-To: <20090226173438.GA3632@adacore.com>

El jue, 26-02-2009 a las 09:34 -0800, Joel Brobecker escribió:
> Hey Thiago,
> 
> Nice initiative :)

Thanks!

> > 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 help is beneficial to the project, but only if we know we have
> GMs available for review, or at least Area Maintainers for the projects
> that we are considering entering...

Indeed. So we can discuss project ideas, and then evaluate this point.

> > 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:
> 
> I agree. I just tutored someone whom we contracted out to give us
> a hand finishing one internal project (which was not GDB, but it was
> something more approachable in a short amount of time), and I sometimes
> felt sucked into the project. This should definitely be weighed in
> anyone's decision to mentor someone.

I'll probably volunteer to mentor someone. I just want to learn a bit
more about what's involved, and writeups from people who did it in the
past.

> > 1. Help with Python scripting support;
> 
> To me, this would be a very promising project because:
>   . The project is very exciting (I think)
>   . We have active developers
>   . Reviews seem to be done very quickly.

Agreed!

> Note that it would be nice if the project was focusing on the FSF GDB,
> but if it makes things simpler for whoever submits an entry and/or
> mentors the project, it's fine with me if the project gets attached
> to Archer, for instance. This decision can only be at the discretion
> of the people who spend the effort on this project, after all...

At least for the Python support, IMHO we could use the Archer repo while
the student is working on it, and then have a requirement of having the
feature submitted and accepted upstream for the project to be considered
finished.
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


  reply	other threads:[~2009-02-26 21:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 14:25 Thiago Jung Bauermann
2009-02-26 17:34 ` Joel Brobecker
2009-02-26 21:55   ` Thiago Jung Bauermann [this message]
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=1235685320.5890.38.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=brobecker@adacore.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