From: Lea Wiemann <lewiemann@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Summer of Code 2008 Midterm Summary
Date: Tue, 12 Aug 2008 17:25:25 +0200 [thread overview]
Message-ID: <48A1AB65.2080809@gmail.com> (raw)
In-Reply-To: <20080726232743.GA16870@spearce.org>
I know I'm 2 weeks late ;-), but here are some comments (I'm a GSoC
student working on gitweb caching):
Shawn O. Pearce wrote:
> Q: How much time have you spent per week interacting with your mentor
>
> All of our students (except 1) said 0-5 hours per week [...].
> Nearly all of the mentors on the other hand chose 6-10 hours
Maybe mentors tended to count public interaction (on the list), and
students tended not to (or to underestimate how long it takes to write
email).
> In terms of community building this question's answers seem to
> suggest we need to try harder to make our students included,
That could include making sure that all students are comfortable with
IRC (which I've found very helpful), and discouraging taking discussion
off the main list (like it happened with GitTorrent).
> Q: Do you feel that you are on track to complete your project?
>
> I'm not sure if this is good or bad. 3 students (50%!) are
> ahead of schedule, 1 is on schedule, and 2 are behind.
I think it's actually fine, since this is mostly a function of how
optimistic your initial plan was. I picked "ahead" because I got
through faster than I originally estimated, but it simply means I can
implement some 'optional' features.
> [Since 3 students are ahead] I wonder if as mentors we didn't
> demand enough of our students?
I'd guess the opposite is true -- demanding more (as long as you don't
hit the 'overwhelm' effect), if anything, tends to make me stay on track
better. E.g. last year I was 'behind schedule', and part of the reason
was that I had to balance GSoC and life and my mentor didn't kick my
butt quite hard enough. ;-)
-- Lea
prev parent reply other threads:[~2008-08-12 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 23:27 Summer of Code 2008 Midterm Summary Shawn O. Pearce
2008-08-12 15:25 ` Lea Wiemann [this message]
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=48A1AB65.2080809@gmail.com \
--to=lewiemann@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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;
as well as URLs for NNTP newsgroup(s).