git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [Outreachy] Final Application Timeline

From
Patrick Steinhardt <ps@pks.im>
Date
Oct 27, 2024, 10:50 UTC
Message-ID
<Zx4bEOGr8Hy-ZfX2@pks.im>
In-Reply-To
<CAGedMteoVFfZy1jtHMPJvByzfq9unomcA7qkCNKx9R6_ZQ6=Cw@mail.gmail.com>
On Sat, Oct 26, 2024 at 03:50:11PM +0100, Seyi Chamber wrote:
> Dear Mentors,
Hi,
> It's almost the deadline to create a final application for the Git
> community, it's a little unclear how I should create a timeline for the
> project *Convert unit tests to use the clar testing framework*.

you may have a look at the recent thread in [1] to get some more input on that.

Show 6 quoted lines
> Does a timeline of the first 8 weeks spent working on converting the unit
> test framework to use the clar framework and the remaining 4 weeks
> spent on *implementing
> additional asserting functions for Git-specific types *and using *clar
> upstream to improve shortcomings discovered during the integration of Git
> with the clar* tasks sound good?

What I'd specifically like to see is how exactly you want to work on things. So it's not only "I will convert X", but a couple more items:

  - Are there things you need to learn? When do you plan to get familiar
    with the codebase and how do you tackle that problem?
  - How do you plan to approach the topic? Do you want to convert
    everything in one go and then send over a huge topic or rather want
    to work on it incrementally? You can also take as inspiration the
    last GSoC students that converted our unit tests from the test
    helpers to our own unit testing framework.
  - Do you plan to work with clar upstream in case you feel like there
    are missing features? It might make sense to have a look at it early
    in the cycle so that you know what to expect and what you may want
    to implement there.
  - Plan sufficient time for review cycles. The Git project is not
    exactly the fastest-moving project, so you need to plan time
    accordingly.

Overall I don't expect a hugely detailed plan that knows ahead of time how long you'll work on each of these items. I just want to see whether you've got an idea for how to approach the project and how to work with the Git community.

Let me know in case you've got further questions!
Patrick
[1]: https://lore.kernel.org/git/CAPSxiM-kf8U=vzp5MoD3tUuOtnNjcCgPhLdriyeQo5CGf=EhyQ@mail.gmail.com/
Next: Seyi Chamber
Message 1 of 3 in “Re: [Outreachy] Final Application Timeline”
  1. Patrick SteinhardtOct 27, 2024
  2. Seyi ChamberOct 27, 2024
  3. Patrick SteinhardtOct 28, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.