From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Christian Couder <christian.couder@gmail.com>,
Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Hariom verma <hariom18599@gmail.com>,
Victoria Dye <vdye@github.com>
Subject: Re: Git in Outreachy? (December, 2023)
Date: Tue, 22 Aug 2023 11:44:41 +0530 [thread overview]
Message-ID: <2c31a3d4-59f7-d036-0c6b-5fd62cc7a2fa@gmail.com> (raw)
In-Reply-To: <CAP8UFD2Yw1XazomxEj0QB20FoaxkO16t_xgRurtnqCCOuhX-eQ@mail.gmail.com>
On 18 August 2023 8:40:25 pm IST, Christian Couder
<christian.couder@gmail.com> wrote:
>(Adding a few people who could be interested in helping with this in Cc:)
>
Thanks, Christian!
>> I think it would be good to participate in this year's December cohort.
>> September 1, 2023 at 4pm UTC is the initial community application
>> deadline.
>
>I agree it would be nice, and I am willing to mentor, or if possible
>co-mentor, someone.
>
>> If we're interested, the project submission deadline is September 29th.
>> By then, we'd need:
>>
>> - Volunteers to act as mentors
Depending on the projects that we'll be proposing, I may be able to
co-mentor for one. Though, my timeline looks uncertain now. So, I'm
unsure about it. I should be able to mention for sure after before the
mentor sign-up deadline.
> I wonder if we need a few Org Admins too.
Regardless, I should be able to help us an Org Admin if there's a need :-)
>
>> - Updates to our applicant materials on git.github.io (project ideas,
>> as well as potential microprojects).
>
>Yeah, I can start working on the applicant material after my current vacation.
>
That's great, Christian. Let me know in case you need any help with it.
>> 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?
--
Sivaraam
next prev parent reply other threads:[~2023-08-22 6:15 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 [this message]
2023-08-23 18:40 ` Taylor Blau
2023-08-29 17:44 ` Kaartic Sivaraam
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=2c31a3d4-59f7-d036-0c6b-5fd62cc7a2fa@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 read-only IMAP folder(s) and NNTP newsgroup(s).