Hi Billy,
I'm a n00b and I faced the tall learning curve too.
I would say that things are easier than before to get started. The API
and Opengrok websites are really helping:
http://api.libreoffice.org/
http://opengrok.libreoffice.org/
Marc-André Laverdière
Software Security Scientist
Innovation Labs, Tata Consultancy Services
Hyderabad, India
On 09/30/2011 09:09 PM, Billy Charlton wrote:
Ha, thanks for the warm welcome! What a difference :-)
So, my pet peeve issue is a Calc bug/feature request first filed in
*2003* -- and is in the OOo bugzilla
at https://issues.apache.org/ooo/show_bug.cgi?id=10864 . I actually
filed one of the 12 dupes around 2006. The comment thread is pretty
depressing. Apparently not low-hanging fruit or this would have been
fixed ages ago right? It's a frustrating UI issue for users who are
accustomed to Excel.
I always wondered if there was some dark reason this issue kept getting
backburned when the project was still in OOo.
Anyway, I've done plenty of C++ and UI development projects so I'm not
afraid of tackling it, but the codebase is pretty impenetrable for
someone just starting out on this project. Pointers welcome!
..Billy
On Fri, Sep 30, 2011 at 1:47 AM, Michael Meeks <michael.meeks@novell.com
<mailto:michael.meeks@novell.com>> wrote:
On Thu, 2011-09-29 at 13:52 -0700, Billy Charlton wrote:
> I just did my first git clone of the core libreoffice codebase, hoping
> to poke around to see if I could start helping out with some
> bugfixing.
Cool ! :-) what bug are you most interested in ? and/or have you
grokked the easy hacks ? prolly the best way to get into the code is to
ask questions and meet with the hackers on #libreoffice-dev on
irc.freenode.net <http://irc.freenode.net> - if you're not familiar
with IRC, it is really worth
getting into it - for interactive discussion & mentoring.
There is a lot to do of course - one of the things that came up
recently was the idea of getting:
http://code.google.com/p/include-what-you-use/
going, but that's prolly going to be quite a bit more
difficult on
Windows than Linux (many things are sadly).
Anyhow - great to have you around & thanks for the report,
looks like
we'll get a nice fix to hide the (apparent) badness in those files -
which we use as regression tests.
All the best,
Michael.
--
michael.meeks@suse.com <mailto:michael.meeks@suse.com> <><, Pseudo
Engineer, itinerant idiot
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.