I have never worked on an open source project before so I'm not exactly sure what I'm doing. But I'm real excited about doing this. I have an advanced degree in mathematics and an emphasis on mathematical physics. I love numerical analysis and coding so I'm real excited about joining the SciPy team. At some point, once I get a handle on things, I will like to contribute to the documentation as well. I guess I will hang out, figure out what's going on, read the archives, and check out the source code. Real excited about this! Regards, Kai
On Sun, Apr 15, 2012 at 10:13 PM, Patrick "Kai" Baker <eigenspaces@gmail.com
wrote:
I have never worked on an open source project before so I'm not exactly sure what I'm doing. But I'm real excited about doing this. I have an advanced degree in mathematics and an emphasis on mathematical physics. I love numerical analysis and coding so I'm real excited about joining the SciPy team. At some point, once I get a handle on things, I will like to contribute to the documentation as well. I guess I will hang out, figure out what's going on, read the archives, and check out the source code. Real excited about this!
Hi Kai, welcome! If you have any specific question or run into some issues getting started, let us know. Looking forward to your contributions. Cheers, Ralf
Hi Kai, On Sun, Apr 15, 2012 at 9:13 PM, Patrick "Kai" Baker <eigenspaces@gmail.com>wrote:
I have never worked on an open source project before so I'm not exactly sure what I'm doing. But I'm real excited about doing this. I have an advanced degree in mathematics and an emphasis on mathematical physics. I love numerical analysis and coding so I'm real excited about joining the SciPy team. At some point, once I get a handle on things, I will like to contribute to the documentation as well. I guess I will hang out, figure out what's going on, read the archives, and check out the source code. Real excited about this!
Regards, Kai
Welcome to the scipy community ! As a newcommer into the community, you are actually in the best position to tell us what's missing for people like you who want to start contributing (FAQ, documents, etc…) cheers, David
Thanks you two. Well, I got scipy installed and got git set up. Now I'm real confused about what I can do. Documentation is one of them, which I will want to do once I become more familiar with the software. But as far as coding goes, I'm not sure what needs to be done. Is there anyplace I can go with a to-do list of things which needs to be done? I looked around and haven't found anything like that so far. On Mon, Apr 16, 2012 at 3:49 PM, David Cournapeau <cournape@gmail.com>wrote:
Hi Kai,
On Sun, Apr 15, 2012 at 9:13 PM, Patrick "Kai" Baker < eigenspaces@gmail.com> wrote:
I have never worked on an open source project before so I'm not exactly sure what I'm doing. But I'm real excited about doing this. I have an advanced degree in mathematics and an emphasis on mathematical physics. I love numerical analysis and coding so I'm real excited about joining the SciPy team. At some point, once I get a handle on things, I will like to contribute to the documentation as well. I guess I will hang out, figure out what's going on, read the archives, and check out the source code. Real excited about this!
Regards, Kai
Welcome to the scipy community !
As a newcommer into the community, you are actually in the best position to tell us what's missing for people like you who want to start contributing (FAQ, documents, etc…)
cheers,
David
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
Hi, 18.04.2012 21:04, Patrick "Kai" Baker kirjoitti:
Thanks you two. Well, I got scipy installed and got git set up. Now I'm real confused about what I can do. Documentation is one of them, which I will want to do once I become more familiar with the software. But as far as coding goes, I'm not sure what needs to be done. Is there anyplace I can go with a to-do list of things which needs to be done? I looked around and haven't found anything like that so far.
A to-do list is not written down anywhere (but that could be a part of the module status summary for the maintainers to write). We however do have a long list of bugs and issues to fix: http://projects.scipy.org/scipy/query?status=apply&status=needs_decision&status=needs_info&status=needs_review&status=needs_work&status=new&status=reopened&group=component&max=100000&order=priority Some of these are easier to do, others are difficult, and some require "deeper" knowledge of how the things work. There are also some feature requests mixed in. Pauli
On Wed, Apr 18, 2012 at 10:33 PM, Pauli Virtanen <pav@iki.fi> wrote:
Hi,
18.04.2012 21:04, Patrick "Kai" Baker kirjoitti:
Thanks you two. Well, I got scipy installed and got git set up. Now I'm real confused about what I can do. Documentation is one of them, which I will want to do once I become more familiar with the software. But as far as coding goes, I'm not sure what needs to be done. Is there anyplace I can go with a to-do list of things which needs to be done? I looked around and haven't found anything like that so far.
A to-do list is not written down anywhere (but that could be a part of the module status summary for the maintainers to write).
We however do have a long list of bugs and issues to fix:
Some of these are easier to do, others are difficult, and some require "deeper" knowledge of how the things work. There are also some feature requests mixed in.
Browsing those tickets may indeed give you a good impression of what things there are to do. If you have preferences/interests, such as a particular topic/module (optimization/interpolation/stats/etc) or language (Python/Cython/C/C++/Fortran), we can give you more specific suggestions. Ralf
That's excellent. Debugging sounds like a good start. I know C/C++ the most since they're my first languages. But I also know Python and would like to gain more working knowledge of it. As far as mathematics, I'm most familiar with analysis: calculus, differential equations, special functions, etc. Kai On Wed, Apr 18, 2012 at 4:59 PM, Ralf Gommers <ralf.gommers@googlemail.com>wrote:
On Wed, Apr 18, 2012 at 10:33 PM, Pauli Virtanen <pav@iki.fi> wrote:
Hi,
18.04.2012 21:04, Patrick "Kai" Baker kirjoitti:
Thanks you two. Well, I got scipy installed and got git set up. Now I'm real confused about what I can do. Documentation is one of them, which I will want to do once I become more familiar with the software. But as far as coding goes, I'm not sure what needs to be done. Is there anyplace I can go with a to-do list of things which needs to be done? I looked around and haven't found anything like that so far.
A to-do list is not written down anywhere (but that could be a part of the module status summary for the maintainers to write).
We however do have a long list of bugs and issues to fix:
Some of these are easier to do, others are difficult, and some require "deeper" knowledge of how the things work. There are also some feature requests mixed in.
Browsing those tickets may indeed give you a good impression of what things there are to do. If you have preferences/interests, such as a particular topic/module (optimization/interpolation/stats/etc) or language (Python/Cython/C/C++/Fortran), we can give you more specific suggestions.
Ralf
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
On Wed, Apr 18, 2012 at 11:11 PM, Patrick "Kai" Baker <eigenspaces@gmail.com
wrote:
That's excellent. Debugging sounds like a good start.
Great.
I know C/C++ the most since they're my first languages. But I also know Python and would like to gain more working knowledge of it. As far as mathematics, I'm most familiar with analysis: calculus, differential equations, special functions, etc.
Special functions (scipy.special) are mostly written in C, its tests are in Python of course. Pauli can perhaps give you more pointers for special, but here's already a ticket with an issue that needs investigating (it came up again today on scipy-user): http://projects.scipy.org/scipy/ticket/1453 scipy.integrate may also fit with your analysis background. Possible ticket to start: http://projects.scipy.org/scipy/ticket/1572 Here's one that needs investigation in interpolate: http://projects.scipy.org/scipy/ticket/1642 The above modules have more issues that require digging into compiled code that issues with pure Python code I'd say. For pure Python code, stats may be a good module: http://projects.scipy.org/scipy/ticket/1183 http://projects.scipy.org/scipy/ticket/1493 http://projects.scipy.org/scipy/ticket/913 The above are all bugs. There are also many tickets with enhancement suggestions, looking at some of those could be interesting too. Cheers, Ralf
Kai
On Wed, Apr 18, 2012 at 4:59 PM, Ralf Gommers <ralf.gommers@googlemail.com
wrote:
On Wed, Apr 18, 2012 at 10:33 PM, Pauli Virtanen <pav@iki.fi> wrote:
Hi,
18.04.2012 21:04, Patrick "Kai" Baker kirjoitti:
Thanks you two. Well, I got scipy installed and got git set up. Now I'm real confused about what I can do. Documentation is one of them, which I will want to do once I become more familiar with the software. But as far as coding goes, I'm not sure what needs to be done. Is there anyplace I can go with a to-do list of things which needs to be done? I looked around and haven't found anything like that so far.
A to-do list is not written down anywhere (but that could be a part of the module status summary for the maintainers to write).
We however do have a long list of bugs and issues to fix:
Some of these are easier to do, others are difficult, and some require "deeper" knowledge of how the things work. There are also some feature requests mixed in.
Browsing those tickets may indeed give you a good impression of what things there are to do. If you have preferences/interests, such as a particular topic/module (optimization/interpolation/stats/etc) or language (Python/Cython/C/C++/Fortran), we can give you more specific suggestions.
Ralf
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
Wow, a lot of great stuff I can't wait to delve in to next week! (I work this weekend - yeah, it sucks!) Once I get the hang of things I'll look in to the other areas of development. I'm not only interested in gaining experience in what I already know but also expand upon it. Kai On Fri, Apr 20, 2012 at 3:34 PM, Ralf Gommers <ralf.gommers@googlemail.com>wrote:
On Wed, Apr 18, 2012 at 11:11 PM, Patrick "Kai" Baker < eigenspaces@gmail.com> wrote:
That's excellent. Debugging sounds like a good start.
Great.
I know C/C++ the most since they're my first languages. But I also know Python and would like to gain more working knowledge of it. As far as mathematics, I'm most familiar with analysis: calculus, differential equations, special functions, etc.
Special functions (scipy.special) are mostly written in C, its tests are in Python of course. Pauli can perhaps give you more pointers for special, but here's already a ticket with an issue that needs investigating (it came up again today on scipy-user): http://projects.scipy.org/scipy/ticket/1453
scipy.integrate may also fit with your analysis background. Possible ticket to start: http://projects.scipy.org/scipy/ticket/1572
Here's one that needs investigation in interpolate: http://projects.scipy.org/scipy/ticket/1642
The above modules have more issues that require digging into compiled code that issues with pure Python code I'd say. For pure Python code, stats may be a good module: http://projects.scipy.org/scipy/ticket/1183 http://projects.scipy.org/scipy/ticket/1493 http://projects.scipy.org/scipy/ticket/913
The above are all bugs. There are also many tickets with enhancement suggestions, looking at some of those could be interesting too.
Cheers, Ralf
Kai
On Wed, Apr 18, 2012 at 4:59 PM, Ralf Gommers < ralf.gommers@googlemail.com> wrote:
On Wed, Apr 18, 2012 at 10:33 PM, Pauli Virtanen <pav@iki.fi> wrote:
Hi,
18.04.2012 21:04, Patrick "Kai" Baker kirjoitti:
Thanks you two. Well, I got scipy installed and got git set up. Now I'm real confused about what I can do. Documentation is one of them, which I will want to do once I become more familiar with the software. But as far as coding goes, I'm not sure what needs to be done. Is there anyplace I can go with a to-do list of things which needs to be done? I looked around and haven't found anything like that so far.
A to-do list is not written down anywhere (but that could be a part of the module status summary for the maintainers to write).
We however do have a long list of bugs and issues to fix:
Some of these are easier to do, others are difficult, and some require "deeper" knowledge of how the things work. There are also some feature requests mixed in.
Browsing those tickets may indeed give you a good impression of what things there are to do. If you have preferences/interests, such as a particular topic/module (optimization/interpolation/stats/etc) or language (Python/Cython/C/C++/Fortran), we can give you more specific suggestions.
Ralf
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
participants (4)
-
David Cournapeau -
Patrick "Kai" Baker -
Pauli Virtanen -
Ralf Gommers