From: "André Walker" <andre@andrewalker.net>
To: Andrew Sayers <andrew-git@pileofstuff.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: GSoC mentors for Git.pm
Date: Sun, 01 Apr 2012 20:43:39 -0300 [thread overview]
Message-ID: <4F78E82B.4080801@andrewalker.net> (raw)
In-Reply-To: <4F78D4F5.4020603@pileofstuff.org>
On 04/01/2012 07:21 PM, Andrew Sayers wrote:
> I'd be interested in doing what I can to help, but I'm not in a position
> to put myself up as a full mentor. The good news is that I've got
> several years of Perl and JS experience under my belt, and am quite used
> to finding where people are stuck and nudging them along. The bad news
> is that I know next to nothing about git internals or about XS (which
> I'd expect to feature heavily in a new Git.pm). I'm also settling in to
> a new job, so can't give strong guarantees about availability - for
> example, I'm pretty sure IRC access from work isn't going to happen, and
> have no idea what the olympics will do to my commute in the summer.
>
> If Jakub needs some kind of teaching assistant to help with code review
> and firming questions up then I'd be happy to help. But if it needs to
> be someone who can infuse a strong vision for the end result then you're
> better off looking elsewhere.
Well, this sounds great, at least to me. Jakub will probably know better
how and if you're fit as a mentor. From what I can tell, specially if
there is more than one mentor for a project, you wouldn't have to spend
more than 5 hours a week on it. Probably even less. And I think the Perl
+ JS experience is good enough for it. Maybe you'd be more fit for the
JavaScript framework in gitweb project?
prev parent reply other threads:[~2012-04-01 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 19:53 GSoC mentors for Git.pm André Walker
2012-04-01 22:21 ` Andrew Sayers
2012-04-01 23:43 ` André Walker [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=4F78E82B.4080801@andrewalker.net \
--to=andre@andrewalker.net \
--cc=andrew-git@pileofstuff.org \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.