On 12/08/2009 10:27 AM, Julio Oliveira wrote:
Hello Lyx Team,

I would like to join the Lyx development, if possible.

Great! We need all the help we can get.

I have very good to excelent skills in C and C++ programming, and I have
good skills in Python.

Even better.

My major interest is to improve my Python proficiency, so I would be glad to
join any Python related development (bugs or new features).

Unfortunately, there's not all that much of this. LyX uses python in certain ways, but most of it is fairly simple interfacing stuff. The one thing that does need doing is for the layout2layout.py script to be cleaned up, but Guenter Milde is already working on this. So the work that needs doing right now is mostly C++ stuff. Bug fixing and any new features you feel motivated to work on. Along the way, you will run into python stuff, but the main work is all in C++.

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 ?

There's no formal assignment process. Everyone more or less does what they want. I guess it's good to start by fixing bugs in areas of the code that interest you. And asking a lot of questions.

2) Is there a todo list where I can find bugs to be fixed and new features to 
be implemented?

This is all on our bug tracker, here: http://www.lyx.org/trac/timeline, then click on "tickets" or something like that. It seems to be down at the moment, or I'd give you more details.

3) Once that I got a task to solve, is it locked to me, or do other people work 
in parallel?

If you're working on a bug, you might post that fact to trac, but it's pretty rare to get overlap there. (Wouldn't it be nice if we had that many developers?) If you want to work on some large-scale feature, then it's probably best to discuss the design on the list first, anyway, and then people will know what you are doing.

4) How do I commit code that I improved?  Who checks it?

Post patches to this list. People will look it over and ask for changes or commit it for you. After a while, you'll get commit rights of your own, and then you can just commit little things or things you are sure about, or else post more complicated things or things you don't really know so much about for comment.

Richard

Reply via email to