git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Tapasweni Pathak <tapaswenipathak@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Hariom verma <hariom18599@gmail.com>,
	Taylor Blau <me@ttaylorr.com>,
	git@vger.kernel.org
Subject: Re: Unify ref-filter formats with other pretty formats: GSoC'22
Date: Fri, 22 Apr 2022 15:58:28 +0530	[thread overview]
Message-ID: <CALOmtcWTw=bo=AqGBN8z9Hf602Peu9AVngwKUZZsCt0cr8jbDg@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD29NgffUBz0CMKyt901Z7Bj5osoBT-4Mfxfp0h_4Qo+Qw@mail.gmail.com>

Hi Christian,

On Fri, Apr 22, 2022 at 2:44 PM Christian Couder
<christian.couder@gmail.com> wrote:
>
> On Wed, Apr 20, 2022 at 1:49 PM Tapasweni Pathak
> <tapaswenipathak@gmail.com> wrote:
> > On Wed, Apr 20, 2022 at 1:45 PM Christian Couder
> > <christian.couder@gmail.com> wrote:
> > > On Tue, Apr 19, 2022 at 1:54 PM Tapasweni Pathak
> > > <tapaswenipathak@gmail.com> wrote:
>
> > > Maybe you could work on continuing ZheNing Hu's work on the "Use
> > > ref-filter formats in `git cat-file`" GSoC 2021 project, which is a
> > > bit related. This is a very difficult task though, as it requires
> > > dealing with tricky performance issues. And the changes you make might
> > > conflict with those made by someone working on the "Unify ref-filter
> > > formats with other pretty formats" GSoC 2022 project.
> >
> > I would like to work on this with a planner, separately, we can see
> > what should be adapted in mine to have everything go smooth and
> > GSoC'22 project especially.
>
> As you seem interested in other things too, I think it's better to
> avoid this one for now. It could be a bad experience as it's a really
> difficult subject, and I think it would be much better for you to
> start with something easier and smaller.

I must insist; would be interested in a planner and document prep for
the project, I can see some details
- https://git.github.io/SoC-2021-Ideas/
- https://lore.kernel.org/git/pull.989.git.1625155693.gitgitgadget@gmail.com/
- https://docs.google.com/document/d/119k-Xa4CKOt5rC1gg1cqPr6H3MvdgTUizndJGAo1Erk/edit
- https://github.blog/2021-11-15-highlights-from-git-2-34/
- https://lore.kernel.org/git/CAOLTT8S8TxuTmddGp2WGoPtTc3gwGXzizBfVzKd87otRw7Dpiw@mail.gmail.com/

to set things for the next steps, let me know if you strongly feel to
not take up the problem right away.
>
> > > Now if we don't find a good applicant for this latter project, you
> > > might of course work on it. The selected Proposals and Applicant will
> > > be known on May 20 though. So if that would be your prefered project,
> > > you would have to wait until then and hope that we don't select
> > > anyone.
> >
> > Happy to take it up, if it remains open.
>
> Great! Let's see on May 20 if it's still open and you haven't found
> anything else to work on in the meantime.
>
> > > See: https://lore.kernel.org/git/xmqq35iaz6n3.fsf@gitster.g/
> > >
> > > I think he wants someone to add a `train` command to `git rerere`
> > > based on what "contrib/rerere-train.sh" does.
> > >
> > > As you can see "contrib/rerere-train.sh" is a 102 line long shell
> > > script, so converting it to a new `train` command in
> > > "builtin/rerere.c" seems like a not very difficult and not too big
> > > task (especially if done the same way as the script). Junio will
> > > likely be involved in this, as it looks like he is interested in it.
> >
> > Can I take it up immediately, if Junio is not working on it?
> > ++gitster@pobox.com. Hi Junio. Do you suggest otherwise?
>
> I don't want to speak for him, but I don't think he is working on it.
> In fact, as he suggested it for a GSoC, I think he doesn't plan to
> work on it soon. Also he might not answer often to emails that aren't
> also sent to the mailing list.
>
> So if you want to work on it, I would suggest starting right away. You
> can of course send an email on the mailing list to let people know
> that you want to start working on this and to check if anyone is
> already working on it or has suggestions about it.

++git@vger.kernel.org. :)
>
> > > Another thing that was discussed recently is that the git-scm.org web
> > > site could be converted to not use Heroku anymore. If you prefer
> > > working on this kind of web oriented thing, this could be another
> > > possibility.
> >
> > I have worked a lot on web-based projects, SAAS, IAAS, PAAS, FAAS,
> > would it be better to share a proposal of comparison of those keeping
> > git-scm.org in mind, or is it pre-decided where git-scm.org will make
> > its new home/work?
> >
> > This shouldn't take more than 3 working days with no downtimes.
>
> Nice that you have some experience in this!
>
> I added Taylor in Cc as he is involved in this and might answer your
> questions much better than me. Now if you are interested in it, I
> suggest starting right away and perhaps also sending an email to the
> mailing list asking your questions and asking for advice there.

Hi Taylor. Great if you can let me know what you want to see
happening, and if we can discuss tech specifications, you have already
decided or plan to.

       reply	other threads:[~2022-04-22 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALOmtcX4+ON7+J7K9X4rSYfWYnkciJdFE=v=Oeb7rUqwRt8_JA@mail.gmail.com>
     [not found] ` <CA+CkUQ8hf5m0GZEwcyqLgxMw1vavYey_R4P7oq8=OXc7iAj6MA@mail.gmail.com>
     [not found]   ` <CALOmtcW=2skmUPXpnano=21i38b7sq2MEWQjH5yF2jLacZ8sQw@mail.gmail.com>
     [not found]     ` <CA+CkUQ9ZnBXU8E=XKTk95hwM4qtZ1M_nX3LTCr5q5njPG3Es5Q@mail.gmail.com>
     [not found]       ` <CALOmtcX7amyw3cAuthMPuagUVzJghybHFNy8ciB50yC5SCUwow@mail.gmail.com>
     [not found]         ` <CA+CkUQ-YgmRa7ysP30GbkX07Cu_=EM5X66w3Vk=TpshP9xoi_w@mail.gmail.com>
     [not found]           ` <CAP8UFD2uUFveiGDAbxObDOh_krmexuLe860Gu397e9KddH0UCg@mail.gmail.com>
     [not found]             ` <CALOmtcVN8K59Zkv7XKM7w2zFCbdWKfKr=97-E3306nQHm4Zw=A@mail.gmail.com>
     [not found]               ` <CAP8UFD1kinAwq7AL68QXqFR_dxkNFaTp2vP_DUU0KKqkbsXCDQ@mail.gmail.com>
     [not found]                 ` <CALOmtcWaQgrPTkRA6F8bL3Hp64cOxYrB4xHUa1WC+P34ZdFEbw@mail.gmail.com>
     [not found]                   ` <CAP8UFD1HGbbmJWB_TksGVLa-7nNBz5pdFi59Y7LP3EODF9Lztg@mail.gmail.com>
     [not found]                     ` <CALOmtcWFwfV11Vxf1xd_fC=HYGPNO1PtKT=E=-A104cGnAbv4g@mail.gmail.com>
     [not found]                       ` <CAP8UFD29NgffUBz0CMKyt901Z7Bj5osoBT-4Mfxfp0h_4Qo+Qw@mail.gmail.com>
2022-04-22 10:28                         ` Tapasweni Pathak [this message]
2022-04-22 18:03                           ` Unify ref-filter formats with other pretty formats: GSoC'22 Junio C Hamano
2022-04-26  9:54                           ` Christian Couder
2022-05-31 16:24                             ` Tapasweni Pathak
     [not found]                               ` <YxvBBZkN6yxUquou@nand.local>
2022-09-12 13:15                                 ` Tapasweni Pathak
     [not found]                         ` <CAP8UFD1f6KCO+=+ZoUFr06XUgEZYOZi8G0V+QKCK=bNbAE9VrQ@mail.gmail.com>
2022-04-22 10:39                           ` Tapasweni Pathak
2022-04-25  8:37                             ` Christian Couder
2022-05-31 16:13                               ` Tapasweni Pathak
     [not found]                           ` <Ymc2Y+U4HQpgD7PE@nand.local>
2022-05-31 16:21                             ` Tapasweni Pathak

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to='CALOmtcWTw=bo=AqGBN8z9Hf602Peu9AVngwKUZZsCt0cr8jbDg@mail.gmail.com' \
    --to=tapaswenipathak@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hariom18599@gmail.com \
    --cc=me@ttaylorr.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).