On Apr 10, 2013, at 10:27 AM, Sabhya Kaushal <sabhya007kaushal@...> wrote:
i would like to know whether I can start working on the proposals straight away, or do I need to prove my worth beforehand by doing the patching. This i asked because I am very keen on these three projects that I chose, but at the same time, I am in the development phase for getting myself familiar with the technologies.
I suggest working on getting at least one proposal filled out enough for us to provide feedback before working on a patch. It's usually better if a patch somehow relates to your project too, so it's relevant to what you'd be working with.
That said, the two activities are completely independent yet mutually supportive. Working on code might help you understand how to write a better proposal. Starting on a proposal will give you an idea of what code to change.
I also would like to ask if not being "ready enough" at this point of time acts against me. beacuse the part on NURBS, that I got, and the other projects that i am interested in are the code refractoring and the solar system simulation, about both of which I have some ideas and would like to proceed with keen interest.
Becoming familiarized with the code is going to be a challenge for everyone, but is part of participating in open source (and GSoC). Given the time constraint is why I suggest focusing on no more than two proposals and to keep the discussion rolling.
Code refactoring requires a very specific plan, what would you change, how, why, when, etc. The solar system simulation is much more concrete but defining a project that is well-integrated with our infrastructure is going to be a challenge for you.
Whatever is proposed should leverage our existing functionality as much as possible and be proposed in a "code complete" fashion such that you could stop any day and nothing would be in an incomplete state. It's a different way of approaching coding than most are used to.
p.s. Please limit top-posting replies unless you refer to nothing you're replying to (in which case it probably should be a new thread).