On Dec 9, 2009, at 12:28 PM, Ondrej Certik wrote: > Hi Julio! > > On Wed, Dec 9, 2009 at 6:49 AM, Julio Oliveira <idiche...@yahoo.com.br> wrote: >> Hello Sympy Team, >> >> I would like to join the Sympy development, if possible.
We are always looking for people wiling to work on SymPy :). >> I have very good to excellent skills in C and C++ programming, and I have >> good skills in Python. > > Thanks for your interest! > >> My major interest is to improve my Python proficiency, so I would be glad to >> join any Python related development (bugs or new features). Feel free to help fix bugs. If you play around with SymPy enough, you will soon find things that are not implemented. The great thing about working on SymPy is that you learn not only Python (and git), but also you end up learning a lot of neat thing in Math. >> I already got the code downloaded, and I am studying it, but I would be glad >> to know: >> >> 1) How does the assignment of tasks occurs ? Work on a feature that interests you (or on a bug that annoys you). > > There is no official assignment of tasks. You work on what you like to > work on. If you want to help out with the release, it's good to work > on the release issues. > >> 2) Is there a todo list where I can find bugs to be fixed and new features >> to be implemented? > > Yes, here is a full list: > > http://code.google.com/p/sympy/issues/list These are mostly the bugs. The best way to find feature that haven't been implemented is to play around with it and see what can and cannot be done. > > all high priority issues should eventually be fixed. Generally just > concentrate on the top issues. Fixing any of them would be a great > help. Here is a list of issues that need a better patch: > > http://code.google.com/p/sympy/issues/list?q=label:NeedsBetterPatch > > and all the details are explained in the issue. Feel free to improve > any of those. > >> 3) Once that I got a task to solve, is it locked to me, or do other people >> work in parallel? > We don't really have "tasks" like you say. If you want to work on something, just do it (though maybe mention that you are doing it so someone else doesn't duplicate the work). If you need help, open source is all about collaboration. > Usually you just write in the respective issue that you are fixing it > (or on the mailinglist/IRC), so that other people know. We are on #sympy in freenode. > >> 4) How do I commit code that I improved? Who checks it? All code is reviewed before it is pushed in, and we also have an extensive test suite that you can run by doing ./setup.py test in the sympy directory, so you can play around with the code and you don't have to worry about breaking it and not knowing it. > > Learn git: > > http://code.google.com/p/sympy/wiki/GitTutorials > > and attach a patch to the issue, or publish your branch somewhere > (e.g. github). Then ask some developer to review it. Once it has > positive review, it will be pushed in. > > Ondrej Aaron Meurer -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sy...@googlegroups.com. To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
