On 1/30/13 8:55 AM, Marek Counts wrote: > > > Hello, > > My name is > Marek and I'm a masters student in computer science with dual concentrations > in > Program Security and database technology. I know C/C++,C# , java, python and > VB > to the extent I have written programs with each. > > I would like to > help with the development of this project. I am currently reading through a > lot > of the starters guide documents as well as some of the other information that > I > can get my hands on. Anyhow, I'm here and ready to help however I can, this > will be my first large project I have ever helped with so I apologize if I > stumble around for a few weeks. > > I have > downloaded some of the code and will be looking though that the rest of this > week most likely trying to at least make heads or tails of it. Anyhow, > anything > simple that any of you need help on just shoot me a message and I would love > to > help you out with it! > > I have a few > operating systems I can test on. > > windows 7, Windows > 8, Gentoo, and backtrack >
Hi Marek, first of all welcome at OpenOffice and your interest to help us to improve the product. I think a good way to get started is to prepare your own build env, you can find a building guide under http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO Once you have prepared your build env you can try to debug certain code areas and can try to analyze some issues. The best way it to get simply started and learn by doing. Once you have picked up an issue you can come back and ask where to get started and we can give you more detailed tips. The code base is huge and focusing on one specific area is probably a good idea. The best debugging tool is of course the Microsoft debugger and I would recommend to start debugging under windows. But it really depends on your own preferences and gdb works as well. Again welcome at Apache OpenOffice and please feel free to ask question. Juergen
