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

Re: Git in GSoC 2025

From
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Date
Jan 28, 2025, 17:30 UTC
Message-ID
<c39c5424-71d0-4b6d-90b1-a6a70f2ee61b@gmail.com>
In-Reply-To
<Z432QXJb_TfzNBa2@pks.im>
(Apologies for the delayed re-send. I just noticed that this one
  got dropped by the mailing list. I'll respond to existing replies
  in that thread)
Hi Patrick, Christian, Karthik and Jialuo,
Thank you very much for your interest in volunteering as a mentor!
On Mon, Jan 20, 2025 at 12:37 PM Patrick Steinhardt <ps@pks.im> wrote:
 > I'd be happy to mentor this year again. A couple of ideas:

Thank you for suggesting these ideas, Patrick! I've incorporated them into a draft ideas page for now. You can see them here:

https://git.github.io/SoC-2025-Ideas/

Kindly suggest any corrections to the description, project size / difficulty as necessary. I've mentioned potential mentors based on what I'm aware of so far.

Patrick, Christian and Karthik, kindly mention the ideas that you're interested to mentor.

While I have not included them as of yet, I wonder if the following ideas which we had last year[1] could still be retained this year:

- Implement consistency checks for refs. The idea could be about
   implementing further ref checks which Jialuo appears to be helping
   out with. We could leave it if Jialuo prefers to continue working on
   the same in a flow.
- Refactor git-bisect(1) to make its state self-contained
- Implement support for reftables in "dumb" HTTP transport

Would these be interesting ones to consider? Is anyone willing to mentor these this time around?

 > I'll keep on thinking about potential topics.

Sure. That would be great! Others could also chime in with your potential ideas. Also, do not hesitate to let us know if you're interested in mentoring.

-- 
Sivaraam
Previous: Oswald BuddenhagenNext: Kaartic Sivaraam
Message 5 of 52 in “Git in GSoC 2025”
  1. Kaartic SivaraamJan 19, 2025
  2. Patrick SteinhardtJan 20, 2025
  3. shejialuoJan 20, 2025
  4. Oswald BuddenhagenJan 21, 2025
  5. Kaartic SivaraamJan 28, 2025
  6. Kaartic SivaraamFeb 2, 2025
  7. Patrick SteinhardtFeb 3, 2025
  8. Karthik NayakFeb 3, 2025
  9. shejialuoFeb 4, 2025
  10. Kaartic SivaraamFeb 4, 2025
  11. Christian CouderFeb 5, 2025
  12. Kaartic SivaraamFeb 7, 2025
  13. Christian CouderFeb 7, 2025
  14. Patrick SteinhardtFeb 7, 2025
  15. Kaartic SivaraamFeb 11, 2025
  16. Ghanshyam ThakkarFeb 16, 2025
  17. Kaartic SivaraamFeb 16, 2025
  18. Junio C HamanoFeb 16, 2025
  19. Ghanshyam ThakkarFeb 17, 2025
  20. Karthik NayakMar 7, 2025
  21. Kaartic SivaraamMar 20, 2025
  22. Karthik NayakMar 21, 2025
  23. shejialuoFeb 8, 2025
  24. Karthik NayakFeb 10, 2025
  25. Christian CouderJan 20, 2025
  26. Patrick SteinhardtJan 20, 2025
  27. Junio C HamanoJan 21, 2025
  28. Kaartic SivaraamJan 30, 2025
  29. Patrick SteinhardtJan 30, 2025
  30. Christian CouderJan 30, 2025
  31. Patrick SteinhardtJan 30, 2025
  32. Junio C HamanoJan 30, 2025
  33. Junio C HamanoJan 30, 2025
  34. Patrick SteinhardtJan 31, 2025
  35. Junio C HamanoJan 31, 2025
  36. Patrick SteinhardtFeb 3, 2025
  37. Patrick SteinhardtJan 31, 2025
  38. Junio C HamanoFeb 3, 2025
  39. Kaartic SivaraamFeb 4, 2025
  40. Kaartic SivaraamJan 30, 2025
  41. Karthik NayakJan 20, 2025
  42. shejialuoJan 20, 2025
  43. Kaartic SivaraamFeb 28, 2025
  44. shejialuoFeb 28, 2025
  45. Patrick SteinhardtFeb 28, 2025
  46. Christian CouderFeb 28, 2025
  47. Ghanshyam ThakkarFeb 28, 2025
  48. Kaartic SivaraamMar 1, 2025
  49. Karthik NayakMar 3, 2025
  50. Patrick SteinhardtJan 27, 2025
  51. shejialuoJan 27, 2025
  52. Kaartic SivaraamJan 28, 2025

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.