[steering-discuss] SC Call on Saturday
Hi, I might not be able to join the SC Call on Saturday, as I am on the TDF admin weekend in Munich. Christoph, can you jump in for me? Thanks, 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 steering-discuss+h...@documentfoundation.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/steering-discuss/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [steering-discuss] SC Call on Saturday
Hi Florian, 2011/6/21 Florian Effenberger flo...@documentfoundation.org Hi, I might not be able to join the SC Call on Saturday, as I am on the TDF admin weekend in Munich. Christoph, can you jump in for me? I got a question about this calls, until now via skype. The last time I talked with Olivier about this calls, he told me that Skype is not always supporting us all in conversation. And even with the Talkyoo helping, still happens any technical difficulties (here and there). I would suggest that (maybe) be interesting to test the TeamSpeak. We can configure a service on a TDF-server to receive the calls, and each participant will have a login to use it in these calls. It's just a suggestion, an idea. My 2 euros, 'cause 2 cents is too little. ;-) MfG., David Thanks, 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 steering-discuss+help@** documentfoundation.org steering-discuss%2bh...@documentfoundation.org Posting guidelines + more: http://wiki.**documentfoundation.org/** Netiquette http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.**documentfoundation.org/www/** steering-discuss/http://listarchives.documentfoundation.org/www/steering-discuss/ All messages sent to this list will be publicly archived and cannot be delete -- Unsubscribe instructions: E-mail to steering-discuss+h...@documentfoundation.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/steering-discuss/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [steering-discuss] SC Call on Saturday
David Emmerich Jourdain wrote: I would suggest that (maybe) be interesting to test the TeamSpeak. We can configure a service on a TDF-server to receive the calls, and each participant will have a login to use it in these calls. Hm, if we go for our own solution - I'd rather suggest Mumble (http://mumble.sourceforge.net/). That reportedly works very well for a number of people. I gather TeamSpeak is not opensource? Cheers, -- Thorsten -- Unsubscribe instructions: E-mail to steering-discuss+h...@documentfoundation.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/steering-discuss/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [steering-discuss] SC Call on Saturday
Hi Thorsten, hi all, 2011/6/21 Thorsten Behrens t...@documentfoundation.org David Emmerich Jourdain wrote: I would suggest that (maybe) be interesting to test the TeamSpeak. We can configure a service on a TDF-server to receive the calls, and each participant will have a login to use it in these calls. Hm, if we go for our own solution - I'd rather suggest Mumble (http://mumble.sourceforge.net/). That reportedly works very well for a number of people. Maybe a better option, I think. I know mumble, but I have never used intensively. So, I can't comment about performance. I gather TeamSpeak is not opensource? No. TeamSpeak is not opensource, as our current solution. I was only thinking to consider another tool, to guarantee quality to the calls. But, as you suggested, perhaps mumble is a better option. MfG., David Cheers, -- Thorsten -- Unsubscribe instructions: E-mail to steering-discuss+h...@documentfoundation.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/steering-discuss/ All messages sent to this list will be publicly archived and cannot be deleted
[steering-discuss] Re: SC Call on Saturday
Hi Florian! Am Dienstag, den 21.06.2011, 14:39 +0200 schrieb Florian Effenberger: Hi, I might not be able to join the SC Call on Saturday, as I am on the TDF admin weekend in Munich. Christoph, can you jump in for me? Hehe, I'm visiting my sister's family as well - but should be doable somehow; as long as we can stick with a usual phone conference. Unfortunately, I won't be able to test/stabilize the mumble service until the weekend. I hope this will be okay for the other participants. And, nice having the opportunity (duty?) to join again :-) Cheers, Christoph -- Unsubscribe instructions: E-mail to steering-discuss+h...@documentfoundation.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/steering-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
[tdf-discuss] Re: Hackfest - September 9th, Ohio Linux Fest
Seems to me this thread used to be longer in Nabble 8-0 I am still interested Drew and I had this thought: Even if a HackFest can't be drawn together it would be very useful to the attendees and LibreOffice to have at least a table where people could report issues (as new or as confirmation of existing issues), get coaching on appropriate upgrades, and maybe do a little testing around their known issues, hard to reproduce issues or just visit areas that are important to them as users. Seems like an excellent chance for solid feedback from committed and skillful users. LeMoyne -- View this message in context: http://nabble.documentfoundation.org/Hackfest-September-9th-Ohio-Linux-Fest-tp3069297p3089492.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))
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: [tdf-discuss] Re: Hackfest - September 9th, Ohio Linux Fest
I proposed a talk on OOo / LO and plan to attend. Did not put in much time on the proposal so not sure if it will be accepted. If something is happening there, count me in. On 06/21/2011 02:46 AM, John LeMoyne Castle wrote: Seems to me this thread used to be longer in Nabble 8-0 I am still interested Drew and I had this thought: Even if a HackFest can't be drawn together it would be very useful to the attendees and LibreOffice to have at least a table where people could report issues (as new or as confirmation of existing issues), get coaching on appropriate upgrades, and maybe do a little testing around their known issues, hard to reproduce issues or just visit areas that are important to them as users. Seems like an excellent chance for solid feedback from committed and skillful users. LeMoyne -- View this message in context: http://nabble.documentfoundation.org/Hackfest-September-9th-Ohio-Linux-Fest-tp3069297p3089492.html Sent from the Discuss mailing list archive at Nabble.com. -- Andrew Pitonyak My Macro Document: http://www.pitonyak.org/AndrewMacro.odt Info: http://www.pitonyak.org/oo.php -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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: [tdf-discuss] Re: Hackfest - September 9th, Ohio Linux Fest
On Tue, 2011-06-21 at 08:25 -0400, Andrew Douglas Pitonyak wrote: I proposed a talk on OOo / LO and plan to attend. Did not put in much time on the proposal so not sure if it will be accepted. If something is happening there, count me in. Hi Andres, It is great to see you here. So where is this: Talked with Beth Ann E. at SELF 10 days ago about, she was very enthusiastic and wanted me to contact her direct about getting it done. Tried to get a little interest started here first - that seems to be getting traction, so sent her a message a couple of days ago. No response yet, thought I'd wait till tomorrow before pinging her again. No formal proposal to them yet, but was thinking that is a good way to ping her - didn't check if the OHLF website is still taking them as the cut-off date has passed - so might still have to rely on a direct email. Anyway - would really be excited about you participating - I'm kind of running blind as to what exactly is needed for this. Might be over thinking it (I have that tendency at times). best wishes, Drew On 06/21/2011 02:46 AM, John LeMoyne Castle wrote: Seems to me this thread used to be longer in Nabble 8-0 I am still interested Drew and I had this thought: Even if a HackFest can't be drawn together it would be very useful to the attendees and LibreOffice to have at least a table where people could report issues (as new or as confirmation of existing issues), get coaching on appropriate upgrades, and maybe do a little testing around their known issues, hard to reproduce issues or just visit areas that are important to them as users. Seems like an excellent chance for solid feedback from committed and skillful users. LeMoyne -- View this message in context: http://nabble.documentfoundation.org/Hackfest-September-9th-Ohio-Linux-Fest-tp3069297p3089492.html Sent from the Discuss mailing list archive at Nabble.com. -- Andrew Pitonyak My Macro Document: http://www.pitonyak.org/AndrewMacro.odt Info: http://www.pitonyak.org/oo.php -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org 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
[tdf-discuss] TDF Certification
The document is on the wiki. http://wiki.documentfoundation.org/TDFCertification This might become a huge project, and a new business model for free software on the desktop. A challenge for the entire community, and one of the reasons for having an independent foundation and not a house for the code. Contents are not confidential, of course, as otherwise they would not be on the wiki, but it must be clear that this is going to become a real project after a long incubation. Everyone is warmly invited to comment and provide suggestions. Ciao, Italo -- 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
