From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Taylor Blau <me@ttaylorr.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 23:14:38 +0530 [thread overview]
Message-ID: <435a2aa3-59f8-d2bc-f653-4f93d86b9c31@gmail.com> (raw)
In-Reply-To: <ZOZSo7vJztHcvb4W@nand.local>
On 24/08/23 00:10, Taylor Blau wrote:
> On Tue, Aug 22, 2023 at 11:44:41AM +0530, Kaartic Sivaraam wrote:
>>>> If folks are interested, I'd be more than happy to answer any questions
>>>> about participating, and overall logistics of the program.
>>
>> I'm guessing the mentor sign up deadline aligns with the project submission
>> timeline. Could you kindly confirm the same, Taylor?
>
> I couldn't find any specific mention of it on the schedule[1], but AFAIR
> we can add mentors at any time after the Git project confirms its
> participation.
>
Ok Taylor. Thanks for the information!
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 ?
[[ References ]]
[1]: https://www.outreachy.org/communities/cfp/git/
--
Sivaraam
next prev parent reply other threads:[~2023-08-29 17:45 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 [this message]
2023-08-29 17:54 ` Taylor Blau
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=435a2aa3-59f8-d2bc-f653-4f93d86b9c31@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=me@ttaylorr.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 NNTP newsgroup(s).