From: "Pablo Sabater" <pabloosabaterr@gmail.com>
To: "Kaartic Sivaraam" <kaartic.sivaraam@gmail.com>,
"Christian Couder" <christian.couder@gmail.com>,
"git" <git@vger.kernel.org>
Cc: "Git at SFC" <git@sfconservancy.org>,
"Pablo Sabater" <pabloosabaterr@gmail.com>
Subject: Re: Participating in Outreachy's December 2026 cohort
Date: Thu, 03 Sep 2026 11:24:48 +0100 [thread overview]
Message-ID: <DL5LWRORZMGW.P7YH0PPIJW93@gmail.com> (raw)
In-Reply-To: <4de9645c-f067-45bb-8168-1f660e11eb8d@gmail.com>
On Wed Sep 2, 2026 at 2:20 PM WEST, Kaartic Sivaraam wrote:
> Hi Christian,
>
> On 8/26/26 16:25, Christian Couder wrote:
>> Hi everyone,
>>
>> Open Source communities have until September 11, 2026, at 4 pm UTC to
>> sign up to participate as mentoring organizations in Outreachy's
>> December 2026 cohort (see
>> https://www.outreachy.org/blog/2026-02-06/may-2026-call-for-mentoring-organizations/).
>> And (co)mentors have until that same time to submit project
>> descriptions.
>>
>> Last year the Git community mentored a single intern. For a long time
>> GitHub or GitLab used to sponsor Outreachy interns working on Git, but
>> last year both declined to do it, so the intern was sponsored by the
>> Git project itself.
>>
>> Let us know if you want to help as a (co)mentor or an Org Admin, if
>> you know a company that would sponsor an intern, if you have ideas for
>> projects that we could propose, or if you have an opinion on Git
>> participating again this year, or on how we should select interns,
>> etc.
>>
>
> I too believe it would be great if Git could participate in Outreachy
> this year.
>
> I would be willing to co-mentor a project this year. I could also help
> as an org admin if needed.
>
> Also, Pablo was interested to volunteer as a co-mentor for Outreachy.
> I've added him in Cc.
>
> --
> Sivaraam
Hello,
Yes, I'd also like to volunteer as a co-mentor for Outreachy this year.
Although I won't have as much time available as I did during the summer,
now that the university semester has started, I believe I can still make
enough time to review and mentor.
I do have exams in October and January, but they shouldn't make me
unavailable for a whole week, so I don't expect them to be a problem.
Regards,
Pablo
next prev parent reply other threads:[~2026-09-03 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 10:55 Participating in Outreachy's December 2026 cohort Christian Couder
2026-08-26 11:39 ` Usman Akinyemi
2026-09-02 13:20 ` Kaartic Sivaraam
2026-09-03 10:24 ` Pablo Sabater [this message]
2026-09-05 8:26 ` Christian Couder
2026-09-09 9:12 ` 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=DL5LWRORZMGW.P7YH0PPIJW93@gmail.com \
--to=pabloosabaterr@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@sfconservancy.org \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.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