Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi Mike,

On Sun, 2011-12-04 at 09:37 -0800, Mike Whiteley wrote:
I am an American, but have lived in Germany for several
years.  My German is pretty decent, but probably not fluent.

        Cool - it's really great to have you helping out and cleaning up the
codebase.

I do not wish to debate , or have an argument on the finer
points of the meanings of some of these words:

        Sure; the big picture is a rather clear improvement - (at least for
those of us not used to the finer nuances of German) ;-)

I am also a pretty experienced coder.  Sometimes I will
stray from the literal meaning of the comment in order to
make the actual code more clear.  If this is not preferred,
then I'll resist the urge to do that.

        Cool - are you particularly interested in hacking on a specific
LibreOffice feature ? (if so we can help out with code pointers), or are
you in more of a cleanup & while learning the code mode ?

        Also; as a final request - any chance of an explicit mail on licensing
to the list: "all my contributions to LibreOffice are licensed under the
MPL/LGPLv3+ dual license" or somesuch so we can link it into:
http://wiki.documentfoundation.org/Development/Developers and not bother
you in the future :-)

        Anyhow, thanks again,

        ATB,

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


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.