From: Christian Couder <christian.couder@gmail.com>
To: git <git@vger.kernel.org>
Cc: "Git at SFC" <git@sfconservancy.org>,
"Taylor Blau" <me@ttaylorr.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Tilda Udufo - Outreachy Organizer" <organizers@outreachy.org>
Subject: [ANNOUNCE] Outreachy mentor sign-up deadline is Wednesday September 11th at 4pm UTC
Date: Thu, 5 Sep 2024 11:50:20 +0200 [thread overview]
Message-ID: <CAP8UFD10B4ROEjvP7MPygALuUFgyBQqZVhAjgSUris3cdiowsQ@mail.gmail.com> (raw)
Hi everyone,
I signed up for Git as a mentoring community in the Outreachy December
2024 internship cohort. The deadline was September 6th at 4pm UTC and
I think we will be able to change our mind later if we decide to not
participate for some reason. So it was better to just sign-up.
I have also added a project with the title: "Finish adding a
'os-version' capability to Git protocol v2" that I am willing to
mentor or co-mentor. I think it's possible to add more projects and to
remove this one if we find better ones.
The mentor sign-up deadline is very soon too: Wednesday September 11th
at 4pm UTC
So if you are interested in mentoring please sign-up. I think
co-mentors might be able to sign-up later but I am not sure.
Tilda, please correct me if I am wrong.
Also please let us know if some companies might be willing to sponsor
an Outreachy intern or Outreachy itself. Outreachy is part of the
Software Freedom Conservancy (https://sfconservancy.org/) like the Git
project.
See: https://www.outreachy.org/communities/cfp/git/
Thanks,
Christian.
next reply other threads:[~2024-09-05 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 9:50 Christian Couder [this message]
2024-09-09 7:53 ` [ANNOUNCE] Outreachy mentor sign-up deadline is Wednesday September 11th at 4pm UTC Patrick Steinhardt
2024-09-09 8:00 ` Patrick Steinhardt
2024-09-10 14:28 ` Christian Couder
2024-09-10 18:31 ` phillip.wood123
2024-09-11 9:32 ` Patrick Steinhardt
2024-09-11 13:27 ` phillip.wood123
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=CAP8UFD10B4ROEjvP7MPygALuUFgyBQqZVhAjgSUris3cdiowsQ@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=avarab@gmail.com \
--cc=git@sfconservancy.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=organizers@outreachy.org \
/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).