On Wed, 12 May 2010 02:04:56 -0700, Davy <[email protected]>
wrote:
I am an 3rd year IT student at the University of Pretoria in South
Africa and I have been meaning to get involved in the development of
Open Office for a long time, and since we now have an assignment that
requires us to fix a bug in an open source project, I feel that this is
a good time to get involved. How would I go about getting started and
finding a bug that suits my assignment's requirements?
I suggest you start by preparing your tools. Make sure your development
environment is comfortable enough, as the OO.o code is pretty big.
I, myself, being completely unrelated to the OO.o development, but
having to go through development bootstrapping once to fix a bug, I
would suggest you try to build it first and get comfortable with
Mercurial. Next, get familiar with the code file structure (where
each component is and what the layers are, UNO, shell, etc.).
As for find a bug of yours that makes your hair go gray. Those are the
ones that you can get fixed the better in the long run.
:-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
