Re: [board-discuss] FTP space for LibreOffice Server Install GUI
Am 05.03.2013 09:45, schrieb Florian Reisinger: Hi, [...] SI-GUI maybe?? Do I have the rights to do git push IMHO not... Norbert -- Liebe Grüße, / Yours, Florian Reisinger
Re: [board-discuss] FTP space for LibreOffice Server Install GUI
On Fri, Mar 8, 2013 at 8:04 AM, Florian Reisinger reisi...@gmail.com wrote: Am 05.03.2013 09:45, schrieb Florian Reisinger: Hi, [...] SI-GUI maybe?? Do I have the rights to do git push IMHO not... 4 days ago I asked you: 1/ I need you to register to gerrit.libreoffice.org and send me the email you used to register (so I can give you proper ACL on the new repo) I have no received such information, so I can not possibly assign 'rights' until I know which user to assign it too. Norbert
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 policy said. This is a matter of community, not just of license. Such combinations of licenses do not lead to a contribution being automatically accepted or rejected, either at Apache or at TDF, we look at each case on its merits. The anonymous contacts you claim to represent should step forward and work on the dev list where I am sure their genuine needs will be accommodated flexibly. Best, Bjoern -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
[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 use email or post in the discussion page as you prefer. Regards, -Keith -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
[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 http://mail-archives.apache.org/mod_mbox/openoffice-dev/201303.mbox/%3c008801ce1c21$0deb3560$29c1a020$@apache.org%3e. - Dennis -Original Message- From: Dennis E. Hamilton [mailto:orc...@apache.org] Sent: Friday, March 08, 2013 09:19 To: d...@openoffice.apache.org Subject: GRANT OF LICENSE: Dennis E. Hamilton The grant of license (below) applies to all of my contributions to ASF projects beyond the provisions of the Contributor License Agreement that I have entered into with The Apache Software Foundation. The purpose is to make my contributions equally available beyond the Apache Project to which I make the contribution. The contri- butions are licensed, by the grant below, to anyone who chooses to make use of them, whether another Apache Project, a non-Apache Project using Alv2, and other projects that choose to rely on the grant. It is my intention that my contributions to the Apache OpenOffice project be available to The Document Foundation under these terms. The license makes no stipulations one way or the other concerning works of mine that are not contributions to LibreOffice. The license does not transfer copyright nor does it assign patents. A complementary grant has been made with respect to my contribu- tions to the LibreOffice project. - Dennis -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 GrantASF 1.00 UTF-8 dh:2013-03-08 GRANT OF LICENSE All of my past and future contributions to Projects of The Apache Software Foundation (ASF) are made with the following stipulations beyond those of my Contributor License Agreement with ASF: 1. I hereby grant to all parties obtaining my ASF contribu- tions a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, combine, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute the contribu- tions and such derivative works. 2. I hereby grant to all parties obtaining my ASF contri- butions a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer works employing my contributions or derivatives thereof, with such license applying only to those claims controlled by myself, now or in the future, that are necessarily infringed due to characteristics of my ASF contributions and such of those that survive in derivatives. I represent that I am legally entitled to grant the above licenses and make those contributions that I offer to ASF projects. March 8, 2013 Dennis E. Hamilton 4401 44th Ave SW Seattle, WA 98116 USA dennis.hamil...@acm.org orc...@apache.org PGP Fingerprint 169F 4BC4 3C47 18B2 7062 E04C B011 4B87 2E94 D8E4 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJROhlsAAoJELARS4culNjkVcMH/jEduLymGTnppBZAlHXSZYIq IsYvfomnaEAJOgLbUETQ3boxvbxcSsJ5hrRsE9OPcm0UGZNQWdutKr9u1m2VnehL qYPm8S/noNV2spdI//Xk73/TrLMvw4ds9FdMw+pr9LqfD6QwdhFNB1f0PYaxLU2z 8/F12qOIPfcYFWWHOU9iR+Yi4tdrdBleHDcBBWOw5BzLU10dAXiMmqPfUr4cgYUD FU+OPuIVyakH32wJ7a2+iZzaT7N0NXcyobluUoYdtGUfiKIbIeW8c2WC8JljB2dw 7h+Aq7952YyHK0mHRBWA/vtQ1WGN1TTTlqBxRK4OT8kqxwOECLI0hhphplt+Qdo= =KBti -END PGP SIGNATURE- - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
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, but I'm interested in feedback. Feel free to use email or post in the discussion page as you prefer. Regards, -Keith What is the target display width for your design? We may have users that are using 800 pixel width CRT monitors. So whatever you design to be on the side panel, the work space that the use will be doing the typing and editing in must be wide enough for them to efficiently work with the document file. When I was working with the display withs under 1024 pixels, I found many packages that were not designed to be easily used with the smaller width display/monitors. I have some that do notwork with any display that are less than 800 pixels high, let alone a narrow width. There bottom buttons were not accessible. So please think about the users we may have that need a package UI that work well and easy with a 800 pixel wide CRT display or similar limiting with display. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
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 developing this. It would be very difficult if built using VCL, etc. The point is to side-step that for now. You could get an intern to make it for Writer. Regards, -Keith -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [tdf-discuss] Experimental UI for LibreOffice proposal
On Fri, Mar 8, 2013 at 1:24 PM, Kracked_P_P---webmaster webmas...@krackedpress.com 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 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 use email or post in the discussion page as you prefer. Regards, -Keith What is the target display width for your design? We may have users that are using 800 pixel width CRT monitors. So whatever you design to be on the side panel, the work space that the use will be doing the typing and editing in must be wide enough for them to efficiently work with the document file. When I was working with the display withs under 1024 pixels, I found many packages that were not designed to be easily used with the smaller width display/monitors. I have some that do notwork with any display that are less than 800 pixels high, let alone a narrow width. There bottom buttons were not accessible. So please think about the users we may have that need a package UI that work well and easy with a 800 pixel wide CRT display or similar limiting with display. 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 okay on the smaller screens. I think as a start, the focus should be on ~1280 pixels wide screens. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
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 okay on the smaller screens. I think as a start, the focus should be on ~1280 pixels wide screens. Really not trying to be pessimistic but in all truth, I don't see this happening. I've seen the work before and personally I like it quite a bit but you have three major issues: 1. Lack of any kind of consensus, without UX input it's kind of DOA. Doing a ton of work and then showing it to them seems worse than working with them and getting their feedback as you plan. There may have already been extensive talk about this already within UX, a quick email over there might result in a huge savings of time on your part. 2. Lack of developers to implement -- if you look on FDO you can see a massive list of bugs that are being worked on and awaiting work. Having a developer spend months implementing this is unlikely as they focus on more pressing issues 3. Lack of funds to pay someone else - for this you're really probably talking about $10's of thousands of dollars. Just my two cents, feel free to take it or leave it. Best, Joel -- *Joel Madero* LibreOffice QA Volunteer jmadero@gmail.com -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
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 discussing it if it's never going to happen -- and I could very well be wrong about that as well, just think the wrong people are being asked if that's the case. Best, Joel On Fri, Mar 8, 2013 at 1:50 PM, Joel Madero jmadero@gmail.com 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 challenges, looking good on the upcoming high-res screens, and working okay on the smaller screens. I think as a start, the focus should be on ~1280 pixels wide screens. Really not trying to be pessimistic but in all truth, I don't see this happening. I've seen the work before and personally I like it quite a bit but you have three major issues: 1. Lack of any kind of consensus, without UX input it's kind of DOA. Doing a ton of work and then showing it to them seems worse than working with them and getting their feedback as you plan. There may have already been extensive talk about this already within UX, a quick email over there might result in a huge savings of time on your part. 2. Lack of developers to implement -- if you look on FDO you can see a massive list of bugs that are being worked on and awaiting work. Having a developer spend months implementing this is unlikely as they focus on more pressing issues 3. Lack of funds to pay someone else - for this you're really probably talking about $10's of thousands of dollars. Just my two cents, feel free to take it or leave it. Best, Joel -- *Joel Madero* LibreOffice QA Volunteer jmadero@gmail.com -- *Joel Madero* LibreOffice QA Volunteer jmadero@gmail.com -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
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 wide. And these days, requiring full use of the 1040 x 768 display by a single app on my Tablet PC is also burdensome. I think an important approach to allowing flexible usage, including accommodation of smaller displays, is simplifying what an application window requires kept inside the application window by having as much as possible fly away and also be easily re-expanded and again collapsed. Having more contextual control (e.g., sensitivity of right-click to context) also matters. And, of course, accessibility considerations apply at all sizes and shapes. - Dennis -Original Message- From: Keith Curtis [mailto:keit...@gmail.com] Sent: Friday, March 08, 2013 13:45 To: Kracked_P_P---webmaster Cc: discuss@documentfoundation.org Subject: Re: [tdf-discuss] Experimental UI for LibreOffice proposal On Fri, Mar 8, 2013 at 1:24 PM, Kracked_P_P---webmaster webmas...@krackedpress.com wrote: [ ... ] What is the target display width for your design? We may have users that are using 800 pixel width CRT monitors. So whatever you design to be on the side panel, the work space that the use will be doing the typing and editing in must be wide enough for them to efficiently work with the document file. When I was working with the display withs under 1024 pixels, I found many packages that were not designed to be easily used with the smaller width display/monitors. I have some that do notwork with any display that are less than 800 pixels high, let alone a narrow width. There bottom buttons were not accessible. So please think about the users we may have that need a package UI that work well and easy with a 800 pixel wide CRT display or similar limiting with display. 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 okay on the smaller screens. I think as a start, the focus should be on ~1280 pixels wide screens. [ ... ] -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [tdf-discuss] Experimental UI for LibreOffice proposal
Hi; On Fri, Mar 8, 2013 at 1:50 PM, Joel Madero jmadero@gmail.com 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 challenges, looking good on the upcoming high-res screens, and working okay on the smaller screens. I think as a start, the focus should be on ~1280 pixels wide screens. Really not trying to be pessimistic but in all truth, I don't see this happening. I've seen the work before and personally I like it quite a bit but you have three major issues: Many things are harder than a Python Writer toolbar built by someone with the skills of a college intern. Depending on how you implemented it would tell you how much it cost. The only new C++ code is in a way to dock this Python toolbar so it looks like it belongs. The C++ changes to LibreOffice here are a lot smaller. It could even start as a separate extension / window, and ignore all these difficult C++ changes indefinitely. I agree you shouldn't take your busy people away from their tasks. There are many things to be done that are higher priority than experimental. However, if it becomes useful to some even while unfinished, it is then adding value back like the other experimental features. It could also be a source of ideas for incremental improvements to other parts of LibreOffice. A task like this will need mentoring, every volunteer is being mentored somewhat, so you can seemingly afford one more. If any designers are comfortable with Python hacking, they could implement some of their ideas and cut devs out of the bottleneck. There are many bitmaps that could be used in the spec. The person doing the work would have to figure out what it will precisely look like and behave, with feedback from other people. I haven't seen a more official bitmap. -Keith -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
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 they would choose to do so. Someone suggested posting to the DEV list. I assume that this means that you should email them, tell them what the contributions are, and then see if they will accept those contributions under the guidelines you state. Perhaps I misunderstood the answers. On 03/07/2013 09:11 AM, Jim Jagielski wrote: Hence my (and others) confusion... It's a pretty easy question; at it's basic: Would code provided under ALv2+MPL+LGPLv3 be acceptable to TDF and LO? On Mar 7, 2013, at 8:59 AM, Jürgen Schmidt jogischm...@gmail.com wrote: back from vacation I stumbled over this interesting thread and for whatever reason my mail filter skipped Florian's answer. But after asking if I missed a reply I was pointed on https://wiki.documentfoundation.org/License_Policy which is an interesting page to read. Is it possible that this page is somewhat outdated and doesn't reflect the current state of the project. I don't read anything about the Apache License and that the project is now based on the Apache OpenOffice code base. Otherwise it wouldn't have been possible to change the license header in the way it was done for LO 4.0. Maybe worth to add a section to explain this and to avoid confusion. It really confuses me and I am now lost a little bit. How can I as individual contributor know where the code comes from originally. Juergen On 3/5/13 6:32 PM, Jim Jagielski wrote: On Mar 5, 2013, at 10:34 AM, Jim Jagielski j...@jagunet.com wrote: So far, I've rec'd an answer from AOO... I'd appreciate an answer from TDF as well. On Mar 4, 2013, at 11:39 AM, Jim Jagielski j...@jagunet.com wrote: BTW, Please be sure that I'm on the CC list, so I get any and all responses :) On Mar 4, 2013, at 8:08 AM, Jim Jagielski j...@jagunet.com wrote: Hello there. This Email is being directed to the 2 controlling bodies of the Apache OpenOffice Project and LibreOffice (TDF). You will notice that I am sending this from my non-ASF account. Recently, at various conferences, I have been approached by numerous people, both 100% volunteer as well as more corporate affiliated, wondering if it was OK for them to submit code, patches and fixes to both AOO and LO at the same time. In general, these people have code that directly patches LO but they also want to dual-license the code such that it can also be consumed by AOO even if it requires work and modification for it to be committed to, and folded into, the AOO repo. My response has always been that as the orig author of their code/patches/whatever, they can license their contributions as they see fit. However, I have been told that they have rec'd word that such dual-licensed code would not be accepted by, or acceptable to, either the AOO project and/or LO and/or TDF and/or the ASF. Therefore, I am asking for official confirmation from both projects and both entities that both projectsSo are fully OK with accepting code/patches/etc that are licensed in such a way as to be 100% consumable by both projects. For example, if I have a code patch which is dual-licensed both under LGPLv3 and ALv2, that such a patch would be acceptable to both LO and AOO. Thank you. -- Andrew Pitonyak My Macro Document: http://www.pitonyak.org/AndrewMacro.odt Info: http://www.pitonyak.org/oo.php -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
