git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Git in Outreachy round 15?
Date: Tue, 5 Sep 2017 07:40:43 -0400	[thread overview]
Message-ID: <20170905114043.dkjczpioxvu7biw6@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqk21ddgz7.fsf@gitster.mtv.corp.google.com>

On Tue, Sep 05, 2017 at 11:19:56AM +0900, Junio C Hamano wrote:

> $6,500 is a bargain if we could guide an intern and help set the
> course to become a competent open source person.  It would be nice
> if the intern stays in our community, but I do not even mind if the
> investment follows the intern elsewhere and enrich other open source
> projects.

Agreed on all counts. I am still dotting i's and crossing t's, but I am
pretty sure I have outside funding lined up anyway, though.

> It is a different matter if our mentor pool is rich enough to give
> sufficient support and training to the intern, but if you are
> volunteering to mentor, I wouldn't have any worries.  I do agree
> with you that it would be a good idea to polish the project-ideas
> page.

We actually need to put together a "landing page". The guidelines are
at:

  https://www.outreachy.org/mentor/landing-page-requirements/

Timing-wise, the application period opens this Thursday. So I'll plan to
work on it over the next day or two, but I'd appreciate any help that
others can provide (even if I end up as the only available mentor).

-Peff

  reply	other threads:[~2017-09-05 11:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 22:30 Git in Outreachy round 15? Jeff King
2017-09-05  2:19 ` Junio C Hamano
2017-09-05 11:40   ` Jeff King [this message]
2017-09-05 21:06 ` Christian Couder
2017-09-07 11:35   ` Jeff King

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=20170905114043.dkjczpioxvu7biw6@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).