Re: [git-users] Re: Where to start coding?

[amey jain]

Hey
Thanks again for the reply. I will be start working on Open source. I found 
Open hatch project and its interesting. You may also look at it.
Regards  
On Monday, November 30, 2015 at 11:06:49 PM UTC+5:30, Konstantin Khomoutov 
wrote:
>
> On Mon, 30 Nov 2015 09:06:29 -0800 (PST) 
> amey jain  wrote: 
>
> > Thanks that you wrote here. Yes that's right that I am new to all of 
> > it. Actually I want to go to GSoC and for that I started contributing 
> > to Open source. I am already running Ubuntu and subscribed to the 
> > mailing list of git to. I will for sure find some easy projects to 
> > tackle. But it was hard to find easy ones. Though I practice 
> > programming on C very much. I don't have any experience on finding 
> > projects. I think from now I will start from mailing lists and bug 
> > reporting in software. 
>
> Speaking as a Debian user, I'm able to point at [3] being a good 
> summary on how to start contributing to your OS. 
> I'm pretty sure Ubuntu has something like this as well. 
> At least folks at [4] should point to a right direction. ;-) 
>
> P.S. 
> Forgot to mention one thing in my original mail: no, Git does not have 
> any documentation outside of the specs of various on-disk data format 
> it maintains (which is present in the source tree in the form of .txt 
> files).  The only other source of documentation is comments. 
> Commit messages are a good source of documentation, too. 
> Don't forget that you can `git blame` a source code file of interest 
> and then study commit messages of those commits which touch the places 
> of that file which are of particular interest to you. 
>
> 3. https://www.debian.org/intro/help 
> 4. https://askubunu.com 
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Re: Where to start coding?

[amey jain]

Hi Konstantin Khomoutov,
Thanks that you wrote here. Yes that's right that I am new to all of it. 
Actually I want to go to GSoC and for that I started contributing to Open 
source. I am already running Ubuntu and subscribed to the mailing list of 
git to. I will for sure find some easy projects to tackle. But it was hard 
to find easy ones. Though I practice programming on C very much. I don't 
have any experience on finding projects. I think from now I will start from 
mailing lists and bug reporting in software. Thanks of you again to write 
here.  

On Monday, November 30, 2015 at 9:59:19 PM UTC+5:30, Konstantin Khomoutov 
wrote:
>
> On Sun, 29 Nov 2015 01:54:57 -0800 (PST) 
> amey jain  wrote: 
>
> > Thanks for your reply. I was working on git-scm. I have the clone of 
> > its repository. I will sure read the complete docs. I am in beginning 
> > of Open source software. Actually I wanted to know whether there are 
> > documents which tell us what function does what or what for a file is 
> > included. By the way thanks again for the answer. 
>
> Please don't perceive what I will say as a discouragement 
> but judging from these two mails of yours in this thread I'd say 
> it would be much better for you to attempt working on some more 
> accessible and simple project than Git. 
>
> "The problem" is that Git is a pretty hard-core software project 
> developed mostly by wizards -- I mean people with decades (literally) 
> of experience in writing hight-performance C code, with intricate 
> knowledge of the hardware platrofms it targets, the compilers it can be 
> built using, networking, odds of particular OSes and so on and so on. 
>
> While the project is definitely open to contribution, the way you're 
> approaching it suggests you're not such a wizard yet ;-) 
>
> I would hence do something like this instead: 
>
> * Subscribe to the main Git list [1]. 
>
> * Lurk there, and see how people discuss problems, post patches, review 
>   them and so on. 
>
>   Consider reading the archives as well [2]. 
>
> * In the meanwhile, find a project easier to tackle and play with it. 
>
>   If you have a GNU/Linux-based OS, helping out its developers with 
>   fixing outstanding bugs would be a great F/OSS experience 
>   (I maintain a pair of packages for Debian so beleive me on this) ;-) 
>
> 1. https://gist.github.com/tfnico/4441562 
> 2. http://dir.gmane.org/gmane.comp.version-control.git 
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Re: Where to start coding?

[Konstantin Khomoutov]

On Sun, 29 Nov 2015 01:54:57 -0800 (PST)
amey jain  wrote:

> Thanks for your reply. I was working on git-scm. I have the clone of
> its repository. I will sure read the complete docs. I am in beginning
> of Open source software. Actually I wanted to know whether there are
> documents which tell us what function does what or what for a file is
> included. By the way thanks again for the answer. 

Please don't perceive what I will say as a discouragement
but judging from these two mails of yours in this thread I'd say
it would be much better for you to attempt working on some more
accessible and simple project than Git.

"The problem" is that Git is a pretty hard-core software project
developed mostly by wizards -- I mean people with decades (literally)
of experience in writing hight-performance C code, with intricate
knowledge of the hardware platrofms it targets, the compilers it can be
built using, networking, odds of particular OSes and so on and so on.

While the project is definitely open to contribution, the way you're
approaching it suggests you're not such a wizard yet ;-)

I would hence do something like this instead:

* Subscribe to the main Git list [1].

* Lurk there, and see how people discuss problems, post patches, review
  them and so on.

  Consider reading the archives as well [2].

* In the meanwhile, find a project easier to tackle and play with it.

  If you have a GNU/Linux-based OS, helping out its developers with
  fixing outstanding bugs would be a great F/OSS experience
  (I maintain a pair of packages for Debian so beleive me on this) ;-)

1. https://gist.github.com/tfnico/4441562
2. http://dir.gmane.org/gmane.comp.version-control.git

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Re: Where to start coding?

[Konstantin Khomoutov]

On Mon, 30 Nov 2015 09:06:29 -0800 (PST)
amey jain  wrote:

> Thanks that you wrote here. Yes that's right that I am new to all of
> it. Actually I want to go to GSoC and for that I started contributing
> to Open source. I am already running Ubuntu and subscribed to the
> mailing list of git to. I will for sure find some easy projects to
> tackle. But it was hard to find easy ones. Though I practice
> programming on C very much. I don't have any experience on finding
> projects. I think from now I will start from mailing lists and bug
> reporting in software.

Speaking as a Debian user, I'm able to point at [3] being a good
summary on how to start contributing to your OS.
I'm pretty sure Ubuntu has something like this as well.
At least folks at [4] should point to a right direction. ;-)

P.S.
Forgot to mention one thing in my original mail: no, Git does not have
any documentation outside of the specs of various on-disk data format
it maintains (which is present in the source tree in the form of .txt
files).  The only other source of documentation is comments.
Commit messages are a good source of documentation, too.
Don't forget that you can `git blame` a source code file of interest
and then study commit messages of those commits which touch the places
of that file which are of particular interest to you.

3. https://www.debian.org/intro/help
4. https://askubunu.com

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] Re: Where to start coding?

[amey jain]

Hi Pranit,
Thanks for your reply. I was working on git-scm. I have the clone of its 
repository. I will sure read the complete docs. I am in beginning of Open 
source software. Actually I wanted to know whether there are documents 
which tell us what function does what or what for a file is included. By 
the way thanks again for the answer. 
Regards
On Sunday, November 29, 2015 at 10:06:16 AM UTC+5:30, Pranit Bauva wrote:
>
>
> Hey Amey,
>
> A git repository stores only the source code and its copies at different 
> commits. The bug reports are not stored in a git repository. If the project 
> that you want to contribute to has a Github repository then you may find 
> there bug reports. Though its not necessary that you will find bug reports 
> there because there are many projects that use Github as a "publish only" 
> repository and manage bugs somewhere else. To start contribution, First 
> read the entire docs not just the coding guidelines. Then start reading 
> code and fixing typos. The docs usually contain a lot of types. Then browse 
> through bugs and find the easy to fix ones. Fix those. Then when you reach 
> the stage where you will know what to do next. The reading of docs is 
> extremely important. Which project are you thinking of working on?
>
> Regards,
> Pranit Bauva
> On Saturday, 28 November 2015 18:13:55 UTC+5:30, amey jain wrote:
>>
>> Hi,
>> I am new to Open source as well as to git. I recently cloned git repo. I 
>> read the coding guidelines as well. I didn't find where to get bug reports 
>> and where to code. I am new to this can you help me out.
>>
>  

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] Re: Where to start coding?

[Pranit Bauva]

Hey Amey,

A git repository stores only the source code and its copies at different 
commits. The bug reports are not stored in a git repository. If the project 
that you want to contribute to has a Github repository then you may find 
there bug reports. Though its not necessary that you will find bug reports 
there because there are many projects that use Github as a "publish only" 
repository and manage bugs somewhere else. To start contribution, First 
read the entire docs not just the coding guidelines. Then start reading 
code and fixing typos. The docs usually contain a lot of types. Then browse 
through bugs and find the easy to fix ones. Fix those. Then when you reach 
the stage where you will know what to do next. The reading of docs is 
extremely important. Which project are you thinking of working on?

Regards,
Pranit Bauva
On Saturday, 28 November 2015 18:13:55 UTC+5:30, amey jain wrote:
>
> Hi,
> I am new to Open source as well as to git. I recently cloned git repo. I 
> read the coding guidelines as well. I didn't find where to get bug reports 
> and where to code. I am new to this can you help me out.
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.