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

Re: Git in GSoC 2022?

From
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Date
Mar 9, 2022, 19:57 UTC
Message-ID
<CA+ARAtqjFhR2W8OjzGgPmtin4g_9M-8jjyJ0XsS1_401uxBrLg@mail.gmail.com>
In-Reply-To
<nycvar.QRO.7.76.6.2203091249060.357@tvgsbejvaqbjf.bet>
Hi Dscho,

On Wed, Mar 9, 2022 at 5:19 PM Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 32 quoted lines
>
> Hi Kaartic,
>
> On Sun, 30 Jan 2022, Kaartic Sivaraam wrote:
>
> > On 28/01/22 4:15 pm, Johannes Schindelin wrote:
> > >
> > > A project that I would personally find a lot of fun, with a great impact,
> > > and never really talked about on this list, would be to offer a good
> > > replacement for the `git daemon`: its purpose is to make it easy to stand
> > > up an ad-hoc server, to allow developers to clone/fetch (and even push, if
> > > that is enabled) via the network, unauthenticated. Now, the git://
> > > protocol has served us well in the beginning, but it is increasingly
> > > obvious that we should use https:// wherever possible. Wouldn't it be fun
> > > to have a `git daemon` that talks https:// by default, maybe even
> > > optionally offering a real web UI via gitweb? This is not as huge of a
> > > project as it sounds, Jeff Hostetler already did a ton of work to that end
> > > over in the Microsoft fork of Git: the `test-gvfs-protocol` helper is used
> > > in the regression tests to offer Git repositories via http:// and the
> > > biggest task to convert this to an HTTP-speaking `git daemon` would be to
> > > rip out the GVFS parts. After that, HTTPS support could be added.
> > >
> >
> > Sounds interesting. Would you mind drafting this into a project proposal
> > for GSoC. Then we could add it to the list of ideas document [1].
> >
> > Also, would you be willing to mentor a student in case they pick this
> > project? Or would you rather leave it to others?
>
> I would _love_ to mentor a student, but my time constraints do not allow
> me to do that.
>
That's understandable. Thanks for sharing the project idea!

In case anyone else is interested to volunteer as a mentor for this project, do chime in. We could then add this one to the ideas list.

-- Sivaraam

Previous: Johannes Schindelin
Message 36 of 36 in “Git in GSoC 2022?”
  1. Kaartic SivaraamJan 26, 2022
  2. Taylor BlauJan 26, 2022
  3. Christian CouderJan 27, 2022
  4. Kaartic SivaraamJan 29, 2022
  5. Christian CouderFeb 13, 2022
  6. Kaartic SivaraamFeb 15, 2022
  7. Hariom vermaFeb 15, 2022
  8. Christian CouderFeb 16, 2022
  9. Hariom vermaFeb 17, 2022
  10. Kaartic SivaraamFeb 17, 2022
  11. Hariom vermaFeb 18, 2022
  12. Kaartic SivaraamFeb 26, 2022
  13. Christian CouderFeb 28, 2022
  14. Kaartic SivaraamFeb 28, 2022
  15. Christian CouderMar 1, 2022
  16. Kaartic SivaraamMar 4, 2022
  17. Bagas SanjayaJan 27, 2022
  18. Christian CouderJan 27, 2022
  19. Derrick StoleeJan 27, 2022
  20. Kaartic SivaraamJan 29, 2022
  21. Derrick StoleeFeb 2, 2022
  22. ZheNing HuJan 27, 2022
  23. Kaartic SivaraamJan 29, 2022
  24. Philip OakleyFeb 3, 2022
  25. Kaartic SivaraamFeb 12, 2022
  26. Christian CouderFeb 13, 2022
  27. Philip OakleyFeb 15, 2022
  28. Kaartic SivaraamFeb 15, 2022
  29. Christian CouderFeb 16, 2022
  30. Kaartic SivaraamFeb 17, 2022
  31. Kaartic SivaraamMar 7, 2022
  32. Derrick StoleeMar 7, 2022
  33. Hariom vermaMar 7, 2022
  34. Kaartic SivaraamJan 29, 2022
  35. Johannes SchindelinMar 9, 2022
  36. Kaartic SivaraamMar 9, 2022

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.