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

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 > (alv2-mpl-lgplv3), they would be refused. Is that correct? That was not what either Florian or the

[tdf-discuss] Experimental UI for LibreOffice proposal

Hi; I'm working on a proposal for building an experimental new LibreOffice toolbar / UI in Python: https://wiki.documentfoundation.org/User:KeithCu I'm going to add some links to places where the C++ code would need to be changed and a few more tweaks, but I'm interested in feedback. Feel free to

Re: [tdf-discuss] Experimental UI for LibreOffice proposal

On Fri, Mar 8, 2013 at 12:44 PM, Keith Curtis wrote: > Hi; > > I'm working on a proposal for building an experimental new LibreOffice > toolbar / UI in Python: > https://wiki.documentfoundation.org/User:KeithCu > > I'm going to add some links to places where the C++ code would need to > be change

[tdf-discuss] FW: GRANT OF LICENSE: Dennis E. Hamilton - ASF Contributions

This is the complementary grant applicable to my contributions to the Apache Software Foundation. I am making copies of both grants available to the ASF Secretary so they can be carried in the records of the Foundation. This posting can be found at

Re: [tdf-discuss] Experimental UI for LibreOffice proposal

On 03/08/2013 03:44 PM, Keith Curtis wrote: Hi; I'm working on a proposal for building an experimental new LibreOffice toolbar / UI in Python: https://wiki.documentfoundation.org/User:KeithCu I'm going to add some links to places where the C++ code would need to be changed and a few more tweaks

Re: [tdf-discuss] Experimental UI for LibreOffice proposal

Hi; >> > This should probably be on the UX mailing list. Also are you developing this > also? Finding developers to implement this could be very very difficult - > just giving you a heads up in case you don't want to waste a bunch of time > for nothing. > > Best, > Joel > I'm not planning on deve

Re: [tdf-discuss] Experimental UI for LibreOffice proposal

On Fri, Mar 8, 2013 at 1:24 PM, Kracked_P_P---webmaster wrote: > On 03/08/2013 03:44 PM, Keith Curtis wrote: >> >> Hi; >> >> I'm working on a proposal for building an experimental new LibreOffice >> toolbar / UI in Python: >> https://wiki.documentfoundation.org/User:KeithCu >> >> I'm going to add

Re: [tdf-discuss] Experimental UI for LibreOffice proposal

> > > > To be clear, the underlying image was created by Paulo José. Working > on smaller screens is a good question, but you have to get something > before you make it work with additional constraints. LibreOffice has > two challenges, looking good on the upcoming high-res screens, and > working o

Re: [tdf-discuss] Experimental UI for LibreOffice proposal

My mistake, thought this was on user list, discuss list seems more appropriate but expanding it to UX list also seems good. Even getting some developer input just to understand what a huge undertaking this is would be useful. Again, personally I like the look ;) Just unsure of "the point" of discu

RE: [tdf-discuss] Experimental UI for LibreOffice proposal

I work with a 2560 x 1600 display. One reason is so that I can do work among multiple documents that I keep open at once. I *never* have a document application running full screen on my 30" monitor. I even object to web pages that can't be viewed properly unless the browser-window is kept too

Re: [tdf-discuss] Experimental UI for LibreOffice proposal

Hi; On Fri, Mar 8, 2013 at 1:50 PM, Joel Madero wrote: > >> > >> >> To be clear, the underlying image was created by Paulo José. Working >> on smaller screens is a good question, but you have to get something >> before you make it work with additional constraints. LibreOffice has >> two challenge

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

My reading of the answers is 1. It depends on how interesting they find the contribution. 2. Some members would vote no because the code is also available under a more permissive license. It is clear that if you provide code to AOO, then LO is able to take the code, but it is not clear that