On Mon, Oct 28, 2024 at 6:11 AM Patrick Steinhardt <ps@xxxxxx> wrote: > > On Mon, Oct 28, 2024 at 01:56:36AM +0000, Usman Akinyemi wrote: > > Hello, > > > > As I planned to submit a proposal for two projects, below is my > > proposal for "Conversion of Git Unit Tests to Clar Testing Framework". > > I would just go straight into the project proposals as the other > > necessary information is in the previous email. I would prefer to work > > on the "Finish adding a 'os-version' capability to Git protocol v2" > > project in case. > > Thanks for your applications! I'll only reply to this email as I'm not > mentoring the other project. > > [snip] > > ---- December 23 - February 10: Incremental Conversions & Feedback > > Integration ----- > > > > - File Renaming: Rename test files from t-<name>.c to <name>.c > > following the structure outlined by prior contributions. > > - Clar Suite Integration: Add the module name to CLAR_TEST_SUITE in > > the Makefile to include the file in the Clar testing suite. > > - Conversion of Test Assertions: Replace the test assertions with > > Clar’s built-in functions (cl_assert, cl_assert_equal_s, > > cl_assert_equal_i, etc.), enhancing readability and functionality. > > - Patch Submission: Submit each converted test as an incremental > > patch to Git's mailing list following the Git contribution guidelines. > > This phased approach enables targeted feedback from the community. > > One thing missing here is the work with upstream in case we want to > implement any functionality that doesn't yet exist in clar. You mention > it in "Additional Goals and Extensions" though, so that might be good > enough. > > Other than that this looks good to me, thanks! Please don't forget to > upload your applications to Outreachy if you haven't done so already. > Hi, Patrick Thanks for your review. Will it be better to include *work with upstream* as part of the whole timeline instead of adding it as an Additional Goals and Extensions? Thanks. > Patrick
