git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Christian Couder <christian.couder@gmail.com>
Subject: Git in Outreachy Dec-Mar?
Date: Tue, 28 Aug 2018 11:14:19 -0400	[thread overview]
Message-ID: <20180828151419.GA17467@sigill.intra.peff.net> (raw)

The Outreachy application period is set to begin on September 10th for
interns participating in the December-March program. Do we want to
participate?

Details on the program are here:

  https://www.outreachy.org/communities/cfp/

If we want to, then we need:

  1. Volunteers to mentor. This is similar in scope to being a GSoC
     mentor.

  2. To get our landing page and list of projects in order (and also
     micro-projects for applicants). This can probably build on the
     previous round at:

       https://git.github.io/Outreachy-15/

     and on the project/microprojects lists for GSoC (which will need
     some updating and culling).

  3. To figure out funding (unlike GSoC, the intern stipend comes from
     the projects). I can look into getting outside funds (which is what
     we did last year). Worst case, we do have enough project money to
     cover an intern. Last year[1] opinions were that this was a
     reasonable use of project money, but of course new opinions are
     welcome.

If the answer is "yes, we should participate", it will hopefully be
accompanied with "yes, I will mentor", and "yes, and I will start
getting the landing page ready." :)

-Peff

[1] https://public-inbox.org/git/20170901223059.xsbcpqff45mnblnj@sigill.intra.peff.net/

             reply	other threads:[~2018-08-28 15:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 15:14 Jeff King [this message]
2018-08-29 13:12 ` Git in Outreachy Dec-Mar? Ævar Arnfjörð Bjarmason
2018-08-30  3:16   ` Jeff King
2018-08-30 11:46     ` Johannes Schindelin
2018-08-30 19:24       ` Jeff King
2018-08-31  8:54         ` Christian Couder
2018-08-31 10:30           ` Оля Тележная
2018-09-01  7:11             ` Christian Couder
2018-09-01  8:34             ` Jeff King
2018-08-30 12:18     ` Ævar Arnfjörð Bjarmason
2018-08-30 19:42       ` Jeff King
2018-09-05 13:23         ` Ævar Arnfjörð Bjarmason
2018-08-31  8:16 ` Christian Couder
2018-09-01  8:43   ` Jeff King
2018-09-02  7:37     ` Christian Couder
2018-09-02  8:43       ` Jeff King
2018-09-03  4:36     ` Christian Couder
2018-09-05  7:20       ` Christian Couder
2018-09-06  1:14         ` Jeff King
2018-09-06  9:58           ` Christian Couder
2018-09-06 19:34             ` Jeff King
2018-09-08  8:59               ` Christian Couder
2018-09-06  1:21       ` Jeff King
2018-09-06  9:51         ` Christian Couder
2018-09-06 19:31           ` Jeff King
2018-09-08  8:57             ` Christian Couder
2018-09-08 15:40               ` 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

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

  git send-email \
    --in-reply-to=20180828151419.GA17467@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=christian.couder@gmail.com \
    --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 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).