From: Jeff King <peff@peff.net>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Git in Outreachy Dec-Mar?
Date: Sun, 2 Sep 2018 04:43:01 -0400 [thread overview]
Message-ID: <20180902084301.GA21979@sigill.intra.peff.net> (raw)
In-Reply-To: <CAP8UFD1yZzbfuss8PyrXQ9SS+rKuS2vey4Mn9xtxWL4rJy2q_A@mail.gmail.com>
On Sun, Sep 02, 2018 at 09:37:59AM +0200, Christian Couder wrote:
> > I also think it doesn't need to be the mentor's responsibility to find
> > the funding. That can be up to an "org admin", and I don't think it
> > should be too big a deal (I had no trouble getting funding from GitHub
> > last year, and I don't expect any this year; I just didn't want to start
> > that process until I knew we were serious about participating).
>
> My experience so far with org admins who don't mentor is that they are
> likely to loose interest in the program over time and stop doing much
> (which is natural, I don't blame anyone). This is what happened with
> GSoC org admins (who don't mentor), so most of the admin work now
> falls back on mentors (org admins that mentor).
>
> That's why I fear that in a few years the burden of finding funds for
> Outreachy might fall back on the mentors too.
Yeah, I agree that might eventually happen. I think if there are admins
willing to look for funds, though, we are better off saving our project
money for now.
-Peff
next prev parent reply other threads:[~2018-09-02 8:45 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 [this message]
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=20180902084301.GA21979@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).