From: Patrick Steinhardt <ps@pks.im>
To: Chizoba ODINAKA <chizobajames21@gmail.com>
Cc: git@vger.kernel.org, phillip.wood@dunelm.org.uk
Subject: Re: [Outreachy] My Final Application
Date: Mon, 28 Oct 2024 07:01:32 +0100 [thread overview]
Message-ID: <Zx8ouGN5ln_VtsHw@pks.im> (raw)
In-Reply-To: <CACwP9aqFY6kPOSzv2JWWZejwAiYbMEJJx2qxomEnyxnxKFvkvA@mail.gmail.com>
On Sun, Oct 27, 2024 at 11:48:39PM +0100, Chizoba ODINAKA wrote:
Thanks for your application! If you haven't done so, please don't forget
to also enter it online via Outreachy.
[snip]
> ## Timeline
>
> Phase 1 (December 9 - December 30)
> Community bonding. Talk with mentors. Read Documentation.
> Write backlog.
>
> Phase 2 (December 31 - January 27)
> Begin migrating unittests to use Clar framework. Send patches
> implementing the migration, get reviews, make changes based on
> mentors and community recommendations.
>
> Phase 3 (January 28 - February 25)
> Look at implement additional assert functions for Git-specific types
>
> Final phase (February 26 - March 7)
> Working with clar upstream to improve shortcomings discovered during
> the integration of Git with Clar.
It's somewhat funny that your timeline mentions backfilling missing
functionality _after_ migrating the unit tests. It's likely that some of
the unit tests will need to use such functionality. So you'll likely
have to:
- Investigate the next batch of unit tests to convert.
- Figure out whether these require functionality not yet present in
either clar or our wrappers thereof.
- Upstream potentially missing features.
- Migrate the tests.
- Send the patches for review and refine them based on feedback.
This would be the core cycle of your work, and you'd probably repeat it
multiple times.
Patrick
next prev parent reply other threads:[~2024-10-28 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 22:48 [Outreachy] My Final Application Chizoba ODINAKA
2024-10-28 6:01 ` Patrick Steinhardt [this message]
2024-10-28 6:38 ` Chizoba ODINAKA
2024-10-28 7:28 ` Patrick Steinhardt
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=Zx8ouGN5ln_VtsHw@pks.im \
--to=ps@pks.im \
--cc=chizobajames21@gmail.com \
--cc=git@vger.kernel.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