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: GDB application for the Google Summer of Code 2009
Date: Sun, 08 Mar 2009 06:37:00 -0000	[thread overview]
Message-ID: <1236494222.9279.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20090305185950.GK3699@adacore.com>

Hi Joel,

El jue, 05-03-2009 a las 10:59 -0800, Joel Brobecker escribió:
> > http://sourceware.org/gdb/wiki/SummerOfCode2009/Proposal
> 
> I had a look at the page. Looks fine for the questions you answered.
> No comment on the FIXMEs. I'm not sure what they mean about the
> "backup organization adminstrator"...

"An organization administrator oversees the overall progress of a
mentoring organization and its students throughout the program.
Organization administrators will have different responsibilities
depending on the organization, but at the very least they will need to:

     1. Submit the organization's program application to Google; 
     2. Act as the main point of contact between Google and the
        organization; 
     3. Respond to any inquiries from Google within 48 hours; 
     4. Assign a backup mentor should a mentor be unable to work with a
        student; 
     5. Ensure all program evaluations are completed on time, on or
        before the deadlines."

So we need to have one of those, and one as backup in case the
administrator has to step down for some reason.

Now is a good time to discuss who should have this role. For Google, it
could be anyone. But maybe in the GDB-side you want someone who is a
global maintainer, for instance? If not, I can volunteer.

> > http://sourceware.org/gdb/wiki/SummerOfCode2009/Ideas
> 
> A couple of suggestions:
> 
>   - I think we should mention the reverse debugging project only
>     it teawater is willing to get involved, if not mentor someone.
>     Do we expect this to be a large project? Doesn't feel like it.
>     Perhaps this should be included as part of the "bug-squashing-fest"
>     idea?

Indeed. I moved it under the bug-squashing fest. If teawater or Michael
won't be able to mentor, I'll remove it.

>   - For the "fix bugs in bugzilla" idea, perhaps we should include
>     a few examples of issues that we'd like to work on. It doesn't
>     have to be bugs, it could be code cleanup, etc.  I think some
>     examples might help create interest.

Good idea. I did just that now.

Thanks for your input!
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


  reply	other threads:[~2009-03-08  6:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05  5:41 Thiago Jung Bauermann
2009-03-05 18:59 ` Joel Brobecker
2009-03-08  6:37   ` Thiago Jung Bauermann [this message]
2009-03-09 18:52     ` Joel Brobecker
2009-03-09 19:49       ` Tom Tromey

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=1236494222.9279.18.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