Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice
Hi Simon, Simon Brouwer wrote on 2011-06-18 17.48: Have a look at the first sentence on the homepage. It simply states that TDF is a Foundation, while strictly spoken, it isn't (yet). The lack of clear information about this on the website might lead outsiders to suspect that TDF want to sweep some uncomfortable facts under the rug. The word Foundation in this sentence could be made a web link to a page that explains about the current situation and the progress towards becoming an actual foundation. That way, things would become much clearer. After the foundation is established, the link could point to the Statutes and similar information. we do share a lot of the current status, e.g. in our blog, but I agree that the wording might be misleading. I just forwarded the topic to the steering-discuss list for feedback from the SC. Thanks for the pointer, indeed. Florian -- Florian Effenberger flo...@documentfoundation.org Steering Committee and Founding Member of The Document Foundation Tel: +49 8341 99660880 | Mobile: +49 151 14424108 Skype: floeff | Twitter/Identi.ca: @floeff -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Hi, Simon Phipps wrote on 2011-06-18 20.15: The project names LibreOffice and The Document Foundation are registered trademarks of their host, [http://www.frodev.org Freies Office Deutschland e.V.], a non-profit organisation registered in Germany. The respective logos and icons used by these projects are also subject to international copyright laws. Use of any of them is subject to the [http://wiki.documentfoundation.org/TradeMark_Policy trademark policy]. I can't see where this should help much in understanding the legal background (like we have posted it regularly to the blog). The trademark holders are not necessarily backing the entity, cf. the Apache example, where Apache is licensee of the trademark, but not (yet?) the trademark holder. However, Oracle, being the trademark holder, is not responsible for Apache's content. Florian -- Florian Effenberger flo...@documentfoundation.org Steering Committee and Founding Member of The Document Foundation Tel: +49 8341 99660880 | Mobile: +49 151 14424108 Skype: floeff | Twitter/Identi.ca: @floeff -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Hi Christian, All, At 23:16 4-6-2011, Christian Lohmaier wrote: Hi Allen, *, On Sat, Jun 4, 2011 at 3:08 PM, Allen Pulsifer pulsi...@openoffice.org wrote: [...] I don't know what vision IBM has for the project. I don't know what code contribution they are going to make--I'm certain they will make some, but I don't know what they will be. I don't know what contributions members of the LibreOffice community will or will not want to make. Given that they had 35 people working on it according to their press releases, that was ended up in OOo was basically nonexistent. As you've been with the OOo project for a couple of years you can probably understand that people that were part of OOo project before switching over to TDF/LibreOffice don't have much trust in IBM's lip service. The few times they did contribute, it was code-dumping, far from contributing in a collaborative manner. The accessibility stuff that Rob just mentioned on the apache list has been promised since 2007 and he correctly stated that is is still (considerable) amount of /work/ needed to get it integrated. They dumped it instead of contributing it. To me that's still a difference. The code is against an obsolete branch (OOo 1.1.5 codeline (!)) http://wiki.services.openoffice.org/wiki/Accessibility/IAccessible2_support I am surprised nobody has responded to this (since there is/was at least one IBM employee on this list...). The accessibility contribution that Rob Weir referred to was probably not the code dump for OpenOffice.org 1.1.5 but a contribution to OpenOffice.org 3.1 (if I remember correctly). See my comment at http://www.robweir.com/blog/2011/06/apache-openoffice.html#comment-20026. (Note: OpenOffice.org 1.1.5 was released in September 2005; IAccessible2 was released in December 2006 http://www-03.ibm.com/press/us/en/pressrelease/20773.wss.) At this moment I know no one at Oracle who can or wants to say how much of the IAccessible2 implementation will end up in OpenOffice.org 3.4. Best regards, Christophe Strobbe I do know this however. There is currently an open invitation for us to get involved. If we get involved, we can have a say in with direction of the project. Not really, as you first have to surrender to the Apache's licence terms. And that alone is reason for me not to join the effort. We can ensure that direction of the project provides the maximum benefit for LibreOffice, which includes any contributions from IBM. Basically, we can get IBM working for us. I really doubt it. What would change for them now, with the permissive licence, that did prevent them in the last 5 years from contributing? They (according to their press release) had massive manpower working on it (35 people), but what ended up in OOo is two code dumps to ancient codeline, one of which being lotuswordprofilter, the other the abovementioned accessibility dump. (...) ciao Christian -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Hi Christoph, *, On Tue, Jul 5, 2011 at 3:34 PM, Christophe Strobbe christophe.stro...@esat.kuleuven.be wrote: At 23:16 4-6-2011, Christian Lohmaier wrote: The few times they did contribute, it was code-dumping, far from contributing in a collaborative manner. The accessibility stuff that Rob just mentioned on the apache list has been promised since 2007 and he correctly stated that is is still (considerable) amount of /work/ needed to get it integrated. They dumped it instead of contributing it. To me that's still a difference. The code is against an obsolete branch (OOo 1.1.5 codeline (!)) http://wiki.services.openoffice.org/wiki/Accessibility/IAccessible2_support I am surprised nobody has responded to this (since there is/was at least one IBM employee on this list...). The accessibility contribution that Rob Weir referred to was probably not the code dump for OpenOffice.org 1.1.5 but a contribution to OpenOffice.org 3.1 Well, as seen on this list (by Malte's post), apparently there has been work on a *private* cws that nobody in the community (and yes, people who are working on private cws are not part of the community in this regard - they are of course for that part of their work that happens in public) All promises IBM is making/has made so far is only lip service for me. I only believe it after I see the actual contributions from them. (And as written I don't consider code dumps that need a man-year of work to get integrated as contribution) (if I remember correctly). See my comment at http://www.robweir.com/blog/2011/06/apache-openoffice.html#comment-20026. (Note: OpenOffice.org 1.1.5 was released in September 2005; IAccessible2 was released in December 2006 http://www-03.ibm.com/press/us/en/pressrelease/20773.wss.) Yes, and that makes it even more pointless to dump the code against the OOo 1.1.5 codeline. Not against the version that is in current development, but to a codeline that is basically done for since two years. (again the commitment statment is from 2007) It is all about the preception of IBM's past contributions to OOo - and those are, despite the massive amount of developers assigned to the project (35 developers, in the announcement from 2007, the same figure stated in the incubation list) is nonexistant basically. Know we know that there has been a behind-the-doors code contribution of the IA2 stuff (or who knows, maybe Sun/Oracle engineers did all the work themselves porting the dump to current codeline, doesn't matter really). But what else did IBM do in the last 4/5 years? At this moment I know no one at Oracle who can or wants to say how much of the IAccessible2 implementation will end up in OpenOffice.org 3.4. Well, then you missed Malte Timmermann's post. (about the status of iaccessible2), As Rob is strongly against releasing OOo 3.4 with the blessing of the apache-OOo project (take that discussion to the old OOo-lists basically (paraphrased)), I doubt there will be a OOo 3.4.0 at all. http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3c4df3a2e8.8010...@gmx.com%3E http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3c4df3a100.2060...@gmx.com%3E (he posted the very same mail twice) Actually the status with IA2 in OOo is quite good - but not in public CWSes yet - I am quite sure it will find it's way to Apache OOo. And until there is a release of Apache-OOo that is comparable in features/functionality to the current OOo codebase: This will take quite a bit of time. Oracle's staff didn't even manage to report the size of current bugzilla's database as has been requested by the Apache-infrastructure team yet. An open question since June 17. Three weeks and still no answer to the simple question: We are looking for more detail about the size of the OOo bugzilla database. How large is the backup, and what database is being used? This is the information that Infrastructure needs to know if they have a preference about our choice. http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201106.mbox/%3c097e5bc1-6218-422b-8989-8c082eb0f...@comcast.net%3E So you can imagine that when it comes on deciding whether to release OOo 3.4.0 on the old infrastructure will take ages as well. It's also somewhat ridiculous how long it takes for them to mirror the hg-repos for merging. But I didn't see any real progress wrt. licencing issues either. So while they then might have a repo will all open/interesting cws merged in, still the problems of what files are exactly covered by the grant remains. Only progress in this regard is to use apache-batik for svg-import (OK), and go back to myspell for spellchecking (and thus crippling spellchecking, nullifying the progress hunspell brought for langauges with complex compound and flexation rules) - but that are at least suggestions to move on. There are many people on the incubator-ooo-dev list, but only few who have a real clue. And even fewer who are actively driving
Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice
Hi Christian, All, At 16:14 5-7-2011, Christian Lohmaier wrote: Hi Christoph, *, On Tue, Jul 5, 2011 at 3:34 PM, Christophe Strobbe christophe.stro...@esat.kuleuven.be wrote: At 23:16 4-6-2011, Christian Lohmaier wrote: The few times they did contribute, it was code-dumping, far from contributing in a collaborative manner. The accessibility stuff that Rob just mentioned on the apache list has been promised since 2007 and he correctly stated that is is still (considerable) amount of /work/ needed to get it integrated. They dumped it instead of contributing it. To me that's still a difference. The code is against an obsolete branch (OOo 1.1.5 codeline (!)) http://wiki.services.openoffice.org/wiki/Accessibility/IAccessible2_support I am surprised nobody has responded to this (since there is/was at least one IBM employee on this list...). The accessibility contribution that Rob Weir referred to was probably not the code dump for OpenOffice.org 1.1.5 but a contribution to OpenOffice.org 3.1 Well, as seen on this list (by Malte's post), apparently there has been work on a *private* cws that nobody in the community (and yes, people who are working on private cws are not part of the community in this regard - they are of course for that part of their work that happens in public) All promises IBM is making/has made so far is only lip service for me. I only believe it after I see the actual contributions from them. (And as written I don't consider code dumps that need a man-year of work to get integrated as contribution) If Oracle asks IBM to implement IAccessible2 on version 3.1 and releases OpenOffice.org 3.2 before IBM has submitted the IAccessible2 implementation, how is IBM to blame? Between 3.1 and 3.2 the code had changed and had been moved to another type of repository. That is the reason for the complex and time-consuming integration work that Oracle needed to do for IAccessible2. The integration and testing were still in progress when Oracle decided to stop investing in OpenOffice.org. As far as I know, that is why the IAccessible2 code did not end up in public repositories. (if I remember correctly). See my comment at http://www.robweir.com/blog/2011/06/apache-openoffice.html#comment-20026. (Note: OpenOffice.org 1.1.5 was released in September 2005; IAccessible2 was released in December 2006 http://www-03.ibm.com/press/us/en/pressrelease/20773.wss.) Yes, and that makes it even more pointless to dump the code against the OOo 1.1.5 codeline. The contribution to the 1.1.5 codeline is irrelevant because completely outdated. I added that note merely as backgound information. Not against the version that is in current development, but to a codeline that is basically done for since two years. (again the commitment statment is from 2007) It is all about the preception of IBM's past contributions to OOo - and those are, despite the massive amount of developers assigned to the project (35 developers, in the announcement from 2007, the same figure stated in the incubation list) is nonexistant basically. Know we know that there has been a behind-the-doors code contribution of the IA2 stuff (or who knows, maybe Sun/Oracle engineers did all the work themselves porting the dump to current codeline, doesn't matter really). If Sun/Oracle engineers state that IBM donated the IAccessible2 implementation, it is unlikely that this piece of work was done by Sun/Oracle. But what else did IBM do in the last 4/5 years? At this moment I know no one at Oracle who can or wants to say how much of the IAccessible2 implementation will end up in OpenOffice.org 3.4. Well, then you missed Malte Timmermann's post. Yes, I missed that. (Curiously, he sent that message from a private address, not an Oracle address.) (about the status of iaccessible2), As Rob is strongly against releasing OOo 3.4 with the blessing of the apache-OOo project (take that discussion to the old OOo-lists basically (paraphrased)), I doubt there will be a OOo 3.4.0 at all. If that is true, that will be a loss for the accessibility of OpenOffice.org and LibreOffice on Windows. Best regards, Christophe http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3c4df3a2e8.8010...@gmx.com%3E http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3c4df3a100.2060...@gmx.com%3E (he posted the very same mail twice) Actually the status with IA2 in OOo is quite good - but not in public CWSes yet - I am quite sure it will find it's way to Apache OOo. And until there is a release of Apache-OOo that is comparable in features/functionality to the current OOo codebase: This will take quite a bit of time. Oracle's staff didn't even manage to report the size of current bugzilla's database as has been requested by the Apache-infrastructure team yet. An open question since June 17. Three weeks and still no answer to the simple question: We are looking for more detail about the size of
Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice
Hi Christophe, *, On Tue, Jul 5, 2011 at 4:50 PM, Christophe Strobbe christophe.stro...@esat.kuleuven.be wrote: At 16:14 5-7-2011, Christian Lohmaier wrote: On Tue, Jul 5, 2011 at 3:34 PM, Christophe Strobbe christophe.stro...@esat.kuleuven.be wrote: At 23:16 4-6-2011, Christian Lohmaier wrote: [...] Well, as seen on this list (by Malte's post), apparently there has been work on a *private* cws that nobody in the community (and yes, people who are working on private cws are not part of the community in this regard - they are of course for that part of their work that happens in public) All promises IBM is making/has made so far is only lip service for me. I only believe it after I see the actual contributions from them. (And as written I don't consider code dumps that need a man-year of work to get integrated as contribution) If Oracle asks IBM to implement IAccessible2 on version 3.1 and releases OpenOffice.org 3.2 before IBM has submitted the IAccessible2 implementation, how is IBM to blame? Reality check please. 1st of all: What is stuff you know, and what is stuff you guess? Do you know that the 3.1 based ia2 dump/work is because Oracle asked for it? If Oracle asked for it, do you know when Oracle asked for it? Do you think Oracle really is so stupid to explicitly ask for code based on an old branch? If Oracle did ask for it, and IBM did contribute - why wasn't the cws integrated? 2nd) Obviously you cannot integrate something that is not ready. Why was it not ready? Because nobody worked on it. Who could do the work on it? Of course best the developers who know the code, i.e IBM developers. And you cannot delay a release for years. (the cws Caolan mentioned in the blog-comment was created in 2010-05 - while the branch-off for 3.2 already happened 2009-09 more than half a year earlier) Between 3.1 and 3.2 the code had changed and had been moved to another type of repository. Again reality check. Oracle surely did ask for the code to be contributed against the current, actively being-worked-on codeline. A codeline that is not in feature-freeze. What IBM then delivers is a completely different question. Also whether Oracle/Sun asks for it in 2008, but IBM delivers in 2010, it's obvious that code makes progress. That is the reason for the complex and time-consuming integration work that Oracle needed to do for IAccessible2. NO! Why does it have to be Oracle to do the integration work. Again one of the points about collaboration. Just uploading a million-line-codepatch somewhere is not contributing. It is complying with whatever deals that were signed or to comply with license matters at best. The integration and testing were still in progress when Oracle decided to stop investing in OpenOffice.org. As far as I know, that is why the IAccessible2 code did not end up in public repositories. Again this is stupid argumentation. We're talking about a OpenSource software here after all. And we're not talking about weeks, but years. We're talking about big announcements to dedicate more than 30 developers to work on the officesuite and collaborate with upstream, but no results after 4/5 years. And this further proves my point about questioning IBM's commitment. Lip service, but no actual work that ends up upstream. They did not contribute to OOo, but they did drop some code at Oracle. Again this is not my idea of contributing to the project. The contribution to the 1.1.5 codeline is irrelevant because completely outdated. I added that note merely as backgound information. No, it is not irrelevant, because it is the very same situation. Big announcement we will conribute, we have lots of manpower but no results. That's the whole point. IBM doesn't have a record of being a good contributor, the opposite is the case. And to change this, we don't need another lip-service announcement, but actual code contribution. That you can only point at Ia2, but not at other work is further prove of this topic. And don't get me wrong, I'm sure that you'll see IBM contributing to apache-OOo, at least until you can actually build something from Apache-OOo sources you can ship to the users, but after that I'm pretty sure that IBM will focus again on its very own Symphony and only do the necessary stuff to keep their own stuff compatible. And don't get me wrong²: I'd be happy if IBM proves me wrong. If Sun/Oracle engineers state that IBM donated the IAccessible2 implementation, it is unlikely that this piece of work was done by Sun/Oracle. Again it is not about the Ia2 work itself, but the porting from the old 1.1.5 codedrop to current codeline. You apparently don't know any hard facts about this, neither do I. So while you claim that Oracle did ask IBM for the code ported to the 3.1 codeline, and that IBM then followed this request, I question this scenario. Or even if IBM did contribute it against the 3.1 codeline: Why is it still not integrated? This can only mean that a huge amount of
Re: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
2011/6/22 Jesús Corrius je...@softcatala.org: I checked those files as well. They are all 'noarch' (do not contain compiled programs; No Architecture), and contain the same .png branding images. The license not only covers the code, also the images. So if those images are in the program, the source code must include them. That's why the link to the source code has to point to them too, that is, it must point to the modified source code of your distribution. And not the original at LibreOffice's. Or point to both ;) Two points: 1. When you reply to an e-mail, it is important to keep the lines which say On Friday 22 June 2011, XYZ x...@gmail.com said: In this way, it is easy to see who said the quoted text. 2. As I said earlier, a user can get LibreOffice from the LibreOffice website, or get it packaged from some other source (such as a Linux distribution). It is the problem of that other source to explain to the user where to get any modifications/additions. We can say somewhere in the About dialog box something along the lines: You can get the source code for this version of LibreOffice by following the instructions at http://wiki.documentfoundation.org/. Please note that if you received LibreOffice from a distributor other than www.libreoffice.org, there might exist additional modifications; consult that distributor for more details. If the distributor is really into making significant changes in their LibreOffice, they can modify the above message and add specific instructions that relate to them. It is quite easy to do so; for Debian/Ubuntu, you can write apt-get source libreoffice However, this is an issue that Debian/Ubuntu and any other distribution have to deal with. Actually, a user of a Linux distribution is supposed to know already that for each package they can use these 'apt-get source xyz' commands to get the source code. Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
On Tue, 21 Jun 2011 01:18:34 +0200 Jesús Corrius je...@softcatala.org wrote: 1. We want to add a paragraph somewhere in the About dialog box which says that if we are interested in the source code, we should read a specific Wiki page, for example http://wiki.documentfoundation.org/Development/AvailabilityOfSourceCode I see a problem here. Usually GNU/Linux distributions make modifications to the original source code. That means that the *real* source code will be the one from your distro and not the one you can download from the LibO website, hence the information will be misleading. In this case the distributions could modifiy the about box as well and change the link accordingly... Or just add an additional link to their specific version. We provide all the required source tarballs for each version and every piece of code is in our git repository. So we fulfill all the requirements but we have the problem that it's not easy to find. I guess writing a good text about how to get the source code for every version and place it in our download page (or a link to the wiki page) is good enough. Should be sufficient as well. Manfred -- Manfred Usselmann usselman...@icg-online.de -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
Manfred Usselmann wrote: I see a problem here. Usually GNU/Linux distributions make modifications to the original source code. That means that the *real* source code will be the one from your distro and not the one you can download from the LibO website, hence the information will be misleading. In this case the distributions could modifiy the about box as well and change the link accordingly... Or just add an additional link to their specific version. I see little point in burdening distros with writing specific instructions into tons of about boxes of their software, when there are well-known distro methods to get the source (pkg-manager install pkgname-src). Especially since all of that needs to be translated into ~100 languages. We provide all the required source tarballs for each version and every piece of code is in our git repository. So we fulfill all the requirements but we have the problem that it's not easy to find. I guess writing a good text about how to get the source code for every version and place it in our download page (or a link to the wiki page) is good enough. Should be sufficient as well. Sure, let's link to some build howto also from the download page - but I consider this discussion somewhat moot, since anyone wanting to modify and/or compile LibreOffice code (which is the whole spirit behind copyleft) will surely visit the Get Involved or Developers subpages (that are very prominently visible on the libreoffice site). And that has all the info. In closing, when a version is retired (3.3.2 is superseded by 3.3.3), both src and binary gets moved to http://download.documentfoundation.org/libreoffice/old/ So nothing is lost. :) Cheers, -- Thorsten -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
2011/6/21 Jesús Corrius je...@softcatala.org: 1. We want to add a paragraph somewhere in the About dialog box which says that if we are interested in the source code, we should read a specific Wiki page, for example http://wiki.documentfoundation.org/Development/AvailabilityOfSourceCode I see a problem here. Usually GNU/Linux distributions make modifications to the original source code. That means that the *real* source code will be the one from your distro and not the one you can download from the LibO website, hence the information will be misleading. As far as I know, the distributions make minimal or no changes to the actually code of LibreOffice. The best they will do is add packaging instructions. If you have information of a distribution that performs extensive LibreOffice development and did not bother to contribute them upstream, then please tell us who they are. I would not see this as a show stopper; we can just append something like If you did not receive LibreOffice from http://www.libreoffice.org/, there might exist extra changes to the source code. Consult the distributor that gave you the LibreOffice installation packages for more details. We provide all the required source tarballs for each version and every piece of code is in our git repository. So we fulfill all the requirements but we have the problem that it's not easy to find. I guess writing a good text about how to get the source code for every version and place it in our download page (or a link to the wiki page) is good enough. So, everyone agrees that in any case we should write a nice wiki page that explains the merits of the copyleft LibreOffice? That is, a Wiki page that explains in simple terms how to benefit from the source code. Stage 1 would be to simply visit http://cgit.freedesktop.org/libreoffice/ and select the version they have. For LibreOffice 3.3.2 and the Writer module, it's http://cgit.freedesktop.org/libreoffice/writer/tree/?h=libreoffice-3-3-2 From there, you can view the files online. Stage 2 would be to clone the source code repositories. The compressed repositories are about 1.2GB, and with the working copies they should reach about 2GB. Then, with git commands it is possible to switch to any branch/version of LibreOffice (such as 3.3.2). Using Git source code tools, it is easy to view changes. For example, see http://trac.novowork.com/gitg/wiki/Screenshots Stage 3 would be to compile the whole lot and produce a new version of LibreOffice. Stage 4 would be to make an elemental change in LibreOffice (such as modify slightly the About dialog box), compile, and view the change in the newly produced LibreOffice. I think that such a document will empower the end-users, and make them appreciate the fact that LibreOffice is copyleft. Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
Þann þri 21.jún 2011 11:18, skrifaði Simos Xenitellis: 2011/6/21 Jesús Corriusje...@softcatala.org: 1. We want to add a paragraph somewhere in the About dialog box which says that if we are interested in the source code, we should read a specific Wiki page, for example http://wiki.documentfoundation.org/Development/AvailabilityOfSourceCode I see a problem here. Usually GNU/Linux distributions make modifications to the original source code. That means that the *real* source code will be the one from your distro and not the one you can download from the LibO website, hence the information will be misleading. As far as I know, the distributions make minimal or no changes to the actually code of LibreOffice. The best they will do is add packaging instructions. If you have information of a distribution that performs extensive LibreOffice development and did not bother to contribute them upstream, then please tell us who they are. At least OpenSuse does more than that; they've been doing extensive 'branding' of both OOo and LO for quite some time. Example: http://software.opensuse.org/search/download?base=openSUSE%3A11.4file=openSUSE%3A%2FTumbleweed%3A%2FTesting%2FopenSUSE_Tumbleweed_standard%2Fnoarch%2Flibreoffice-branding-openSUSE-3.3.1-1.1.noarch.rpmquery=libreoffice-branding Regards, Sveinn í Felli -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
On Tue, Jun 21, 2011 at 3:11 PM, Sveinn í Felli svei...@nett.is wrote: Þann þri 21.jún 2011 11:18, skrifaði Simos Xenitellis: 2011/6/21 Jesús Corriusje...@softcatala.org: 1. We want to add a paragraph somewhere in the About dialog box which says that if we are interested in the source code, we should read a specific Wiki page, for example http://wiki.documentfoundation.org/Development/AvailabilityOfSourceCode I see a problem here. Usually GNU/Linux distributions make modifications to the original source code. That means that the *real* source code will be the one from your distro and not the one you can download from the LibO website, hence the information will be misleading. As far as I know, the distributions make minimal or no changes to the actually code of LibreOffice. The best they will do is add packaging instructions. If you have information of a distribution that performs extensive LibreOffice development and did not bother to contribute them upstream, then please tell us who they are. At least OpenSuse does more than that; they've been doing extensive 'branding' of both OOo and LO for quite some time. Example: http://software.opensuse.org/search/download?base=openSUSE%3A11.4file=openSUSE%3A%2FTumbleweed%3A%2FTesting%2FopenSUSE_Tumbleweed_standard%2Fnoarch%2Flibreoffice-branding-openSUSE-3.3.1-1.1.noarch.rpmquery=libreoffice-branding I opened the file (file-roller can open .rpm files) and I only saw some OpenSUSE branding icons and a small rc file. There was no code in there, and the file is a 'noarch' one (No Architecture). Perhaps you are referring to a different file? Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
Þann þri 21.jún 2011 12:11, skrifaði Sveinn í Felli: Þann þri 21.jún 2011 11:18, skrifaði Simos Xenitellis: 2011/6/21 Jesús Corriusje...@softcatala.org: 1. We want to add a paragraph somewhere in the About dialog box which says that if we are interested in the source code, we should read a specific Wiki page, for example http://wiki.documentfoundation.org/Development/AvailabilityOfSourceCode I see a problem here. Usually GNU/Linux distributions make modifications to the original source code. That means that the *real* source code will be the one from your distro and not the one you can download from the LibO website, hence the information will be misleading. As far as I know, the distributions make minimal or no changes to the actually code of LibreOffice. The best they will do is add packaging instructions. If you have information of a distribution that performs extensive LibreOffice development and did not bother to contribute them upstream, then please tell us who they are. At least OpenSuse does more than that; they've been doing extensive 'branding' of both OOo and LO for quite some time. Example: http://software.opensuse.org/search/download?base=openSUSE%3A11.4file=openSUSE%3A%2FTumbleweed%3A%2FTesting%2FopenSUSE_Tumbleweed_standard%2Fnoarch%2Flibreoffice-branding-openSUSE-3.3.1-1.1.noarch.rpmquery=libreoffice-branding Regards, Sveinn í Felli Better link here: http://software.opensuse.org/search?q=libreoffice-brandingbaseproject=openSUSE%3A11.4lang=enexclude_debug=true Regards, Sveinn -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
Þann þri 21.jún 2011 12:46, skrifaði Simos Xenitellis: On Tue, Jun 21, 2011 at 3:11 PM, Sveinn í Fellisvei...@nett.is wrote: Þann þri 21.jún 2011 11:18, skrifaði Simos Xenitellis: 2011/6/21 Jesús Corriusje...@softcatala.org: 1. We want to add a paragraph somewhere in the About dialog box which says that if we are interested in the source code, we should read a specific Wiki page, for example http://wiki.documentfoundation.org/Development/AvailabilityOfSourceCode I see a problem here. Usually GNU/Linux distributions make modifications to the original source code. That means that the *real* source code will be the one from your distro and not the one you can download from the LibO website, hence the information will be misleading. As far as I know, the distributions make minimal or no changes to the actually code of LibreOffice. The best they will do is add packaging instructions. If you have information of a distribution that performs extensive LibreOffice development and did not bother to contribute them upstream, then please tell us who they are. At least OpenSuse does more than that; they've been doing extensive 'branding' of both OOo and LO for quite some time. Example: http://software.opensuse.org/search/download?base=openSUSE%3A11.4file=openSUSE%3A%2FTumbleweed%3A%2FTesting%2FopenSUSE_Tumbleweed_standard%2Fnoarch%2Flibreoffice-branding-openSUSE-3.3.1-1.1.noarch.rpmquery=libreoffice-branding I opened the file (file-roller can open .rpm files) and I only saw some OpenSUSE branding icons and a small rc file. There was no code in there, and the file is a 'noarch' one (No Architecture). Perhaps you are referring to a different file? Simos Better link here: http://software.opensuse.org/search?q=libreoffice-brandingbaseproject=openSUSE%3A11.4lang=enexclude_debug=true BTW, there may be other packages as well. regards, Sveinn -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
On Tue, Jun 21, 2011 at 10:25 PM, Sveinn í Felli svei...@nett.is wrote: Þann þri 21.jún 2011 12:46, skrifaði Simos Xenitellis: On Tue, Jun 21, 2011 at 3:11 PM, Sveinn í Fellisvei...@nett.is wrote: Þann þri 21.jún 2011 11:18, skrifaði Simos Xenitellis: 2011/6/21 Jesús Corriusje...@softcatala.org: 1. We want to add a paragraph somewhere in the About dialog box which says that if we are interested in the source code, we should read a specific Wiki page, for example http://wiki.documentfoundation.org/Development/AvailabilityOfSourceCode I see a problem here. Usually GNU/Linux distributions make modifications to the original source code. That means that the *real* source code will be the one from your distro and not the one you can download from the LibO website, hence the information will be misleading. As far as I know, the distributions make minimal or no changes to the actually code of LibreOffice. The best they will do is add packaging instructions. If you have information of a distribution that performs extensive LibreOffice development and did not bother to contribute them upstream, then please tell us who they are. At least OpenSuse does more than that; they've been doing extensive 'branding' of both OOo and LO for quite some time. Example: http://software.opensuse.org/search/download?base=openSUSE%3A11.4file=openSUSE%3A%2FTumbleweed%3A%2FTesting%2FopenSUSE_Tumbleweed_standard%2Fnoarch%2Flibreoffice-branding-openSUSE-3.3.1-1.1.noarch.rpmquery=libreoffice-branding I opened the file (file-roller can open .rpm files) and I only saw some OpenSUSE branding icons and a small rc file. There was no code in there, and the file is a 'noarch' one (No Architecture). Perhaps you are referring to a different file? Simos Better link here: http://software.opensuse.org/search?q=libreoffice-brandingbaseproject=openSUSE%3A11.4lang=enexclude_debug=true BTW, there may be other packages as well. I checked those files as well. They are all 'noarch' (do not contain compiled programs; No Architecture), and contain the same .png branding images. Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
I checked those files as well. They are all 'noarch' (do not contain compiled programs; No Architecture), and contain the same .png branding images. The license not only covers the code, also the images. So if those images are in the program, the source code must include them. That's why the link to the source code has to point to them too, that is, it must point to the modified source code of your distribution. And not the original at LibreOffice's. Or point to both ;) -- Jesús Corrius je...@softcatala.org Document Foundation founding member Mobile: +34 661 11 38 26 Skype: jcorrius | Twitter: @jcorrius -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
On 2011-06-18 5:39 AM, Simos Xenitellis wrote: And there is no better way to do this than have the 'git repositories' of the LibreOffice source code. You were correct earlier - he is merely pointing out that nowhere in the license agreement (I haven't read it so am not making the same claim) does it say where or how to GET ACCESS TO the source code. If this is true, it should be rectified immediately. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
Dennis, Tanstaafl, I take your point. Users that have 3.3.2 installed can only get the code for 3.3.3 from the website. As discussed above, I think this meets the spirit of the license but not the specific letter. Simon's idea about downloading the repo at the 3.3.2 marker is a great one, but there is no path to that on either website or wiki. -- View this message in context: http://nabble.documentfoundation.org/Availability-of-source-code-Was-Re-OFF-TOPIC-about-GPL-enforcement-Was-Re-tdf-discuss-Re-Libreoffice-tp3078442p3087960.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
On Mon, Jun 20, 2011 at 11:22 PM, John LeMoyne Castle lemoyne.cas...@gmail.com wrote: Dennis, Tanstaafl, I take your point. Users that have 3.3.2 installed can only get the code for 3.3.3 from the website. As discussed above, I think this meets the spirit of the license but not the specific letter. Simon's idea about downloading the repo at the 3.3.2 marker is a great one, but there is no path to that on either website or wiki. Let's do it then! 1. We want to add a paragraph somewhere in the About dialog box which says that if we are interested in the source code, we should read a specific Wiki page, for example http://wiki.documentfoundation.org/Development/AvailabilityOfSourceCode 2. We create the web page which talks about the git repositories, links to the pages about cloning and checking out branches such as libreoffice 3.3.2. 3. We write a patch for LibreOffice to add the special text and test it. 4. We submit a bug report to have the feature added to the next version of LibreOffice. I can help with items 2, 3 and 4. I need help however as to a. where exactly in the About box (or in the Help menu) shall we put the short paragraph Take screenshots and show on them where to add the text. Put those screenshots on www.imgur.com, send the URL here so we can view them. b. what shall the text say. Propose something that will be helpful for someone who genuinely wants to learn and use the LibreOffice source code. Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
1. We want to add a paragraph somewhere in the About dialog box which says that if we are interested in the source code, we should read a specific Wiki page, for example http://wiki.documentfoundation.org/Development/AvailabilityOfSourceCode I see a problem here. Usually GNU/Linux distributions make modifications to the original source code. That means that the *real* source code will be the one from your distro and not the one you can download from the LibO website, hence the information will be misleading. We provide all the required source tarballs for each version and every piece of code is in our git repository. So we fulfill all the requirements but we have the problem that it's not easy to find. I guess writing a good text about how to get the source code for every version and place it in our download page (or a link to the wiki page) is good enough. -- Jesús Corrius je...@softcatala.org Document Foundation founding member Mobile: +34 661 11 38 26 Skype: jcorrius | Twitter: @jcorrius -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
On 18/06/2011 09:39, Simos Xenitellis wrote: The spirit does go well beyond the letter. Ideally, the 'git repositories' should be what everyone gets, rather than a source code snapshot that has no source change history. A couple of years ago I sent a question to FSF about meeting source code requirements for GPLG programs. Specifically, I asked if substituting the entire current code repository was acceptable, rather than a tarball of the specific code that was (supposedly) used. Their response was that the repository was acceptable. They also suggested that a ReadMe file that contained the instructions on pulling the code that the program used be included on the DVD. jonathon -- If Bing copied Google, there wouldn't be anything new worth requesting. If Bing did not copy Google, there wouldn't be anything relevant worth requesting. DaveJakeman 20110207 Groklaw. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
-Original Message- From: Simos Xenitellis [mailto:simos.li...@googlemail.com] Sent: Friday, June 17, 2011 17:44 To: discuss@documentfoundation.org Subject: Re: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)) On Sat, Jun 18, 2011 at 2:50 AM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: I didn't say I didn't know how to do it. I didn't say I wanted to build it. This is about honoring the spirit of the free software promise. It is not even about building the code. People may want to do any number of things with the source code (inspect for bugs, for example). To honour the spirit of the free software promise, it should be more than adequate to grab the git repositories. Ask me if you want more details for this. To honour the letter of the free software promise, then you do need those 3.3.2 tarballs. A quick look at the TDF download website shows that it currently covers the latest versions (due to space?), 3.3.3 for the 3.3 line, and 3.4.0 for the 3.4 line. Digging a bit deeper shows this http://ftp.heanet.ie/mirrors/tdf/libreoffice/box/3.3.2/LibO_3.3.2-2_DVD_allplatforms_de.iso 2.8GB DVD ISO which I believe has the source code. People who actually want to do things with the source code would need to use the git repositories, as it shows the changes between different versions. You can also view online your 3.3.2 branch at http://cgit.freedesktop.org/libreoffice On Sat, Jun 18, 2011 at 4:16 AM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: I consider the spirit to always go beyond the letter. The spirit does go well beyond the letter. The spirit of the free software promise wants to enable you to actually work on the source code, compile it, make your private enhancements and possibly submit those modifications back to the community. And there is no better way to do this than have the 'git repositories' of the LibreOffice source code. Ideally, the 'git repositories' should be what everyone gets, rather than a source code snapshot that has no source change history. Admittedly, the 'git repositories' are about 1.2GB, but once you have a local copy, you can use frequently 'git pull' to update them with any upstream changes. Do you want to switch the repository view to the 3.3.2 version? Simply run the command git checkout --track origin/libreoffice-3-3-2 Having a source code snapshot (tarball) is probably not much useful compared to what you get with using the repositories, http://wiki.documentfoundation.org/Development/How_to_build Simos -- A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Fri, Jun 17, 2011 at 5:46 PM, Keith Curtis keit...@gmail.com wrote: On Fri, Jun 17, 2011 at 8:08 AM, BRM bm_witn...@yahoo.com wrote: Yet, Calligra and KOffice - which both have very similar codebases - have a much healthier relationship, etc. They don't see themselves as competing with each other either. I didn't know the details of the Calligra fork but I did a bit of researching. It seems like it was created because ONE person was causing problems (http://aseigo.blogspot.com/2010/12/rose-by-any-other-name.html) so the rest moved. However, if everyone but one moves, it is not really a fork, but a mutiny / change in leadership. -Keith It wasn't even that. A mutiny or change in leadership would imply that one person was the leader of KOffice, which he wasn't. He was just the maintainer of one part of the suite (the word processor). But it was clear he was never going to be able to reconcile his differences with the rest of the developers, so both sides decided to split. The reason for the name change is largely independent of the split and more to do with the fact that they have a number of non-office-related programs and the office name was turning users off from those program. -Todd -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Hi, Jim Jagielski wrote on 2011-06-15 17.28: Maybe it's a language issue, but no, the imprint does nothing at all to make it clear. It simply says, in effect, FroDev wrote the content and they are responsible for the content on the site. It says nothing at all about the legal structure at all. so, how would you write things to be understandable much better? I'm really curious to hear how the perception could be made better... (seriously asking, not meant with bad intentions) Florian -- Florian Effenberger flo...@documentfoundation.org Steering Committee and Founding Member of The Document Foundation Tel: +49 8341 99660880 | Mobile: +49 151 14424108 Skype: floeff | Twitter/Identi.ca: @floeff -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Op 18-6-2011 12:35, Florian Effenberger schreef: Hi, Jim Jagielski wrote on 2011-06-15 17.28: Maybe it's a language issue, but no, the imprint does nothing at all to make it clear. It simply says, in effect, FroDev wrote the content and they are responsible for the content on the site. It says nothing at all about the legal structure at all. so, how would you write things to be understandable much better? I'm really curious to hear how the perception could be made better... (seriously asking, not meant with bad intentions) Have a look at the first sentence on the homepage. It simply states that TDF is a Foundation, while strictly spoken, it isn't (yet). The lack of clear information about this on the website might lead outsiders to suspect that TDF want to sweep some uncomfortable facts under the rug. The word Foundation in this sentence could be made a web link to a page that explains about the current situation and the progress towards becoming an actual foundation. That way, things would become much clearer. After the foundation is established, the link could point to the Statutes and similar information. -- Vriendelijke groet, Simon Brouwer. | http://nl.openoffice.org | http://www.opentaal.org | -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
Simos Xenitellis wrote: On Sat, Jun 18, 2011 at 1:30 AM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: Ignoring the repetition on who is entitled to source code and how they are told about it, I would like to know the answers to some very specific, tangible matters closer to home. My question is basically whether the terms of a GPL license attached to a software distribution are applicable to that software distribution, not just downstream derivatives of it. I assume the answer is yes. - Dennis WHY I ASK I have a copy of LibreOffice 3.3.2 installed on my computer. I am looking for any place that I am offered access to the specific (or, indeed, any) source code for the LibreOffice 3.3.2 distribution that I have installed (en-win-x86). Admittedly, I never checked the UI text as to where you can get the source code. To build LibreOffice, I would simply follow the instructions at http://wiki.documentfoundation.org/Development/How_to_build which cover different operating systems. By following the instructions, you create a local repository of the source code, and this repository has *all* versions of LibreOffice (such as 3.3.2 and 3.4.0) and you can select which to build. It should take you a few hours of downloading + compilation to create your own LibreOffice. If you have a fast Internet speed and a good computer, it should take you about 3 hours of compilation. Your question is actually about whether we can make the Help→License information more informative so that users who would like to build LibreOffice, will get directed to the How_to_build page. I had no trouble finding and downloading source code, it is posted right there on the download site. Actually I downloaded it purely for curiosity, I am not qualified to write code in C++ , but I looked at it using Notepad. In that form, it is basically just gibberish, perhaps you have to have a copy of the C++ programming language on your computer in order to see it in an intelligible form, but at least I know that I succeeded in getting the source of part of the Writer module. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On 18 Jun 2011, at 11:35, Florian Effenberger wrote: Hi, Jim Jagielski wrote on 2011-06-15 17.28: Maybe it's a language issue, but no, the imprint does nothing at all to make it clear. It simply says, in effect, FroDev wrote the content and they are responsible for the content on the site. It says nothing at all about the legal structure at all. so, how would you write things to be understandable much better? I'm really curious to hear how the perception could be made better... (seriously asking, not meant with bad intentions How about changing the text in the footer that reads: LibreOffice and The Document Foundation are registered trademarks. Their respective logos and icons are subject to international copyright laws. The use of these therefore is subject to our trademark policy. to read: The project names LibreOffice and The Document Foundation are registered trademarks of their host, [http://www.frodev.org Freies Office Deutschland e.V.], a non-profit organisation registered in Germany. The respective logos and icons used by these projects are also subject to international copyright laws. Use of any of them is subject to the [http://wiki.documentfoundation.org/TradeMark_Policy trademark policy]. S. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
- Original Message From: Simon Phipps si...@webmink.com On 18 Jun 2011, at 11:35, Florian Effenberger wrote: Jim Jagielski wrote on 2011-06-15 17.28: Maybe it's a language issue, but no, the imprint does nothing at all to make it clear. It simply says, in effect, FroDev wrote the content and they are responsible for the content on the site. It says nothing at all about the legal structure at all. so, how would you write things to be understandable much better? I'm really curious to hear how the perception could be made better... (seriously asking, not meant with bad intentions How about changing the text in the footer that reads: LibreOffice and The Document Foundation are registered trademarks. Their respective logos and icons are subject to international copyright laws. The use of these therefore is subject to our trademark policy. to read: The project names LibreOffice and The Document Foundation are registered trademarks of their host, [http://www.frodev.org Freies Office Deutschland e.V.], a non-profit organisation registered in Germany. The respective logos and icons used by these projects are also subject to international copyright laws. Use of any of them is subject to the [http://wiki.documentfoundation.org/TradeMark_Policy trademark policy]. +1. I would have written something similar but you beat me to it ;-) Ben -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)
On Fri, Jun 17, 2011 at 2:56 AM, BRM bm_witn...@yahoo.com wrote: - Original Message From: Simos Xenitellis simos.li...@googlemail.com To: discuss@documentfoundation.org Sent: Thu, June 16, 2011 6:31:25 PM Subject: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice) On Fri, Jun 17, 2011 at 1:03 AM, Greg Stein gst...@gmail.com wrote: On Thu, Jun 16, 2011 at 17:54, Simos Xenitellis simos.li...@googlemail.com wrote: ... The key thing being that person. That person is most likely not You, the developer who is contributing to the software. Thus, You won't get those changes unless that person decides to pass them back to you. So you don't necessarily have a right to the code. You are relying on the goodwill of that person to help you out. Of course, they might not even know who you are. They might not care. They might not ever ask for the source code. It's a common misconception. If a TV uses Linux (most LCD/LED TV use Linux), you do not need to show evidence you bought one in order to ask for the Linux source code. See the GPLv2 (per Linux kernel) license text, http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt “Accompany it with a written offer, valid for at least three years, to give **any third party**, for a charge no more than your cost of physically performing source distribution,” That written offer goes to the recipient (your statement comes from 3(b), which is dependent upon the primary part of (3), which talks about distributions to a recipient). The recipient does not need to transfer or pass that offer to third parties. Here is the full sentence, omitting some details for clarity: a. You [i.e. manufacturer, etc] may copy and distribute the Program, b. in object code or executable form c. provided that you also d. accompany it with a written offer e. to give **any** third party f. a complete machine-readable copy of the corresponding source code Again, you're relying on the goodwill of the recipient to get changes returned. Anyone can get a copy of the source code for copyleft software. Please read: http://www.gnu.org/licenses/gpl-faq.html#RedistributedBinariesGetSource Directly from the FSF, authors of the GPL. You must have a copy of the written offer in order to be entitled to receipt of the source. Tell me which LCD/LED TV you have (brand, model), and I'll get for you the source code (of the copyleft) software. Only if you also have a copy of the written offer are they required to do so. See above. So, what you are telling me is that if a manufacturer is already violating the GPL, then a third party cannot ask for the source code? Is this a claim that the GPL is not enforceable? If a product is violating the GPL, then you can ask http://gpl-violations.org/ for assistance so that the manufacturer makes available the source code as required, for the full range of products. For my TV, I click on a. Yellow button (documentation) b. (It's already on the Get started menu) c. Select Open source Licenses. That's it. Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)
BRM wrote: Directly from the FSF, authors of the GPL. You must have a copy of the written offer in order to be entitled to receipt of the source. It's amazing how you distort arguments to keep your own perspective. What the GPL says is that whoever gives you a copy of the program is also obliged to give you the written offer. They can not be separated. your friend must give you a copy of the offer along with a copy of the binary I don't understand how you can quote something that says the opposite of what you are trying to prove! -- View this message in context: http://nabble.documentfoundation.org/OFF-TOPIC-about-GPL-enforcement-Was-Re-tdf-discuss-Re-Libreoffice-Proposal-to-join-Apache-OpenOffice-tp3074299p3075368.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Hi Allen, So - first, I've enjoyed interacting with you over many years around OO.o / LibreOffice :-) and I value many of your insights. On Thu, 2011-06-16 at 10:43 -0400, Allen Pulsifer wrote: Thorsten Behrens wrote: .. I do not agree with your conclusion that the Apache OpenOffice project is a competing project. The overlap between TDF ASF's goals for an office product (modulo enabling 'mixed-source') is a pretty compelling proof of competition. SUV manufacturers compete with hybrid car vendors for mindshare, marketshare etc. despite having somewhat different product emphasis. I think you need to re-consider your argument comparing python with OO.o with LibreOffice here - they are simply not comparable as a proportion of each other, and as sources of bugs / problems etc. Second, I can recommend that LibreOffice contributors join Apache OpenOffice because I am firmly convinced that would be in the best interests of the LibreOffice project. Joining is one thing - fair enough for some to be included. But knowingly making life harder for LibreOffice by contributing code to ASF and thus helping the code-bases to diverge is a different thing. Here's what could have been: Hypothetical different worlds don't always work out so swimmingly in real life. Instead, due to your personal issues You appear to assert the conclusion to your argument. Personally, I have a great deal of respect for Thorsten - his substantial raw contribution, his judgement and so on. I don't believe he has substantial personal issues on this topic :-) no matter how much it is denied, the nagging feeling persists that it might be true; and that the LibreOffice community refuses to work with IBM or the Apache Foundation for personal reasons. There are many motivations for not working with the ASF, sure you can cherry pick some that are some transient soreness from having done a ton of work for OO.o, then seeing our views ignored, our governance duplicated and our wise licensing choices crippled. Certainly some people would feel offended by being told what to do, and what is and is not possible by many new faces that have never contributed a single thing to the project :-) That is not a surprise, just human nature - and as you point out it is not really a good reason to do anything: proposals (no matter how poorly articulated) should be evaluated on their merits. I don't believe we are deciding this sort of thing on that basis however. There are a multitude of good business, ethical, pragmatic, structural and common-sense problems with wholeheartedly embracing IBM's move facilitated by the ASF. Those are the ones that are worth discussing. Having said that - personally, I don't believe that any of these issues is susceptible to negotiation, ASF is what it is - and arguably WYSIWYG - it was chosen primarily because it structurally cannot change any of these things. Ergo, (as I've said) engaging with it on the basis that change is possible is not a productive use of time. My plan is to simply wait and see whether the promised benefits of AL2 arrive, that seems the only sensible course of action as of now. With just a few simple actions on your part, you could have accomplished in a few minutes what would have taken you at least a year to accomplish with just programming (if it can even be accomplished that way at all). We could also have severely confused our contributor-base, and landed them in the ASF's lap: code and all, substantially contributing to a vision of the world that I find pragmatically unhelpful for software freedom, and driving away another great chunk of our contributors. Sure - it would have been only a few simple actions to assure that outcome, to me though that medicine is far worse than the problem it supposedly fixes. Ultimately, to me - the people doing the work are more valuable than gold-dust around here; which is just one reason why I love, and listen carefully to Thorsten: he is such an effective hacker. So my all means, continue forward with your decision that your personal story is what really matters. Software freedom is built on the work of countless un-sung heroes investing their time and effort to build something better. I like their stories. To try to totally de-couple cold/calculating software decisions from real flesh and blood relationships in a community project is going to be doomed to failure. Having said that, I am optimistic that focusing on product excellence via a fun community of developers - particularly in a market with a low marginal cost of migration will ultimately lead to both success for LibreOffice, and a single united project again in the long run. But - beyond this, I don't think any good purpose is solved in discussing it acrimoniously and at length. All the best, Michael. -- michael.me...@novell.com , Pseudo Engineer, itinerant idiot --
Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)
DISCLAIMER: IANAL. Consult one for real legal advice if you need it. - Original Message From: plino pedl...@gmail.com BRM wrote: Directly from the FSF, authors of the GPL. You must have a copy of the written offer in order to be entitled to receipt of the source. It's amazing how you distort arguments to keep your own perspective. What the GPL says is that whoever gives you a copy of the program is also obliged to give you the written offer. They can not be separated. your friend must give you a copy of the offer along with a copy of the binary I don't understand how you can quote something that says the opposite of what you are trying to prove! Here's the mythical situation: Group A makes a product - B - that is under the GPL. Group C takes that product and makes product 'D' - also under the GPL - but only releases it to their customers for a fee. (Perfectly valid!) Group C provides the written notice to said customers; but does not make it publically available to non-customers. (Perfectly valid!) Customer E provides a copy with written notice to Party F. Party F may ask Group C for the code, showing the written notice he received from Customer E which matches what Group C provided to Customer E. The above is what the FSF states - in what I referenced - is required. Now, suppose there is another party in the mythical situation: Customer E also provide a copy _without_ written notice to Party G. Customer E violated the GPL by not providing the written notice to Party G; however, as a result Party G has no recourse against Group C. Their recourse is first against Customer E for not providing the written notice; at which point they can then approach Group C just like Party F did. However in both cases, if a Party H who has not received any distribution from Group C either directly (e.g. Customer E) or indirectly (e.g. Party F and Party G) decides they want a copy of the source for product D produced by Group C then the GPL has not taken effect - there was no distribution involved with respect to Party H, and Group C owes nothing to Party H. Remember, GPL only takes affect at point of Distribution. That does not mean that Group C may not be honorable and provide the source for product 'D' to Party H any way, but there is no requirement in the GPL to do so. BTW - the FSF also addresses the issue of if Party H obtained a distribution illegally, and states that Party H in such case may have to wait until they exit prison to be able to then be act on the distribution clause. (http://www.gnu.org/licenses/gpl-faq.html#StolenCopy) I am not twisting anything, and I could have referenced several other FAQ entries on the FSF website as well - just chose the one most relevant - one explicitly stating the from the FSF's perspective that the party asking for the source must also have the written notice. It may not be a popular view - in that you all may not like it. That does not necessarily mean that it is therefore incorrect - it is quite correct with regards to reading the GPL, and the various information the FSF has published on it. So just b/c a company does not provide the source to everyone under the sun does not mean they are in violation of the GPL. Note that the above situation also matches this FAQ entry: http://www.gnu.org/licenses/gpl-faq.html#WhatDoesWrittenOfferValid The _written offer_ must be provided and valid for any third party who has received the distribution. If you haven't received the distribution directly or indirectly then it is not valid for you as no distribution was involved. Indeed, you can also look at http://www.gnu.org/licenses/gpl-faq.html#ModifiedJustBinary - it only has to be available to the users. Please, if you are going to try to refute this at least quote from the FSF, Lessig, or SFLC to do so - they (and not 'gpl-violations.org' )are the authors of the GPL. That doesn't mean that 'gpl-violations.org' is not providing a useful service, or don't necessarily have a very good understanding of the license. But they are primarily acting on behalf of people that do have that written offer, or are helping to enforce that people receive that written offer when one was not made. If a company is in compliance - even if it is not a way that you necessarily like - then there is nothing gpl-violations.org can do - they are in compliance. As it is you haven't even quoted anything from them to refute what I have said - and there is nothing on their website about it either. Still, they are less authoritative on the matter than FSF, Lessig, and SFLC - from which I _have_ quoted, and extensively at that. Sorry to burst your bubble. From: Simos Xenitellis simos.li...@googlemail.com So, what you are telling me is that if a manufacturer is already violating the GPL, then a third party cannot ask for the source code? Is this a claim that the GPL is not enforceable? If they are
Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice
On Jun 17, 2011, at 7:44 AM, Michael Meeks wrote: The overlap between TDF ASF's goals for an office product (modulo enabling 'mixed-source') is a pretty compelling proof of competition. I disagree... competition implies a winner and a loser... in FOSS, how do you measure that? Market Share? Feh. When you start looking at it that way, then what makes FOSS FOSS kinda gets overlooked. The intent of FOSS is not to take over but to instead provide freedom and choices to end-users. If having 2 competing implementations means that a larger set of end-users will enjoy those freedoms and choices than if there was only 1 implementation, then the competition is most valid. It's being complementary, not competitive. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)
@BRM sorry to burst your fantasy world... We are not discussing some theoretical situation with A, B, C, D, etc This topic and this forum is about a PUBLIC free office suite (yes, I noticed you deliberately ignored my argument) In this case the GPL clearly says that the written license MUST be distributed with the program. Period. Arguing that someone might not obey to that requirement is the same as discussing if you should pay the items in your cart at the supermarket. Of course you can choose not to. And if there is no security at that particular supermarket you can also argue that no one can enforce that law. But it is still breaking the law even if you get away with it. Let's keep the discussion realistic (or end it). -- View this message in context: http://nabble.documentfoundation.org/OFF-TOPIC-about-GPL-enforcement-Was-Re-tdf-discuss-Re-Libreoffice-Proposal-to-join-Apache-OpenOffice-tp3074299p3076400.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)
- Original Message From: plino pedl...@gmail.com To: discuss@documentfoundation.org Sent: Fri, June 17, 2011 10:12:01 AM Subject: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice) @BRM sorry to burst your fantasy world... We are not discussing some theoretical situation with A, B, C, D, etc No, that is just to help aid the conversation on the actual topic which you seem to have lost. Please go back and read the archives. This topic and this forum is about a PUBLIC free office suite (yes, I noticed you deliberately ignored my argument) And no, I never ignored that portion of your argument. The whole discussion (so summarize) - which you seem to have lost - is what happens if someone takes a copy of that PUBLIC free office suite called TDF/LO and makes their own version of it, making a non-public release - a release similar to a closed source one that only goes to their customers - and what then happens to the changes, and who has standing to get the source - even under the GPL. In other words, what is to prevent IBM, Oracle, or any other similar company from making a derivation of TDF/LO and only it to their own customers? The argument presented against the ASL was that they could do that and that the GPL guarenteed that the community would get the source back from them; and the point is that it does not do that - only that their customers get that right, not the community - not TDF/LO. In this case the GPL clearly says that the written license MUST be distributed with the program. Period. I have never disputed that. It also says that a binary only distribution must be provided with a written offer to obtain the source, implying that the written offer is in addition to the copy of the license. Ben -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Fri, Jun 17, 2011 at 6:55 AM, Jim Jagielski j...@jagunet.com wrote: On Jun 17, 2011, at 7:44 AM, Michael Meeks wrote: The overlap between TDF ASF's goals for an office product (modulo enabling 'mixed-source') is a pretty compelling proof of competition. I disagree... competition implies a winner and a loser... in FOSS, how do you measure that? Market Share? Feh. When you start looking at it that way, then what makes FOSS FOSS kinda gets overlooked. The intent of FOSS is not to take over but to instead provide freedom and choices to end-users. If having 2 competing implementations means that a larger set of end-users will enjoy those freedoms and choices than if there was only 1 implementation, then the competition is most valid. It's being complementary, not competitive. I think it is a helpful exercise to have a starting position that forks are bad. They might be necessary and useful sometimes, like war, but that doesn't make them ideal. This is not like KOffice because that codebase is so different and missing lots of features. No one is arguing to get rid of KOffice here, or that a merge would be possible or makes sense.This is only about very slightly different versions of a 10M line codebase. Another way to think about it: what features does Apache want that LibreOffice does *not* want? Ubuntu forked Debian because they wanted 6-month release cycles, proprietary drivers, etc. I see no list. Even if you had a list of features LibreOffice didn't want, you could include the code in LibreOffice and turn it off by default. OpenOffice could be LibreOffice with different defaults. I don't think there is anything like that either. -Keith -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Jun 17, 2011, at 10:39 AM, Keith Curtis wrote: I think it is a helpful exercise to have a starting position that forks are bad. They might be necessary and useful sometimes, like war, but that doesn't make them ideal. I'm not sure about that... Some forks are good, some are bad. It's the reasons that make them either good or bad, but the forks themselves aren't. In fact, the ability to fork is one of the great benefits of FOSS. OT: but, of course, numerous forks, like the uncontrolled growth which is cancer, is bad for the community, imo. Cheers! -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
- Original Message From: Keith Curtis keit...@gmail.com On Fri, Jun 17, 2011 at 6:55 AM, Jim Jagielski j...@jagunet.com wrote: On Jun 17, 2011, at 7:44 AM, Michael Meeks wrote: The overlap between TDF ASF's goals for an office product (modulo enabling 'mixed-source') is a pretty compelling proof of competition. I disagree... competition implies a winner and a loser... in FOSS, how do you measure that? Market Share? Feh. When you start looking at it that way, then what makes FOSS FOSS kinda gets overlooked. The intent of FOSS is not to take over but to instead provide freedom and choices to end-users. If having 2 competing implementations means that a larger set of end-users will enjoy those freedoms and choices than if there was only 1 implementation, then the competition is most valid. It's being complementary, not competitive. I think it is a helpful exercise to have a starting position that forks are bad. They might be necessary and useful sometimes, like war, but that doesn't make them ideal. And TDF/LO is the real fork in this case. In your opinion it would have been a necessary fork, but it is the fork nonetheless. Any argument otherwise is revisionist history. This is not like KOffice because that codebase is so different and missing lots of features. No one is arguing to get rid of KOffice here, or that a merge would be possible or makes sense.This is only about very slightly different versions of a 10M line codebase. No it is not. But KOffice does provide a very good example of this. KOffice recently had a fork - Calligra - that most all of the development team moved to as the KOffice proper was not being properly managed. Very similar to to the OOo vs TDF/LO situation. Yet, Calligra and KOffice - which both have very similar codebases - have a much healthier relationship, etc. They don't see themselves as competing with each other either. Another way to think about it: what features does Apache want that LibreOffice does *not* want? Ubuntu forked Debian because they wanted 6-month release cycles, proprietary drivers, etc. I see no list. Even if you had a list of features LibreOffice didn't want, you could include the code in LibreOffice and turn it off by default. OpenOffice could be LibreOffice with different defaults. I don't think there is anything like that either. The real question is - since TDF/LO is the real fork, what does LibreOffice want that Oracle did not, and that Apache does not? And that is primarily the LGPL+MPL. Ben -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Fri, Jun 17, 2011 at 8:08 AM, BRM bm_witn...@yahoo.com wrote: And TDF/LO is the real fork in this case. In your opinion it would have been a necessary fork, but it is the fork nonetheless. Any argument otherwise is revisionist history. LO was a fork, but that was the for many months ago. Yet, Calligra and KOffice - which both have very similar codebases - have a much healthier relationship, etc. They don't see themselves as competing with each other either. I didn't know the details of the Calligra fork but I did a bit of researching. It seems like it was created because ONE person was causing problems (http://aseigo.blogspot.com/2010/12/rose-by-any-other-name.html) so the rest moved. However, if everyone but one moves, it is not really a fork, but a mutiny / change in leadership. -Keith -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Fri, 2011-06-17 at 08:46 -0700, Keith Curtis wrote: On Fri, Jun 17, 2011 at 8:08 AM, BRM bm_witn...@yahoo.com wrote: And TDF/LO is the real fork in this case. In your opinion it would have been a necessary fork, but it is the fork nonetheless. Any argument otherwise is revisionist history. LO was a fork, but that was the for many months ago. Yes and the transfer of OpenOffice.org to Apache is just that, a transfer. I'd add only one other comment - One doesn't have to like something in order to accept or acknowledge it. Best wishes, Drew Jensen -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)
On Fri, Jun 17, 2011 at 4:54 PM, BRM bm_witn...@yahoo.com wrote: DISCLAIMER: IANAL. Consult one for real legal advice if you need it. ... Party F may ask Group C for the code, showing the written notice he received from Customer E which matches what Group C provided to Customer E. I think your misconception arises from the fact that you consider a company can collude with the customers and ask them to keep secret those written notices they received. Without these written notices, a third party would not be able to get the source code? It's not a written notice; it is a written offer by a company to make available the source code to anyone who asks. ... I am not twisting anything, and I could have referenced several other FAQ entries on the FSF website as well - just chose the one most relevant - one explicitly stating the from the FSF's perspective that the party asking for the source must also have the written notice. You are describing a company that tries to get away with the responsibilities of the GPL by denying that they have made a written offer for the source code, by colluding with customers not to divulge the mention of the GPL in the said products. So, if I go and buy one such GPL product from the company, would the company refuse to sell me in order not to export the written offer? So just b/c a company does not provide the source to everyone under the sun does not mean they are in violation of the GPL. Note that the above situation also matches this FAQ entry: http://www.gnu.org/licenses/gpl-faq.html#WhatDoesWrittenOfferValid Which says: “If you choose to provide source through a written offer, then anybody who requests the source from you is entitled to receive it.” It's the opposite of what you have just said. ... Please, if you are going to try to refute this at least quote from the FSF, Lessig, or SFLC to do so - they (and not 'gpl-violations.org' )are the authors of the GPL. Your views are not mainstream; if you want to gain traction, you should make the effort to subscribe to the gpl-violations.org mailing list and discuss these views there. Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)
- Original Message From: Simos Xenitellis simos.li...@googlemail.com On Fri, Jun 17, 2011 at 4:54 PM, BRM bm_witn...@yahoo.com wrote: DISCLAIMER: IANAL. Consult one for real legal advice if you need it. ... Party F may ask Group C for the code, showing the written notice he received from Customer E which matches what Group C provided to Customer E. I think your misconception arises from the fact that you consider a company can collude with the customers and ask them to keep secret those written notices they received. Without these written notices, a third party would not be able to get the source code? It's not a written notice; it is a written offer by a company to make available the source code to anyone who asks. I never said they were colluding. No collusion was required, and no one need deny they were providing GPL'd products. If you want, you could change out every group/party/company in that scenario to be individual people - it doesn't change a thing wrt to the GPL. It also doesn't entitle someone who has not received a copy of the product to receiving a copy of the source code. ... I am not twisting anything, and I could have referenced several other FAQ entries on the FSF website as well - just chose the one most relevant - one explicitly stating the from the FSF's perspective that the party asking for the source must also have the written notice. You are describing a company that tries to get away with the responsibilities of the GPL by denying that they have made a written offer for the source code, by colluding with customers not to divulge the mention of the GPL in the said products. So, if I go and buy one such GPL product from the company, would the company refuse to sell me in order not to export the written offer? If you have a the GPL'd product, then you have the right to get the source. If not, you don't. If you received it second hand - e.g. indirectly - then you still have the right to the source, but you may have to show the product or written offer. So just b/c a company does not provide the source to everyone under the sun does not mean they are in violation of the GPL. Note that the above situation also matches this FAQ entry: http://www.gnu.org/licenses/gpl-faq.html#WhatDoesWrittenOfferValid Which says: “If you choose to provide source through a written offer, then anybody who requests the source from you is entitled to receive it.” It's the opposite of what you have just said. No, it implies (or rather, another FAQ entry - I forget which off hand - states) that you need the written offer as well. So as long as you provide a copy of the written offer, they are required to provide it to you. Said written offer being acquired either directly or indirectly. ... Please, if you are going to try to refute this at least quote from the FSF, Lessig, or SFLC to do so - they (and not 'gpl-violations.org' )are the authors of the GPL. Your views are not mainstream; if you want to gain traction, you should make the effort to subscribe to the gpl-violations.org mailing list and discuss these views there. Doesn't have to be mainstream. As I said - there is a very common misconception on the issue. It's not a mainstream view that GPL'd software be charged for too (people - especially GPL people - like getting stuff for free as in beer) - yet, FSF states that's perfectly acceptable to do as its not about Free as in beer (that's a good thing) but free as in speech. Ben -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)
On Fri, Jun 17, 2011 at 9:59 PM, BRM bm_witn...@yahoo.com wrote: - Original Message From: Simos Xenitellis simos.li...@googlemail.com ... Your views are not mainstream; if you want to gain traction, you should make the effort to subscribe to the gpl-violations.org mailing list and discuss these views there. Doesn't have to be mainstream. As I said - there is a very common misconception on the issue. I have moved the discussion to the gpl-violations legal mailing list, http://lists.gpl-violations.org/pipermail/legal/2011-June/002872.html Anyone can subscribe at http://lists.gpl-violations.org/mailman/listinfo/legal Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)
Ignoring the repetition on who is entitled to source code and how they are told about it, I would like to know the answers to some very specific, tangible matters closer to home. My question is basically whether the terms of a GPL license attached to a software distribution are applicable to that software distribution, not just downstream derivatives of it. I assume the answer is yes. - Dennis WHY I ASK I have a copy of LibreOffice 3.3.2 installed on my computer. I am looking for any place that I am offered access to the specific (or, indeed, any) source code for the LibreOffice 3.3.2 distribution that I have installed (en-win-x86). Looking at the Help | License Information ... tells me about licenses and where to find them, but nothing about source code. If I give this to my friends, none of them will see anything about source code either. If I examine the license, I see that LGPL3 incorporates terms of the GPL3 by reference, and license follows immediately thereafter. The LGPL3 has definitions about source code and it being conveyed. The GPL3 has the details. The preface to the GPL sys that Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. Section 6, which applies to the non-source form of the LibreOffice 3.3.2 that I installed specifies a number of ways that source code is still to be made available. 6(d) seems applicable to the way I obtained LibreOffice 3.3.2 by download: d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. ... SO WHERE IS IT? I know of no offer conveyed with the code. If I go back to the site, all I see are 3.3.3 Final and 3.4.0 Final. I see nothing that would allow me to re-retrieve or find the source of the 3.3.2 that I have in my possession. If I follow the Download the source code to build your own installer (why does that have to be the reason?), I see a set of logs that tell me nothing. Under 3.4.1.1, 3.4.0.2, and 3.3.3.1 I see lists of 20-21 tar.bz2's. Well, maybe that qualifies. Maybe not. But what about for my 3.3.2? AND ABOUT THOSE DEPENDENCIES If any of the listed dependencies also have derivatives used, is there some place where, ahem, those modified sources are available in some suitable way? -Original Message- From: Simos Xenitellis [mailto:simos.li...@googlemail.com] Sent: Friday, June 17, 2011 13:49 To: discuss@documentfoundation.org Subject: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice) On Fri, Jun 17, 2011 at 9:59 PM, BRM bm_witn...@yahoo.com wrote: - Original Message From: Simos Xenitellis simos.li...@googlemail.com ... Your views are not mainstream; if you want to gain traction, you should make the effort to subscribe to the gpl-violations.org mailing list and discuss these views there. Doesn't have to be mainstream. As I said - there is a very common misconception on the issue. I have moved the discussion to the gpl-violations legal mailing list, http://lists.gpl-violations.org/pipermail/legal/2011-June/002872.html Anyone can subscribe at http://lists.gpl-violations.org/mailman/listinfo/legal Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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 -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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
Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
On Sat, Jun 18, 2011 at 1:30 AM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: Ignoring the repetition on who is entitled to source code and how they are told about it, I would like to know the answers to some very specific, tangible matters closer to home. My question is basically whether the terms of a GPL license attached to a software distribution are applicable to that software distribution, not just downstream derivatives of it. I assume the answer is yes. - Dennis WHY I ASK I have a copy of LibreOffice 3.3.2 installed on my computer. I am looking for any place that I am offered access to the specific (or, indeed, any) source code for the LibreOffice 3.3.2 distribution that I have installed (en-win-x86). Admittedly, I never checked the UI text as to where you can get the source code. To build LibreOffice, I would simply follow the instructions at http://wiki.documentfoundation.org/Development/How_to_build which cover different operating systems. By following the instructions, you create a local repository of the source code, and this repository has *all* versions of LibreOffice (such as 3.3.2 and 3.4.0) and you can select which to build. It should take you a few hours of downloading + compilation to create your own LibreOffice. If you have a fast Internet speed and a good computer, it should take you about 3 hours of compilation. Your question is actually about whether we can make the Help→License information more informative so that users who would like to build LibreOffice, will get directed to the How_to_build page. Looking at the Help | License Information ... tells me about licenses and where to find them, but nothing about source code. If I give this to my friends, none of them will see anything about source code either. If I examine the license, I see that LGPL3 incorporates terms of the GPL3 by reference, and license follows immediately thereafter. The LGPL3 has definitions about source code and it being conveyed. The GPL3 has the details. The preface to the GPL sys that Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. Section 6, which applies to the non-source form of the LibreOffice 3.3.2 that I installed specifies a number of ways that source code is still to be made available. 6(d) seems applicable to the way I obtained LibreOffice 3.3.2 by download: d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. ... SO WHERE IS IT? I know of no offer conveyed with the code. If I go back to the site, all I see are 3.3.3 Final and 3.4.0 Final. I see nothing that would allow me to re-retrieve or find the source of the 3.3.2 that I have in my possession. If I follow the Download the source code to build your own installer (why does that have to be the reason?), I see a set of logs that tell me nothing. Under 3.4.1.1, 3.4.0.2, and 3.3.3.1 I see lists of 20-21 tar.bz2's. Well, maybe that qualifies. Maybe not. But what about for my 3.3.2? Indeed, the 3.3.2 version is not showing, because there are newer versions (3.4.1, 3.4.0 and 3.3.3) and the 3.3.2 does not fit to be in that page. You can get 3.3.2 files at http://download.documentfoundation.org/libreoffice/ http://download.documentfoundation.org/libreoffice/old/src/ As I said earlier, if you really want to compile, you would go for the 'git repositories' and the instructions at http://wiki.documentfoundation.org/Development/How_to_build AND ABOUT THOSE DEPENDENCIES If any of the listed dependencies also have derivatives used, is there some place where, ahem, those modified sources are available in some suitable way? See the dependencies at http://wiki.documentfoundation.org/Development/How_to_build#Dependencies Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
I didn't say I didn't know how to do it. I didn't say I wanted to build it. This is about honoring the spirit of the free software promise. It is not even about building the code. People may want to do any number of things with the source code (inspect for bugs, for example). I *did* say I don't see where the distro tells me how to find it and I don't see where the download page lets me find it in the same way (and now I can't even find the version that I am running). 20-21 tar.bz's are also rather intimidating, but way better than nothing. So, where is the link on the web site that would let me find the version I am running and the source code for it? (The same question for dependency derivatives is a bonus question.) - Dennis -Original Message- From: Simos Xenitellis [mailto:simos.li...@googlemail.com] Sent: Friday, June 17, 2011 16:31 To: discuss@documentfoundation.org Subject: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)) On Sat, Jun 18, 2011 at 1:30 AM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: [ ... ] I have a copy of LibreOffice 3.3.2 installed on my computer. I am looking for any place that I am offered access to the specific (or, indeed, any) source code for the LibreOffice 3.3.2 distribution that I have installed (en-win-x86). Admittedly, I never checked the UI text as to where you can get the source code. To build LibreOffice, I would simply follow the instructions at http://wiki.documentfoundation.org/Development/How_to_build which cover different operating systems. [ ... ] Your question is actually about whether we can make the Help→License information more informative so that users who would like to build LibreOffice, will get directed to the How_to_build page. [ ... ] If I follow the Download the source code to build your own installer (why does that have to be the reason?), I see a set of logs that tell me nothing. Under 3.4.1.1, 3.4.0.2, and 3.3.3.1 I see lists of 20-21 tar.bz2's. Well, maybe that qualifies. Maybe not. But what about for my 3.3.2? Indeed, the 3.3.2 version is not showing, because there are newer versions (3.4.1, 3.4.0 and 3.3.3) and the 3.3.2 does not fit to be in that page. You can get 3.3.2 files at http://download.documentfoundation.org/libreoffice/ http://download.documentfoundation.org/libreoffice/old/src/ As I said earlier, if you really want to compile, you would go for the 'git repositories' and the instructions at http://wiki.documentfoundation.org/Development/How_to_build AND ABOUT THOSE DEPENDENCIES If any of the listed dependencies also have derivatives used, is there some place where, ahem, those modified sources are available in some suitable way? See the dependencies at http://wiki.documentfoundation.org/Development/How_to_build#Dependencies Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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 -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))
On Sat, Jun 18, 2011 at 2:50 AM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: I didn't say I didn't know how to do it. I didn't say I wanted to build it. This is about honoring the spirit of the free software promise. It is not even about building the code. People may want to do any number of things with the source code (inspect for bugs, for example). To honour the spirit of the free software promise, it should be more than adequate to grab the git repositories. Ask me if you want more details for this. To honour the letter of the free software promise, then you do need those 3.3.2 tarballs. A quick look at the TDF download website shows that it currently covers the latest versions (due to space?), 3.3.3 for the 3.3 line, and 3.4.0 for the 3.4 line. Digging a bit deeper shows this http://ftp.heanet.ie/mirrors/tdf/libreoffice/box/3.3.2/LibO_3.3.2-2_DVD_allplatforms_de.iso 2.8GB DVD ISO which I believe has the source code. People who actually want to do things with the source code would need to use the git repositories, as it shows the changes between different versions. You can also view online your 3.3.2 branch at http://cgit.freedesktop.org/libreoffice Simos I *did* say I don't see where the distro tells me how to find it and I don't see where the download page lets me find it in the same way (and now I can't even find the version that I am running). 20-21 tar.bz's are also rather intimidating, but way better than nothing. So, where is the link on the web site that would let me find the version I am running and the source code for it? (The same question for dependency derivatives is a bonus question.) - Dennis -Original Message- From: Simos Xenitellis [mailto:simos.li...@googlemail.com] Sent: Friday, June 17, 2011 16:31 To: discuss@documentfoundation.org Subject: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)) On Sat, Jun 18, 2011 at 1:30 AM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: [ ... ] I have a copy of LibreOffice 3.3.2 installed on my computer. I am looking for any place that I am offered access to the specific (or, indeed, any) source code for the LibreOffice 3.3.2 distribution that I have installed (en-win-x86). Admittedly, I never checked the UI text as to where you can get the source code. To build LibreOffice, I would simply follow the instructions at http://wiki.documentfoundation.org/Development/How_to_build which cover different operating systems. [ ... ] Your question is actually about whether we can make the Help→License information more informative so that users who would like to build LibreOffice, will get directed to the How_to_build page. [ ... ] If I follow the Download the source code to build your own installer (why does that have to be the reason?), I see a set of logs that tell me nothing. Under 3.4.1.1, 3.4.0.2, and 3.3.3.1 I see lists of 20-21 tar.bz2's. Well, maybe that qualifies. Maybe not. But what about for my 3.3.2? Indeed, the 3.3.2 version is not showing, because there are newer versions (3.4.1, 3.4.0 and 3.3.3) and the 3.3.2 does not fit to be in that page. You can get 3.3.2 files at http://download.documentfoundation.org/libreoffice/ http://download.documentfoundation.org/libreoffice/old/src/ As I said earlier, if you really want to compile, you would go for the 'git repositories' and the instructions at http://wiki.documentfoundation.org/Development/How_to_build AND ABOUT THOSE DEPENDENCIES If any of the listed dependencies also have derivatives used, is there some place where, ahem, those modified sources are available in some suitable way? See the dependencies at http://wiki.documentfoundation.org/Development/How_to_build#Dependencies Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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 -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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 -- A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On 6/15/11, Allen Pulsifer pulsi...@openoffice.org wrote: ... End users do not care about who's right, who's wrong, who's been slighted, who is more pure, etc. They just care about products and technologies that are going to meet their needs. Painting quite a poor picture of end users? Are they really like that? Or do we say so to support our argument? -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
There are end users that care of freedom in a broad sense. I'm one of them, using Linux-based systems since late 90s :) And we aren't so few, because the number is growing and specially in this worldwide economical crisis. You can see by objective stadistics that the adoption of FOSS is bigger in economically poorer (I dislike the poor term in essence, but..) countries than economically richer ones. The need of a corporate entity that monopolizes the support is contrary to the spirit of Open/Free Source. The same work can be done by local companies, improve competing and also those smaller companies can contribute in developing the product too. You can also follow the Mozilla approach, but that's a very different and difficult topic. On Thu, Jun 16, 2011 at 2:18 PM, Augustine Souza aesouza2...@gmail.com wrote: On 6/15/11, Allen Pulsifer pulsi...@openoffice.org wrote: ... End users do not care about who's right, who's wrong, who's been slighted, who is more pure, etc. They just care about products and technologies that are going to meet their needs. Painting quite a poor picture of end users? Are they really like that? Or do we say so to support our argument? -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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 -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Allen Pulsifer wrote: If most or almost all of the LO contributors joined the Apache OpenOffice project, if only to lend moral support and help heal the rift, that would only be good for LO and the TdF. Thorsten Behrens wrote: Allen, how can you, with a straight face, ask people here to come over to a different project, that likely noone here is really happy with, that was setup as a fait acompli, marketed as the natural upstream, removes rights from people's contributions, and is effectively competing (by how the proposal reads)? Hello Thorsten, I do not agree with your conclusion that the Apache OpenOffice project is a competing project. You simply chose to view it that way. There are others, such as myself, who view it as a potential upstream project, where all of the contributions at the upstream project can be used by LibreOffce. In that respect, it is similar to python, java, boost, hsqldb, libjpeg, curl, lpsolve, or anyone of hundreds of other project. Are those competing projects? Second, I can recommend that LibreOffice contributors join Apache OpenOffice because I am firmly convinced that would be in the best interests of the LibreOffice project. Amazingly, your response does not even argue otherwise. Instead, your response focuses on the fact even if it were in the best interests of the LibreOffice project, for personal reasons you would never consider reconciling with it. That to me is just astounding, that you are open and brazen about putting your personal issues ahead of the project. Here's what could have been: The world could have woken up one morning to an announcement by the TdF congratulating the Apache Foundation for joining the OpenOffice community, and stating that it was looking forward to working with Apache, IBM and all other interested parties to create the best possible open document technologies, and that the TdF would be incorporating those technologies into LibreOffice in order to make it the best end-user office suite possible. The world could have then read in the press and trade magazines that virtually all of the LibreOffice developers had joined the Apache OpenOffice project, that the community had been reunited and that the future was bright. The end users (remember the end users, the ones I talked about in my last post that you seem intent on ignoring?), heartened by the optimistic message and comforted by the reunification of the community, would have come back off the sidelines looking to benefit from the project, and many of them would have discovered LibreOffice. The LibreOffice project would when be boosted by thousands of new users, and possibly could over time have developed a reputation as the best OpenOffice package. Instead, due to your personal issues, the world has heard a much different story: that you were dissed or slighted; that there is possibly some problem with the TdF or LibreOffice that people keep talking about, and no matter how much it is denied, the nagging feeling persists that it might be true; and that the LibreOffice community refuses to work with IBM or the Apache Foundation for personal reasons. It seems that your story about being dissed or slighted in one of your favorite stories, and you are determined to keep telling it for a long time. I'm quite certain that the end users (remember the end users, the ones I talked about in my last post that you seem intent on ignoring?) aren't interested in that story. With just a few simple actions on your part, you could have accomplished in a few minutes what would have taken you at least a year to accomplish with just programming (if it can even be accomplished that way at all). That's right, in this world, marketing matters. User perception matters. The best mouse trap does not always win. A few positives stories in the press can make or break a fledgling project. You can spend years developing software, and then sabotage it in a minute with a poor marketing decision. Such is that nature of business. So my all means, continue forward with your decision that your personal story is what really matters. That is your prerogative. Meanwhile, the LibreOffice project will never be what it could have been. The opportunity that has been lost will never come back again. That is the tragedy. Best Regards, Allen -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
- Original Message From: plino pedl...@gmail.com Greg Stein wrote: how can you say that Apache removes rights from people's contributions? As a developer, you still own your code. You can do whatever you like with it. Apache doesn't take anything from You. Easy. Even a non-developer like myself can see that :) Compared to GPL (which is what Apache is asking developers to give up on) it removes the right to be given back any improvement or fix to the code you contributed. Since many people are doing this pro bono, I think that it is fair that at least they retain the right to have access to any fix or improvement to their code. Even the GPL does not provide that right. If a company wanted it could take a GPL product, make whatever changes it wanted, and distribute it internally to itself without ever contributing back to the community as a whole. Likewise, it could also distribute that same project to its customers, making the source available to them and them alone. The community will may never see any changes from them; yet that is perfectly valid under all Open Source licenses - even the GPL. Nothing forces people to work with the community. No license can do that. So please do yourself a favor and put that notion - the myth - aside. GPL, like all Open Source licenses, is about the end-user NOT the developer. Yes, there are a lot of developers that are also end-users, and developers are required to help make Open Source open source, but ultimately it is about providing a product to end-users with the same rights, etc that you had to start with. Now, granted, the Apache License is more liberal in that it allows companies to not have to pass on those same rights; that is the difference - it doesn't require that they also make the source available to the end-user. So IBM is free to develop Symphony without having to provide source to the end-users. But there is nothing preventing them from having Symphony derived from LibreOffice under the LGPL and not providing any changes back to LibreOffice either; they only have to provide the source (in that case) to the end-users _upon request_ for up to 3 years for each version they release from the time they make the sale. (See the GPL license.) Under the Apache license any company can take your code, fix it and say: Hey, this function in the open source version doesn't work. I just spend a day fixing it (instead of months to write it from scratch). Why don't you buy mine which works? They can do that under the GPL too. Ben -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Hi Allen, While I am rather tired of this combative thread of discussion and think it is way overdue for it to stop, you make some statements that can't be left unchallenged. On 16 Jun 2011, at 15:43, Allen Pulsifer wrote: Allen Pulsifer wrote: Hello Thorsten, I do not agree with your conclusion that the Apache OpenOffice project is a competing project. You simply chose to view it that way. The main proposer of the project, Rob Weir of IBM, clearly stated his intent for it to be a competing project - he even accused me of being potentially in breach of anti-trust law on the Apache list[1], and has just re-asserted his view on his blog[2]. So while many of us had hoped for a collaborative approach, there are powerful forces who don't want that. Here's what could have been: The world could have woken up one morning to an announcement by the TdF congratulating the Apache Foundation for joining the OpenOffice community The TDF press release was in fact remarkably positive considering the situation[3], welcomed the move and offered scope for discussion over collaboration. So my all means, continue forward with your decision that your personal story is what really matters. That is your prerogative. Meanwhile, the LibreOffice project will never be what it could have been. The opportunity that has been lost will never come back again. That is the tragedy. The tragedy is that people want to keep this divisive argument alive way beyond its sell-by date. I think it's time to stop it, and either to focus on the project that you want to work on or seek positively for ways to create collaborations. Cheers, Simon [1] http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3cof225fdf79.6bebc50b-on852578a7.00052da4-852578a7.00065...@lotus.com%3E [2] http://www.robweir.com/blog/2011/06/openoffice-libreoffice-and-the-scarcity-fallacy.html [3] http://blog.documentfoundation.org/2011/06/01/statement-about-oracles-move-to-donate-openoffice-org-assets-to-the-apache-foundation/ -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On 6/16/11 4:43 PM, Allen Pulsifer wrote: So my all means, continue forward with your decision that your personal story is what really matters. That is your prerogative. Meanwhile, the LibreOffice project will never be what it could have been. The opportunity that has been lost will never come back again. That is the tragedy. It looks like you have different views from ours, and ours are as legitimate as yours (unless you belong to the same family of Rob Weir, who assumes to be the only person with legitimate views about TDF and LibreOffice). Opportunities are symmetrical, while this opportunity looks asymmetrical (we have the opportunity of reuniting the community under the ASF umbrella, while ASF has not the opportunity of reuniting the community inside TDF mixing bowl). I understand that you are very happy with the ASF project. If you are happy we are happy for you. Users will decide on their own: they don't need your suggestions. -- Italo Vignoli italo.vign...@gmail.com mobile +39.348.5653829 VoIP +39.02.320621813 skype italovignoli -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Allen Pulsifer wrote: I do not agree with your conclusion that the Apache OpenOffice project is a competing project. You simply chose to view it that way. Simon Phipps wrote: The main proposer of the project, Rob Weir of IBM, clearly stated his intent for it to be a competing project - he even accused me of being potentially in breach of anti-trust law on the Apache list[1], and has just re-asserted his view on his blog[2]. So while many of us had hoped for a collaborative approach, there are powerful forces who don't want that. Hello Simon, The donation of the OpenOffice code, trademark and domain were made to the Apache Foundation, not to IBM or to Rob Weir. Rob Weir is only one of many people who are now members of the project at Apache. As the board members of the Apache Foundation made it clear, those members will have the primary responsibility for determining the direction of the project, not IBM or Rob Weir. I happen to be one of those persons, and as a member, I have the same voice as Rob Weir. That means the same voice in determining what goes on the openoffice.org website, how the openoffice.org trademark is used, and whether the project direction is collaborative or competitive. As an experienced person in the open source world, I would think you know by now that it is a lot easier to influence a project when have a seat at the table and are working from the inside rather of the outside. You could have also been one of those persons with a seat at the table, and together, we would have had twice the voice as Rob Weir. Every other member of this community could have also joined, and that would have been an overwhelming voice. Again, a lost opportunity. Allen -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On 16 Jun 2011, at 16:58, Allen Pulsifer wrote: You could have also been one of those persons with a seat at the table, and together, we would have had twice the voice as Rob Weir. Excuse me? What are all the contributions I am making on that list? Chopped liver? S. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Allen Pulsifer wrote: As an experienced person in the open source world, I would think you know by now that it is a lot easier to influence a project when have a seat at the table and are working from the inside rather of the outside. You could have also been one of those persons with a seat at the table, and together, we would have had twice the voice as Rob Weir. Simon Phipps replied: Excuse me? What are all the contributions I am making on that list? Chopped liver? Pretty much, yes. As a person who chose not to have a seat at the table, you are serving up chopped liver for the people at the table to taste and decide whether they want to eat it. That's a fair analogy, I think, if it's the one you want to use. Allen -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On 16 Jun 2011, at 17:31, Allen Pulsifer wrote: Allen Pulsifer wrote: As an experienced person in the open source world, I would think you know by now that it is a lot easier to influence a project when have a seat at the table and are working from the inside rather of the outside. You could have also been one of those persons with a seat at the table, and together, we would have had twice the voice as Rob Weir. Simon Phipps replied: Excuse me? What are all the contributions I am making on that list? Chopped liver? Pretty much, yes. As a person who chose not to have a seat at the table, you are serving up chopped liver for the people at the table to taste and decide whether they want to eat it. That's a fair analogy, I think, if it's the one you want to use. Given I've showed up in both conversations at Apache and made actual tangible contributions of at least the same scale as yours, I honestly have no idea what you are getting at, Allen. Thanks, S. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Thu, Jun 16, 2011 at 5:43 PM, Allen Pulsifer pulsi...@openoffice.org wrote: Allen Pulsifer wrote: If most or almost all of the LO contributors joined the Apache OpenOffice project, if only to lend moral support and help heal the rift, that would only be good for LO and the TdF. Thorsten Behrens wrote: Allen, how can you, with a straight face, ask people here to come over to a different project, that likely noone here is really happy with, that was setup as a fait acompli, marketed as the natural upstream, removes rights from people's contributions, and is effectively competing (by how the proposal reads)? ...snip... Best Regards, Allen If that is your best attempt for reconciliation, you are doing it wrong. Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Augustine Souza wrote: On 6/15/11, Allen Pulsifer pulsi...@openoffice.org wrote: ... End users do not care about who's right, who's wrong, who's been slighted, who is more pure, etc. They just care about products and technologies that are going to meet their needs. Painting quite a poor picture of end users? Are they really like that? Or do we say so to support our argument? As one of those end users I would have to say that that is probably about right. Unless something interferes with the quality or availability of the software or the support available for it, we are probably not going to care. Now the situation with OOo and Sun, and later Oracle was that comments, complaints and requests by end users seemed to basically be ignored, that does bother end users! This situation is notably better with TDF running things. I could be wrong about this, but I don't think I am, OOo being primarily the responsibility of a large for profit corporation it was treated like a proprietary software package as far as development and support was concerned. Comparing Microsoft Internet Explorer with Mozilla Firefox shows that an independent not-for-profit foundation can actually produce a better software Product than a huge for-profit corporation. So I am confidently hoping that LO under TDF will actually fare better than OO under Sun and Oracle. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
- Original Message From: plino pedl...@gmail.com BRM wrote: Even the GPL does not provide that right. If a company wanted it could take a GPL product, make whatever changes it wanted, and distribute it internally to itself without ever contributing back to the community as a whole. Likewise, it could also distribute that same project to its customers, making the source available to them and them alone. The community will may never see any changes from them; yet that is perfectly valid under all Open Source licenses - even the GPL. Nothing forces people to work with the community. No license can do that. So please do yourself a favor and put that notion - the myth - aside. So basically GPL is worth nothing because no one can force anybody to contribute back? Is that an argument in favor of convincing developers to use the Apache license (because they aren't getting anything back anyway) or to simply stop contributing to Open Source projects? No. I am merely pointing out the fallacy in what we being said. To many people assume that GPL means contribute back to the community when it does not. So to argue forcing people to contribute back under any FLOSS license is 100% wrong, when the topic should be about the rights of the end-users - GPL guarantees them while Apache and other permissive licenses do not necessarily do so - in most all cases I am aware of they do not at all. IOW, if you are going to argue differences in the license and reasons to go one way or the other, at least get your facts straight about the license and its implications. Then you can have a proper debate on the merits of which one to go with. BTW, I typically lean towards using the GPL/LGPL myself. However, that won't stop me from contributing to BSD/Apache licensed projects either - or even projects governed by ICLA/CLA/etc (so long as they don't inhibit my abilities to work on other projects under other licenses). Each license has its use; and each community has their favored license. TDF/LO favors LGPL/GPL; Apache favors the more permissive Apache License. So far as I am concerned, with certain exceptions (e.g. MS Public License) as long as the license is approved by the Open Source Initiative as being a proper Open Source license - requirements being derived from the early Debian Social Contract - then what does it matter as long as the users can make an informed decision? - that is, if they don't like IBM Symphony they can make the decision to use Apache's OOo or any derived product, or even LO (since you guys have at least expressed the concept that you are truly an OOo fork and don't want to be seen as a derived product from OOo/ApacheOOo). That is just me - and I know many on this list will disagree, that is their right. Ben P.S. On the other hand, I get really pissed at companies like March Hare Software, Ltd. that have taken open source - even GPL licensed - software and essentially made them proprietary. It is very hard to move off of CVSNT to a proper CVS install, or even to another system (e.g. SVN, git) because of the changes they have made and the non-availability of the source. Yet, they support projects like TortoiseCVS so that users can continue to use CVSNT. (http://www.evscm.org/modules/Downloads/) -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
As an interested user I see a lot of noise passing by on this topic. I must say I am totally unimpressed. What counts for me is reality, not dreaming in the cloud. I was used to getting no response from Microsoft on my bug reports. I did join in a bug report in OOo about table autoformats not being saved properly. I did approach Sun and Oracle directly about this silly bug that has been sitting untouched since 2008 in the OpenOffice bug repository. I did not get any answers from Sun/Oracle either. I resubmitted the original bug report to the new TDF bug repository. There, within a quarter of a year, it has been evaluated and elevated to the Easyhack status. I would not be surprised if that problem would be solved by the end of this year. They have already done quite a pile of cleaning code and bug fixing. My confidence as a user is with them. The indians have to prove as yet. That is what matters at the end of the day. P -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Thu, Jun 16, 2011 at 04:27, plino pedl...@gmail.com wrote: Greg Stein wrote: how can you say that Apache removes rights from people's contributions? As a developer, you still own your code. You can do whatever you like with it. Apache doesn't take anything from You. Easy. Even a non-developer like myself can see that :) Compared to GPL (which is what Apache is asking developers to give up on) it removes the right to be given back any improvement or fix to the code you contributed. As Ben has explained later in this thread, you never had that right. Ergo, Apache has not removed any rights from You. This is why I think the statement removes rights from people's contributions is wrong, or there is some other right that I'm unaware of. ... Cheers, -g -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Thu, Jun 16, 2011 at 13:40, Pieter E. Zanstra pie...@zanstra.eu wrote: As an interested user I see a lot of noise passing by on this topic. I must say I am totally unimpressed. What counts for me is reality, not dreaming in the cloud. I was used to getting no response from Microsoft on my bug reports. I did join in a bug report in OOo about table autoformats not being saved properly. I did approach Sun and Oracle directly about this silly bug that has been sitting untouched since 2008 in the OpenOffice bug repository. I did not get any answers from Sun/Oracle either. I resubmitted the original bug report to the new TDF bug repository. There, within a quarter of a year, it has been evaluated and elevated to the Easyhack status. I would not be surprised if that problem would be solved by the end of this year. They have already done quite a pile of cleaning code and bug fixing. My confidence as a user is with them. The indians have to prove as yet. That is what matters at the end of the day. Absolutely that is what matters. Whether the caretakers place *you* at the forefront. Big faceless corporations generally don't, while smaller communities usually do. I believe the (recent) discussion stemmed from whether end-users care about the *license*. They mostly want a great product and a responsive caretaker. That's it. I can guarantee you that my mother, father, brother, sister, and the rest of my extended family would give me a blank stare if I told them they needed to use Free Software rather than proprietary. Crickets would echo in the room. There *are* end-users who want Free Software. Many of you care strongly about it, and seek out Free Software. Granted. But when you look at the tens of millions (hundreds?) of OOo and LO users, they simply don't care. Building and providing LibreOffice is a fabulous thing for people who really care about Free Software. LO has an important place in our software ecosystem. I just don't think projecting that philosophy onto the typical end-user makes sense, however. Cheers, -g -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Ben explained much of this already, but let's see if I can add some more: On Thu, Jun 16, 2011 at 14:46, plino pedl...@gmail.com wrote: Greg Stein wrote: As Ben has explained later in this thread, you never had that right. Ergo, Apache has not removed any rights from You. This is why I think the statement removes rights from people's contributions is wrong, or there is some other right that I'm unaware of. GPL does say that if you make a derivative work and distribute it to someone else, you must provide that person with the source code under the terms of the GPL so that they may modify and redistribute it under the terms of the GPL as well. The key thing being that person. That person is most likely not You, the developer who is contributing to the software. Thus, You won't get those changes unless that person decides to pass them back to you. So you don't necessarily have a right to the code. You are relying on the goodwill of that person to help you out. Of course, they might not even know who you are. They might not care. They might not ever ask for the source code. The Apache license says you don't have to distribute under the same license and therefore you don't have to provide the source code. Correct. In the context of a public free Office Suite isn't that the same? If under GPL you MUST release the source as GPL, isn't that in practical terms the same as releasing the modifications you made??? Nope. Again, because I only need to release it to the people that I gave a binary to. That is not the same as the community making the software. Also, recognize that I might make a TON of changes. Create a massively superior product. And then use it *internally*. I might not ever distribute my work outside of the company. Or... hey... I might put a web interface on the front of that Office Suite, and run a web-based version of it. That isn't releasing the software to anybody, so all of that awesome work that I did does not have to be released. (see the AGPL if you want to solve this scenario) Doesn't this mean that changing the license to Apache removes the right to have access to the modified source code if a company so chooses? As a developer, you never had those rights to begin with. Apache is not removing any rights from You. People who use Apache code (developers, admins, end-users, hobbyists, companies, etc) have more rights: they can decide whether to return changes or not. But they do not have to operate under Free Software principles. That understandably bugs people. But as a developer, Apache is not reducing your rights (the original phrase that I took issue with). Cheers, -g -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Thu, Jun 16, 2011 at 9:05 PM, Greg Stein gst...@gmail.com wrote: Ben explained much of this already, but let's see if I can add some more: On Thu, Jun 16, 2011 at 14:46, plino pedl...@gmail.com wrote: In the context of a public free Office Suite isn't that the same? If under GPL you MUST release the source as GPL, isn't that in practical terms the same as releasing the modifications you made??? Nope. Again, because I only need to release it to the people that I gave a binary to. That is not the same as the community making the software. I think you missed the public free Office Suite bit. In that case the people you gave the binary to is anyone who wants it, which would include the developers if they want to use the source code. So in this case, in practice, having the code as GPL means you must give the code back to the developers, or rather you must make the code available for the developers to get for themselves. This is the situation software suites like IBM's would have fallen under. -Todd -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Greg Stein wrote: On Thu, Jun 16, 2011 at 13:40, Pieter E. Zanstra pie...@zanstra.eu wrote: As an interested user I see a lot of noise passing by on this topic. I must say I am totally unimpressed. What counts for me is reality, not dreaming in the cloud. I was used to getting no response from Microsoft on my bug reports. I did join in a bug report in OOo about table autoformats not being saved properly. I did approach Sun and Oracle directly about this silly bug that has been sitting untouched since 2008 in the OpenOffice bug repository. I did not get any answers from Sun/Oracle either. I resubmitted the original bug report to the new TDF bug repository. There, within a quarter of a year, it has been evaluated and elevated to the Easyhack status. I would not be surprised if that problem would be solved by the end of this year. They have already done quite a pile of cleaning code and bug fixing. My confidence as a user is with them. The indians have to prove as yet. That is what matters at the end of the day. Absolutely that is what matters. Whether the caretakers place *you* at the forefront. Big faceless corporations generally don't, while smaller communities usually do. I believe the (recent) discussion stemmed from whether end-users care about the *license*. They mostly want a great product and a responsive caretaker. That's it. I can guarantee you that my mother, father, brother, sister, and the rest of my extended family would give me a blank stare if I told them they needed to use Free Software rather than proprietary. Crickets would echo in the room. There *are* end-users who want Free Software. Many of you care strongly about it, and seek out Free Software. Granted. But when you look at the tens of millions (hundreds?) of OOo and LO users, they simply don't care. Building and providing LibreOffice is a fabulous thing for people who really care about Free Software. LO has an important place in our software ecosystem. I just don't think projecting that philosophy onto the typical end-user makes sense, however. Cheers, -g This is exactly how I feel about this, and why I think that TDF forking the OOo code is the best thing that could have happened. I suspect that in the first 1 to three months not much code development happened, naturally it takes time for things to get started. So it would be my best guess that there has been about six months of software development under TDF. That being the case, it seems like the LO software package has been evolving and improving at from 4 to 8 times the pace that it was under Sun/Oracle. I have been on the OOo discuss list since 2001 perhaps even 2000, its hard to remember, anyway, from all the various comments and complaints over the years it seems like the real show-stoppers got fixed and the nuisance problems just got ignored for the most part. Now it seems like with an all volunteer group rather than developers being assigned chores by corporate management, all the bugs are being addressed in a more impartial way. Not having done any programming since college and BASIC, I don't know how to read C++ source code, but I have read here that there has been more work at cleaning up the source code, removing remarked out lines of code, and such during the last 6 months than during the previous 6 years. An example of M$ work, Vista was well over a year late in being released, and even then it was a horrible mess! Over the years one theme on the OOo Discuss List was a sort of competition between OOo and M$ Office. I think the only way to judge the relative merits of two such software suites is by relative user satisfaction. By that metric it always seemed that OOo was about 2 to 3 years behind M$ Office, judging by the talk on the list. Now if M$ continues at their current rate of progress, and if LO does likewise, then sometime during the next year LO would pass M$ Office in user satisfaction. What could be better than that!? -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Why is that a poor picture? I am confident that some users choose Open/LibreOffice distributions for ideological reasons. I also think many adopt software because they have a need that it satisfies in their use of it in creating and interchanging documents and the FOSS assurance has little meaning for them. It simply is not relevant in their world. What's poor about that? Is it more important that LO be a political weapon than it be useful to people who have work to do? - Dennis -Original Message- From: Augustine Souza [mailto:aesouza2...@gmail.com] Sent: Thursday, June 16, 2011 07:18 To: discuss@documentfoundation.org Subject: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice On 6/15/11, Allen Pulsifer pulsi...@openoffice.org wrote: ... End users do not care about who's right, who's wrong, who's been slighted, who is more pure, etc. They just care about products and technologies that are going to meet their needs. Painting quite a poor picture of end users? Are they really like that? Or do we say so to support our argument? -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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 -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
I am not happy with Allen's characterization of Simon's participation. I suspect the difference is that Allen put himself on the list of initial committers and is now on the podling PPMC at Apache. Simon did not choose to put himself on that list. That's Simon's business. Simon has been a vocal, active participant in the run-up to the Apache Incubator vote to accept the Oracle contribution and on the public lists that are now established for the Apache podling. I, for one, welcome any contributions that Simon cares to make, and that Allen will be making. I should point out that it is a waste of time to become an initial committer and member of the podling PPMC with the goal of canceling Rob Weir's (or anyone else's) vote, because there is rarely any voting, *especially* on technical matters. I am learning as a newcomer there that Apache is a *serious* inclusive meritocracy and it is better to look at it as there being no one who has a privileged seat at the table. - Dennis -Original Message- From: Simon Phipps [mailto:si...@webmink.com] Sent: Thursday, June 16, 2011 09:37 To: discuss@documentfoundation.org Subject: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice On 16 Jun 2011, at 17:31, Allen Pulsifer wrote: Allen Pulsifer wrote: As an experienced person in the open source world, I would think you know by now that it is a lot easier to influence a project when have a seat at the table and are working from the inside rather of the outside. You could have also been one of those persons with a seat at the table, and together, we would have had twice the voice as Rob Weir. Simon Phipps replied: Excuse me? What are all the contributions I am making on that list? Chopped liver? Pretty much, yes. As a person who chose not to have a seat at the table, you are serving up chopped liver for the people at the table to taste and decide whether they want to eat it. That's a fair analogy, I think, if it's the one you want to use. Given I've showed up in both conversations at Apache and made actual tangible contributions of at least the same scale as yours, I honestly have no idea what you are getting at, Allen. Thanks, S. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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 -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
+1 -Original Message- From: Greg Stein [mailto:gst...@gmail.com] Sent: Thursday, June 16, 2011 11:37 To: discuss@documentfoundation.org Subject: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice On Thu, Jun 16, 2011 at 13:40, Pieter E. Zanstra pie...@zanstra.eu wrote: As an interested user I see a lot of noise passing by on this topic. I must say I am totally unimpressed. What counts for me is reality, not dreaming in the cloud. I was used to getting no response from Microsoft on my bug reports. I did join in a bug report in OOo about table autoformats not being saved properly. I did approach Sun and Oracle directly about this silly bug that has been sitting untouched since 2008 in the OpenOffice bug repository. I did not get any answers from Sun/Oracle either. I resubmitted the original bug report to the new TDF bug repository. There, within a quarter of a year, it has been evaluated and elevated to the Easyhack status. I would not be surprised if that problem would be solved by the end of this year. They have already done quite a pile of cleaning code and bug fixing. My confidence as a user is with them. The indians have to prove as yet. That is what matters at the end of the day. Absolutely that is what matters. Whether the caretakers place *you* at the forefront. Big faceless corporations generally don't, while smaller communities usually do. I believe the (recent) discussion stemmed from whether end-users care about the *license*. They mostly want a great product and a responsive caretaker. That's it. I can guarantee you that my mother, father, brother, sister, and the rest of my extended family would give me a blank stare if I told them they needed to use Free Software rather than proprietary. Crickets would echo in the room. There *are* end-users who want Free Software. Many of you care strongly about it, and seek out Free Software. Granted. But when you look at the tens of millions (hundreds?) of OOo and LO users, they simply don't care. Building and providing LibreOffice is a fabulous thing for people who really care about Free Software. LO has an important place in our software ecosystem. I just don't think projecting that philosophy onto the typical end-user makes sense, however. Cheers, -g -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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 -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
I want to clear up one thing (I hope): Doesn't this mean that changing the license to Apache removes the right to have access to the modified source code if a company so chooses? As a developer, you never had those rights to begin with. Apache is not removing any rights from You. People who use Apache code (developers, admins, end-users, hobbyists, companies, etc) have more rights: they can decide whether to return changes or not. But they do not have to operate under Free Software principles. That understandably bugs people. But as a developer, Apache is not reducing your rights (the original phrase that I took issue with). If I am the copyright holder of my code, I can issue it with a license that requires anyone who modifies my source code to provide me with the changes to my code that they make. There have been licenses like that, some of which were satisfied by patches being provided and not the whole source of the downstream use of the source code, possibly embedded in a proprietary software product. Not sure how that sort of thing is enforceable, but as a copyright holder I think that comes under the exclusive rights that are mine, to be licensed as I see fit, at least in the US. - Dennis PS: It is the case that neither the GPL nor APLv2 have such a compulsory condition and it would be interesting to see what the FSF would say in the event someone sublicensed a GPL derivative in that manner. I suppose there could be a similar sublicensing of an APLv2 derivative, but not sure the Apache Foundation would have anything to say about it at all so long as the conditions of ALv2 were otherwise satisfied. -Original Message- From: Greg Stein [mailto:gst...@gmail.com] Sent: Thursday, June 16, 2011 12:05 To: discuss@documentfoundation.org Subject: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice Ben explained much of this already, but let's see if I can add some more: On Thu, Jun 16, 2011 at 14:46, plino pedl...@gmail.com wrote: Greg Stein wrote: As Ben has explained later in this thread, you never had that right. Ergo, Apache has not removed any rights from You. This is why I think the statement removes rights from people's contributions is wrong, or there is some other right that I'm unaware of. GPL does say that if you make a derivative work and distribute it to someone else, you must provide that person with the source code under the terms of the GPL so that they may modify and redistribute it under the terms of the GPL as well. The key thing being that person. That person is most likely not You, the developer who is contributing to the software. Thus, You won't get those changes unless that person decides to pass them back to you. So you don't necessarily have a right to the code. You are relying on the goodwill of that person to help you out. Of course, they might not even know who you are. They might not care. They might not ever ask for the source code. The Apache license says you don't have to distribute under the same license and therefore you don't have to provide the source code. Correct. In the context of a public free Office Suite isn't that the same? If under GPL you MUST release the source as GPL, isn't that in practical terms the same as releasing the modifications you made??? Nope. Again, because I only need to release it to the people that I gave a binary to. That is not the same as the community making the software. Also, recognize that I might make a TON of changes. Create a massively superior product. And then use it *internally*. I might not ever distribute my work outside of the company. Or... hey... I might put a web interface on the front of that Office Suite, and run a web-based version of it. That isn't releasing the software to anybody, so all of that awesome work that I did does not have to be released. (see the AGPL if you want to solve this scenario) Doesn't this mean that changing the license to Apache removes the right to have access to the modified source code if a company so chooses? As a developer, you never had those rights to begin with. Apache is not removing any rights from You. People who use Apache code (developers, admins, end-users, hobbyists, companies, etc) have more rights: they can decide whether to return changes or not. But they do not have to operate under Free Software principles. That understandably bugs people. But as a developer, Apache is not reducing your rights (the original phrase that I took issue with). Cheers, -g -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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 -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Posting guidelines + more: http://wiki.documentfoundation.org
Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice
- Original Message From: todd rme toddrme2...@gmail.com To: discuss@documentfoundation.org Sent: Thu, June 16, 2011 3:13:15 PM Subject: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice On Thu, Jun 16, 2011 at 9:05 PM, Greg Stein gst...@gmail.com wrote: Ben explained much of this already, but let's see if I can add some more: On Thu, Jun 16, 2011 at 14:46, plino pedl...@gmail.com wrote: In the context of a public free Office Suite isn't that the same? If under GPL you MUST release the source as GPL, isn't that in practical terms the same as releasing the modifications you made??? Nope. Again, because I only need to release it to the people that I gave a binary to. That is not the same as the community making the software. I think you missed the public free Office Suite bit. In that case the people you gave the binary to is anyone who wants it, which would include the developers if they want to use the source code. So in this case, in practice, having the code as GPL means you must give the code back to the developers, or rather you must make the code available for the developers to get for themselves. This is the situation software suites like IBM's would have fallen under. Wrong. OOo, TDF/LO, etc may be making a public release. IBM, for example, may not. They are only releasing to people who _pay them_ for the product. _ONLY_ those people (the ones they specifically distributed the product to) are required to be able to receive it - not necessarily the developer they drew the code from. Someone could take TDF/LO and make changes and do the same thing - only release to their paying customers. And they only have to give the source to one of those paying customers - not anyone that comes along and asks for it. Granted, if _one_ of those paying customers asked for the source they would then have the rights to pass it back to TDF/LO, but you cannot rely on that happening. Their paying customers are guaranteed that right by the GPL; but that GPL grants _you_ as the developer nothing other than that. So as Greg said, who has the rights (per the GPL) to receive the source is not necessarily the same as the community. The only people that have rights to receiving the source are the ones that the product was specifically distributed to. If you are are not someone that received the product distributed by them, then you have no rights to receive the source - plain simple. Ben -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Fri, Jun 17, 2011 at 12:49 AM, BRM bm_witn...@yahoo.com wrote: So as Greg said, who has the rights (per the GPL) to receive the source is not necessarily the same as the community. The only people that have rights to receiving the source are the ones that the product was specifically distributed to. If you are are not someone that received the product distributed by them, then you have no rights to receive the source - plain simple. As I said earlier, you do not need to be a copyright holder to request the source code of a copyleft software. Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Dennis E. Hamilton wrote: If I am the copyright holder of my code, I can issue it with a license that requires anyone who modifies my source code to provide me with the changes to my code that they make. ... PS: It is the case that neither the GPL nor APLv2 have such a compulsory condition and it would be interesting to see what the FSF would say in the event someone sublicensed a GPL derivative in that manner. Adding to what Greg already wrote (i.e., you need that a distribution of the software happens in order to enforce this), this requirement is considered compatible with Free Software licenses. See http://www.gnu.org/philosophy/free-sw.html (search for previous developer or read the last line about revision 1.11). But it is not possible to attach it to existing LGPL3/GPL3 code since it would violate section 10 of GPL3: http://www.gnu.org/licenses/gpl-faq.html#OrigBSD Regards, Andrea. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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
OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)
On Fri, Jun 17, 2011 at 1:03 AM, Greg Stein gst...@gmail.com wrote: On Thu, Jun 16, 2011 at 17:54, Simos Xenitellis simos.li...@googlemail.com wrote: ... The key thing being that person. That person is most likely not You, the developer who is contributing to the software. Thus, You won't get those changes unless that person decides to pass them back to you. So you don't necessarily have a right to the code. You are relying on the goodwill of that person to help you out. Of course, they might not even know who you are. They might not care. They might not ever ask for the source code. It's a common misconception. If a TV uses Linux (most LCD/LED TV use Linux), you do not need to show evidence you bought one in order to ask for the Linux source code. See the GPLv2 (per Linux kernel) license text, http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt “Accompany it with a written offer, valid for at least three years, to give **any third party**, for a charge no more than your cost of physically performing source distribution,” That written offer goes to the recipient (your statement comes from 3(b), which is dependent upon the primary part of (3), which talks about distributions to a recipient). The recipient does not need to transfer or pass that offer to third parties. Here is the full sentence, omitting some details for clarity: a. You [i.e. manufacturer, etc] may copy and distribute the Program, b. in object code or executable form c. provided that you also d. accompany it with a written offer e. to give **any** third party f. a complete machine-readable copy of the corresponding source code Again, you're relying on the goodwill of the recipient to get changes returned. Anyone can get a copy of the source code for copyleft software. Tell me which LCD/LED TV you have (brand, model), and I'll get for you the source code (of the copyleft) software. Simos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
I'm sorry. I have IBM Lotus Symphony 3.0 with fixpack 2 installed on my computer and I didn't pay anyone for it. It is free to download. Registration required. That's it. If I want support, that is different. Not much different than with Sun Star Office and Oracle Office, actually. True, they have not offered me the source code. But still, free as in free beer was enough for my purposes. - Dennis -Original Message- From: BRM [mailto:bm_witn...@yahoo.com] Sent: Thursday, June 16, 2011 14:50 To: discuss@documentfoundation.org Subject: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice [ ... ] Wrong. OOo, TDF/LO, etc may be making a public release. IBM, for example, may not. They are only releasing to people who _pay them_ for the product. _ONLY_ those people (the ones they specifically distributed the product to) are required to be able to receive it - not necessarily the developer they drew the code from. [ ... ] -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice)
- Original Message From: Simos Xenitellis simos.li...@googlemail.com To: discuss@documentfoundation.org Sent: Thu, June 16, 2011 6:31:25 PM Subject: OFF TOPIC about GPL enforcement (Was: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice) On Fri, Jun 17, 2011 at 1:03 AM, Greg Stein gst...@gmail.com wrote: On Thu, Jun 16, 2011 at 17:54, Simos Xenitellis simos.li...@googlemail.com wrote: ... The key thing being that person. That person is most likely not You, the developer who is contributing to the software. Thus, You won't get those changes unless that person decides to pass them back to you. So you don't necessarily have a right to the code. You are relying on the goodwill of that person to help you out. Of course, they might not even know who you are. They might not care. They might not ever ask for the source code. It's a common misconception. If a TV uses Linux (most LCD/LED TV use Linux), you do not need to show evidence you bought one in order to ask for the Linux source code. See the GPLv2 (per Linux kernel) license text, http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt “Accompany it with a written offer, valid for at least three years, to give **any third party**, for a charge no more than your cost of physically performing source distribution,” That written offer goes to the recipient (your statement comes from 3(b), which is dependent upon the primary part of (3), which talks about distributions to a recipient). The recipient does not need to transfer or pass that offer to third parties. Here is the full sentence, omitting some details for clarity: a. You [i.e. manufacturer, etc] may copy and distribute the Program, b. in object code or executable form c. provided that you also d. accompany it with a written offer e. to give **any** third party f. a complete machine-readable copy of the corresponding source code Again, you're relying on the goodwill of the recipient to get changes returned. Anyone can get a copy of the source code for copyleft software. Please read: http://www.gnu.org/licenses/gpl-faq.html#RedistributedBinariesGetSource Directly from the FSF, authors of the GPL. You must have a copy of the written offer in order to be entitled to receipt of the source. Tell me which LCD/LED TV you have (brand, model), and I'll get for you the source code (of the copyleft) software. Only if you also have a copy of the written offer are they required to do so. See above. Ben -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Allen Pulsifer wrote: The seeds of that fork were germinated in the Go-Oo project, which created patches and enhancements that were not contributed back to the official OOo distribution. That became a full fork when the LibreOffice project was started by importing all of the OOo source code into a new repository. Hi Allen - will that story never die? The creation of the TDF and LibreOffice was a movement far above and beyond Go-Oo. It just happened to assimilate that code (and much more). Also, if you are going to talk about a split in the community, you should mention that TdF and LibreOffice were created in secret, without any public discussions or community input. Factually incorrect. Large parts of the community were involved setting up the idea - but you don't discuss e.g. trademark issues on a public list, if you want to stand a chance actually obtaining it. What's more, and pointed out in this very thread - TDF is still in the process of being fully established, and *all* things, like bylaws, location etc. were available for discussion on public lists. Cheers, -- Thorsten -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Thorsten Behrens wrote (15-06-11 09:50) Allen Pulsifer wrote: The seeds of that fork were germinated in the Go-Oo project, which created patches and enhancements that were not contributed back to the official OOo distribution. That became a full fork when the LibreOffice project was started by importing all of the OOo source code into a new repository. Hi Allen - will that story never die? The creation of the TDF and LibreOffice was a movement far above and beyond Go-Oo. It just happened to assimilate that code (and much more). I can, have to, testimony that. I was involved in already two serious discussions about starting a foundation (after all those years) when there was even not a single hair on my head thinking about go-oo. -- - Cor - http://nl.libreoffice.org -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Hi Greg, Greg Stein wrote on 2011-06-14 17.09: It is simply that newbie's have NO UNDERSTANDING of this. Florian had to explain all the details because they are not on the website. I guess the truth lies in between. :-) Indeed, we seem to lack some comprehensible page directly reachable with all the details. However, we have been regular announcing status and facts via e-mail, our blog, social networks, and the donations (challenge) page has also some background on it. I would say anyone who looked a bit at the project would find out things. I agree, however, at a first glance, things might indeed be a bit hard to discover, and looking at how fast things went at Apache, I understand that things needed explanation. We should indeed add a short note to http://www.documentfoundation.org/faq/ Florian -- Florian Effenberger flo...@documentfoundation.org Steering Committee and Founding Member of The Document Foundation Tel: +49 8341 99660880 | Mobile: +49 151 14424108 Skype: floeff | Twitter/Identi.ca: @floeff -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Jun 14, 2011, at 8:00 PM, Keith Curtis wrote: \ I also make more posts because I'm amazed that some leaders in our movement with the pedigree of IBM are actually hindrances. I see a story worthy of the New York Times. In fact, I have a connection ;-) And I'm surprised that some leaders are more concerned about PR and marketing and being perceived as something they are not, rather than trying to be more inclusive to the much larger eco-system in which they live. Sometimes personal ideological stances blind people so much that they forget what's important: it's building FOSS that changes the world, not sticking it to companies, people or entities that one feels slighted by. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
May I suggest we call time[1] on this discussion please? S. [1] http://www.urbandictionary.com/define.php?term=Time%20Gentlemen%20Please -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Wed, Jun 15, 2011 at 9:18 AM, Simon Phipps si...@webmink.com wrote: May I suggest we call time[1] on this discussion please? +1 S. [1] http://www.urbandictionary.com/define.php?term=Time%20Gentlemen%20Please - Sam Ruby -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
- Original Message From: Florian Effenberger flo...@documentfoundation.org Greg Stein wrote on 2011-06-14 17.09: It is simply that newbie's have NO UNDERSTANDING of this. Florian had to explain all the details because they are not on the website. I guess the truth lies in between. :-) Indeed, we seem to lack some comprehensible page directly reachable with all the details. However, we have been regular announcing status and facts via e-mail, our blog, social networks, and the donations (challenge) page has also some background on it. My primary point is that to side-line the discussion (of which Greg was responding to, and I assume you are too) the text at the bottom of each webpage on the LO website which presently reads as follows: 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 GNU Lesser General Public License (LGPLv3). LibreOffice and The Document Foundation are registered trademarks. Their respective logos and icons are subject to international copyright laws. The use of these therefore is subject to our trademark policy. should be updated to reflect the legal reality that while TDF is being setup it is an sub-entity of FroDeV; listing out who specifically owns the trademarks, etc. That would go a long way in saying TDF is or is backed by an actual legal entity, and not something that is simply a project put together by a lot of people without any legal standing. (The above was specifically taken from the http://www.documentfoundation.org/faq/ webpage.) Note: I am not saying anything about the actual legal standing of TDF in this e-mail; just pointing out how that legal standing could be _better_ communicated to by-standers and visitors of the TDF/LO websites - of which there are many more than are known by the community, or participate in the community - e.g. reporters that go on the website for some tidbit of information, or someone looking to simply download LO for use. $0.02 Ben -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Hi, BRM wrote on 2011-06-15 15.47: should be updated to reflect the legal reality that while TDF is being setup it is an sub-entity of FroDeV; listing out who specifically owns the trademarks, etc. That would go a long way in saying TDF is or is backed by an actual legal hm, isn't this the exact information contained in the imprint? It reads: [...] The party responsible for the content of this website is: Freies Office Deutschland e.V. Riederbergstr. 92 65195 Wiesbaden Deutschland/Germany E-mail address: i...@frodev.org Website: http://www.frodev.org Vertretungsberechtigter Vorstand/Board of Directors: Thomas Krumbein (Vorsitzender), Jacqueline Rahemipour, Florian Effenberger (Anschrift jeweils wie oben) [...] Florian -- Florian Effenberger flo...@documentfoundation.org Steering Committee and Founding Member of The Document Foundation Tel: +49 8341 99660880 | Mobile: +49 151 14424108 Skype: floeff | Twitter/Identi.ca: @floeff -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Maybe it's a language issue, but no, the imprint does nothing at all to make it clear. It simply says, in effect, FroDev wrote the content and they are responsible for the content on the site. It says nothing at all about the legal structure at all. On Jun 15, 2011, at 10:54 AM, Florian Effenberger wrote: Hi, BRM wrote on 2011-06-15 15.47: should be updated to reflect the legal reality that while TDF is being setup it is an sub-entity of FroDeV; listing out who specifically owns the trademarks, etc. That would go a long way in saying TDF is or is backed by an actual legal hm, isn't this the exact information contained in the imprint? It reads: [...] The party responsible for the content of this website is: Freies Office Deutschland e.V. Riederbergstr. 92 65195 Wiesbaden Deutschland/Germany E-mail address: i...@frodev.org Website: http://www.frodev.org Vertretungsberechtigter Vorstand/Board of Directors: Thomas Krumbein (Vorsitzender), Jacqueline Rahemipour, Florian Effenberger (Anschrift jeweils wie oben) [...] Florian -- Florian Effenberger flo...@documentfoundation.org Steering Committee and Founding Member of The Document Foundation Tel: +49 8341 99660880 | Mobile: +49 151 14424108 Skype: floeff | Twitter/Identi.ca: @floeff -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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 -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Allen Pulsifer wrote: Thorsten Behrens wrote: ...you don't discuss e.g. trademark issues on a public list, if you want to stand a chance actually obtaining it. I can see how you might believe this, but I'm not sure it is grounded in fact or experience. Hi Allen, oh, I was referring to LibreOffice / TDF here. [handing OOo to ASF] Regardless of who's fault this is, had the discussions been done in public and involved all of the community instead of a select group, the results might have been different. You lost me here - it was Oracle who decided this behind closed doors. If that was the point you wanted to make earlier, then I of course agree that this was unfortunate. That's water under the bridge at this point, but given the results, a little bit of introspection and willingness to make accommodations might benefit everyone. That's universally true, indeed. :) Cheers, -- Thorsten -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
It's also not located on _every_ page on the TDF/LO websites. The text I quoted is, and the change I called for would be. Ben - Original Message From: Jim Jagielski j...@jagunet.com To: discuss@documentfoundation.org Sent: Wed, June 15, 2011 11:28:33 AM Subject: Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice Maybe it's a language issue, but no, the imprint does nothing at all to make it clear. It simply says, in effect, FroDev wrote the content and they are responsible for the content on the site. It says nothing at all about the legal structure at all. On Jun 15, 2011, at 10:54 AM, Florian Effenberger wrote: Hi, BRM wrote on 2011-06-15 15.47: should be updated to reflect the legal reality that while TDF is being setup it is an sub-entity of FroDeV; listing out who specifically owns the trademarks, etc. That would go a long way in saying TDF is or is backed by an actual legal hm, isn't this the exact information contained in the imprint? It reads: [...] The party responsible for the content of this website is: Freies Office Deutschland e.V. Riederbergstr. 92 65195 Wiesbaden Deutschland/Germany E-mail address: i...@frodev.org Website: http://www.frodev.org Vertretungsberechtigter Vorstand/Board of Directors: Thomas Krumbein (Vorsitzender), Jacqueline Rahemipour, Florian Effenberger (Anschrift jeweils wie oben) [...] Florian -- Florian Effenberger flo...@documentfoundation.org Steering Committee and Founding Member of The Document Foundation Tel: +49 8341 99660880 | Mobile: +49 151 14424108 Skype: floeff | Twitter/Identi.ca: @floeff -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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 -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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 -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Il 15/06/2011 17:44, Allen Pulsifer ha scritto: Thorsten Behrens wrote: ...you don't discuss e.g. trademark issues on a public list, if you want to stand a chance actually obtaining it. I can see how you might believe this, but I'm not sure it is grounded in fact or experience. In fact, look at where we ended up: - Oracle pulled all resources from the project. - TdF did not obtain the trademark or the openoffice.org domain. - The community ended up fractured. Regardless of who's fault this is, had the discussions been done in public and involved all of the community instead of a select group, the results might have been different. That's water under the bridge at this point, but given the results, a little bit of introspection and willingness to make accommodations might benefit everyone. Sorry Allen but you are in contradiction. Before you say Regardless of who's fault and at the end it seems you are accusing TDF to be the cause of the community fracture. I just want to remember you we have been discussing about a foundation since 2003. Sun/IBM before and then Oracle/IBM after, always in silence. Don't you think people can become tired of non-changing things? Don't you think the introspection should be made on both parts? Anyway, maybe TDF (and Sun/Oracle/IBM) made some mistakes but to keep discussing about spilt milk is completely useless. Davide -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Davide Dozza wrote: Sorry Allen but you are in contradiction. Before you say Regardless of who's fault and at the end it seems you are accusing TDF to be the cause of the community fracture. I made no accusations and assigned no fault. I'm also not interested in assigning fault or blame. That's an unfortunate distraction it seems many have gotten caught up in, and IMO, it has only hurt the project not helped it. On that point, let me be clear: There are millions of potential users for OOo, LO, and open document formats. Many of those potential users work in companies, government agencies and other organizations that routinely trust Microsoft, Oracle, IBM and other large corporations to meet their IT needs. Getting in a public spat with any of those companies does not help the project in the least, it only hurts it. End users do not care about who's right, who's wrong, who's been slighted, who is more pure, etc. They just care about products and technologies that are going to meet their needs. For many users, the best thing OOo had going for it was that it was backed by Sun and there was a commercial version users they could turn to if they needed support, etc. Now that Oracle has pulled out, that is gone and TdF cannot replace it. Regardless of individual feelings, the best the TdF and its members could do at this point would be to put on a smiling face, magnanimously congratulate the ASF for joining the community, and at least make it look like they were working closely with IBM to bring the best possible open document technologies to the world. If most or almost all of the LO contributors joined the Apache OpenOffice project, if only to lend moral support and help heal the rift, that would only be good for LO and the TdF. The best time to do that is now. Best Regards, Allen -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Allen Pulsifer wrote: If most or almost all of the LO contributors joined the Apache OpenOffice project, if only to lend moral support and help heal the rift, that would only be good for LO and the TdF. Allen, how can you, with a straight face, ask people here to come over to a different project, that likely noone here is really happy with, that was setup as a fait acompli, marketed as the natural upstream, removes rights from people's contributions, and is effectively competing (by how the proposal reads)? Whatever good intentions you may have, but basic psychology must tell you that this hey folks, come all over, we need your help here is not gonna fly - quite the contrary, it comes across as rather condescending. Please move to a different strategy - if your intentions are good, the current one is not helping your cause - if they're ill, I'm even less willing to tolerate it. Cheers, -- Thorsten -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
Hi Allen, *, Allen Pulsifer schrieb: On that point, let me be clear: There are millions of potential users for OOo, LO, and open document formats. Many of those potential users work in companies, government agencies and other organizations that routinely trust Microsoft, Oracle, IBM and other large corporations to meet their IT needs. Getting in a public spat with any of those companies does not help the project in the least, it only hurts it. End users do not care about who's right, who's wrong, who's been slighted, who is more pure, etc. They just care about products and technologies that are going to meet their needs. Well, for a healthy community not *only* happy end users are an essetial ingredient as aren't *only* happy coders. If it isn't possible to achive having all parts of the community happy and that way satisfying a significant range of end users (which I also count as part of it) then we definitly should rethink the questions: who are we? Where do we go? For many users, the best thing OOo had going for it was that it was backed by Sun and there was a commercial version users they could turn to if they needed support, etc. Did You ask some of them about the degree of happyness with the results. I'd be interested to read positive feedback regarding this (preferably big numbers!). Now that Oracle has pulled out, that is gone and TdF cannot replace it. Regardless of individual feelings, the best the TdF and its members could do at this point would be to put on a smiling face, magnanimously congratulate the ASF for joining the community, and at least make it look like they were working closely with IBM to bring the best possible open document technologies to the world. If most or almost all of the LO contributors joined the Apache OpenOffice project, if only to lend moral support and help heal the rift, that would only be good for LO and the TdF. The best time to do that is now. Simply don't agree - as of having bad *experience* regarding a big company beeing bad balanced power community member. I notice Your claims beeing questions of faith packed as facts and put mine at the opposite side. So 1:1 ;o)) Gruß/regards -- Friedrich Libreoffice-Box http://libreofficebox.org/ LibreOffice and more on CD/DVD images -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Wed, Jun 15, 2011 at 17:53, Thorsten Behrens t...@documentfoundation.org wrote: ... Allen, how can you, with a straight face, ask people here to come over to a different project, that likely noone here is really happy with, that was setup as a fait acompli, marketed as the natural upstream, removes rights from people's contributions, and is effectively competing (by how the proposal reads)? I don't really want to debate most of your points because (frankly) some of it is true. Arguable to some extent, blah blah blah. :-) But the one point that I'm curious about: how can you say that Apache removes rights from people's contributions? As a developer, you still own your code. You can do whatever you like with it. Apache doesn't take anything from You. Did I misunderstand you in some way? Cheers, -g -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Mon, Jun 13, 2011 at 15:05, David Nelson comme...@traduction.biz wrote: Hi Jim, BRM, On Tue, Jun 14, 2011 at 00:43, Jim Jagielski j...@jagunet.com wrote: There was, and still is, the perception that TDF is an official, fully- setup, self-controlled and self-existing foundation (similar to what the ASF is) Personally, I'm very happy with what's been achieved, and I'm optimistic for the project's future. Nobody is denying that or arguing otherwise. It is simply that newbie's have NO UNDERSTANDING of this. Florian had to explain all the details because they are not on the website. You describe how all the committers and people on the steering committee know these details. Well, of course. But what about all the people at Apache who are trying to learn about the work you guys have done here? Trying to learn the details of your Foundation, its organization, and its (current) backing association? Trying to learn who handles your donations, and how those proceeds are disbursed? BRM, Jim, and I are trying to say that that information is opaque. It takes direct involvement from Florian to achieve understanding. ... BTW, I'm very happy to welcome you here to chew the fat with us. If you really feel you have a different path forward that you want to follow, then I sincerely wish you well with the endeavour. But you We've chosen to take this path, yes... so thanks for the well wishes. have a lot of running to do in every area to catch up with us, guys! ;-) The competition will be interesting and probably not without Our goal is not to beat you. This is not a competition. That is not how Apache operates. Apache is a charity conceived and constructed to provide code to the world. We believe the best way to provide that code to *everybody* is to do so under a permissive license. If we can create a release of OOo, then we have performed our mission. Our charitable status specifically precludes us from competition. But would not want to compete, regardless. We will produce the best OOo we can. If yours is better, then we believe that is just fine. If you are able to use some portion of our code to make your job easier, then even better. Cheers, -g -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On 14 Jun 2011, at 16:09, Greg Stein wrote: Our charitable status specifically precludes us from competition. What does it say about collaborating with others? Anything? (serious question, I have no idea). S. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Jun 14, 2011, at 11:12 AM, Simon Phipps wrote: On 14 Jun 2011, at 16:09, Greg Stein wrote: Our charitable status specifically precludes us from competition. What does it say about collaborating with others? Anything? (serious question, I have no idea). In essence, as a public trust, the ASF must operate in a way that does not favor one vendor or partner or collaborator over another. This is one reason why the ASF was, for example, unable to continue within the JCP EC, since our involvement in there provided more benefit to Oracle than to anyone else. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On 14 Jun 2011, at 16:54, Jim Jagielski wrote: On Jun 14, 2011, at 11:12 AM, Simon Phipps wrote: On 14 Jun 2011, at 16:09, Greg Stein wrote: Our charitable status specifically precludes us from competition. What does it say about collaborating with others? Anything? (serious question, I have no idea). In essence, as a public trust, the ASF must operate in a way that does not favor one vendor or partner or collaborator over another. This is one reason why the ASF was, for example, unable to continue within the JCP EC, since our involvement in there provided more benefit to Oracle than to anyone else. Would that preclude treating TDF as a collaborative peer? Being a non-profit itself FrODeV is presumably bound by the same limitation so collaborating with it would not violate that requirement for neutrality. S. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Tue, Jun 14, 2011 at 8:09 AM, Greg Stein gst...@gmail.com wrote: You describe how all the committers and people on the steering committee know these details. Well, of course. But what about all the people at Apache who are trying to learn about the work you guys have done here? Trying to learn the details of your Foundation, its organization, and its (current) backing association? Trying to learn who handles your donations, and how those proceeds are disbursed? If you had come up with a plan of merging the foundations, all these details would have been worked through. I don't think it matters now given the fork. BRM, Jim, and I are trying to say that that information is opaque. It takes direct involvement from Florian to achieve understanding. You should have gotten your question answered before the proposal was submitted for a vote. Our goal is not to beat you. This is not a competition. That is not how Apache operates. Your goal is not to beat LO, but by choosing a fork you make cooperation difficult via license incompatibilities and social engineering. So if you aren't cooperating or competing then what word would you recommend? -Keith -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Tue, Jun 14, 2011 at 17:04, Keith Curtis keit...@gmail.com wrote: On Tue, Jun 14, 2011 at 8:09 AM, Greg Stein gst...@gmail.com wrote: You describe how all the committers and people on the steering committee know these details. Well, of course. But what about all the people at Apache who are trying to learn about the work you guys have done here? Trying to learn the details of your Foundation, its organization, and its (current) backing association? Trying to learn who handles your donations, and how those proceeds are disbursed? If you had come up with a plan of merging the foundations, all these details would have been worked through. I don't think it matters now given the fork. BRM, Jim, and I are trying to say that that information is opaque. It takes direct involvement from Florian to achieve understanding. You should have gotten your question answered before the proposal was submitted for a vote. We got our answer (before the vote) because Florian explained it. Our point is that other people visiting the site will not have Florian's attention. This has nothing to do with Apache, except by way of example and that Florian was engaged. Others will not be so lucky. I don't think the questions that I posed had anything to do with merging, but simply the kinds of curiosity that TDF supporters may have (or those who may be interested in *becoming* supporters). In short: suggestions on website improvements, for an audience that we weren't describing to David very well. Our goal is not to beat you. This is not a competition. That is not how Apache operates. Your goal is not to beat LO, but by choosing a fork you make cooperation difficult via license incompatibilities and social engineering. So if you aren't cooperating or competing then what word would you recommend? We want to cooperate. It is quite possible, and there have been several suggestions on ways to do that. If cooperation doesn't happen, then you're simply talking co-existence. Competition requires intent, I believe. But we can choose to disagree on that, I suppose. Cheers, -g -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Tue, Jun 14, 2011 at 2:40 PM, Greg Stein gst...@gmail.com wrote: We got our answer (before the vote) because Florian explained it. Our point is that other people visiting the site will not have Florian's attention. This has nothing to do with Apache, except by way of example and that Florian was engaged. Others will not be so lucky. It isn't very frequently that people with the OpenOffice trademark come along. I don't think the questions that I posed had anything to do with merging, but simply the kinds of curiosity that TDF supporters may have (or those who may be interested in *becoming* supporters). They are irrelevant to you now that you aren't merging, and they would only have been relevant to you if you had merged, and they aren't relevant to typical people in the community so you can imagine why it is low priority. Our goal is not to beat you. This is not a competition. That is not how Apache operates. Your goal is not to beat LO, but by choosing a fork you make cooperation difficult via license incompatibilities and social engineering. So if you aren't cooperating or competing then what word would you recommend? We want to cooperate. Forking makes cooperation more expensive. Your intentions are less important than your consequences. -Keith -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [Libreoffice] Proposal to join Apache OpenOffice
On Tue, Jun 14, 2011 at 17:52, Keith Curtis keit...@gmail.com wrote: ... I don't think the questions that I posed had anything to do with merging, but simply the kinds of curiosity that TDF supporters may have (or those who may be interested in *becoming* supporters). They are irrelevant to you now that you aren't merging, and they would only have been relevant to you if you had merged, and they aren't relevant to typical people in the community so you can imagine why it is low priority. Agreed. ... Forking makes cooperation more expensive. Your intentions are less important than your consequences. Sounds like we'll have to agree to disagree. Cheers, -g -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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