Re: Starting with development

Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
Newsgroups gmane.comp.programming.tools.scons.devel
Message-ID <CAEyG4CEvm64VJ08DU0DvKpbetm52Wu6X-CQpkFgvmT9SKNibeA@mail.gmail.com>
Gaurav,

Welcome!

Please take a read through:
https://bitbucket.org/scons/scons/wiki/DeveloperGuide

If you're familiar with git and not so much with mercurial, please pay
careful attention to the mercurial work flos page.

Definitely don't be shy about asking if you get stuck or have questions.
I'm frequently on the #scons IRC channel at freenode as well.

-Bill
Co-Manager, SCons Project

On Tue, Jan 10, 2017 at 9:58 AM, William Blevins <[email protected]>
wrote:

> The easy unassigned tickets are free game. I would assume tickets that
> aren't worked on in years are free game also. I recommend asking in the
> scons-dev for tips, since the current tigris issue list probably needs to
> be groomed.
>
> V/R,
> William
>
> On Jan 10, 2017 1:45 AM, "Gaurav Juvekar" <[email protected]> wrote:
>
> Hi everyone,
>
> I want to start contributing. I want to start with "easy" bugs, so that
> I can get to know the code better. Should I start with unassigned "Easy"
> keyword issues on the tigris issue tracker? I also found some old issues
> that are assigned, but haven't seen any activity in a long time (2
> years). Should I contact the assigned person and ask if I can take over
> that issue?
>
> --
> Regards,
> Gaurav Juvekar
>
>
> _______________________________________________
> Scons-dev mailing list
> [email protected]
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
>
> _______________________________________________
> Scons-dev mailing list
> [email protected]
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>

_______________________________________________
Scons-dev mailing list
[email protected]
https://pairlist2.pair.net/mailman/listinfo/scons-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.