Hello everyone, My name is Yeswanth . I am doing my third year Btech in Computer Science in India. My desire is to get into gsoc 2011 . I have been looking over the projects of last year to see where I would fit in. And I found python to be interesting, something I can contribute. I dont know if Python Software Foundation will apply for Gsoc this year, I just hope it will . So here I am , planning to make an entry in contributing to this open source project. I can just program in Python ,never contributed anything to it , atleast of now. So I have read the development links provided in the python.org site. Can anyone suggest me some areas where I can actually start with developing for this proje
On Wed, 05 Jan 2011 17:18:00 +0530, yeswanth <swamiyeswanth@hotmail.com> wrote:
My name is Yeswanth . I am doing my third year Btech in Computer Science [...] Can anyone suggest me some areas where I can actually start with developing for this proje
Welcome, Yeswanth. Great idea to get involved early :) I'm guessing the PSF will apply to GSoC in 2011, but I'm not involved in that decision so I don't really know anything. The best way to start out helping is to do what you've done, read the developer docs (which Brett Cannon is currently updating, by the way). Next you could take a look at the bug tracker at bugs.python.org. There are plenty of open issues there that need to be reviewed (anyone can do reviews). Try out patches for issues that have existing patches, note anything missing (tests, doc updates, etc) (supply them if you like), and report your experiences with testing the patch, and any comments you may have on it. When you feel ready to try your hand at writing patches, click on the 'easy issues' button on the left. That tag is assigned to bugs where the reviewer thought the patch could be written in a day or less of work (of course, if you are still relatively new to Python coding it may take longer to do the necessary research to be able to write the patch). If you like you can also come hang out on the #python-dev IRC channel on freenode, where a number of the core developers and other folks hang out and discuss issues (among other things :) -- R. David Murray www.bitdance.com
On Wed, Jan 5, 2011 at 05:48, yeswanth <swamiyeswanth@hotmail.com> wrote:
Hello everyone, My name is Yeswanth . I am doing my third year Btech in Computer Science in India. My desire is to get into gsoc 2011 . I have been looking over the projects of last year to see where I would fit in. And I found python to be interesting, something I can contribute. I dont know if Python Software Foundation will apply for Gsoc this year, I just hope it will . So here I am , planning to make an entry in contributing to this open source project. I can just program in Python ,never contributed anything to it , atleast of now. So I have read the development links provided in the python.org site.
Can anyone suggest me some areas where I can actually start with developing for this proje
Yeswanth, http://docs.pythonsprints.com/core_development/beginners.html might be helpful for getting started, and to supplement David's suggestions. It was written for users like yourself to go from zero to successful contribution as quick as possible. Brian
Am 05.01.2011 12:48, schrieb yeswanth:
Hello everyone, My name is Yeswanth . I am doing my third year Btech in Computer Science in India. My desire is to get into gsoc 2011 . I have been looking over the projects of last year to see where I would fit in. And I found python to be interesting, something I can contribute. I dont know if Python Software Foundation will apply for Gsoc this year, I just hope it will . So here I am , planning to make an entry in contributing to this open source project. I can just program in Python ,never contributed anything to it , atleast of now. So I have read the development links provided in the python.org site.
Can anyone suggest me some areas where I can actually start with developing for this proje
PSF GSoC applicants will be asked to submit a patch to the Python(ic) project they are going to contribute to, as a proof that they actually know how to write code. So I suggest you browse through the bug tracker, find an open issue with no patch, and write a patch. You may want to focus on issues marked as "easy". Regards, Martin
participants (4)
-
"Martin v. Löwis" -
Brian Curtin -
R. David Murray -
yeswanth