All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	Git Community <git@vger.kernel.org>
Cc: Christian Couder <christian.couder@gmail.com>,
	Junio C Hamano <gitster@pobox.com>, Taylor Blau <me@ttaylorr.com>,
	Emily Shaffer <emilyshaffer@google.com>,
	Atharva Raykar <raykar.ath@gmail.com>,
	ZheNing Hu <adlternative@gmail.com>,
	Victoria Dye <vdye@github.com>
Subject: Re: Git in GSoC 2022?
Date: Wed, 2 Feb 2022 12:42:18 -0500	[thread overview]
Message-ID: <356a8f62-9ab7-9c80-6d5f-337a2dc4049a@gmail.com> (raw)
In-Reply-To: <aa324a28-2336-c7b0-c1b7-ca4d440d9ff5@gmail.com>

On 1/29/2022 1:19 PM, Kaartic Sivaraam wrote:
> 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?

Victoria Dye and I are willing to co-mentor if a student picks this
project.

I'll make a PR that adds a description to the linked doc soon.
 
Thanks,
-Stolee


  reply	other threads:[~2022-02-02 17:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 18:29 Git in GSoC 2022? Kaartic Sivaraam
2022-01-26 20:05 ` Taylor Blau
2022-01-27  9:32   ` Christian Couder
2022-01-29 18:09     ` Kaartic Sivaraam
2022-02-13 13:35     ` Christian Couder
2022-02-15 20:34       ` Kaartic Sivaraam
2022-02-15 23:18       ` Hariom verma
2022-02-16 15:40         ` Christian Couder
2022-02-17 15:07           ` Hariom verma
2022-02-17 17:18           ` Kaartic Sivaraam
2022-02-18  2:14             ` Hariom verma
2022-02-26 20:29   ` Kaartic Sivaraam
2022-02-28 11:03     ` Christian Couder
2022-02-28 18:02       ` Kaartic Sivaraam
2022-03-01 13:51         ` Christian Couder
2022-03-04 18:34           ` Kaartic Sivaraam
2022-01-27  3:55 ` Bagas Sanjaya
2022-01-27  9:44   ` Christian Couder
     [not found]     ` <nycvar.QRO.7.76.6.2201281114440.347@tvgsbejvaqbjf.bet>
2022-01-29 18:36       ` Kaartic Sivaraam
2022-03-09 11:49         ` Johannes Schindelin
2022-03-09 19:57           ` Kaartic Sivaraam
2022-01-27 14:39 ` Derrick Stolee
2022-01-29 18:19   ` Kaartic Sivaraam
2022-02-02 17:42     ` Derrick Stolee [this message]
2022-01-27 15:00 ` ZheNing Hu
2022-01-29 17:43   ` Kaartic Sivaraam
2022-02-03 14:12 ` Philip Oakley
2022-02-12 18:12   ` Kaartic Sivaraam
2022-02-13  9:33     ` Christian Couder
2022-02-15 15:05       ` Philip Oakley
2022-02-15 20:32       ` Kaartic Sivaraam
2022-02-16 15:55         ` Christian Couder
2022-02-17 17:28           ` Kaartic Sivaraam
2022-03-07 19:38 ` Kaartic Sivaraam
2022-03-07 19:50   ` Derrick Stolee
2022-03-07 22:25   ` Hariom verma

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=356a8f62-9ab7-9c80-6d5f-337a2dc4049a@gmail.com \
    --to=stolee@gmail.com \
    --cc=adlternative@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=me@ttaylorr.com \
    --cc=raykar.ath@gmail.com \
    --cc=vdye@github.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.