From: Pranit Bauva <pranit.bauva@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Git in Outreachy December-March?
Date: Fri, 2 Sep 2016 15:05:17 +0530 [thread overview]
Message-ID: <CAFZEwPNDScR-+KGEWS__fAMrdKupe+ibKLFMceBMf5pqJ2kjYw@mail.gmail.com> (raw)
In-Reply-To: <20160902090247.b5gtui75hiwococc@sigill.intra.peff.net>
Probably off-topic.
On Fri, Sep 2, 2016 at 2:32 PM, Jeff King <peff@peff.net> wrote:
> As some of you may recall, we signed up to participate in Outreachy for
> the May-August session, but did not end up selecting an intern. The
> original thread with details is here:
>
> http://public-inbox.org/git/20160308224625.GA29922@sigill.intra.peff.net/
>
> There's another session that runs from December to March. If we want to
> participate, we need to sign up in the next few days.
>
> I'm happy to act as admin. We will need a few things:
>
> - to arrange funding for the stipend. GitHub offered to cover this
> last time, and if we are interested, I can see if this is still the
> case. We can also cover it out of the Git project money.
>
> - mentor volunteers. This is similar in scope to GSoC, but I don't
> want to just assume that people who volunteered for GSoC would still
> be available
>
> - projects. We can pull from the ideas that were not selected for the
> 2016 GSoC, but we may need to update or add to it.
I have a few friends who too did GSoC along with me but in different
orgs. Their orgs have a separate channel (slack or IRC) for
GSoC/Outreachy communications. In that channel is that all potential
mentors are added and students too are pointed to it. In that channel
the very basic doubts are covered. Let's say I am online and probably
the student's mentor is currently unavailable, so he/she can post a
trivial doubt there for someone to respond quickly. It takes off a
little load from the list and the mentor as well. I am aware that
there exists a channel named #git-devel but unfortunately its not
really active. I will be wiling to help other students with their
early days!
These days a lot of my fellow students don't really use IRC for
communication and see you can see there were really less number of
people inquiring about GSoC in #git-devel. We can prefer slack or any
other alternative.
Regards,
Pranit Bauva
next prev parent reply other threads:[~2016-09-02 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 9:02 Git in Outreachy December-March? Jeff King
2016-09-02 9:35 ` Pranit Bauva [this message]
2016-09-02 14:34 ` Christian Couder
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=CAFZEwPNDScR-+KGEWS__fAMrdKupe+ibKLFMceBMf5pqJ2kjYw@mail.gmail.com \
--to=pranit.bauva@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).