{"thread":{"id":"44485","subject":"New to git, need help!","startedAt":"2016-11-15T12:30:13Z","lastAt":"2016-11-15T15:43:34Z","messageCount":2,"participants":["Mayank Gupta","Pranit Bauva"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"305945","messageId":"CAJNRPQRhyrALj0zdaTxKgwo8j8r8_7ixgX21+C=ue+CGKYgaCg@mail.gmail.com","threadId":"44485","inReplyTo":null,"subject":"New to git, need help!","fromName":"Mayank Gupta","fromEmail":"mayankgupta18198@gmail.com","sentAt":"2016-11-15T12:30:06Z","receivedAt":"2016-11-15T12:30:13Z","isPatch":false,"sender":{"key":"mayankgupta18198@gmail.com","avatar":null},"body":"Hi All,\n\nI'm new to open source and have recently joined this mailing list.\nSince I'm new at this, I think I can initially contribute to the\ncommunity by fixing some small bugs or errors but as the documentation\nis too large, I don't know where to start.\nSo if anybody could guide me on how to go about it, it would be really\nappreciated.\n\nThanks,\nMayank\n"},{"id":"305958","messageId":"CAFZEwPPiQpP+Nr1x2852DBZu71gwHNpKf0WS8htunHpBkBqMCw@mail.gmail.com","threadId":"44485","inReplyTo":"CAJNRPQRhyrALj0zdaTxKgwo8j8r8_7ixgX21+C=ue+CGKYgaCg@mail.gmail.com","subject":"Re: New to git, need help!","fromName":"Pranit Bauva","fromEmail":"pranit.bauva@gmail.com","sentAt":"2016-11-15T15:43:28Z","receivedAt":"2016-11-15T15:43:34Z","isPatch":false,"sender":{"key":"pranit.bauva@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2959938?v=4"},"body":"Hey Mayank,\n\nOn Tue, Nov 15, 2016 at 6:00 PM, Mayank Gupta\n<mayankgupta18198@gmail.com> wrote:\n> Hi All,\n>\n> I'm new to open source and have recently joined this mailing list.\n> Since I'm new at this, I think I can initially contribute to the\n> community by fixing some small bugs or errors but as the documentation\n> is too large, I don't know where to start.\n> So if anybody could guide me on how to go about it, it would be really\n> appreciated.\n\nIt is really nice that you want to start contributing. We have a user\ndocumentation[1] and a developer documentation[2]. To contribute to a\nfeature, firstly you need to learn about that feature. So go through\nthe man pages of the tool which you would want to work on. The things\nthat you would be using are documented in the technical documentation.\nApart from this, you can start hunting small errors but I think it\nwould be difficult in the initial stages. So read this[3] even though\nit is specific for GSoC, it is helpful for any new developer. Also you\ncan search the mailing list archives for \"low hanging fruit\" to get\nthings which were thought of but not done or something like that.\n\n[1]: https://github.com/git/git/tree/master/Documentation\n[2]: https://github.com/git/git/tree/master/Documentation/technical\n[3]: https://git.github.io/SoC-2016-Microprojects/\n\nHope to see a patch from your side soon! :)\n\nRegards,\nPranit Bauva\n"}]}