Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
	git@vger.kernel.org, Hariom verma <hariom18599@gmail.com>,
	Victoria Dye <vdye@github.com>
Subject: Re: Git in Outreachy? (December, 2023)
Date: Tue, 29 Aug 2023 13:54:13 -0400	[thread overview]
Message-ID: <ZO4wxU1ilpa6/3EW@nand.local> (raw)
In-Reply-To: <435a2aa3-59f8-d2bc-f653-4f93d86b9c31@gmail.com>

On Tue, Aug 29, 2023 at 11:14:38PM +0530, Kaartic Sivaraam wrote:
> BTW, I think the deadline to sign up for Outreachy is approaching soon I
> believe. The community page [1] seems to indicate that we haven't signed up
> yet. Given that there was an interest in us participating in Outreachy, I
> just wanted to check whether we've signed up our community ?

Indeed. I was waiting to see if interested parties had the resources to
sponsor an Outreachy student, since we have to pay Outreachy for each
student we accept.

If you (or others) are interested in mentoring but don't have a way to
pay Outreachy, we could certainly discuss allocating some of the
project's funds to support one or two students.

Thanks,
Taylor

  reply	other threads:[~2023-08-29 17:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  1:07 Git in Outreachy? (December, 2023) Taylor Blau
2023-08-18 15:10 ` Christian Couder
2023-08-18 15:17   ` Taylor Blau
2023-08-22  6:14   ` Kaartic Sivaraam
2023-08-23 18:40     ` Taylor Blau
2023-08-29 17:44       ` Kaartic Sivaraam
2023-08-29 17:54         ` Taylor Blau [this message]
2023-08-29 20:38           ` Christian Couder
2023-09-02  6:06             ` Kaartic Sivaraam
2023-09-21 20:46             ` Taylor Blau
2023-09-22  6:19               ` Christian Couder
2023-10-29 18:23                 ` Kaartic Sivaraam

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=ZO4wxU1ilpa6/3EW@nand.local \
    --to=me@ttaylorr.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hariom18599@gmail.com \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=vdye@github.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).