Re: Unify ref-filter formats with other pretty formats: GSoC'22

[Christian Couder <christian.couder@gmail.com>]

Hi Tapasweni,

On Fri, Apr 22, 2022 at 12:29 PM Tapasweni Pathak
<tapaswenipathak@gmail.com> wrote:
> 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:

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

I am not sure what "planner" and "document prep" mean exactly to you,
and what "the problem" is. I replied to your other email and I hope it
helps, but maybe in my replies here and to your other email I am
missing something. In this case please let me know.

We are ok to describe projects in a few sentences or paragraphs, like
in https://git.github.io/SoC-2021-Ideas/ where we describe the
projects we propose, but for GSoC and Outreachy, applicants interested
in a project are those who actually write the proposals which usually
include a timeline.

I am sure not, but it looks to me like you would like us (not you) to
write a full proposal including a timeline.

For example the proposal in
https://docs.google.com/document/d/119k-Xa4CKOt5rC1gg1cqPr6H3MvdgTUizndJGAo1Erk/edit
which includes a timeline was fully writen by ZheNing Hu, and was then
accepted by us, so that ZheNing Hu could then participate in the GSoC
2021 and start the actual work.

https://lore.kernel.org/git/pull.989.git.1625155693.gitgitgadget@gmail.com/
shows some of the work he did and sent to the mailing list as part of
the GSoC.

https://github.blog/2021-11-15-highlights-from-git-2-34/ is not
especially related to any GSoC.

https://lore.kernel.org/git/CAOLTT8S8TxuTmddGp2WGoPtTc3gwGXzizBfVzKd87otRw7Dpiw@mail.gmail.com/
is a discussion about the Outreachy Winter 2021-2022 round (not GSoC)
where ZheNing Hu accepted to co-mentor with me someone who would work
on continuing Hariom's GSoC 2020 "Unify ref-filter formats with other
\-\-pretty formats" project. As there were no Outreachy applicants
interested in working on this, we proposed this same project to the
upcoming GSoC.

So I don't see any problem that we should take up with the links you
listed. If someone would have it write a full proposal and a detailed
timeline it would be you, not us. Of course, as you propose to work
outside GSoC and Outreachy, we don't require that from you, because
you would not be part of any such official program and wouldn't get
paid.

I hope I don't misunderstand what you said.