git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Git in Outreachy Dec-Mar?
Date: Wed, 5 Sep 2018 21:14:28 -0400	[thread overview]
Message-ID: <20180906011428.GA5024@sigill.intra.peff.net> (raw)
In-Reply-To: <CAP8UFD3DrhA9C0=k-ie_fnpKwmbezQ9ufp1RPHrZ7A-VUjhz0g@mail.gmail.com>

On Wed, Sep 05, 2018 at 09:20:23AM +0200, Christian Couder wrote:

> >> Thanks. I think sooner is better for this (for you or anybody else who's
> >> interested in mentoring). The application period opens on September
> >> 10th, but I think the (still growing) list of projects is already being
> >> looked at by potential candidates.
> 
> Do you know where is this list? On
> https://www.outreachy.org/apply/project-selection/ they say
> "Information about projects are unavailable until applications open".

This was the list I was looking at (scroll down below the timeline):

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

But yeah, most of the "current projects" lists just say "not available
yet", so I think we're actually OK until the 10th.

> > So here is a landing page for the next Outreachy round:
> >
> > https://git.github.io/Outreachy-17/
> >
> > about the microprojects I am not sure which page I should create or improve.
> 
> Any idea about this? Also any idea about new microprojects would be nice.

I think #leftoverbits is your best bet for micro-projects. Last year I
think we had interns actually hunt for them via the list archive. That's
a little unfriendly for total newcomers, I think, but it also does give
a chance to demonstrate some skills. Perhaps it would be help to create
a curated list of such bits.

-Peff

  reply	other threads:[~2018-09-06  1:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 15:14 Git in Outreachy Dec-Mar? Jeff King
2018-08-29 13:12 ` Æ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 [this message]
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=20180906011428.GA5024@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --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).