Re: GSoC 2019: Git's application submitted

>
> On Mon, Feb 11, 2019 at 6:48 AM Оля Тележная <olyatelezhnaya@gmail.com> wrote:
> >
> > > It would be nice to have a few more project ideas.
> >
> > I am not sure I have additional ideas for 3-month project for the intern, but
> >
> > > https://git.github.io/SoC-2019-Ideas/ currently lists only 2 possible
> > > projects:
> > >
> > > - Unify ref-filter formats with other --pretty formats (which is new)
> >
> > I am ready to act as a mentor in this task, I know that part of
> > project good enough.
>
> Great! I thought that it would be a good project for you to mentor and
> that's why I added it.
>
> By the way if you would prefer not to mentor the other project I can
> remove you from its possible mentor list.

>
> > I have additional related task: We have a function called
> > oid_object_info, it allows to download meta-info of the file. It was
> > used in cat-file, and inspired by that example, I improved ref-filter,
> > so now ref-filter works faster with it. Moreover, I have found that
> > oid_object_info allows to get the contents of the file. It was useful
> > in ref-filter, and actually it could be also useful in cat-file, but
> > we still download the file differently in cat-file, and it looks
> > awkward. I need to make just one last move to finish my patch: it will
> > close the task about migrating cat-file formatting logic to
> > ref-filter. But cat-file still will not use general way to download
> > the file. So, the task is to get rid of additional file-reading logic.
> > I guess this task is much smaller than original one, but at least the
> > student will have chance to finish it in 3 months.
> > My patch is here: https://github.com/git/git/pull/568
> > But I hope you will also see it this week in the mailing list.
> > Proposed task is in TODO in the end of ref-filter file.
>
> Do you mean the following comment from
> https://github.com/git/git/blob/c17ed82b8983ea7e172181d869966db546c6a528/ref-filter.c#L2393-L2399:
>
> /*
> * TODO: add support of %(*raw). Need to switch between oi and oi_deref for that.
> * TODO: split logic and printing (as it is done in format_ref_array_item and
> * show_ref_array_item). After that we could use %(raw) in all
> ref-filter commands.
> * TODO: rewrite print_object_or_die so that it will reuse result of general
> * oid_object_info_extended call.
> */
>
> ?
>
> It doesn't look like that's it. Could you just copy the task into an
> email? Or if you think it could be an idea for a GSoC project, could
> you send a pull request to add it to:
>
> https://github.com/git/git.github.io/blob/master/SoC-2019-Ideas.md
>
> ?

>
> > By the way, we had a letter from Google, it is said that our tasks are
> > sparsed. I am not sure I understand it correctly. Should I help the
> > project somehow to solve our issues?
>
> Yeah, we got en email from Stephanie Taylor saying that our idea list
> is quite sparse this year with a link to:
>
> https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list
>
> which contains:
>
> "Even if you are a new organization and only want one or two students
> showing that you have multiple ideas (a bare minimum of 4 solid ideas)
> is vital."
>
> They also want "more detailed description of [each] project (2-5
> sentences)", so I think we should work on that too.

>
> So yeah, any help to fix the idea list is very welcome!
>
> Thanks,
> Christian.