threads / discuss / 56433

Git in Outreachy?

Subject: Git in Outreachy?

## tl;dr

23 messages between Sep 3, 2021 and Sep 29, 2021.

replies: 22people: 7as markdown or json

Taylor Blau· Sep 3, 2021, 02:40 UTC · lore

Are we interested in participating in the December 2021 round of Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community application deadline.

Christian, Peff, and I discussed off-list that we would each try to pull together funding for one intern from GitHub and GitLab respectively.

If we're interested, the project submission deadline is September 23rd [1]. By then, we'd need:

  - Volunteers to act as mentors
  - Updates to our applicant materials on git.github.io (project ideas,
    as well as potential microprojects).

Thanks, Taylor

[1]: https://www.outreachy.org/docs/community/#current-timeline
Emily Shaffer· Sep 3, 2021, 18:33 UTC · re: Taylor Blau · lore

Re: Git in Outreachy?

On Thu, Sep 2, 2021 at 7:41 PM Taylor Blau <ttaylorr@github.com> wrote:
Show 12 quoted lines
>
> Are we interested in participating in the December 2021 round of
> Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community
> application deadline.
>
> Christian, Peff, and I discussed off-list that we would each try to pull
> together funding for one intern from GitHub and GitLab respectively.
>
> If we're interested, the project submission deadline is September 23rd
> [1]. By then, we'd need:
>
>   - Volunteers to act as mentors

I'd be happy to mentor actively during the application stage, but I don't have bandwidth to host/mentor an accepted intern this term. I would also be happy to be CC'd, pinged, and so on on any reviews from interns which aren't receiving enough love.

>   - Updates to our applicant materials on git.github.io (project ideas,
>     as well as potential microprojects).
Will bring this up with Google folks today and see if we've got any ideas.
Thanks for mentioning it, Taylor.
Christian Couder· Sep 4, 2021, 04:30 UTC · re: Taylor Blau · lore

Re: Git in Outreachy?

On Fri, Sep 3, 2021 at 4:40 AM Taylor Blau <ttaylorr@github.com> wrote:
Show 7 quoted lines
>
> Are we interested in participating in the December 2021 round of
> Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community
> application deadline.
>
> Christian, Peff, and I discussed off-list that we would each try to pull
> together funding for one intern from GitHub and GitLab respectively.
Yeah, and we submitted an initial community application.
> If we're interested, the project submission deadline is September 23rd
> [1]. By then, we'd need:
>
>   - Volunteers to act as mentors
I am ok with co-mentoring 2 interns.
>   - Updates to our applicant materials on git.github.io (project ideas,
>     as well as potential microprojects).

About microprojects, I have been wondering if there are run_command*() calls that could be replaced by direct calls to C functions like what Junio did in ffcb4e94d3 (bisect: do not run show-branch just to show the current commit, 2021-07-27), and if that could make a good microproject.

About project ideas, maybe continuing Hariom Verma's GSoC 2020 "Unify ref-filter formats with other \-\-pretty formats" project could be and idea, though maybe it could interact too much with ZheNing Hu continuing his GSoC 2021 "Use ref-filter formats in `git cat-file`" project.

ZheNing Hu· Sep 4, 2021, 07:40 UTC · re: Christian Couder · lore

Re: Git in Outreachy?

Hi,
Christian Couder <christian.couder@gmail.com> 于2021年9月4日周六 下午12:30写道：
Show 33 quoted lines
>
> On Fri, Sep 3, 2021 at 4:40 AM Taylor Blau <ttaylorr@github.com> wrote:
> >
> > Are we interested in participating in the December 2021 round of
> > Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community
> > application deadline.
> >
> > Christian, Peff, and I discussed off-list that we would each try to pull
> > together funding for one intern from GitHub and GitLab respectively.
>
> Yeah, and we submitted an initial community application.
>
> > If we're interested, the project submission deadline is September 23rd
> > [1]. By then, we'd need:
> >
> >   - Volunteers to act as mentors
>
> I am ok with co-mentoring 2 interns.
>
> >   - Updates to our applicant materials on git.github.io (project ideas,
> >     as well as potential microprojects).
>
> About microprojects, I have been wondering if there are run_command*()
> calls that could be replaced by direct calls to C functions like what
> Junio did in ffcb4e94d3 (bisect: do not run show-branch just to show
> the current commit, 2021-07-27), and if that could make a good
> microproject.
>
> About project ideas, maybe continuing Hariom Verma's GSoC 2020 "Unify
> ref-filter formats with other \-\-pretty formats" project could be and
> idea, though maybe it could interact too much with ZheNing Hu
> continuing his GSoC 2021 "Use ref-filter formats in `git cat-file`"
> project.

If the project idea is related to Hariom or my GSoC project, I think I can provide a lot of help. :) I can help them as a mentor.

This may be a place to promote my patches: See [1][2][3]. It can provide some extra atoms for git cat-file --batch | --batch-check, like %(tree), %(author), %(tagger) etc. Although some performance optimizations have been made, It still has small performance gap.

If the community still expects git cat-file --batch to reuse the logic of ref-filter, I expect it to get the attention of reviewers.

The solutions I can think of to further optimize performance are:
1. Delay the evaluation of some ref-filter intermediate data.
2. Let ref-filter code reentrant and can be called in multi-threaded  to take
advantage of multi-core.
These ideas may be very difficult to implement now.

[1]: https://lore.kernel.org/git/CAOLTT8SxHuH2EbiSwQX6pyJJs5KyVuKx6ZOPxpzWLH+Tbz5F+A@mail.gmail.com/ [2]: https://lore.kernel.org/git/pull.1025.git.1629882532.gitgitgadget@gmail.com/ [3]: https://github.com/adlternative/git/commits/cat-file-reuse-ref-filter-logic

Thanks. -- ZheNing Hu

Jeff King· Sep 4, 2021, 12:50 UTC · re: ZheNing Hu · lore

Re: Git in Outreachy?

On Sat, Sep 04, 2021 at 03:40:41PM +0800, ZheNing Hu wrote:
Show 13 quoted lines
> This may be a place to promote my patches: See [1][2][3].
> It can provide some extra atoms for git cat-file --batch | --batch-check,
> like %(tree), %(author), %(tagger) etc. Although some performance
> optimizations have been made, It still has small performance gap.
> 
> If the community still expects git cat-file --batch to reuse the logic
> of ref-filter,
> I expect it to get the attention of reviewers.
> 
> The solutions I can think of to further optimize performance are:
> 1. Delay the evaluation of some ref-filter intermediate data.
> 2. Let ref-filter code reentrant and can be called in multi-threaded  to take
> advantage of multi-core.

I don't think trying to thread it will help much. For expensive formats, where we have to actually open and parse objects, in theory we could do that in parallel. But most of our time there is spent in zlib getting the object data, and that all needs to be done under a big lock.

For little formats (e.g., just printing "%(refname)"), we need to serialize the output anyway. So our unit of work is so tiny, I suspect that the threading overhead would be a net negative.

I was coincidentally looking at ref-filter last week, and it seemed to me that a lot of the slowness is because of the over-use of malloc (e.g., we allocate a substring for every atom_value, and then form them into a separate buffer). If we could parse the original format into a form that could be traversed without having to do further allocations, just writing directly to a strbuf (or even a file handle), I think that would be a big improvement.

I just posted the results of some of my experiments to the list:
  https://lore.kernel.org/git/YTNpQ7Od1U%2F5i0R7@coredump.intra.peff.net/

I don't think that gives any kind of useful base to build on, but it shows what's possible by skipping past various segments of the ref-filter code.

-Peff
ZheNing Hu· Sep 5, 2021, 08:58 UTC · re: Jeff King · lore

Re: Git in Outreachy?

Jeff King <peff@peff.net> 于2021年9月4日周六 下午8:50写道：
Show 22 quoted lines
>
> On Sat, Sep 04, 2021 at 03:40:41PM +0800, ZheNing Hu wrote:
>
> > This may be a place to promote my patches: See [1][2][3].
> > It can provide some extra atoms for git cat-file --batch | --batch-check,
> > like %(tree), %(author), %(tagger) etc. Although some performance
> > optimizations have been made, It still has small performance gap.
> >
> > If the community still expects git cat-file --batch to reuse the logic
> > of ref-filter,
> > I expect it to get the attention of reviewers.
> >
> > The solutions I can think of to further optimize performance are:
> > 1. Delay the evaluation of some ref-filter intermediate data.
> > 2. Let ref-filter code reentrant and can be called in multi-threaded  to take
> > advantage of multi-core.
>
> I don't think trying to thread it will help much. For expensive formats,
> where we have to actually open and parse objects, in theory we could do
> that in parallel. But most of our time there is spent in zlib getting
> the object data, and that all needs to be done under a big lock.
>

This big lock is "obj_read_lock()", right? If there are indeed the limitations of these locks, I am afraid that the parallel scheme is not good.

> For little formats (e.g., just printing "%(refname)"), we need to
> serialize the output anyway. So our unit of work is so tiny, I suspect
> that the threading overhead would be a net negative.
>
Make sence.
> I was coincidentally looking at ref-filter last week, and it seemed to
> me that a lot of the slowness is because of the over-use of malloc

Agree. malloc() and data-copy is the reason for the poor performance of ref-filter.

Show 6 quoted lines
> (e.g., we allocate a substring for every atom_value, and then form them
> into a separate buffer). If we could parse the original format into a
> form that could be traversed without having to do further allocations,
> just writing directly to a strbuf (or even a file handle), I think that
> would be a big improvement.
>

This patch has been tried to eliminate some malloc and data-copy: https://lore.kernel.org/git/3760ff032bb1dec3812881fd408f8d78ec125477.1629184489.git.gitgitgadget@gmail.com/ It is indeed possible to obtain some optimizations.

Show 9 quoted lines
> I just posted the results of some of my experiments to the list:
>
>   https://lore.kernel.org/git/YTNpQ7Od1U%2F5i0R7@coredump.intra.peff.net/
>
> I don't think that gives any kind of useful base to build on, but it
> shows what's possible by skipping past various segments of the
> ref-filter code.
>
> -Peff

Thanks. -- ZheNing Hu

Matheus Tavares Bernardino· Sep 6, 2021, 12:36 UTC · re: ZheNing Hu · lore

Re: Git in Outreachy?

On Sun, Sep 5, 2021 at 5:59 AM ZheNing Hu <adlternative@gmail.com> wrote:
Show 25 quoted lines
>
> Jeff King <peff@peff.net> 于2021年9月4日周六 下午8:50写道：
> >
> > On Sat, Sep 04, 2021 at 03:40:41PM +0800, ZheNing Hu wrote:
> >
> > > This may be a place to promote my patches: See [1][2][3].
> > > It can provide some extra atoms for git cat-file --batch | --batch-check,
> > > like %(tree), %(author), %(tagger) etc. Although some performance
> > > optimizations have been made, It still has small performance gap.
> > >
> > > If the community still expects git cat-file --batch to reuse the logic
> > > of ref-filter,
> > > I expect it to get the attention of reviewers.
> > >
> > > The solutions I can think of to further optimize performance are:
> > > 1. Delay the evaluation of some ref-filter intermediate data.
> > > 2. Let ref-filter code reentrant and can be called in multi-threaded  to take
> > > advantage of multi-core.
> >
> > I don't think trying to thread it will help much. For expensive formats,
> > where we have to actually open and parse objects, in theory we could do
> > that in parallel. But most of our time there is spent in zlib getting
> > the object data, and that all needs to be done under a big lock.
>
> This big lock is "obj_read_lock()", right?

The object reading code actually releases this lock before doing zlib decompression (and acquires it right after), to allow better multi-threaded performance.

However, it is unfortunately not so simple to call object reading routines in multi-threaded code, even with this lock. The lock mainly protects `oid_object_info_extended()` and its wrappers. Some global resources used by these functions are also accessed outside of them, which could lead to race conditions in threaded code.

That's why `builtin/grep.c` and `grep.c` have some explicit calls to `obj_read_lock()` outside `object-file.c` and `packfile.c`. (And it can be quite tricky to identity these cases.)

ZheNing Hu· Sep 7, 2021, 05:50 UTC · re: Matheus Tavares Bernardino · lore

Re: Git in Outreachy?

Matheus Tavares Bernardino <matheus.bernardino@usp.br> 于2021年9月6日周一 下午8:36写道：
Show 32 quoted lines
>
> On Sun, Sep 5, 2021 at 5:59 AM ZheNing Hu <adlternative@gmail.com> wrote:
> >
> > Jeff King <peff@peff.net> 于2021年9月4日周六 下午8:50写道：
> > >
> > > On Sat, Sep 04, 2021 at 03:40:41PM +0800, ZheNing Hu wrote:
> > >
> > > > This may be a place to promote my patches: See [1][2][3].
> > > > It can provide some extra atoms for git cat-file --batch | --batch-check,
> > > > like %(tree), %(author), %(tagger) etc. Although some performance
> > > > optimizations have been made, It still has small performance gap.
> > > >
> > > > If the community still expects git cat-file --batch to reuse the logic
> > > > of ref-filter,
> > > > I expect it to get the attention of reviewers.
> > > >
> > > > The solutions I can think of to further optimize performance are:
> > > > 1. Delay the evaluation of some ref-filter intermediate data.
> > > > 2. Let ref-filter code reentrant and can be called in multi-threaded  to take
> > > > advantage of multi-core.
> > >
> > > I don't think trying to thread it will help much. For expensive formats,
> > > where we have to actually open and parse objects, in theory we could do
> > > that in parallel. But most of our time there is spent in zlib getting
> > > the object data, and that all needs to be done under a big lock.
> >
> > This big lock is "obj_read_lock()", right?
>
> The object reading code actually releases this lock before doing zlib
> decompression (and acquires it right after), to allow better
> multi-threaded performance.
>
Yeah, I guess this unlock place is in unpack_loose_short_header().
Show 9 quoted lines
> However, it is unfortunately not so simple to call object reading
> routines in multi-threaded code, even with this lock. The lock mainly
> protects `oid_object_info_extended()` and its wrappers. Some global
> resources used by these functions are also accessed outside of them,
> which could lead to race conditions in threaded code.
>
> That's why `builtin/grep.c` and `grep.c` have some explicit calls to
> `obj_read_lock()` outside `object-file.c` and `packfile.c`. (And it
> can be quite tricky to identity these cases.)

Indeed, a large number of global variables in ref-filter code are worth eliminating.

Thanks. -- ZheNing Hu

Taylor Blau· Sep 4, 2021, 17:51 UTC · re: Taylor Blau · lore

Re: Git in Outreachy?

On Thu, Sep 02, 2021 at 10:40:45PM -0400, Taylor Blau wrote:
>   - Updates to our applicant materials on git.github.io (project ideas,
>     as well as potential microprojects).

One project I have been thinking of is a grab-bag of bitmap-related tasks. Some ideas for general improvements are:

  - Designing a new .bitmap format (perhaps using the new chunkfile
    API?) to allow us to add optional data to it in the future, like any
    information we might need for a stable object order.
  - Experimenting with replacing EWAH with different bitmap compression
    algorithms to see if we can increase read performance and/or
    decrease file size.
  - Tidy up and take measurements from my RFC patch(es) to add an
    extension which indicates which commits have bitmaps, and at what
    position. These were discussed beginning at:
        https://lore.kernel.org/git/YNuiM8TR5evSeNsN@nand.local/
    (but they seem to help most when there isn't too much traversal
    required between the ref tips and the bitmapped commits).
  - Rethinking bitmap selection to be more robust against repositories
    which have "spikey" ref tips and for which follow-on traversal is
    expensive.

These are all fairly open-ended, and so may not make a good Outreachy project. But I would be in favor of having more people familiar with and interested in reachability bitmaps.

I'll think of some others, too.

Thanks, Taylor

Taylor Blau· Sep 18, 2021, 16:10 UTC · re: Taylor Blau · lore

Re: Git in Outreachy?

[+everybody from upthread to cc]
On Thu, Sep 02, 2021 at 10:40:45PM -0400, Taylor Blau wrote:
> Are we interested in participating in the December 2021 round of
> Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community
> application deadline.

The project deadline of September 23rd is fast approaching, and we do not have any proposed projects or signed-up mentors.

If you are interested in mentoring, the time to sign-up and propose a project is definitely ASAP :-). You can do so by clicking "Submit a project proposal" at:

    https://www.outreachy.org/communities/cfp/git/

Thanks, Taylor

ZheNing Hu· Sep 20, 2021, 07:45 UTC · re: Taylor Blau · lore

Re: Git in Outreachy?

Taylor Blau <me@ttaylorr.com> 于2021年9月19日周日 上午12:10写道：
Show 17 quoted lines
>
> [+everybody from upthread to cc]
>
> On Thu, Sep 02, 2021 at 10:40:45PM -0400, Taylor Blau wrote:
> > Are we interested in participating in the December 2021 round of
> > Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community
> > application deadline.
>
> The project deadline of September 23rd is fast approaching, and we do
> not have any proposed projects or signed-up mentors.
>
> If you are interested in mentoring, the time to sign-up and propose a
> project is definitely ASAP :-). You can do so by clicking "Submit a
> project proposal" at:
>
>     https://www.outreachy.org/communities/cfp/git/
>

I haven't thought of any good projects for the time being, Christian, any ideas?

> Thanks,
> Taylor

Thanks. -- ZheNing Hu

Christian Couder· Sep 20, 2021, 14:52 UTC · re: ZheNing Hu · lore

Re: Git in Outreachy?

On Mon, Sep 20, 2021 at 9:45 AM ZheNing Hu <adlternative@gmail.com> wrote:
Show 21 quoted lines
>
> Taylor Blau <me@ttaylorr.com> 于2021年9月19日周日 上午12:10写道：
> >
> > [+everybody from upthread to cc]
> >
> > On Thu, Sep 02, 2021 at 10:40:45PM -0400, Taylor Blau wrote:
> > > Are we interested in participating in the December 2021 round of
> > > Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community
> > > application deadline.
> >
> > The project deadline of September 23rd is fast approaching, and we do
> > not have any proposed projects or signed-up mentors.
> >
> > If you are interested in mentoring, the time to sign-up and propose a
> > project is definitely ASAP :-). You can do so by clicking "Submit a
> > project proposal" at:
> >
> >     https://www.outreachy.org/communities/cfp/git/
>
> I haven't thought of any good projects for the time being,
> Christian, any ideas?
I already suggested the following project upthread:
Show 5 quoted lines
> > About project ideas, maybe continuing Hariom Verma's GSoC 2020 "Unify
> > ref-filter formats with other \-\-pretty formats" project could be and
> > idea, though maybe it could interact too much with ZheNing Hu
> > continuing his GSoC 2021 "Use ref-filter formats in `git cat-file`"
> > project.
and you replied:
> If the project idea is related to Hariom or my GSoC project, I think I can
> provide a lot of help. :)  I can help them as a mentor.
so I am ok to co-mentor this project with you.
If you are still ok, I will submit it.

I will also prepare soon a page with a few micro-projects. Of course more micro-project and regular project ideas are very welcome!

Christian Couder· Sep 20, 2021, 15:15 UTC · re: Christian Couder · lore

Re: Git in Outreachy?

On Mon, Sep 20, 2021 at 4:52 PM Christian Couder <christian.couder@gmail.com> wrote:

> I will also prepare soon a page with a few micro-projects. Of course
> more micro-project and regular project ideas are very welcome!
So here is the page:
https://git.github.io/Outreachy-23-Microprojects/

It's very similar as last year's page (https://git.github.io/Outreachy-21-Microprojects/). The differences are:

- added new "Replace a run_command*() call by direct calls to C functions" idea
- removed "Unify the meaning of -dirty between diff and describe" idea
as it looks a bit complex for a micro-project (though I can add it
back if someone disagree with this opinion).
ZheNing Hu· Sep 21, 2021, 05:41 UTC · re: Christian Couder · lore

Re: Git in Outreachy?

Christian Couder <christian.couder@gmail.com> 于2021年9月20日周一 下午11:15写道：
Show 11 quoted lines
>
> On Mon, Sep 20, 2021 at 4:52 PM Christian Couder
> <christian.couder@gmail.com> wrote:
>
> > I will also prepare soon a page with a few micro-projects. Of course
> > more micro-project and regular project ideas are very welcome!
>
> So here is the page:
>
> https://git.github.io/Outreachy-23-Microprojects/
>
s/Outreachy-23-Microprojects/Outreachy-22-Microprojects/
Show 8 quoted lines
> It's very similar as last year's page
> (https://git.github.io/Outreachy-21-Microprojects/). The differences
> are:
>
> - added new "Replace a run_command*() call by direct calls to C functions" idea
> - removed "Unify the meaning of -dirty between diff and describe" idea
> as it looks a bit complex for a micro-project (though I can add it
> back if someone disagree with this opinion).
Christian Couder· Sep 21, 2021, 15:39 UTC · re: ZheNing Hu · lore

Re: Git in Outreachy?

On Tue, Sep 21, 2021 at 7:41 AM ZheNing Hu <adlternative@gmail.com> wrote:
Show 15 quoted lines
>
> Christian Couder <christian.couder@gmail.com> 于2021年9月20日周一 下午11:15写道：
> >
> > On Mon, Sep 20, 2021 at 4:52 PM Christian Couder
> > <christian.couder@gmail.com> wrote:
> >
> > > I will also prepare soon a page with a few micro-projects. Of course
> > > more micro-project and regular project ideas are very welcome!
> >
> > So here is the page:
> >
> > https://git.github.io/Outreachy-23-Microprojects/
> >
>
> s/Outreachy-23-Microprojects/Outreachy-22-Microprojects/

I think the number is not linked to the year but rather to the number of Outreachy rounds since the beginning.

Last year's Winter round was round 21 and there has been a Summer round we didn't participate in, so I think the Winter 2021-2022 is round 23.

But yeah, it might be clearer to rename all the Outreachy files with names like Outreachy-Winter-21-22-Microprojects to avoid such confusion, as I think the round number is not used much anymore by anyone.

ZheNing Hu· Sep 22, 2021, 15:01 UTC · re: Christian Couder · lore

Re: Git in Outreachy?

Christian Couder <christian.couder@gmail.com> 于2021年9月21日周二 下午11:39写道：
Show 25 quoted lines
>
> On Tue, Sep 21, 2021 at 7:41 AM ZheNing Hu <adlternative@gmail.com> wrote:
> >
> > Christian Couder <christian.couder@gmail.com> 于2021年9月20日周一 下午11:15写道：
> > >
> > > On Mon, Sep 20, 2021 at 4:52 PM Christian Couder
> > > <christian.couder@gmail.com> wrote:
> > >
> > > > I will also prepare soon a page with a few micro-projects. Of course
> > > > more micro-project and regular project ideas are very welcome!
> > >
> > > So here is the page:
> > >
> > > https://git.github.io/Outreachy-23-Microprojects/
> > >
> >
> > s/Outreachy-23-Microprojects/Outreachy-22-Microprojects/
>
> I think the number is not linked to the year but rather to the number
> of Outreachy rounds since the beginning.
>
> Last year's Winter round was round 21 and there has been a Summer
> round we didn't participate in, so I think the Winter 2021-2022 is
> round 23.
>
Ok. I thought it was related to the year before.
> But yeah, it might be clearer to rename all the Outreachy files with
> names like Outreachy-Winter-21-22-Microprojects to avoid such
> confusion, as I think the round number is not used much anymore by
> anyone.

Thanks. -- ZheNing Hu

ZheNing Hu· Sep 21, 2021, 05:39 UTC · re: Christian Couder · lore

Re: Git in Outreachy?

Christian Couder <christian.couder@gmail.com> 于2021年9月20日周一 下午10:52写道：
Show 41 quoted lines
>
> On Mon, Sep 20, 2021 at 9:45 AM ZheNing Hu <adlternative@gmail.com> wrote:
> >
> > Taylor Blau <me@ttaylorr.com> 于2021年9月19日周日 上午12:10写道：
> > >
> > > [+everybody from upthread to cc]
> > >
> > > On Thu, Sep 02, 2021 at 10:40:45PM -0400, Taylor Blau wrote:
> > > > Are we interested in participating in the December 2021 round of
> > > > Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community
> > > > application deadline.
> > >
> > > The project deadline of September 23rd is fast approaching, and we do
> > > not have any proposed projects or signed-up mentors.
> > >
> > > If you are interested in mentoring, the time to sign-up and propose a
> > > project is definitely ASAP :-). You can do so by clicking "Submit a
> > > project proposal" at:
> > >
> > >     https://www.outreachy.org/communities/cfp/git/
> >
> > I haven't thought of any good projects for the time being,
> > Christian, any ideas?
>
> I already suggested the following project upthread:
>
> > > About project ideas, maybe continuing Hariom Verma's GSoC 2020 "Unify
> > > ref-filter formats with other \-\-pretty formats" project could be and
> > > idea, though maybe it could interact too much with ZheNing Hu
> > > continuing his GSoC 2021 "Use ref-filter formats in `git cat-file`"
> > > project.
>
> and you replied:
>
> > If the project idea is related to Hariom or my GSoC project, I think I can
> > provide a lot of help. :)  I can help them as a mentor.
>
> so I am ok to co-mentor this project with you.
>
> If you are still ok, I will submit it.
>
Yeah, I am ok. grateful.
> I will also prepare soon a page with a few micro-projects. Of course
> more micro-project and regular project ideas are very welcome!

I am still looking at the code in ref-filter.c these two days, I deeply doubt whether we can add a --no-sort option to git for-each-ref,

Inspired by Peff's experimental patches [1], I think the --no-sort option may improve the performance of ref-filter by avoiding the execution of ref_array_sort().

I don't know if this can be regarded as a micro-project.

This may require the help of this patch of mine: [2] which use list api for ref_sorting. This may can help eliminate unnecessary sorting.

[1] https://lore.kernel.org/git/YTTC2IUO1ZmTOEoR@coredump.intra.peff.net/ [2] https://lore.kernel.org/git/pull.1025.git.1629882532.gitgitgadget@gmail.com/

Thanks. -- ZheNing Hu

Christian Couder· Sep 21, 2021, 15:35 UTC · re: ZheNing Hu · lore

Re: Git in Outreachy?

On Tue, Sep 21, 2021 at 7:39 AM ZheNing Hu <adlternative@gmail.com> wrote:
>
> Christian Couder <christian.couder@gmail.com> 于2021年9月20日周一 下午10:52写道：
> >
> > On Mon, Sep 20, 2021 at 9:45 AM ZheNing Hu <adlternative@gmail.com> wrote:
Show 21 quoted lines
> > > I haven't thought of any good projects for the time being,
> > > Christian, any ideas?
> >
> > I already suggested the following project upthread:
> >
> > > > About project ideas, maybe continuing Hariom Verma's GSoC 2020 "Unify
> > > > ref-filter formats with other \-\-pretty formats" project could be and
> > > > idea, though maybe it could interact too much with ZheNing Hu
> > > > continuing his GSoC 2021 "Use ref-filter formats in `git cat-file`"
> > > > project.
> >
> > and you replied:
> >
> > > If the project idea is related to Hariom or my GSoC project, I think I can
> > > provide a lot of help. :)  I can help them as a mentor.
> >
> > so I am ok to co-mentor this project with you.
> >
> > If you are still ok, I will submit it.
>
> Yeah, I am ok. grateful.
I submitted it. You should see it and be able to register as a co-mentor there:
https://www.outreachy.org/communities/cfp/git/
Show 8 quoted lines
> I am still looking at the code in ref-filter.c these two days, I deeply
> doubt whether we can add a --no-sort option to git for-each-ref,
>
> Inspired by Peff's experimental patches [1], I think the --no-sort option
> may improve the performance of ref-filter by avoiding the execution
> of ref_array_sort().
>
> I don't know if this can be regarded as a micro-project.

If you think that such a patch is likely to be accepted and that would take you less than a few hours to prepare and submit, then it can probably be regarded as a micro-project, and you are welcome to send a pull request to add it to the micro-project page.

Show 6 quoted lines
> This may require the help of this patch of mine: [2]
> which use list api for ref_sorting. This may can help eliminate unnecessary
> sorting.
>
> [1] https://lore.kernel.org/git/YTTC2IUO1ZmTOEoR@coredump.intra.peff.net/
> [2] https://lore.kernel.org/git/pull.1025.git.1629882532.gitgitgadget@gmail.com/
Then please add this information to the description of the micro-project.
Thanks!
ZheNing Hu· Sep 22, 2021, 14:58 UTC · re: Christian Couder · lore

Re: Git in Outreachy?

Christian Couder <christian.couder@gmail.com> 于2021年9月21日周二 下午11:35写道：
Show 33 quoted lines
>
> On Tue, Sep 21, 2021 at 7:39 AM ZheNing Hu <adlternative@gmail.com> wrote:
> >
> > Christian Couder <christian.couder@gmail.com> 于2021年9月20日周一 下午10:52写道：
> > >
> > > On Mon, Sep 20, 2021 at 9:45 AM ZheNing Hu <adlternative@gmail.com> wrote:
>
> > > > I haven't thought of any good projects for the time being,
> > > > Christian, any ideas?
> > >
> > > I already suggested the following project upthread:
> > >
> > > > > About project ideas, maybe continuing Hariom Verma's GSoC 2020 "Unify
> > > > > ref-filter formats with other \-\-pretty formats" project could be and
> > > > > idea, though maybe it could interact too much with ZheNing Hu
> > > > > continuing his GSoC 2021 "Use ref-filter formats in `git cat-file`"
> > > > > project.
> > >
> > > and you replied:
> > >
> > > > If the project idea is related to Hariom or my GSoC project, I think I can
> > > > provide a lot of help. :)  I can help them as a mentor.
> > >
> > > so I am ok to co-mentor this project with you.
> > >
> > > If you are still ok, I will submit it.
> >
> > Yeah, I am ok. grateful.
>
> I submitted it. You should see it and be able to register as a co-mentor there:
>
> https://www.outreachy.org/communities/cfp/git/
>
Yes, I saw it. Thanks!
Show 14 quoted lines
> > I am still looking at the code in ref-filter.c these two days, I deeply
> > doubt whether we can add a --no-sort option to git for-each-ref,
> >
> > Inspired by Peff's experimental patches [1], I think the --no-sort option
> > may improve the performance of ref-filter by avoiding the execution
> > of ref_array_sort().
> >
> > I don't know if this can be regarded as a micro-project.
>
> If you think that such a patch is likely to be accepted and that would
> take you less than a few hours to prepare and submit, then it can
> probably be regarded as a micro-project, and you are welcome to send a
> pull request to add it to the micro-project page.
>

Eh, It may not be simple, I can try to solve it by myself first, but I think it is appropriate for novices to complete this mini-project to understand the technical details of ref-filter.

Show 9 quoted lines
> > This may require the help of this patch of mine: [2]
> > which use list api for ref_sorting. This may can help eliminate unnecessary
> > sorting.
> >
> > [1] https://lore.kernel.org/git/YTTC2IUO1ZmTOEoR@coredump.intra.peff.net/
> > [2] https://lore.kernel.org/git/pull.1025.git.1629882532.gitgitgadget@gmail.com/
>
> Then please add this information to the description of the micro-project.
>
ok!
> Thanks!

Thanks. -- ZheNing Hu

Taylor Blau· Sep 21, 2021, 21:25 UTC · re: Taylor Blau · lore

Re: Git in Outreachy?

On Sat, Sep 18, 2021 at 12:10:40PM -0400, Taylor Blau wrote:
Show 7 quoted lines
> On Thu, Sep 02, 2021 at 10:40:45PM -0400, Taylor Blau wrote:
> > Are we interested in participating in the December 2021 round of
> > Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community
> > application deadline.
>
> The project deadline of September 23rd is fast approaching, and we do
> not have any proposed projects or signed-up mentors.

It looks like the deadline was extended to September 29th at 4pm UTC. So we have a little less than an extra week. The below link is still the right place to submit proposals:

    https://www.outreachy.org/communities/cfp/git/

Thanks, Taylor

Christian Couder· Sep 29, 2021, 14:18 UTC · re: Taylor Blau · lore

Re: Git in Outreachy?

Hi Taylor and all,
On Tue, Sep 21, 2021 at 11:26 PM Taylor Blau <me@ttaylorr.com> wrote:
Show 8 quoted lines
> > The project deadline of September 23rd is fast approaching, and we do
> > not have any proposed projects or signed-up mentors.
>
> It looks like the deadline was extended to September 29th at 4pm UTC. So
> we have a little less than an extra week. The below link is still the
> right place to submit proposals:
>
>     https://www.outreachy.org/communities/cfp/git/

So the deadline for mentors to submit projects has been extended again to Wednesday, October 6 at 4pm UTC.

We still have only one project ("Unify ref-filter formats with other pretty formats", that ZheNing and me are willing to co-mentor) submitted though.

I plan to submit another project that I will be willing to (co-)mentor before the deadline.

It's confirmed that GitLab will sponsor one intern.

Best, Christian.

Taylor Blau· Sep 29, 2021, 17:34 UTC · re: Christian Couder · lore

Re: Git in Outreachy?

On Wed, Sep 29, 2021 at 04:18:43PM +0200, Christian Couder wrote:
Show 15 quoted lines
> Hi Taylor and all,
>
> On Tue, Sep 21, 2021 at 11:26 PM Taylor Blau <me@ttaylorr.com> wrote:
>
> > > The project deadline of September 23rd is fast approaching, and we do
> > > not have any proposed projects or signed-up mentors.
> >
> > It looks like the deadline was extended to September 29th at 4pm UTC. So
> > we have a little less than an extra week. The below link is still the
> > right place to submit proposals:
> >
> >     https://www.outreachy.org/communities/cfp/git/
>
> So the deadline for mentors to submit projects has been extended again
> to Wednesday, October 6 at 4pm UTC.

Thanks for mentioning. I got an email from Sage announcing this yesterday, but neglected to share it here.

> We still have only one project ("Unify ref-filter formats with other
> pretty formats", that ZheNing and me are willing to co-mentor)
> submitted though.

I plan to submit and mentor a project myself. (I'm thinking that I'll do a grab-bag of bitmap-related items that I'd like to see implemented, but that may be too open-ended for a successful Outreachy project).

GitHub is planning on sponsoring an intern, too, but I haven't finalized the paperwork.

Thanks, Taylor

Taylor Blau· Sep 29, 2021, 20:30 UTC · re: Taylor Blau · lore

Re: Git in Outreachy?

On Wed, Sep 29, 2021 at 01:34:08PM -0400, Taylor Blau wrote:
Show 7 quoted lines
> > We still have only one project ("Unify ref-filter formats with other
> > pretty formats", that ZheNing and me are willing to co-mentor)
> > submitted though.
>
> I plan to submit and mentor a project myself. (I'm thinking that I'll do
> a grab-bag of bitmap-related items that I'd like to see implemented, but
> that may be too open-ended for a successful Outreachy project).

I think (open-ended as it may be) that I'll be able to provide the most guidance for a bitmap-related project. I submitted that as a intern project, which anybody logged in through the Outreachy site can view here:

  https://www.outreachy.org/apply/project-selection/#git

Thanks, Taylor

← back to recent threads