From: Patrick Steinhardt <ps@pks.im>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>, "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>,
"Phillip Wood" <phillip.wood@dunelm.org.uk>
Subject: Re: [ANNOUNCE] Outreachy mentor sign-up deadline is Wednesday September 11th at 4pm UTC
Date: Mon, 9 Sep 2024 09:53:20 +0200 [thread overview]
Message-ID: <Zt6pbMP3Rpjy-pC_@pks.im> (raw)
In-Reply-To: <CAP8UFD10B4ROEjvP7MPygALuUFgyBQqZVhAjgSUris3cdiowsQ@mail.gmail.com>
On Thu, Sep 05, 2024 at 11:50:20AM +0200, Christian Couder wrote:
> 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 for organizing this! With the clar unit testing framework having
landed I think it would be a nice project for Outreachy to convert (a
subset of) our unit tests to that new framework.
There is still a bunch of work that I'm in the process of upstreaming
[1][2][3][4] as well as a refactoring of the macros to make them
typesafe that I'm currently preparing. But none of these changes should
impact how the clar is used, so I would say that it is fine to queue up
such a project.
Patrick
[1]: https://github.com/clar-test/clar/pull/99 (MinGW and HPE support, merged)
[2]: https://github.com/clar-test/clar/pull/100 (CI support for Windows)
[3]: https://github.com/clar-test/clar/pull/101 (out-of-memory handling)
[4]: https://github.com/clar-test/clar/pull/102 (selftests)
next prev parent reply other threads:[~2024-09-09 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 9:50 [ANNOUNCE] Outreachy mentor sign-up deadline is Wednesday September 11th at 4pm UTC Christian Couder
2024-09-09 7:53 ` Patrick Steinhardt [this message]
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=Zt6pbMP3Rpjy-pC_@pks.im \
--to=ps@pks.im \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@sfconservancy.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=organizers@outreachy.org \
--cc=phillip.wood@dunelm.org.uk \
/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).