A developer almost has to be a user first. What works for me, what doesn't, what can I fix, what can I play with. From there, what to do becomes obvious. Just play with it.vicmarcal wrote:One problem is that a "dev" or a "skilled user" doesnt know "how" and "where" to begin. "How" is explained in the Wiki, but the "Where" and not having a defined target is the main problem, from my pov.
The list with small tasks to be done can help. Totally agree with Murmur.
Turns out I like taking things apart, not building them. So I dig through bug reports (even vague ones and see what the program is doing that ReactOS doesn't expect, or has not implemented. I don't mind writing a simple test case once I find the problem, and letting someone else fix it. If I had more time, I'd submit patches.
In fact, if I won the lottery (I'd have to play to win, but if I were to...) I'd spend a few hours a week pulling random things from sourceforge and compiling/running them in ROS. Lots easier to debug that way.