Git in GSoC 2022?

> On Wed, Jan 26, 2022 at 11:59:16PM +0530, Kaartic Sivaraam wrote:
> > First, are we interested in participating in the 2022 round of
> > GSoC?
>
> I think it would be great to participate this year, provided that we can
> come up with some interesting projects and mentors to help out.

> >     Taylor showed interest in a bitmap-related project during
> >     the Outreachy application period [4]. Taylor, are you still
> >     interested in mentoring a bitmap-related project? Would it
> >     be possible for you to do so for the upcoming GSoC?
>
> I'm available and interested in mentoring. I don't think I found many
> interested folks via Outreachy who wanted to work on bitmaps, but I
> think it's worth trying again via GSoC. I can rejigger the proposed
> projects there a bit, too.

> Hi,
> 
> On Wed, Jan 26, 2022 at 9:05 PM Taylor Blau <me@ttaylorr.com> wrote:
> 
>> On Wed, Jan 26, 2022 at 11:59:16PM +0530, Kaartic Sivaraam wrote:
>>> First, are we interested in participating in the 2022 round of
>>> GSoC?
>>
>> I think it would be great to participate this year, provided that we can
>> come up with some interesting projects and mentors to help out.
> 
> I agree.
> 

>>>      Taylor showed interest in a bitmap-related project during
>>>      the Outreachy application period [4]. Taylor, are you still
>>>      interested in mentoring a bitmap-related project? Would it
>>>      be possible for you to do so for the upcoming GSoC?
>>
>> I'm available and interested in mentoring. I don't think I found many
>> interested folks via Outreachy who wanted to work on bitmaps, but I
>> think it's worth trying again via GSoC. I can rejigger the proposed
>> projects there a bit, too.
> 
> I am also available and interested in mentoring and I can reuse a
> project prepared for the last Outreachy round too.
> 

> On Thu, Jan 27, 2022 at 10:32 AM Christian Couder
> <christian.couder@gmail.com> wrote:
>> On Wed, Jan 26, 2022 at 9:05 PM Taylor Blau <me@ttaylorr.com> wrote:
> 
>> I am also available and interested in mentoring and I can reuse a
>> project prepared for the last Outreachy round too.
> 
> I added the "Unify ref-filter formats with other pretty formats" to
> continue Hariom Verma's work during GSoC 2020. I would be happy to
> co-mentor it if someone is interested to co-mentor it with me.
> 

>
> Hi,
>
> On Mon, Feb 14, 2022 at 2:59 PM Christian Couder
> <christian.couder@gmail.com> wrote:
> >
> > I added the "Unify ref-filter formats with other pretty formats" to
> > continue Hariom Verma's work during GSoC 2020. I would be happy to
> > co-mentor it if someone is interested to co-mentor it with me.
>
> Since I worked on this for quite some time. I maybe am able to provide
> some insights. If it's not too late, I would like to co-mentor it with
> you.

>
> > > I added the "Unify ref-filter formats with other pretty formats" to
> > > continue Hariom Verma's work during GSoC 2020. I would be happy to
> > > co-mentor it if someone is interested to co-mentor it with me.
> >
> > Since I worked on this for quite some time. I maybe am able to provide
> > some insights. If it's not too late, I would like to co-mentor it with
> > you.
>
> Great! I am happy to co-mentor it with you!
>

> Hi,
> 
> On Wed, Feb 16, 2022 at 12:18 AM Hariom verma <hariom18599@gmail.com> wrote:
>>
>> Hi,
>>
>> On Mon, Feb 14, 2022 at 2:59 PM Christian Couder
>> <christian.couder@gmail.com> wrote:
>>>
>>> I added the "Unify ref-filter formats with other pretty formats" to
>>> continue Hariom Verma's work during GSoC 2020. I would be happy to
>>> co-mentor it if someone is interested to co-mentor it with me.
>>
>> Since I worked on this for quite some time. I maybe am able to provide
>> some insights. If it's not too late, I would like to co-mentor it with
>> you.
> 
> Great! I am happy to co-mentor it with you!
> 

> 
> On Wed, Jan 26, 2022 at 11:59:16PM +0530, Kaartic Sivaraam wrote:
>> First, are we interested in participating in the 2022 round of
>> GSoC?
> 
> I think it would be great to participate this year, provided that we can
> come up with some interesting projects and mentors to help out.
> 
>>      Taylor showed interest in a bitmap-related project during
>>      the Outreachy application period [4]. Taylor, are you still
>>      interested in mentoring a bitmap-related project? Would it
>>      be possible for you to do so for the upcoming GSoC?
> 
> I'm available and interested in mentoring. I don't think I found many
> interested folks via Outreachy who wanted to work on bitmaps, but I
> think it's worth trying again via GSoC. I can rejigger the proposed
> projects there a bit, too.
> 

>
> On Sat, Feb 26, 2022 at 9:30 PM Kaartic Sivaraam
> <kaartic.sivaraam@gmail.com> wrote:
>
> > Thanks for adding the ideas to the SoC-2022-Ideas[1] list! I noticed that
> > you're the only one mentioned as mentor for the idea there. It's usually
> > good to have at least 2 mentors per project. Is anyone else interested
> > in co-mentoring with Taylor for the idea?
>
> If no one else wants to co-mentor with Taylor, I am happy with it.

> On Mon, Feb 28, 2022 at 4:33 PM Christian Couder
> <christian.couder@gmail.com> wrote:
> > On Sat, Feb 26, 2022 at 9:30 PM Kaartic Sivaraam
> > <kaartic.sivaraam@gmail.com> wrote:
> >
> > > Thanks for adding the ideas to the SoC-2022-Ideas[1] list! I noticed that
> > > you're the only one mentioned as mentor for the idea there. It's usually
> > > good to have at least 2 mentors per project. Is anyone else interested
> > > in co-mentoring with Taylor for the idea?
> >
> > If no one else wants to co-mentor with Taylor, I am happy with it.
>
> If it's fine, I would be willing to co-mentor with Taylor. In case
> there are other
> potential mentors who are willing to volunteer, do chime in :-)

> On Mon, Feb 28, 2022 at 7:02 PM Kaartic Sivaraam
> <kaartic.sivaraam@gmail.com> wrote:
> 
>> On Mon, Feb 28, 2022 at 4:33 PM Christian Couder
>> <christian.couder@gmail.com> wrote:
>>> On Sat, Feb 26, 2022 at 9:30 PM Kaartic Sivaraam
>>> <kaartic.sivaraam@gmail.com> wrote:
>>>
>>>> Thanks for adding the ideas to the SoC-2022-Ideas[1] list! I noticed that
>>>> you're the only one mentioned as mentor for the idea there. It's usually
>>>> good to have at least 2 mentors per project. Is anyone else interested
>>>> in co-mentoring with Taylor for the idea?
>>>
>>> If no one else wants to co-mentor with Taylor, I am happy with it.
>>
>> If it's fine, I would be willing to co-mentor with Taylor. In case
>> there are other
>> potential mentors who are willing to volunteer, do chime in :-)
> 
> Great! As I already co-mentor another project, I will let you
> co-mentor this one with Taylor.
> 

>
> On 27/01/22 01.29, Kaartic Sivaraam wrote:
> >    - Project ideas: There are two mentioned in SoC-2021-Ideas[3]
> >      but both were picked by GSoC students the previous year. So,
> >      we would need new ones this year.
>
> I have several project ideas:
>
>    - Document the "binary diff" format. Right now we have documentation
>      for all diff formats used in Git, except for binary diff. Hint:
>      read `diff.c`

>    - Rewrite `git-request-pull.sh` in C. Currently the shell script
>      implementation hard-codes message template and only outputs to
>      stdout (though can be redirected to a file using shell means).
>      In the C version, message template can be configured (with the
>      default is same as current version) and introduces new
>      `-o/--output` option to specify output file.

> If we are interested in participating we need:
> 
>   - Volunteers who are wiling to act as mentors. I would be
>     willing to be volunteer myself as a mentor for one student.
>  
>   - Microprojects: I believe we could repurpose the Outreachy
>     microproject ideas[2] for GSoC too. If others have suggestions
>     for microproject ideas, please share them.
> 
>   - Project ideas: There are two mentioned in SoC-2021-Ideas[3]
>     but both were picked by GSoC students the previous year. So,
>     we would need new ones this year.

>   - Multiple Sizes of Projects: In 2021, project size was reduced
>     (~175 hours). This year, both medium sized projects (~175 hours)
>     and large projects (~350 hours) are supported.
> 
>     GSoC organizers recommend communities to have both medium _and_
>     large size projects.

> On 1/26/2022 1:29 PM, Kaartic Sivaraam wrote:
>> If we are interested in participating we need:
>>
>>    - Volunteers who are wiling to act as mentors. I would be
>>      willing to be volunteer myself as a mentor for one student.
>>   
>>    - Microprojects: I believe we could repurpose the Outreachy
>>      microproject ideas[2] for GSoC too. If others have suggestions
>>      for microproject ideas, please share them.
>>
>>    - Project ideas: There are two mentioned in SoC-2021-Ideas[3]
>>      but both were picked by GSoC students the previous year. So,
>>      we would need new ones this year.
> 
> One project that could be interesting for GSoC (and the timing
> should work out) is to complete the sparse index integrations for
> some of the less critical commands. Some examples include 'git mv'
> and 'git rm', I think.
> 
> This of course depends on some ongoing work to integrate more of
> the critical commands that we implemented early in microsoft/git,
> such as Victoria's current series which is leading to a 'git stash'
> integration and a series I have waiting in the wings for a 'git
> sparse-checkout' integration.
> 
> However, I think we have a decent paved-path for a new contributor
> to jump in and get started on the remaining commands. The granularity
> means that the project has multiple milestones that can be hit
> without an all-in-one series.
> 

>>    - Multiple Sizes of Projects: In 2021, project size was reduced
>>      (~175 hours). This year, both medium sized projects (~175 hours)
>>      and large projects (~350 hours) are supported.
>>
>>      GSoC organizers recommend communities to have both medium _and_
>>      large size projects.
> 
> I think this project would fit in the "medium" category.
>

> On 27/01/22 8:09 pm, Derrick Stolee wrote:
>> On 1/26/2022 1:29 PM, Kaartic Sivaraam wrote:
>>> If we are interested in participating we need:
>>>
>>>    - Volunteers who are wiling to act as mentors. I would be
>>>      willing to be volunteer myself as a mentor for one student.
>>>      - Microprojects: I believe we could repurpose the Outreachy
>>>      microproject ideas[2] for GSoC too. If others have suggestions
>>>      for microproject ideas, please share them.
>>>
>>>    - Project ideas: There are two mentioned in SoC-2021-Ideas[3]
>>>      but both were picked by GSoC students the previous year. So,
>>>      we would need new ones this year.
>>
>> One project that could be interesting for GSoC (and the timing
>> should work out) is to complete the sparse index integrations for
>> some of the less critical commands. Some examples include 'git mv'
>> and 'git rm', I think.
>>
>> This of course depends on some ongoing work to integrate more of
>> the critical commands that we implemented early in microsoft/git,
>> such as Victoria's current series which is leading to a 'git stash'
>> integration and a series I have waiting in the wings for a 'git
>> sparse-checkout' integration.
>>
>> However, I think we have a decent paved-path for a new contributor
>> to jump in and get started on the remaining commands. The granularity
>> means that the project has multiple milestones that can be hit
>> without an all-in-one series.
>>
> 
> Sounds good.
> 
> As I mentioned up thread, you could feel free to share the project
> description here or open a PR by adding it directly to this document:
> 
>   https://github.com/git/git.github.io/blob/master/SoC-2022-Ideas.md
> 
>   (note: currently returns a 404; it should work when the
>    related PR [pr-1] is merged)
> 
> Just to be sure, would you be willing to mentor in case a student
> picks this project?

>
> Hi all,
>
> GSoC 2022 is approaching. The timeline has been released [1].
> Mentoring organizations should submit applications between
> February 7 and 21 at 1800 UTC. So, I thought I'll kick off
> the discussion about our plans for GSoC 2022.
>
> First, are we interested in participating in the 2022 round of
> GSoC?
>
> If we are interested in participating we need:
>
>    - Volunteers who are wiling to act as mentors. I would be
>      willing to be volunteer myself as a mentor for one student.
>
>    - Microprojects: I believe we could repurpose the Outreachy
>      microproject ideas[2] for GSoC too. If others have suggestions
>      for microproject ideas, please share them.
>
>    - Project ideas: There are two mentioned in SoC-2021-Ideas[3]
>      but both were picked by GSoC students the previous year. So,
>      we would need new ones this year.
>
>      Taylor showed interest in a bitmap-related project during
>      the Outreachy application period [4]. Taylor, are you still
>      interested in mentoring a bitmap-related project? Would it
>      be possible for you to do so for the upcoming GSoC?
>
>

> Kaartic Sivaraam <kaartic.sivaraam@gmail.com> 于2022年1月27日周四 02:29写道：
>>
>> GSoC 2022 is approaching. The timeline has been released [1].
>> Mentoring organizations should submit applications between
>> February 7 and 21 at 1800 UTC. So, I thought I'll kick off
>> the discussion about our plans for GSoC 2022.
>>
>> First, are we interested in participating in the 2022 round of
>> GSoC?
>>
>> If we are interested in participating we need:
>>
>>     - Volunteers who are wiling to act as mentors. I would be
>>       willing to be volunteer myself as a mentor for one student.
>>
>>     - Microprojects: I believe we could repurpose the Outreachy
>>       microproject ideas[2] for GSoC too. If others have suggestions
>>       for microproject ideas, please share them.
>>
>>     - Project ideas: There are two mentioned in SoC-2021-Ideas[3]
>>       but both were picked by GSoC students the previous year. So,
>>       we would need new ones this year.
>>
>>       Taylor showed interest in a bitmap-related project during
>>       the Outreachy application period [4]. Taylor, are you still
>>       interested in mentoring a bitmap-related project? Would it
>>       be possible for you to do so for the upcoming GSoC?
>>
>>
> 
> I've been busy preparing for some internships lately and may not have
> enough time as a mentor to help this year's GSOC students, but I can
> occasionally provide my review for interesting projects this year.
> 

> If we are interested in participating we need:
>
>   - Volunteers who are wiling to act as mentors. I would be
>     willing to be volunteer myself as a mentor for one student.
>  
>   - Microprojects: I believe we could repurpose the Outreachy
>     microproject ideas[2] for GSoC too. If others have suggestions
>     for microproject ideas, please share them.
>
>   - Project ideas: There are two mentioned in SoC-2021-Ideas[3]
>     but both were picked by GSoC students the previous year. So,
>     we would need new ones this year.

>
>     Taylor showed interest in a bitmap-related project during
>     the Outreachy application period [4]. Taylor, are you still
>     interested in mentoring a bitmap-related project? Would it
>     be possible for you to do so for the upcoming GSoC?

> On 26/01/2022 18:29, Kaartic Sivaraam wrote:
>>
>>    - Project ideas: There are two mentioned in SoC-2021-Ideas[3]
>>      but both were picked by GSoC students the previous year. So,
>>      we would need new ones this year.
> Git Demonstration Repositories
> =============================
> 
> One idea/concept that I've had that might be suitable for a project
> either here or within the Google Season of Docs is to generate
> demonstration repositories that match the examples used in the
> documentation and parts of the test suite to help users explore and
> understand the concepts that are being documented in the man pages.
> 
> It's more than a classic coding problem because it impinges on a lot of
> subjective and admin areas but should be fairly beneficial for users.
> 

> The two examples that come to mind are the --show-pulls repo [1], and
> the 'history simplification' repo [2].
> 
> Using the test suite as the repo generator ensures the Demo Repos are
> reproducible/deterministic.
> 
> My latest thinking is that the repos would be held in-tree under
> /Documentation/RepoBundles and have been exported as bundles by an
> explicit test_export_function. Of key importance in the project is to
> minimise/eliminate any extra maintainer actions, so once a patch with a
> repo export is accepted, the flow through the delivery process to user
> installs is essentially the same as the man pages.
>

> > My latest thinking is that the repos would be held in-tree under
> > /Documentation/RepoBundles and have been exported as bundles by an
> > explicit test_export_function. Of key importance in the project is to
> > minimise/eliminate any extra maintainer actions, so once a patch with a
> > repo export is accepted, the flow through the delivery process to user
> > installs is essentially the same as the man pages.
>
> We could possibly include this one in the idea list but I suppose we might
> need a more concrete idea on what needs to be done as part of this project.
> That would help very much with guiding the student during the project
> period.
>
> We also need to know if the end result of such a project would be an
> acceptable contribution to the project. What it would take for the contribution
> to be acceptable? etc.

> Just to make it clear, I'm trying to think through on what we need to do to
> make this a GSoC idea proposal.
>
> > Not sure if that's fleshed out enough, or if it's at the wrong level for
> > GSoC, or If I'm right as a Mentor, but I'd be happy to co-mentor.
>
> That's nice. Thanks for volunteering.

> On Sat, Feb 12, 2022 at 7:12 PM Kaartic Sivaraam
> <kaartic.sivaraam@gmail.com> wrote:
>> On 03/02/22 7:42 pm, Philip Oakley wrote:
>>> My latest thinking is that the repos would be held in-tree under
>>> /Documentation/RepoBundles and have been exported as bundles by an
>>> explicit test_export_function. Of key importance in the project is to
>>> minimise/eliminate any extra maintainer actions, so once a patch with a
>>> repo export is accepted, the flow through the delivery process to user
>>> installs is essentially the same as the man pages.
>> We could possibly include this one in the idea list but I suppose we might
>> need a more concrete idea on what needs to be done as part of this project.
>> That would help very much with guiding the student during the project
>> period.
>>
>> We also need to know if the end result of such a project would be an
>> acceptable contribution to the project. What it would take for the contribution
>> to be acceptable? etc.
> Yeah, I think this is the main issue with this idea. We have a section
> named "Note about refactoring projects versus projects that implement
> new features" in
> https://git.github.io/General-Application-Information/ explaining why
> projects implementing new things can be a bad idea, and what can be
> done about it.

>
>> Just to make it clear, I'm trying to think through on what we need to do to
>> make this a GSoC idea proposal.
>>
>>> Not sure if that's fleshed out enough, or if it's at the wrong level for
>>> GSoC, or If I'm right as a Mentor, but I'd be happy to co-mentor.
>> That's nice. Thanks for volunteering.
> Yeah, thanks for volunteering anyway!

>
>> On a related note, the organization registrations are now open for this year.
>> The deadline is February 21 - 18:00 UTC. I'm not sure if anyone else is
>> planning on applying for Git. In case no one else beats me to it, I plan on
>> applying for Git around February 15 17:00 UTC.
> I was thinking about applying for Git, but I am glad that you plan to
> do it. I will try to add some project ideas to SoC-2022-Ideas.md
> before February 15.
>
> Thanks,
> Christian.

> On Sat, Feb 12, 2022 at 7:12 PM Kaartic Sivaraam
> <kaartic.sivaraam@gmail.com> wrote:
> 
>> On a related note, the organization registrations are now open for this year.
>> The deadline is February 21 - 18:00 UTC. I'm not sure if anyone else is
>> planning on applying for Git. In case no one else beats me to it, I plan on
>> applying for Git around February 15 17:00 UTC.
> 
> I was thinking about applying for Git, but I am glad that you plan to
> do it. I will try to add some project ideas to SoC-2022-Ideas.md
> before February 15.

>
> On 13/02/22 3:03 pm, Christian Couder wrote:
> > On Sat, Feb 12, 2022 at 7:12 PM Kaartic Sivaraam
> > <kaartic.sivaraam@gmail.com> wrote:
> >
> >> On a related note, the organization registrations are now open for this year.
> >> The deadline is February 21 - 18:00 UTC. I'm not sure if anyone else is
> >> planning on applying for Git. In case no one else beats me to it, I plan on
> >> applying for Git around February 15 17:00 UTC.
> >
> > I was thinking about applying for Git, but I am glad that you plan to
> > do it. I will try to add some project ideas to SoC-2022-Ideas.md
> > before February 15.
>
> Thanks for adding it! I've applied for Git in GSoC 2022. The application
> information could be found here:
>
>    https://git.github.io/SoC-2022-Org-Application/

> On Tue, Feb 15, 2022 at 9:32 PM Kaartic Sivaraam
> 
> Thanks, I accepted the invite!
> 
> Not sure we can invite possible mentors yet.
> 

>
> I'm glad to share the news that Git has been accepted as a mentoring
> organization [1] for GSoC!
>
> Since it is possible to invite mentors now, I've invited the mentors who
> have suggested ideas[2] so far. I've used the e-mail mentioned in the
> ideas page to send the invite.

> 
> 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.
> 

> 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?

>
> [1]: https://github.com/git/git.github.io/pull/540
>
> --
> Sivaraam
>
>

>
> 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.
>