[SciPy-Dev] Electronics student with programming background - Like to participate in SciPy - Write some code and learn!

josef.pktd@gmai... josef.pktd@gmai...
Tue Jan 22 20:26:30 CST 2013


On Tue, Jan 22, 2013 at 8:17 PM, Charles R Harris
<charlesr.harris@gmail.com> wrote:
>
>
> On Tue, Jan 22, 2013 at 5:56 PM, Surya Kasturi <suryak@ieee.org> wrote:
>>
>> On Mon, Jan 21, 2013 at 11:35 PM, Surya Kasturi <suryak@ieee.org> wrote:
>>>
>>> Hi,
>>>
>>> I am Surya, studying Junior Year - Electronics & Communication
>>> Engineering with Computer Science/ Programming background. I have looked
>>> into SciPy and its really amazing!
>>>
>>> In this regard, I would like to explore the possibility of contributing
>>> to this project by writing code and simultaneously learn the real
>>> engineering stuff. My skills lie in Python, Django, C - and little Facebook
>>> API, Cloud platforms (Openshift), Git.
>>>
>>> Also, I wrote some fun-stuff projects during week ends which you might
>>> like to take a look.
>>>
>>> 1. Https://apps.facebook.com/pingmee -- Lets people ping their friends
>>> using cartoons (Python, Django -- PIL)
>>> 2. Https://apps.facebook.com/suryaphotography -- social reader framework
>>> for my photography blog; Not yet finished (Python, Django -- Google Feed
>>> API) - Got to finish if time permits
>>> 3. Https://github.com/ksurya -- Github handle
>>>
>>> So, I am ready to take up any work and get along with it that involves
>>> Python!
>>>
>>> Regarding my scientific skills, I studied Engineering Mathematics,
>>> Digital Signal Processing (now studying), Signals & Systems etc. [ More on
>>> signals ]
>>>
>>>
>>> Thanks for reading! waiting for your reply
>>>
>>> -- Surya
>>>
>>
>> Guys can anyone let me know about this above message.. please
>>
>
> You  don't need permission to work on open source projects. You can make
> pull requests, review others' pull requests, post to the list and
> participate in discussions, or look over the bug reports on trac and see if
> there are any you can fix. There is always a lack of developers so anyone
> who does work is welcome. But the work is voluntary and a person's interest
> is measured by their participation. You have made the first step by posting,
> so don't be shy, but don't expect a formal induction into the 'club', just
> start doing things. If you need more specific pointers to things to do,
> perhaps someone here can offer some suggestions.

some more details
https://github.com/scipy/scipy/blob/master/HACKING.rst.txt

I think, a good way to get started, if you don't have any specific
code submission in mind, is to go through the tickets of a subpackage
like scipy.signal and see if you can fix or improve something. Some
less commonly used functions might also have insufficient test
coverage, and it's very useful to go through the code and unit tests,
for new developers to learn how the code works, and for users to get
better tested code.

scikits.signal doesn't seem to have taken off, but scipy.signal is
pretty active, although I think it doesn't have a dedicated
"maintainer".

With your web programming background there might also be interesting
contributions to http://scikits.appspot.com/ http://scipy-central.org/
 or ...

Josef



>
> Chuck
>
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev@scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
>


More information about the SciPy-Dev mailing list