Hello Steve, and welcome! As a person knowledgeable with C and C++, you may help with fixing bugs, implementing new functions, or also carrying out additional -- but very important -- tasks such as documenting code.
If you want to get started with the (huge!) OpenOffice code base, I suggest you begin by building it for the first time. The Wiki has general build instructions: https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO as well as step-by-step instructions for the most used platforms: https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO#Step-by-Step_Building_Guide_for_Different_Platforms I believe that the "trunk" branch is the best starting point, because it is where the most active development should be carried out. I also suggest to subscribe to the dev@ mailing list so that... you can complain on that list if anything in the build instructions is not clear! ;-) We are looking forward to hear you there. Or also here if you have any other general questions! Best regards. On Tue, Feb 23, 2021 at 10:49:44PM +0000, Stephen Greensides wrote: > Hi > I am Steve. Now retired and hoping to put something back. I have been using > C/C++ on and off since 1988, so do not presume me to be some sort of C++ Guru > :) > > Basically I have done a bit of everything in computing - (to ensure I stayed > employed and paid!), so the spread of knowledge is far, but definitely thin :( > > Mostly, I use OpenOffice as a preference to Excel - I much prefer the > semi-colon separator in formulii to MS’s comma. > > Oh, and my 3 faults are being a Yorkshireman, modest and having no sense of > humour! > > Steve > H +44 (0) 24 76466809 > M +44 (0) 7811 167 157 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Arrigo http://rigo.altervista.org --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
