Re: Interested in contributing to Bash

[Pranav Deshpande]

Thank you!
I will be reading it now. What do you think of the 'bugs' Eduardo mentioned?

Regards,
Pranav.

On Wed, May 24, 2017 at 12:09 AM, Chet Ramey <chet.ramey@case.edu> wrote:

> On 5/21/17 11:53 AM, Eduardo Bustamante wrote:
> > On Sun, May 21, 2017 at 5:44 AM, Pranav Deshpande
> > <deshpande.v.pranav@gmail.com> wrote:
> > [...]
> >> Any guidance on so as how to get started? Are there any tasks that I can
> >> take up so that I get introduced to the code base.
> >
> > My recommendations would be:
> >
> > - Clone the git repository (https://savannah.gnu.org/git/?group=bash)
> > - Subscribe both bug-bash@gnu.org and help-bash@gnu.org. Try to
> > reproduce bug reports and report back the results.
> > - Read the mailing list archives
> > (https://lists.gnu.org/archive/html/bug-bash/ and
> > https://lists.gnu.org/archive/html/help-bash/), and take note of any
> > reported bugs that are not answered or fixed yet in the latest `devel'
> > branch of the git repository.
> > - Some people place bug reports in the Savannah issue tracker
> > (https://savannah.gnu.org/support/?group=bash). You might also want to
> > check there and see if any of the issues reported there are still not
> > fixed in the latest `devel' branch.
>
> The best thing to read to learn about how the shell is structured -- other
> than the code itself -- is the unedited version of the chapter I wrote for
> AOSA (The Architecture of Open Source Applications).  It's in the bash-4.4
> distribution in doc/aosa-bash-full.pdf.
>
> Chet
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~
> chet/
>