From: Christian Couder <christian.couder@gmail.com>
To: Emily Shaffer <nasamuffin@google.com>
Cc: git <git@vger.kernel.org>,
Kousik Sanagavarapu <five231003@gmail.com>,
Shuqi Liang <cheskaqiqi@gmail.com>,
Victoria Dye <vdye@github.com>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Hariom verma <hariom18599@gmail.com>
Subject: Re: Projects for the next Outreachy round
Date: Wed, 27 Sep 2023 08:14:39 +0200 [thread overview]
Message-ID: <CAP8UFD1gdLG2VMH2fkPQAajw17qz-FuVatiKrguh70e2VYEWAQ@mail.gmail.com> (raw)
In-Reply-To: <CAJoAoZmC-Ku80aSp5xkxfirJitoi_ai6ryK3cJ7Jkx_2fUjENw@mail.gmail.com>
Hi Emily,
On Wed, Sep 27, 2023 at 12:23 AM Emily Shaffer <nasamuffin@google.com> wrote:
>
> On Tue, Sep 26, 2023 at 7:48 AM Christian Couder
> <christian.couder@gmail.com> wrote:
> >
> > Hi everyone, especially Shuqi and Kousik,
> >
> > September 29 is the deadline for proposing Outreachy projects. As we
> > have at least one mentor for now (me), we should propose at least one
> > project though.
> >
> > All ideas for projects are welcome, don't hesitate to suggest one!
>
> It is probably premature for this cycle. But once we have unit testing
> framework[1] in, I expect that moving tests from t/helper/test-foo.c +
> a sh test to invoke test-foo over to using the unit testing framework
> could be a tidy project for GSOC/Outreachy. Especially if we can have
> an example migration to refer to, which Siddharth from Google is
> working on in his 20% time just now :)
>
> 1: https://lore.kernel.org/git/cover.1692297001.git.steadmon@google.com/
Thanks for the great idea! I am going to propose this as the coding
part of Outreachy should start only in December and I think there are
good chances that the unit test framework will be merged by then. In
case everything is not ready when Outreachy starts, I think we will
probably find other unit tests or libification related work that the
intern can do.
For example, I recently thought about converting commands that store
config info in global variables and use old config functions like
git_config_(int|bool|string|...) to instead use the git_config_get_*()
functions and no more global variables. I wanted to ask about it
today, but I think your suggestion would be better.
Thanks,
Christian.
next prev parent reply other threads:[~2023-09-27 6:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 14:48 Projects for the next Outreachy round Christian Couder
2023-09-26 16:39 ` Kousik Sanagavarapu
2023-09-27 6:26 ` Christian Couder
2023-09-26 17:18 ` Victoria Dye
2023-09-27 6:18 ` Christian Couder
2023-09-26 22:23 ` Emily Shaffer
2023-09-27 6:14 ` Christian Couder [this message]
2023-09-27 3:30 ` Shuqi Liang
2023-09-27 6:33 ` 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=CAP8UFD1gdLG2VMH2fkPQAajw17qz-FuVatiKrguh70e2VYEWAQ@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=cheskaqiqi@gmail.com \
--cc=five231003@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=nasamuffin@google.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 NNTP newsgroup(s).