Re: Contribution for an Open Source Git

Re: Contribution for an Open Source Git

[Gaux Nation]

https://drive.google.com/open?id=0B_6x2GR6_FTMc2RERHlJZVpQc0RIMFMxNi13bE95UU1fZmp3
On Tue, Aug 21, 2018 at 10:54 PM Gaux Nation <satingaux@gmail.com> wrote:
>
> Hey there,
>
> The name is Sachin Sharma(19 yrs old, student, India) and passionate
> for innovative technology and digital content.
>
>
>
> Why Open Source?
>
> Open Source connects like-minded genes in the whole world. This lets
> contributors to get engaged with the groups of different communities.
>
>
>
> Why Git?
>
> I just love the platform your organization had built,
>
> 1.Branching and merging.
>
> 2.Small and fast.
>
> 3. Distributed.
>
> 4.Free and Open Source.*
>
>
>
> Why I?
>
> I’m a new bee, therefore I might not have that long list of projects
> but I have that level of commitment, attitude and ability to follow
> directions which are expected from a student.
>
>
>
> What do I need from Git?
>
> Guidance, neither too deep nor too short(optimum).
>
> How can I get started for a contribution?
>
> What are the necessary technical skills needed for a contribution to Git?
>
>
>
>
>
>
>
> GitHub:  satingaux@github
>
> Contact: 8572020330,9138258580.
>
>
>
> Quote: I might not get selected, but an interaction with you will make my day.
>
>        I assure you, sir I will work hard to give my 100%.
>
>        I feel blessed if I got chance for contributing to an open
> source community.
>
>
>
>
>
> Technical Skills: JAVA, JavaScript, SQL, C, C++.
>
>
>
> Thank you

Re: Contribution for an Open Source Git

[Stefan Beller]

Welcome!

In the Git community we do not ask permission to write code, but just do it.
See https://github.com/git/git/blob/master/Documentation/SubmittingPatches
or Documentation/SubmittingPatches in your local copy of git.

Cheers,
Stefan
On Tue, Aug 21, 2018 at 11:01 PM Gaux Nation <satingaux@gmail.com> wrote:
>
> https://drive.google.com/open?id=0B_6x2GR6_FTMc2RERHlJZVpQc0RIMFMxNi13bE95UU1fZmp3
> On Tue, Aug 21, 2018 at 10:54 PM Gaux Nation <satingaux@gmail.com> wrote:
> >
> > Hey there,
> >
> > The name is Sachin Sharma(19 yrs old, student, India) and passionate
> > for innovative technology and digital content.
> >
> >
> >
> > Why Open Source?
> >
> > Open Source connects like-minded genes in the whole world. This lets
> > contributors to get engaged with the groups of different communities.
> >
> >
> >
> > Why Git?
> >
> > I just love the platform your organization had built,
> >
> > 1.Branching and merging.
> >
> > 2.Small and fast.
> >
> > 3. Distributed.
> >
> > 4.Free and Open Source.*
> >
> >
> >
> > Why I?
> >
> > I’m a new bee, therefore I might not have that long list of projects
> > but I have that level of commitment, attitude and ability to follow
> > directions which are expected from a student.
> >
> >
> >
> > What do I need from Git?
> >
> > Guidance, neither too deep nor too short(optimum).
> >
> > How can I get started for a contribution?
> >
> > What are the necessary technical skills needed for a contribution to Git?
> >
> >
> >
> >
> >
> >
> >
> > GitHub:  satingaux@github
> >
> > Contact: 8572020330,9138258580.
> >
> >
> >
> > Quote: I might not get selected, but an interaction with you will make my day.
> >
> >        I assure you, sir I will work hard to give my 100%.
> >
> >        I feel blessed if I got chance for contributing to an open
> > source community.
> >
> >
> >
> >
> >
> > Technical Skills: JAVA, JavaScript, SQL, C, C++.
> >
> >
> >
> > Thank you

Re: Contribution for an Open Source Git

[Jonathan Nieder]

Hi,

Sachin Sharma wrote:

> What do I need from Git?
>
> Guidance, neither too deep nor too short(optimum).
>
> How can I get started for a contribution?
>
> What are the necessary technical skills needed for a contribution to
> Git?

To add to what Stefan wrote:

This is a good question.  There are a wide variety of ways that a
person can improve Git, from the point of view of improving how it
works, adding features, documenting it better, helping users directly,
and so on.  All of these kinds of projects require different skills.

I think that for many, the first barrier to entry is intimidation.
As Stefan staid, don't be intimidated --- we won't bite. ;-)  If you
make an improvement and the project doesn't take it, you still get the
satisfaction to being able to use that improvement.  And the project
is quite open to improvements and after a first false step can help
point you in a good direction to get things done in a maintainable
way.

Another piece of advice is to take advantage of the real-time help you
can get from IRC.  See the IRC channel link in https://git-scm.com/community
for details.  https://kiwiirc.com/nextclient/ might be useful for
getting started with IRC.

Thanks and hope that helps,
Jonathan