[Outreachy] Introduction and Interest in Contributing to the Git Community

[Outreachy] Introduction and Interest in Contributing to the Git Community

[Isoken Ibizugbe]

Dear Git Community,

I hope this email finds you well. My name is Isoken Ibizugbe, and I am
writing to express my strong interest in joining the Git community as
a contributor to the FOSS project. I recently came across the project
description regarding "Moving existing tests to a unit testing
framework" and was particularly intrigued by the opportunity to be
part of this exciting endeavor.

As an aspiring software engineer, I have always admired the incredible
work done by the Git community in developing and maintaining this
widely-used version control system. The project's commitment to
fostering collaboration and innovation aligns perfectly with my values
and aspirations as a developer.

I understand that Christian Couder is the mentor for this project, and
I would be honored to have the opportunity to work under his guidance
and expertise. I would greatly appreciate any advice or direction he
can provide to help me get started on this journey.

I am eager to learn, collaborate with the community, and contribute
meaningfully to this project. Please let me know how I can formally
start my journey as a Git contributor and if there are any specific
guidelines or resources that you recommend for newcomers, as it was a
bit confusing process for me to join this mailing list.

Once again, thank you for your time and for providing an opportunity
for individuals like me to contribute to this remarkable project. I am
enthusiastic about the potential of this project and the journey
ahead.

Best regards,

Isoken

Re: [Outreachy] Introduction and Interest in Contributing to the Git Community

[Christian Couder]

Hi Isoken,

On Tue, Oct 3, 2023 at 12:21 PM Isoken Ibizugbe <isokenjune@gmail.com> wrote:
>
> Dear Git Community,
>
> I hope this email finds you well. My name is Isoken Ibizugbe, and I am
> writing to express my strong interest in joining the Git community as
> a contributor to the FOSS project. I recently came across the project
> description regarding "Moving existing tests to a unit testing
> framework" and was particularly intrigued by the opportunity to be
> part of this exciting endeavor.

Great, welcome to the Git community!

> As an aspiring software engineer, I have always admired the incredible
> work done by the Git community in developing and maintaining this
> widely-used version control system. The project's commitment to
> fostering collaboration and innovation aligns perfectly with my values
> and aspirations as a developer.
>
> I understand that Christian Couder is the mentor for this project, and
> I would be honored to have the opportunity to work under his guidance
> and expertise. I would greatly appreciate any advice or direction he
> can provide to help me get started on this journey.
>
> I am eager to learn, collaborate with the community, and contribute
> meaningfully to this project. Please let me know how I can formally
> start my journey as a Git contributor and if there are any specific
> guidelines or resources that you recommend for newcomers, as it was a
> bit confusing process for me to join this mailing list.

Sure, please take a look at the documentation we have on
https://git.github.io/, especially the pages and sections I mention
below.

First, we require that applicants make a small code contribution (we
call that a micro-project) to the Git project. This is explained here:

https://git.github.io/General-Microproject-Information/

If I have time, I will perhaps prepare a small list of possible
micro-project. For example we prepared this one for the Outreachy
Winter 2021-2022 round:

https://git.github.io/Outreachy-23-Microprojects/

but no promise. The "General-Microproject-Information" page has
information about how to find micro-project ideas anyway.

Now we have recently added a "Thoroughly check your eligibility in the
program" sub-section to that page. Please read it, check your
eligibility and confirm that you meet all the requirements soon.

Then there are links to tutorials and a number of other useful link
for Git developers on this page:

https://git.github.io/Hacking-Git/

Also the following page is useful as it contains more general
information about how to apply:

https://git.github.io/General-Application-Information/

> Once again, thank you for your time and for providing an opportunity
> for individuals like me to contribute to this remarkable project. I am
> enthusiastic about the potential of this project and the journey
> ahead.

Thanks for your enthusiasm,
Christian.

Re: [Outreachy] Introduction and Interest in Contributing to the Git Community

[Isoken Ibizugbe]

Good day,
I am interested in working on this issue
https://github.com/gitgitgadget/git/issues/1555 as a micro project. Is
it worth doing and appropriate for a micro project?

On Wed, Oct 4, 2023 at 11:21 AM Christian Couder
<christian.couder@gmail.com> wrote:
>
> Hi Isoken,
>
> On Tue, Oct 3, 2023 at 12:21 PM Isoken Ibizugbe <isokenjune@gmail.com> wrote:
> >
> > Dear Git Community,
> >
> > I hope this email finds you well. My name is Isoken Ibizugbe, and I am
> > writing to express my strong interest in joining the Git community as
> > a contributor to the FOSS project. I recently came across the project
> > description regarding "Moving existing tests to a unit testing
> > framework" and was particularly intrigued by the opportunity to be
> > part of this exciting endeavor.
>
> Great, welcome to the Git community!
>
> > As an aspiring software engineer, I have always admired the incredible
> > work done by the Git community in developing and maintaining this
> > widely-used version control system. The project's commitment to
> > fostering collaboration and innovation aligns perfectly with my values
> > and aspirations as a developer.
> >
> > I understand that Christian Couder is the mentor for this project, and
> > I would be honored to have the opportunity to work under his guidance
> > and expertise. I would greatly appreciate any advice or direction he
> > can provide to help me get started on this journey.
> >
> > I am eager to learn, collaborate with the community, and contribute
> > meaningfully to this project. Please let me know how I can formally
> > start my journey as a Git contributor and if there are any specific
> > guidelines or resources that you recommend for newcomers, as it was a
> > bit confusing process for me to join this mailing list.
>
> Sure, please take a look at the documentation we have on
> https://git.github.io/, especially the pages and sections I mention
> below.
>
> First, we require that applicants make a small code contribution (we
> call that a micro-project) to the Git project. This is explained here:
>
> https://git.github.io/General-Microproject-Information/
>
> If I have time, I will perhaps prepare a small list of possible
> micro-project. For example we prepared this one for the Outreachy
> Winter 2021-2022 round:
>
> https://git.github.io/Outreachy-23-Microprojects/
>
> but no promise. The "General-Microproject-Information" page has
> information about how to find micro-project ideas anyway.
>
> Now we have recently added a "Thoroughly check your eligibility in the
> program" sub-section to that page. Please read it, check your
> eligibility and confirm that you meet all the requirements soon.
>
> Then there are links to tutorials and a number of other useful link
> for Git developers on this page:
>
> https://git.github.io/Hacking-Git/
>
> Also the following page is useful as it contains more general
> information about how to apply:
>
> https://git.github.io/General-Application-Information/
>
> > Once again, thank you for your time and for providing an opportunity
> > for individuals like me to contribute to this remarkable project. I am
> > enthusiastic about the potential of this project and the journey
> > ahead.
>
> Thanks for your enthusiasm,
> Christian.

Re: [Outreachy] Introduction and Interest in Contributing to the Git Community

[Christian Couder]

On Sat, Oct 7, 2023 at 12:26 PM Isoken Ibizugbe <isokenjune@gmail.com> wrote:
>
> Good day,
> I am interested in working on this issue
> https://github.com/gitgitgadget/git/issues/1555 as a micro project. Is
> it worth doing and appropriate for a micro project?

(I have added Dscho, alias Johannes Schindelin, in Cc as he might know
more about this.)

I think it's worth doing, but I am not sure, as I think it might
generate regressions for a low number of users who might rely on
core.fileMode for some special use cases. (Not sure we would want to
support such hypothetical use cases though.)

Also it's not so simple to implement, you will have to dig a bit in
the code, and not just implement it, but likely also write tests for
it. So it's definitely significantly more complex than a simple "test
cleanup" micro-project. I might overlook things too.

But if you feel like it suits your skills well and are not afraid with
something a bit complex, I would think that you can go for it.

Best,
Christian.

Re: [Outreachy] Introduction and Interest in Contributing to the Git Community

[Isoken Ibizugbe]

Thank you Christian for the help, I have another idea for a micro
project "modernizing a test script". I have found test scripts that
needs modernizing , which is to rename the setup test 'prepare
reference tree' to 'setup'. Is it appropriate for a micro project and
should I go ahead with it.


On Sun, Oct 8, 2023 at 11:50 AM Christian Couder
<christian.couder@gmail.com> wrote:
>
> On Sat, Oct 7, 2023 at 12:26 PM Isoken Ibizugbe <isokenjune@gmail.com> wrote:
> >
> > Good day,
> > I am interested in working on this issue
> > https://github.com/gitgitgadget/git/issues/1555 as a micro project. Is
> > it worth doing and appropriate for a micro project?
>
> (I have added Dscho, alias Johannes Schindelin, in Cc as he might know
> more about this.)
>
> I think it's worth doing, but I am not sure, as I think it might
> generate regressions for a low number of users who might rely on
> core.fileMode for some special use cases. (Not sure we would want to
> support such hypothetical use cases though.)
>
> Also it's not so simple to implement, you will have to dig a bit in
> the code, and not just implement it, but likely also write tests for
> it. So it's definitely significantly more complex than a simple "test
> cleanup" micro-project. I might overlook things too.
>
> But if you feel like it suits your skills well and are not afraid with
> something a bit complex, I would think that you can go for it.
>
> Best,
> Christian.

Re: [Outreachy] Introduction and Interest in Contributing to the Git Community

[Christian Couder]

On Mon, Oct 9, 2023 at 3:33 PM Isoken Ibizugbe <isokenjune@gmail.com> wrote:
>
> Thank you Christian for the help, I have another idea for a micro
> project "modernizing a test script". I have found test scripts that
> needs modernizing , which is to rename the setup test 'prepare
> reference tree' to 'setup'. Is it appropriate for a micro project and
> should I go ahead with it.

I am not sure these kinds of renames are worth doing, but if you find
some clear doc or Junio saying that setup tests should be named
"setup", then that might be worth a try.

Re: [Outreachy] Introduction and Interest in Contributing to the Git Community

[Isoken Ibizugbe]

Hi Christian,

I hope you're doing well. I did some research, but unfortunately, I
couldn't find any clear documentation stating that setup tests should
be renamed. However, I did find another issue that I think I could
work on - 'Amend error messages and prompts of various (sub)commands
#635'. Should I go on with it?
Thank you for your help and your guidance, I appreciate it.

On Mon, Oct 9, 2023 at 2:38 PM Christian Couder
<christian.couder@gmail.com> wrote:
>
> On Mon, Oct 9, 2023 at 3:33 PM Isoken Ibizugbe <isokenjune@gmail.com> wrote:
> >
> > Thank you Christian for the help, I have another idea for a micro
> > project "modernizing a test script". I have found test scripts that
> > needs modernizing , which is to rename the setup test 'prepare
> > reference tree' to 'setup'. Is it appropriate for a micro project and
> > should I go ahead with it.
>
> I am not sure these kinds of renames are worth doing, but if you find
> some clear doc or Junio saying that setup tests should be named
> "setup", then that might be worth a try.

Re: [Outreachy] Introduction and Interest in Contributing to the Git Community

[Christian Couder]

Hi Isoken,

On Wed, Oct 11, 2023 at 7:48 AM Isoken Ibizugbe <isokenjune@gmail.com> wrote:
>
> Hi Christian,
>
> I hope you're doing well. I did some research,

Nice that you did some research and are mentioning it.

However please reply inline instead of top-posting (see
https://en.wikipedia.org/wiki/Posting_style). On
https://git.github.io/General-Microproject-Information/ there is a
section called "Some conventions and tips" which has a "Reply inline"
subsection about this.

> but unfortunately, I
> couldn't find any clear documentation stating that setup tests should
> be renamed.

Ok, so it's indeed better to find something else to work on.

> However, I did find another issue that I think I could
> work on - 'Amend error messages and prompts of various (sub)commands
> #635'. Should I go on with it?

Yeah, I think it's a good idea to work on this. See this discussion
thread where we give advice to Naomi about improving error messages as
microproject:

https://lore.kernel.org/git/CACS=G2zsJxP+NWuosZyrFGctJptHNYTrULErRo_Ns41KeMuMqA@mail.gmail.com/#r

Thanks,
Christian.

[Outreachy] Introduction and Interest in Contributing to the Git Community

[Doreen Wanyama]

Dear Git community,

I hope you are all doing well. I am writing to show my interest in
working in the project titled move existing tests to a unit testing
framework. This is because I have always been intrigued by the work
the git community does and hence I am interested in being part of
this. I have gone through the links provided about getting started on
this. I spent yesterday evening and a better part of today trying to
understand the resources. As of now I would like to start working on a
microproject since I understand this is the first step. I am finding
it difficult though to start. Someone to please help me understand how
I should go about this or how I should go about finding my first
microproject. Just a brief explanation will help.
Thank you in advance.

Best regards,

Doreen Wanyama

Re: [Outreachy] Introduction and Interest in Contributing to the Git Community

[Naomi Ibe]

Good morning, I followed this link
https://github.com/gitgitgadget/git/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22
We're not expected to pick something too tasking like working on heavy
code fixes, just pick a project you know you can round up and
contribute to. A project that doesn't involve plenty of major code
manipulations. For task submission, you'd need to learn how to
navigate "git format-patch" and "git send-email" commands(If you read
up on these two and their applications and you should be fine), or how
to use GitGitGadget pull requests to send code patches directly to
this mailing list (https://github.com/gitgitgadget/git)

On Mon, Oct 9, 2023 at 7:32 PM Doreen Wanyama <doreenwanyama20@gmail.com> wrote:
>
> Dear Git community,
>
> I hope you are all doing well. I am writing to show my interest in
> working in the project titled move existing tests to a unit testing
> framework. This is because I have always been intrigued by the work
> the git community does and hence I am interested in being part of
> this. I have gone through the links provided about getting started on
> this. I spent yesterday evening and a better part of today trying to
> understand the resources. As of now I would like to start working on a
> microproject since I understand this is the first step. I am finding
> it difficult though to start. Someone to please help me understand how
> I should go about this or how I should go about finding my first
> microproject. Just a brief explanation will help.
> Thank you in advance.
>
> Best regards,
>
> Doreen Wanyama

Re: [Outreachy] Introduction and Interest in Contributing to the Git Community

[Doreen Wanyama]

Thank you for this. Let me check them out


On Wed, Oct 11, 2023 at 9:07 AM Naomi Ibe <naomi.ibeh69@gmail.com> wrote:
>
> Good morning, I followed this link
> https://github.com/gitgitgadget/git/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22
> We're not expected to pick something too tasking like working on heavy
> code fixes, just pick a project you know you can round up and
> contribute to. A project that doesn't involve plenty of major code
> manipulations. For task submission, you'd need to learn how to
> navigate "git format-patch" and "git send-email" commands(If you read
> up on these two and their applications and you should be fine), or how
> to use GitGitGadget pull requests to send code patches directly to
> this mailing list (https://github.com/gitgitgadget/git)
>
> On Mon, Oct 9, 2023 at 7:32 PM Doreen Wanyama <doreenwanyama20@gmail.com> wrote:
> >
> > Dear Git community,
> >
> > I hope you are all doing well. I am writing to show my interest in
> > working in the project titled move existing tests to a unit testing
> > framework. This is because I have always been intrigued by the work
> > the git community does and hence I am interested in being part of
> > this. I have gone through the links provided about getting started on
> > this. I spent yesterday evening and a better part of today trying to
> > understand the resources. As of now I would like to start working on a
> > microproject since I understand this is the first step. I am finding
> > it difficult though to start. Someone to please help me understand how
> > I should go about this or how I should go about finding my first
> > microproject. Just a brief explanation will help.
> > Thank you in advance.
> >
> > Best regards,
> >
> > Doreen Wanyama