threads / discuss / 65036

[GSoC] Lambert Presentation

Subject: [GSoC] Lambert Presentation

## tl;dr

4 messages between Feb 21, 2026 and Feb 22, 2026.

replies: 3people: 3as markdown or json

Lambert Duclos· Feb 21, 2026, 16:57 UTC · lore

Hi everyone,

I’m Lambert (he/him), and that’s the name I’d like you to use. All co-mentors are included in To/Cc as suggested.

I can confirm that I meet the eligibility requirements for GSoC.

So far, I’ve:

- Read the community documentation, including MyFirstContribution.txt
and the General Microproject Information guide.

- Built Git from source.

- Submitted my first patch using GitGitGadget:
https://github.com/gitgitgadget/git/pull/2049

I’m really excited to keep contributing and to learn more about the process. Please let me know what you think would be a good next step for me.

Thanks! Lambert

Usman Akinyemi· Feb 21, 2026, 17:30 UTC · re: Lambert Duclos · lore

Re: [GSoC] Lambert Presentation

On Sat, Feb 21, 2026 at 10:27 PM Lambert Duclos <lambertddg@gmail.com> wrote:

>
> Hi everyone,

Hello Lambert, welcome to the Git community.

Show 5 quoted lines

>
> I’m Lambert (he/him), and that’s the name I’d like you to use. All
> co-mentors are included in To/Cc as suggested.
>
> I can confirm that I meet the eligibility requirements for GSoC.

Good.

Show 10 quoted lines

>
> So far, I’ve:
>
> - Read the community documentation, including MyFirstContribution.txt
> and the General Microproject Information guide.
>
> - Built Git from source.
>
> - Submitted my first patch using GitGitGadget:
> https://github.com/gitgitgadget/git/pull/2049

Git uses a mailing list and GitGitGadget is a way to send patches to the mailing list through Github, there are other ways like through the terminal.

So, your patches are on Github not yet in the mailing list for review.

You have to use /submit commands to allow GitGitGadget to send your patches to the mailing list. You can use /preview to see how your patches look.

Also, you need to read [1] to understand how to write a good commit message when sending patches to the Git community. You should always sign off your commit and that is missing in your current patches.

[1]: https://git-scm.com/docs/SubmittingPatches

Show 7 quoted lines

>
> I’m really excited to keep contributing and to learn more about the
> process. Please let me know what you think would be a good next step
> for me.
>
> Thanks!
> Lambert

Thanks for your interest in contributing to the Git community.

Usman Akinyemi· Feb 21, 2026, 17:31 UTC · re: Usman Akinyemi · lore

Re: [GSoC] Lambert Presentation

Show 6 quoted lines

> mailing list. You can use /preview to see how your patches look.
>
> Also, you need to read [1] to understand how to write a good commit message when
> sending patches to the Git community. You should always sign off your
> commit and that
> is missing in your current patches.

Disregard this, I see your patches now with the Signed-Off. Good job.

Show 12 quoted lines

>
>
> [1]: https://git-scm.com/docs/SubmittingPatches
> >
> > I’m really excited to keep contributing and to learn more about the
> > process. Please let me know what you think would be a good next step
> > for me.
> >
> > Thanks!
> > Lambert
> Thanks for your interest in contributing to the Git community.
> >

Lucas Seiki Oshiro· Feb 22, 2026, 21:28 UTC · re: Lambert Duclos · lore

Re: [GSoC] Lambert Presentation

> Hi everyone,

Hi, Lambert!

> - Submitted my first patch using GitGitGadget:
> https://github.com/gitgitgadget/git/pull/2049

Even though it's ok to send patches through GitGitGadget, your patches will be reviewed through the Git mailing list. This way, it would be better to reference the message sent by GitGitGadget rather than the pull request. In this case, the message is this: pull.2049.git.1771694893208.gitgitgadget@gmail.com

> I’m really excited to keep contributing and to learn more about the
> process. Please let me know what you think would be a good next step
> for me.

Take a look at the General Application Information [1]. You can send other patches that you find relevant and join the discussions on the mailing lists.

I'm one of the GSoC'25 alumni, and you can see in my blog what I did before I was accepted [2]. You can also take a look on the other GSoC alumni and see what they did to have other ideas.

You can also send the draft of your GSoC proposal to see if you are going in the right direction.

[1] https://git.github.io/General-Application-Information/ [2] https://lucasoshiro.github.io/gsoc-en/ [3] https://git.github.io/GSoC-Participants/