Hi Deep, I second the easy-fix label. Furthermore, this is the general GSoC list so you won't get much help specific to SciPy here. If you have other questions or have an idea for a project (start early!) then the scipy-dev mailing list (see http://www.scipy.org/Mailing_Lists) is the place to ask Cheers, Ralf On Wed, Oct 19, 2016 at 11:16 PM, Ankur Ankan <ankurankan@gmail.com> wrote:

Hi,

You can try to filter the issues using labels. There are a few easy fix issues: https://github.com/scipy/scipy/issues?q=is% 3Aopen+is%3Aissue+label%3Aeasy-fix.

Cheers Ankur

On Wed, Oct 19, 2016 at 11:37 AM, deep tavker <tavkerdeep@gmail.com> wrote:

...

Dear developers,

It's been a while since I started preparing for GSoC and as guided by senior developers like you people, I started looking at organisations and I finally decided I wanted to so GSoC with python. I also narrowed it down to SciPy.

I've been trying to fix the bugs from the issues page (Github) of SciPy but I am not being able to distinguish between a simple bug and a complex one. Some guidance on that front would really help. And in general, some advice on what kind of generic topics should one learn to get started/better at open source dev.

Thank you, Deep

_______________________________________________ GSoC-general mailing list GSoC-general@python.org https://mail.python.org/mailman/listinfo/gsoc-general

_______________________________________________ GSoC-general mailing list GSoC-general@python.org https://mail.python.org/mailman/listinfo/gsoc-general