Welcome Hamza, You can do like I did :)
For code clean ups, and newcomer programmer level tasks, you can take a look at https://wiki.documentfoundation.org/Development/Easy_Hacks (is the wiki down BTW?) Other easy tasks for the UI are here: https://wiki.documentfoundation.org/Development/Default_UI_Improvements . You can also take a look at the Google Summer Of Code (Gsoc) on the wiki. To build libreoffice, you can take a look at https://wiki.documentfoundation.org/Development/Native_Build . I am not so sure about building on an eepc. The problem would be that building C++ code is _very_ slow and the eeepc has a very slow processor too. I'll let other comment on building on eeepc. You will find th wiki page for sending contributions through this one: http://www.documentfoundation.org/develop/ (Wiki seems down, so I cannot easily ensure this) Best of luck! Jean-Noël 2013/2/5 hamza abdelkebir <[email protected]> > hi, > I was at most of the libreoffice presentations at fosdem this year and I > would like to help. > I used the wiki to get the core code using git. > > - Where can I start if I would like to do some code clean up ? (to > detect/remove dead code, useless comment...etc)? > - how internationalization is done in the ui ? > - is it possible to build and test libreoffice under a not so powerful > machine like an eeepc? > - what is the exact procedure to send ones modifications (do I have to > use git to commit or send staff by email)? > > > I know how to code in java but have no knowledge in python and some > limited knowledge in ui coding with glade. > > thanks for your help :) > > Regards, > Hamza > > > _______________________________________________ > LibreOffice mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/libreoffice > >
_______________________________________________ LibreOffice mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice
