git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: Git in Outreachy round 15?
Date: Fri, 1 Sep 2017 18:30:59 -0400	[thread overview]
Message-ID: <20170901223059.xsbcpqff45mnblnj@sigill.intra.peff.net> (raw)

Hi all,

I know we're just finishing up GSoC, but I want to get opinions on Git
participating in the next round of Outreachy, which will be accepting
interns over the next month or two.

Details and timelines are here:

  https://www.outreachy.org/

  https://www.outreachy.org/mentor/

For those not familiar with Outreachy, it's an internship program
focused on providing mentorship and stipends to groups that are
under-represented in Tech. The internship term is 3 months. Unlike other
programs like GSoC, individual projects (rather than the program) cover
the stipend, which is $6500 this round.

The big questions on whether we can make this happen are:

  1. Do we have mentor interest?

     I'm willing to mentor, but I'd like to hear whether other people
     are interested, as well. Either way I can take responsibility for
     the administrative bits.

     We could probably use some effort brushing up our project-ideas
     page. I've also considered whether it would make sense to do a
     "mixed bag" project where somebody works on multiple smaller
     projects, and we try to get them more involved in day-to-day
     project activities (after all, very few of us started working on
     Git with a dedicated 3-month project; people typically ease into it
     by fixing small problems, reviewing code, etc).

  2. Do we have the money (and want to spend it on this)?

     The Git project does have money to cover at least one intern.

     I'm looking into securing outside funding, so that we don't have to
     use project funds. If for whatever reason that doesn't happen, is
     this something we want to spend project money on?

     (My opinion is yes, but I'd like to hear what others in the
     community think).

-Peff

             reply	other threads:[~2017-09-01 22:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 22:30 Jeff King [this message]
2017-09-05  2:19 ` Git in Outreachy round 15? Junio C Hamano
2017-09-05 11:40   ` Jeff King
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=20170901223059.xsbcpqff45mnblnj@sigill.intra.peff.net \
    --to=peff@peff.net \
    --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.
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).