Re: [tdf-discuss] Scripting for LibreOffice

2013-03-10 Thread lordmax tdf
Hi Il 10/03/2013 01:16, Keith Curtis ha scritto: Hi; I'm totally with you Keith While working on my wiki page about a new Writer toolbar, I realized that independently of my proposal, I believe it makes sense for LibreOffice to prefer Python. I see how LO is heading in this direction, but

Re: [tdf-discuss] Dual licensing of patches and code

2013-03-10 Thread Jim Jagielski
On Mar 8, 2013, at 8:07 AM, Bjoern Michaelsen bjoern.michael...@canonical.com wrote: Hi Jim, On Thu, Mar 07, 2013 at 12:42:26PM -0500, Jim Jagielski wrote: Just so I'm clear: If a company wishes to contribute code to TDF/LO, but wants their contributions to be triple-licensed

[tdf-discuss] Grant of License

2013-03-10 Thread Dennis E. Hamilton
This grant does not specify any particular open-source license. My intention is to not limit in any way the licensing of works that my contributions are incorporated in. The license is self- contained for that reason. There is no conflict with how LibreOffice releases are licensed and there is

Re: [tdf-discuss] Dual licensing of patches and code

2013-03-10 Thread Jim Jagielski
Just so I'm clear: If a company wishes to contribute code to TDF/LO, but wants their contributions to be triple-licensed (alv2-mpl-lgplv3), they would be refused. Is that correct? If so, what, exactly, is the reason? tia! On Mar 7, 2013, at 9:42 AM, Florian Effenberger flor...@effenberger.org

Re: [tdf-discuss] Dual licensing of patches and code

2013-03-10 Thread Simon Phipps
How could you possibly infer from any earlier answer that triple-licensed contributions would be inherently refused? Like Andrew Pitonyak I read exactly the opposite. Florian said that in the sort of theoretical argument you're attempting, code under a triple license is just as acceptable and

[tdf-discuss] Re: Dual licensing of patches and code

2013-03-10 Thread Simon Phipps
On 13-03-09, at 05:39 , Andrea Pescetti pesce...@apache.org wrote: The conversation below happened in public, but not on the OpenOffice public lists. I believe it's good to record its outcome here on the OpenOffice dev list too. Do you know why the question was asked and settled in secret

RE: [tdf-discuss] Re: Dual licensing of patches and code

2013-03-10 Thread Dennis E. Hamilton
@Simon: Andrea Pescetti cross-posted to [tdf-discuss] and [openoffice-dev] some clarifying information, but his sending from an @apache.org e-mail is apparently hung up in a moderation queue - he has probably not subscribed with that one. So you are seeing threads following from it that

Re: [tdf-discuss] Re: Dual licensing of patches and code

2013-03-10 Thread Simon Phipps
On Sun, Mar 10, 2013 at 5:17 PM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: In Andrea's post, the contribution page on the AOO Wiki is offered as the Apache OpenOffice response to Jim Jagielski's question: Thanks, Dennis - I'd pieced all that together from the posts I could find. What

[tdf-discuss] Re: Install path for LibreOffice under Windows

2013-03-10 Thread V Stuart Foote
Pedro wrote So my question is: is there any reason that LibreOffice under Windows does not install to \LibreOffice\? There are a few issues that make it problematic. Paramount is that the .MSI packaging for Microsoft Installer is kind of fragile, and Andras Timar is just one deep as primary

[tdf-discuss] Re: Install path for LibreOffice under Windows

2013-03-10 Thread Pedro
Hi Stuart Thank you for your answer! V Stuart Foote wrote There are a few issues that make it problematic. Paramount is that the .MSI packaging for Microsoft Installer is kind of fragile, and Andras Timar is just one deep as primary maintainer of the multilanguage packaging. We'd need to

Re: [tdf-discuss] Dual licensing of patches and code

2013-03-10 Thread jonathon
On 03/10/2013 01:44 PM, Jim Jagielski wrote: unable to get a simple answer should be proof-positive You were given an official answer. have also have been unable to get a clear, official answer as well. If the code is crap, it doesn't matter what license is used, it will not be accepted. If