Re: Project Information
Hi Pedro, Am 04.03.23 um 17:35 schrieb Matthias Seidel: > Hi Pedro, > > Am 04.03.23 um 17:17 schrieb Pedro Lino: >> That is odd! >> >> Because what I see is the code where 4.1.13 no longer exists... >> >> https://github.com/apache/openoffice-project/blob/main/content/doap_openoffice.rdf > That is the data that we update. >> This is really beyond my understanding... > The Project Information page itself is updated (based on our submitted > data) by a cron job. Apparently that failed this time. Now it is updated! We can close this task now... Regards, Matthias > > No magic involved! ;-) > > Regards, > > Matthias > >> Best, >> Pedro >> >>> On 03/04/2023 3:25 PM WET Matthias Seidel >>> wrote: >>> >>> >>> FYI: >>> >>> https://github.com/apache/openoffice-project/commit/c58b9b83932cd4f4ed522934fdd785bb68fc03d4#commitcomment-103032533 >>> >>> Regards, >>> >>> Matthias >>> >>> Am 04.03.23 um 13:29 schrieb Matthias Seidel: >>>> Hi Pedro, >>>> >>>> Am 04.03.23 um 13:22 schrieb Pedro Lino: >>>>> Hi Matthias >>>>> >>>>>> On 03/04/2023 11:03 AM WET Matthias Seidel >>>>>> wrote: >>>>>> Our updated Project Information is still not published: >>>>>> >>>>>> https://projects.apache.org/project.html?openoffice >>>>>> >>>>>> Normally this is done by a cron job. Am I missing something? >>>>> Maybe the expectation "runs maybe every 24h" is not realistic? :) >>>>> >>>>> Or it appeared to be a cron job but in fact it was someone (Andrea?) who >>>>> updated it manually? >>>> No, it worked that way all the years before... >>>> >>>> But maybe the "second release" that was introduced (and reversed) broke >>>> our chain? >>>> >>>> Regards, >>>> >>>> Matthias >>>> >>>>> Best, >>>>> Pedro >>>>> >>>>> - >>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>>> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> smime.p7s Description: S/MIME Cryptographic Signature
Re: Project Information
Hi Pedro, Am 04.03.23 um 17:17 schrieb Pedro Lino: > That is odd! > > Because what I see is the code where 4.1.13 no longer exists... > > https://github.com/apache/openoffice-project/blob/main/content/doap_openoffice.rdf That is the data that we update. > > This is really beyond my understanding... The Project Information page itself is updated (based on our submitted data) by a cron job. Apparently that failed this time. No magic involved! ;-) Regards, Matthias > > Best, > Pedro > >> On 03/04/2023 3:25 PM WET Matthias Seidel wrote: >> >> >> FYI: >> >> https://github.com/apache/openoffice-project/commit/c58b9b83932cd4f4ed522934fdd785bb68fc03d4#commitcomment-103032533 >> >> Regards, >> >> Matthias >> >> Am 04.03.23 um 13:29 schrieb Matthias Seidel: >>> Hi Pedro, >>> >>> Am 04.03.23 um 13:22 schrieb Pedro Lino: >>>> Hi Matthias >>>> >>>>> On 03/04/2023 11:03 AM WET Matthias Seidel >>>>> wrote: >>>>> Our updated Project Information is still not published: >>>>> >>>>> https://projects.apache.org/project.html?openoffice >>>>> >>>>> Normally this is done by a cron job. Am I missing something? >>>> Maybe the expectation "runs maybe every 24h" is not realistic? :) >>>> >>>> Or it appeared to be a cron job but in fact it was someone (Andrea?) who >>>> updated it manually? >>> No, it worked that way all the years before... >>> >>> But maybe the "second release" that was introduced (and reversed) broke >>> our chain? >>> >>> Regards, >>> >>> Matthias >>> >>>> Best, >>>> Pedro >>>> >>>> - >>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>> > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Project Information
That is odd! Because what I see is the code where 4.1.13 no longer exists... https://github.com/apache/openoffice-project/blob/main/content/doap_openoffice.rdf This is really beyond my understanding... Best, Pedro > On 03/04/2023 3:25 PM WET Matthias Seidel wrote: > > > FYI: > > https://github.com/apache/openoffice-project/commit/c58b9b83932cd4f4ed522934fdd785bb68fc03d4#commitcomment-103032533 > > Regards, > > Matthias > > Am 04.03.23 um 13:29 schrieb Matthias Seidel: > > Hi Pedro, > > > > Am 04.03.23 um 13:22 schrieb Pedro Lino: > >> Hi Matthias > >> > >>> On 03/04/2023 11:03 AM WET Matthias Seidel > >>> wrote: > >>> Our updated Project Information is still not published: > >>> > >>> https://projects.apache.org/project.html?openoffice > >>> > >>> Normally this is done by a cron job. Am I missing something? > >> Maybe the expectation "runs maybe every 24h" is not realistic? :) > >> > >> Or it appeared to be a cron job but in fact it was someone (Andrea?) who > >> updated it manually? > > No, it worked that way all the years before... > > > > But maybe the "second release" that was introduced (and reversed) broke > > our chain? > > > > Regards, > > > > Matthias > > > >> Best, > >> Pedro > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >> For additional commands, e-mail: dev-h...@openoffice.apache.org > >> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Project Information
FYI: https://github.com/apache/openoffice-project/commit/c58b9b83932cd4f4ed522934fdd785bb68fc03d4#commitcomment-103032533 Regards, Matthias Am 04.03.23 um 13:29 schrieb Matthias Seidel: > Hi Pedro, > > Am 04.03.23 um 13:22 schrieb Pedro Lino: >> Hi Matthias >> >>> On 03/04/2023 11:03 AM WET Matthias Seidel >>> wrote: >>> Our updated Project Information is still not published: >>> >>> https://projects.apache.org/project.html?openoffice >>> >>> Normally this is done by a cron job. Am I missing something? >> Maybe the expectation "runs maybe every 24h" is not realistic? :) >> >> Or it appeared to be a cron job but in fact it was someone (Andrea?) who >> updated it manually? > No, it worked that way all the years before... > > But maybe the "second release" that was introduced (and reversed) broke > our chain? > > Regards, > > Matthias > >> Best, >> Pedro >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> smime.p7s Description: S/MIME Cryptographic Signature
Re: Project Information
Hi Pedro, Am 04.03.23 um 13:22 schrieb Pedro Lino: > Hi Matthias > >> On 03/04/2023 11:03 AM WET Matthias Seidel >> wrote: >> Our updated Project Information is still not published: >> >> https://projects.apache.org/project.html?openoffice >> >> Normally this is done by a cron job. Am I missing something? > Maybe the expectation "runs maybe every 24h" is not realistic? :) > > Or it appeared to be a cron job but in fact it was someone (Andrea?) who > updated it manually? No, it worked that way all the years before... But maybe the "second release" that was introduced (and reversed) broke our chain? Regards, Matthias > > Best, > Pedro > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Project Information
Hi Matthias > On 03/04/2023 11:03 AM WET Matthias Seidel wrote: > Our updated Project Information is still not published: > > https://projects.apache.org/project.html?openoffice > > Normally this is done by a cron job. Am I missing something? Maybe the expectation "runs maybe every 24h" is not realistic? :) Or it appeared to be a cron job but in fact it was someone (Andrea?) who updated it manually? Best, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Project Information
Hi all, Our updated Project Information is still not published: https://projects.apache.org/project.html?openoffice Normally this is done by a cron job. Am I missing something? Regards, Matthias smime.p7s Description: S/MIME Cryptographic Signature
[GitHub] [openoffice] ardovm merged pull request #160: Remove SuSE packaging information
ardovm merged PR #160: URL: https://github.com/apache/openoffice/pull/160 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice] ardovm commented on pull request #160: Remove SuSE packaging information
ardovm commented on PR #160: URL: https://github.com/apache/openoffice/pull/160#issuecomment-1312416674 I will merge this PR in one week if no one objects -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice] ardovm opened a new pull request, #160: Remove SuSE packaging information
ardovm opened a new pull request, #160: URL: https://github.com/apache/openoffice/pull/160 The SuSE RPMs depend on certain files that were once present in SuSE distributions, and were deprecated. Freedesktop RPMs should work flawlessly on today's SUSE and openSUSE distributions. See https://bz.apache.org/ooo/show_bug.cgi?id=128424 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to get debug information (Java, oxt)
Hi Rony, Am 06.06.22 um 16:07 schrieb Rony G. Flatscher (Apache): Hi Peter, thank you very much for coming back to this! A pleasure. If you would be aware of such examples I would be grateful for any links. I am sorry. I have no clue. I wanted to get the discussion started, and just did a classic consultant Bullshit bingo move. Which sometimes helps to get on the road to the real solution. So I hoped it worked by catching Carls attention. However I will have look when I find time. Maybe I come back to this once I started with my "getting rid of the assembler code" - project :-D Again, thank you very much for taking time for this! you are welcome. All the best Peter ---rony On 6/4/2022 7:40 AM, Peter Kovacs wrote: I going through old emails and no one seems to answer you. Can you describe your setup? OS, have you sdk installed? All the best Peter Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to get debug information (Java, oxt)
Hi Carl, On 6/7/2022 12:07 AM, Carl Marcum wrote: Hi Rony, On 6/6/22 10:15 AM, Rony G. Flatscher (Apache) wrote: Hi Carl, On 6/4/2022 3:31 PM, Carl Marcum wrote: ... cut ... Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). So the error is during unopkg and not when using the installed extension correct? Yes. For runtime errors on Linux I start the office from the command line and you can println output to it from the extension. Thank you very much for this hint! Are you using the --verbose option when using unopkg from the command line? Yes. As mentioned in the other reply, one of my problems is that in order to quickly get (re-)adjusted to this infrastructure (being away because of other efforts for quite some time in between activities) I would need some short, functional examples (like a nutshell extension in Java with proper packaging to become able to experiment with both, the Java code and the packaging, hoping to develop a conceptual model by doing so). It may be the case that these samples exist, but that I have not found them. So any hint or link to such (Java) nutshell examples would be great as they probably help a lot getting afloat quickly. It might be a larger example that what you're looking for but take a look at my openoffice-groovy project [1] that adds Apache Groovy as a macro language. There is also an OXT on the extensions site [2]. Thank you very much, indeed! As a matter of fact, like yourself I used the BeanShell example to add ooRexx as a macro extension. Nevertheless I will look into it (in the middle of July when things have settled down a little bit around here), as I might learn how to install the macros in share and user space (doing this "manually" currently). [On the side: my premiere platform for this has been AOO, but because of the students I have been also trying to allow for using ooRexx as a macro language also for LO. It seems that LO has changed too much to allow that to be still the case, which is awkward. Short of time I am not able to pursue that, as the platform defining OO is AOO only.] If you would rather have an basic stripped down extension example I can generate you one from my templates or guide you in setting up so you can generate your own addons and addins. [1] https://github.com/cbmarcum/openoffice-groovy [2] https://extensions.openoffice.org/en/project/groovy-scripting-openoffice That is *very* kind of you and I would like to pick up your offer about samples that would show/demonstrate/guide to become able to create/generate also own addons and addins in ooRexx (this is something I have been thinking of for quite some time)! Probably only a brief sample/pattern for an addon and an addin and what the relevant definitions would be terrific (especially what has to be taken into account for registering) and maybe where to find the relevant documentation! Groovy and/or Java would be more than fine! Best regards ---rony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to get debug information (Java, oxt)
Hi Rony, On 6/6/22 10:15 AM, Rony G. Flatscher (Apache) wrote: Hi Carl, On 6/4/2022 3:31 PM, Carl Marcum wrote: ... cut ... Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). So the error is during unopkg and not when using the installed extension correct? Yes. For runtime errors on Linux I start the office from the command line and you can println output to it from the extension. Thank you very much for this hint! Are you using the --verbose option when using unopkg from the command line? Yes. As mentioned in the other reply, one of my problems is that in order to quickly get (re-)adjusted to this infrastructure (being away because of other efforts for quite some time in between activities) I would need some short, functional examples (like a nutshell extension in Java with proper packaging to become able to experiment with both, the Java code and the packaging, hoping to develop a conceptual model by doing so). It may be the case that these samples exist, but that I have not found them. So any hint or link to such (Java) nutshell examples would be great as they probably help a lot getting afloat quickly. It might be a larger example that what you're looking for but take a look at my openoffice-groovy project [1] that adds Apache Groovy as a macro language. There is also an OXT on the extensions site [2]. If you would rather have an basic stripped down extension example I can generate you one from my templates or guide you in setting up so you can generate your own addons and addins. [1] https://github.com/cbmarcum/openoffice-groovy [2] https://extensions.openoffice.org/en/project/groovy-scripting-openoffice Best regards, Carl ---rony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to get debug information (Java, oxt)
Hi Carl, On 6/4/2022 3:31 PM, Carl Marcum wrote: ... cut ... Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). So the error is during unopkg and not when using the installed extension correct? Yes. For runtime errors on Linux I start the office from the command line and you can println output to it from the extension. Thank you very much for this hint! Are you using the --verbose option when using unopkg from the command line? Yes. As mentioned in the other reply, one of my problems is that in order to quickly get (re-)adjusted to this infrastructure (being away because of other efforts for quite some time in between activities) I would need some short, functional examples (like a nutshell extension in Java with proper packaging to become able to experiment with both, the Java code and the packaging, hoping to develop a conceptual model by doing so). It may be the case that these samples exist, but that I have not found them. So any hint or link to such (Java) nutshell examples would be great as they probably help a lot getting afloat quickly. ---rony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to get debug information (Java, oxt)
Hi Peter, thank you very much for coming back to this! I do not have the SDK installed. Unfortunately, the exact details have escaped me since (having done too many other things in between). Background: many, many years ago I have authored a bridge for the scripting language ooRexx taking advantage of the AOO scripting framework which is Java based. Basically I copied the BeanShell engine (editor and dispatching the scripts) and adjusted it for ooRexx (is C++ but there is a Java bridge). The packaging was done copying some other samples, but could get it done only after receiving help from some developers back then who knew about the uno packaging process and what the xml configuration files need to contain. (Also, I reverse-engineered the file layout for scripting language scripts in order to place ooRexx samples there.) So my problem in essence is lack of knowledge of how to properly debug Java code in this context when the Java exceptions are not carried over and displayed. Also, I have no real working knowledge of how one could/should go about configuring uno packages. It would be of great help if there was (and maybe there is, yet, not found so far) a minimal, but working ("nutshell") Java example that would demonstrate and briefly explain how to create an uno package in Java, being able to deploy it (maybe with a method/function that returns "hello, world from a Java uno extension") and explaining the minimal configuration definitions. If you would be aware of such examples I would be grateful for any links. Again, thank you very much for taking time for this! ---rony On 6/4/2022 7:40 AM, Peter Kovacs wrote: I going through old emails and no one seems to answer you. Can you describe your setup? OS, have you sdk installed? All the best Peter Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to get debug information (Java, oxt)
Hi Rony, On 6/4/22 1:40 AM, Peter Kovacs wrote: I going through old emails and no one seems to answer you. Can you describe your setup? OS, have you sdk installed? All the best Peter Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). So the error is during unopkg and not when using the installed extension correct? For runtime errors on Linux I start the office from the command line and you can println output to it from the extension. Are you using the --verbose option when using unopkg from the command line? Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to get debug information (Java, oxt)
I going through old emails and no one seems to answer you. Can you describe your setup? OS, have you sdk installed? All the best Peter Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO available in the Microsoft Store app (background information)
Hi Marcus, Am 16.01.22 um 16:18 schrieb Marcus: > Am 15.01.22 um 15:05 schrieb Matthias Seidel: >> Since there were no public information from me until this "project" was >> successfully launched on the last minute in parallel with Windows 11, I >> want to give some details (now that I have time): >> >> Microsoft introduced the possibility to publish "classic" Windows >> programs via their Microsoft Store app. This was a new feature for >> Windows 11 and is now also available for some time on Windows 10. >> So what you download and install via Microsoft Store app is an >> unmodified binary, identical to what we distribute via SourceForge. >> >> The only requirement from Microsoft were to install AOO totally >> "silent". This needed some parameters [1] and a minor change in the >> installation of the MSVC runtimes [2]. >> >> Downloads point to the Apache Download server [3] because we had issues >> with the SourceForge mirrors. >> >> After all, this was technically no big problem but required some >> "struggle" with the Microsoft Developer Network. >> My thanks go to Santhosh Panchapagesam from Microsoft and to Ross >> Gardler (ASF) who made the initial contact. >> >> [1] >> https://svn.apache.org/repos/asf/openoffice/devtools/Microsoft%20Store/Parameters.txt >> >> [2] >> https://github.com/apache/openoffice/commit/908cc4a92408d9aa3bc9d002845a580a2175543f >> >> [3] https://downloads.apache.org/openoffice/4.1.11/binaries/ > > thanks for the background information. Let's see if we can see or feel > one day the increased downloads. The download stats in my Microsoft account still don't show, but we have about 1000 downloads per day: https://logging1-he-de.apache.org/stats/ Not sure how much are related to the Microsoft Store. Regards, Matthias > > Marcus > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: AOO available in the Microsoft Store app (background information)
Am 15.01.22 um 15:05 schrieb Matthias Seidel: Since there were no public information from me until this "project" was successfully launched on the last minute in parallel with Windows 11, I want to give some details (now that I have time): Microsoft introduced the possibility to publish "classic" Windows programs via their Microsoft Store app. This was a new feature for Windows 11 and is now also available for some time on Windows 10. So what you download and install via Microsoft Store app is an unmodified binary, identical to what we distribute via SourceForge. The only requirement from Microsoft were to install AOO totally "silent". This needed some parameters [1] and a minor change in the installation of the MSVC runtimes [2]. Downloads point to the Apache Download server [3] because we had issues with the SourceForge mirrors. After all, this was technically no big problem but required some "struggle" with the Microsoft Developer Network. My thanks go to Santhosh Panchapagesam from Microsoft and to Ross Gardler (ASF) who made the initial contact. [1] https://svn.apache.org/repos/asf/openoffice/devtools/Microsoft%20Store/Parameters.txt [2] https://github.com/apache/openoffice/commit/908cc4a92408d9aa3bc9d002845a580a2175543f [3] https://downloads.apache.org/openoffice/4.1.11/binaries/ thanks for the background information. Let's see if we can see or feel one day the increased downloads. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
AOO available in the Microsoft Store app (background information)
Hi all, Since there were no public information from me until this "project" was successfully launched on the last minute in parallel with Windows 11, I want to give some details (now that I have time): Microsoft introduced the possibility to publish "classic" Windows programs via their Microsoft Store app. This was a new feature for Windows 11 and is now also available for some time on Windows 10. So what you download and install via Microsoft Store app is an unmodified binary, identical to what we distribute via SourceForge. The only requirement from Microsoft were to install AOO totally "silent". This needed some parameters [1] and a minor change in the installation of the MSVC runtimes [2]. Downloads point to the Apache Download server [3] because we had issues with the SourceForge mirrors. After all, this was technically no big problem but required some "struggle" with the Microsoft Developer Network. My thanks go to Santhosh Panchapagesam from Microsoft and to Ross Gardler (ASF) who made the initial contact. Regards, Matthias [1] https://svn.apache.org/repos/asf/openoffice/devtools/Microsoft%20Store/Parameters.txt [2] https://github.com/apache/openoffice/commit/908cc4a92408d9aa3bc9d002845a580a2175543f [3] https://downloads.apache.org/openoffice/4.1.11/binaries/ smime.p7s Description: S/MIME Cryptographic Signature
How to get debug information (Java, oxt)
Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
What information do we know about the market penetration of AOO?
Hello, back in the days of OpenOffice.org, there was a well-maintained pool of information about the market penetration of OpenOffice.org (links to market research, third-party analysis, etc.). I would like to ask if anyone, beyond the bare download numbers, knows of similar information on AOO? Does anyone know if possibly the ASF collects/archives information on this? greetings, Jörg Note: unfortunately, as an AOO project, we do not have any effective marketing activities, which is why I am not sending this email to market...@openoffice.apache.org, because there is no one there (I have been subscribing to market...@openoffice.apache.org for years and I know that no emails come through it). - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Hi - > On Nov 15, 2020, at 9:56 AM, Matthias Seidel > wrote: > > Hi Dave, > > Am 15.11.20 um 18:52 schrieb Dave Fisher: >> >>> On Nov 15, 2020, at 9:34 AM, Matthias Seidel >>> wrote: >>> >>> Hi Andrea, >>> >>> Am 15.11.20 um 18:25 schrieb Andrea Pescetti: >>>> Marcus ha scritto: >>>>> Am 15.11.20 um 16:07 schrieb Matthias Seidel: >>>>>> Am 15.11.20 um 15:54 schrieb Andrea Pescetti: >>>>>>> Matthias Seidel wrote: >>>>>>> >>>>>>> By the way: these were my first edits to the the project site after >>>>>>> the migration and everything was smooth, thanks a lot Dave! It really >>>>>>> looks good for production. >>>>>> Technically yes, but I recognized a slightly bigger vertical space >>>>>> between the topics on the main page and also the boxes on the download >>>>>> page. This may be a css issue. Nothing really big. >>>>> right, but have a look also for the fonts and font sizes. Also here >>>>> are visible changes. >>>> Just to be clear: by "project site" I mean >>>> https://github.com/apache/openoffice-project not >>>> https://github.com/apache/openoffice-org which I haven't built yet. >>> Yes, you are right. The project information is located on the project >>> site. Sorry for the confusion. ;-) >>> IMO the project site is ready for switching. >>>> And I don't really see any difference in the project site between the >>>> "old" and "new" version, besides the underlining of links which is an >>>> easy CSS fix (if wanted; I actually prefer the staged version). There >>>> would be room for other CSS improvements but these apply to the >>>> current https://openoffice.apache.org too. >>> The underlining has changed with my latest css commit. I didn't find the >>> time to explain it: >>> >>> Permanent underlining makes the links esp. on the download page >>> unreadable. Underlining now appears only with "mouser-over". >>> >>> Links are all in blue, so I changed the Heading of the pages to a grey >>> from our logo. This way it cannot be confused with a clickable link. >>> >>> If these changes are OK for everyone I would like to make them also to >>> openoffice.org. >> The css is here: >> https://github.com/apache/openoffice-org/blob/main/assets/css/ooo.css > > I assume we now have *one* single css? Don’t assume. I just moved the site. We still have all the other css and I tried to make sure that these are still included in the same order. When I was testing the Hebrew site with rtl overrides I found that I had ooo.css at the end and not the first style of the block. > > Because on the "old" page there were used lots of them resulting in > different layouts depending on the localized page. We also have the product page css overrides which give us the program icons instead of bullets. A larger question to be discussed as Marketing - Why are the product names different from the Application Quick Start? Regards, Dave > > Regards, > >Matthias > >> >> Regards, >> Dave >> >>> Regards, >>> >>> Matthias >>> >>>> Regards, >>>> Andrea. >>>> >>>> - >>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Hi Dave, Am 15.11.20 um 18:52 schrieb Dave Fisher: > >> On Nov 15, 2020, at 9:34 AM, Matthias Seidel >> wrote: >> >> Hi Andrea, >> >> Am 15.11.20 um 18:25 schrieb Andrea Pescetti: >>> Marcus ha scritto: >>>> Am 15.11.20 um 16:07 schrieb Matthias Seidel: >>>>> Am 15.11.20 um 15:54 schrieb Andrea Pescetti: >>>>>> Matthias Seidel wrote: >>>>>> >>>>>> By the way: these were my first edits to the the project site after >>>>>> the migration and everything was smooth, thanks a lot Dave! It really >>>>>> looks good for production. >>>>> Technically yes, but I recognized a slightly bigger vertical space >>>>> between the topics on the main page and also the boxes on the download >>>>> page. This may be a css issue. Nothing really big. >>>> right, but have a look also for the fonts and font sizes. Also here >>>> are visible changes. >>> Just to be clear: by "project site" I mean >>> https://github.com/apache/openoffice-project not >>> https://github.com/apache/openoffice-org which I haven't built yet. >> Yes, you are right. The project information is located on the project >> site. Sorry for the confusion. ;-) >> IMO the project site is ready for switching. >>> And I don't really see any difference in the project site between the >>> "old" and "new" version, besides the underlining of links which is an >>> easy CSS fix (if wanted; I actually prefer the staged version). There >>> would be room for other CSS improvements but these apply to the >>> current https://openoffice.apache.org too. >> The underlining has changed with my latest css commit. I didn't find the >> time to explain it: >> >> Permanent underlining makes the links esp. on the download page >> unreadable. Underlining now appears only with "mouser-over". >> >> Links are all in blue, so I changed the Heading of the pages to a grey >> from our logo. This way it cannot be confused with a clickable link. >> >> If these changes are OK for everyone I would like to make them also to >> openoffice.org. > The css is here: > https://github.com/apache/openoffice-org/blob/main/assets/css/ooo.css I assume we now have *one* single css? Because on the "old" page there were used lots of them resulting in different layouts depending on the localized page. Regards, Matthias > > Regards, > Dave > >> Regards, >> >>Matthias >> >>> Regards, >>> Andrea. >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Apache OpenOffice Project Information
> On Nov 15, 2020, at 9:34 AM, Matthias Seidel > wrote: > > Hi Andrea, > > Am 15.11.20 um 18:25 schrieb Andrea Pescetti: >> Marcus ha scritto: >>> Am 15.11.20 um 16:07 schrieb Matthias Seidel: >>>> Am 15.11.20 um 15:54 schrieb Andrea Pescetti: >>>>> Matthias Seidel wrote: >>>>> >>>>> By the way: these were my first edits to the the project site after >>>>> the migration and everything was smooth, thanks a lot Dave! It really >>>>> looks good for production. >>>> >>>> Technically yes, but I recognized a slightly bigger vertical space >>>> between the topics on the main page and also the boxes on the download >>>> page. This may be a css issue. Nothing really big. >>> >>> right, but have a look also for the fonts and font sizes. Also here >>> are visible changes. >> >> Just to be clear: by "project site" I mean >> https://github.com/apache/openoffice-project not >> https://github.com/apache/openoffice-org which I haven't built yet. > Yes, you are right. The project information is located on the project > site. Sorry for the confusion. ;-) > IMO the project site is ready for switching. >> >> And I don't really see any difference in the project site between the >> "old" and "new" version, besides the underlining of links which is an >> easy CSS fix (if wanted; I actually prefer the staged version). There >> would be room for other CSS improvements but these apply to the >> current https://openoffice.apache.org too. > > The underlining has changed with my latest css commit. I didn't find the > time to explain it: > > Permanent underlining makes the links esp. on the download page > unreadable. Underlining now appears only with "mouser-over". > > Links are all in blue, so I changed the Heading of the pages to a grey > from our logo. This way it cannot be confused with a clickable link. > > If these changes are OK for everyone I would like to make them also to > openoffice.org. The css is here: https://github.com/apache/openoffice-org/blob/main/assets/css/ooo.css Regards, Dave > > Regards, > >Matthias > >> >> Regards, >> Andrea. >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Hi - > On Nov 15, 2020, at 9:31 AM, Dave Fisher wrote: > > > >> On Nov 15, 2020, at 8:17 AM, Marcus wrote: >> >> Am 15.11.20 um 16:07 schrieb Matthias Seidel: >>> Am 15.11.20 um 15:54 schrieb Andrea Pescetti: Matthias Seidel wrote: By the way: these were my first edits to the the project site after the migration and everything was smooth, thanks a lot Dave! It really looks good for production. >>> Technically yes, but I recognized a slightly bigger vertical space >>> between the topics on the main page and also the boxes on the download >>> page. This may be a css issue. Nothing really big. >> >> right, but have a look also for the fonts and font sizes. Also here are >> visible changes. >> >> But I also think that this is just CSS and nothing big. > > Strange because on macOS Safari and Chrome the two sites look identical. > Firefox does differ from Safari and Chrome, but the old and new are identical > to each other. > > So, we have a small CSS issue, but not a new CSS issue. > > Please report your Browsers and OSs ... Nevermind - we are not explicitly setting line-height and Firefox’s “normal” differs from the other browsers. Regards, Dave > > Regards, > Dave > >> >> Marcus >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Hi Andrea, Am 15.11.20 um 18:25 schrieb Andrea Pescetti: > Marcus ha scritto: >> Am 15.11.20 um 16:07 schrieb Matthias Seidel: >>> Am 15.11.20 um 15:54 schrieb Andrea Pescetti: >>>> Matthias Seidel wrote: >>>> >>>> By the way: these were my first edits to the the project site after >>>> the migration and everything was smooth, thanks a lot Dave! It really >>>> looks good for production. >>> >>> Technically yes, but I recognized a slightly bigger vertical space >>> between the topics on the main page and also the boxes on the download >>> page. This may be a css issue. Nothing really big. >> >> right, but have a look also for the fonts and font sizes. Also here >> are visible changes. > > Just to be clear: by "project site" I mean > https://github.com/apache/openoffice-project not > https://github.com/apache/openoffice-org which I haven't built yet. Yes, you are right. The project information is located on the project site. Sorry for the confusion. ;-) IMO the project site is ready for switching. > > And I don't really see any difference in the project site between the > "old" and "new" version, besides the underlining of links which is an > easy CSS fix (if wanted; I actually prefer the staged version). There > would be room for other CSS improvements but these apply to the > current https://openoffice.apache.org too. The underlining has changed with my latest css commit. I didn't find the time to explain it: Permanent underlining makes the links esp. on the download page unreadable. Underlining now appears only with "mouser-over". Links are all in blue, so I changed the Heading of the pages to a grey from our logo. This way it cannot be confused with a clickable link. If these changes are OK for everyone I would like to make them also to openoffice.org. Regards, Matthias > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Apache OpenOffice Project Information
> On Nov 15, 2020, at 9:25 AM, Andrea Pescetti wrote: > > Marcus ha scritto: >> Am 15.11.20 um 16:07 schrieb Matthias Seidel: >>> Am 15.11.20 um 15:54 schrieb Andrea Pescetti: Matthias Seidel wrote: By the way: these were my first edits to the the project site after the migration and everything was smooth, thanks a lot Dave! It really looks good for production. >>> >>> Technically yes, but I recognized a slightly bigger vertical space >>> between the topics on the main page and also the boxes on the download >>> page. This may be a css issue. Nothing really big. >> right, but have a look also for the fonts and font sizes. Also here are >> visible changes. > > Just to be clear: by "project site" I mean > https://github.com/apache/openoffice-project not > https://github.com/apache/openoffice-org which I haven't built yet. > > And I don't really see any difference in the project site between the "old" > and "new" version, besides the underlining of links which is an easy CSS fix > (if wanted; I actually prefer the staged version). That was a test change. I prefer that the links be underlined for accessibility reasons. Meaning color blind people might have trouble noticing these hyperlinks. > There would be room for other CSS improvements but these apply to the current > https://openoffice.apache.org too. Exactly. Regards, Dave > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
> On Nov 15, 2020, at 8:17 AM, Marcus wrote: > > Am 15.11.20 um 16:07 schrieb Matthias Seidel: >> Am 15.11.20 um 15:54 schrieb Andrea Pescetti: >>> Matthias Seidel wrote: >>> >>> By the way: these were my first edits to the the project site after >>> the migration and everything was smooth, thanks a lot Dave! It really >>> looks good for production. >> Technically yes, but I recognized a slightly bigger vertical space >> between the topics on the main page and also the boxes on the download >> page. This may be a css issue. Nothing really big. > > right, but have a look also for the fonts and font sizes. Also here are > visible changes. > > But I also think that this is just CSS and nothing big. Strange because on macOS Safari and Chrome the two sites look identical. Firefox does differ from Safari and Chrome, but the old and new are identical to each other. So, we have a small CSS issue, but not a new CSS issue. Please report your Browsers and OSs ... Regards, Dave > > Marcus > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Marcus ha scritto: Am 15.11.20 um 16:07 schrieb Matthias Seidel: Am 15.11.20 um 15:54 schrieb Andrea Pescetti: Matthias Seidel wrote: By the way: these were my first edits to the the project site after the migration and everything was smooth, thanks a lot Dave! It really looks good for production. Technically yes, but I recognized a slightly bigger vertical space between the topics on the main page and also the boxes on the download page. This may be a css issue. Nothing really big. right, but have a look also for the fonts and font sizes. Also here are visible changes. Just to be clear: by "project site" I mean https://github.com/apache/openoffice-project not https://github.com/apache/openoffice-org which I haven't built yet. And I don't really see any difference in the project site between the "old" and "new" version, besides the underlining of links which is an easy CSS fix (if wanted; I actually prefer the staged version). There would be room for other CSS improvements but these apply to the current https://openoffice.apache.org too. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Am 15.11.20 um 16:07 schrieb Matthias Seidel: Am 15.11.20 um 15:54 schrieb Andrea Pescetti: Matthias Seidel wrote: By the way: these were my first edits to the the project site after the migration and everything was smooth, thanks a lot Dave! It really looks good for production. Technically yes, but I recognized a slightly bigger vertical space between the topics on the main page and also the boxes on the download page. This may be a css issue. Nothing really big. right, but have a look also for the fonts and font sizes. Also here are visible changes. But I also think that this is just CSS and nothing big. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Hi Andrea, Am 15.11.20 um 15:54 schrieb Andrea Pescetti: > Matthias Seidel wrote: >>>> https://github.com/apache/openoffice-project/blob/main/content/doap_openoffice.rdf >>>> >>> I'll regenerate it from the standard template, just in case something >>> changed there too. >> Please update it in the new repository. > > Pushed. The template had indeed been updated (references to the Apache > License) and the content is also current now, including references to > the Git repository. Thanks, I already copied it to our project site and published it. However the cron job needs some time to pick up the new information: https://projects.apache.org/project.html?openoffice > > By the way: these were my first edits to the the project site after > the migration and everything was smooth, thanks a lot Dave! It really > looks good for production. Technically yes, but I recognized a slightly bigger vertical space between the topics on the main page and also the boxes on the download page. This may be a css issue. Nothing really big. Regards, Matthias > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Apache OpenOffice Project Information
Matthias Seidel wrote: https://github.com/apache/openoffice-project/blob/main/content/doap_openoffice.rdf I'll regenerate it from the standard template, just in case something changed there too. Please update it in the new repository. Pushed. The template had indeed been updated (references to the Apache License) and the content is also current now, including references to the Git repository. By the way: these were my first edits to the the project site after the migration and everything was smooth, thanks a lot Dave! It really looks good for production. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Hi Andrea, Am 14.11.20 um 23:04 schrieb Andrea Pescetti: > Dave Fisher wrote: >> The file in question is here: >> https://github.com/apache/openoffice-project/blob/main/content/doap_openoffice.rdf >> > > You can leave further updates to this file to me for this weekend. > I'll regenerate it from the standard template, just in case something > changed there too. > > I mean I'll update the copy in the new repository, not the online one: > if I got it correctly, we don't have a process for bringing all > updates from the old infrastructure (which is still writable, right?) > to the new one, so I will push to the new repositories only. Thanks for that! Please update it in the new repository. But I'd like to have that information updated asap, so I will probably copy it to online version in SVN then. Regards, Matthias > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Apache OpenOffice Project Information
Dave Fisher wrote: The file in question is here: https://github.com/apache/openoffice-project/blob/main/content/doap_openoffice.rdf You can leave further updates to this file to me for this weekend. I'll regenerate it from the standard template, just in case something changed there too. I mean I'll update the copy in the new repository, not the online one: if I got it correctly, we don't have a process for bringing all updates from the old infrastructure (which is still writable, right?) to the new one, so I will push to the new repositories only. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
The file in question is here: https://github.com/apache/openoffice-project/blob/main/content/doap_openoffice.rdf <https://github.com/apache/openoffice-project/blob/main/content/doap_openoffice.rdf> Compare it with this: https://projects.apache.org/project.html?openoffice <https://projects.apache.org/project.html?openoffice> If you update it the new git then that will go live once we make the switch. Regards, Dave > On Nov 14, 2020, at 10:57 AM, Matthias Seidel > wrote: > > Hi all, > > After the release of AOO 4.1.8 it is time to bump this topic up again. > > Our Project Information still lists SVN as Code Repository. We moved to > Git long ago. > People who look into SVN will get the impression that there is > absolutely no development going on... > > Is it possible to update the data now? > > Regards, > >Matthias > > Am 25.04.20 um 13:19 schrieb Matthias Seidel: >> Hi Andrea, >> >> Am 13.04.20 um 17:26 schrieb Andrea Pescetti: >>> On 12/04/2020 Matthias Seidel wrote: >>>> https://svn.apache.org/repos/asf/openoffice/site/trunk/content/doap_openoffice.rdf >>>> >>>> I would like to have it updated, esp. for the repository change from >>>> Subversion to Git. >>>> >>>> There is a tool for creating such a file: >>>> https://projects.apache.org/create.html >>> The tool is for initial creation as it says in the first lines; but it >>> doesn't harm to re-run it from scratch and ensure differences in the >>> generated XML are as expected. >>> >>>> @Andrea: You are listed as project data maintainer, is this still >>>> current? >>> I can update it, sure. If I recall correctly, this used to be done at >>> every release before we had a different way to track releases, so it's >>> been a while since the last update. >>> >>> The updates I see now, as discussed, are: >>> >>> 1. Source from Git >>> >>> 2. ISO for ODF 1.2 (ISO/IEC 26300:2015) >>> >>> Anything else? Or I will just regenerate, check the diffs with respect >>> to the current one, and commit. Of course, we can accommodate other >>> suggestions at any time, generating/editing the file is quick. >> Any news on this one? >> >> Regards, >> >>Matthias >> >>> Regards, >>> Andrea. >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >>> >
Re: Apache OpenOffice Project Information
Hi all, After the release of AOO 4.1.8 it is time to bump this topic up again. Our Project Information still lists SVN as Code Repository. We moved to Git long ago. People who look into SVN will get the impression that there is absolutely no development going on... Is it possible to update the data now? Regards, Matthias Am 25.04.20 um 13:19 schrieb Matthias Seidel: > Hi Andrea, > > Am 13.04.20 um 17:26 schrieb Andrea Pescetti: >> On 12/04/2020 Matthias Seidel wrote: >>> https://svn.apache.org/repos/asf/openoffice/site/trunk/content/doap_openoffice.rdf >>> >>> I would like to have it updated, esp. for the repository change from >>> Subversion to Git. >>> >>> There is a tool for creating such a file: >>> https://projects.apache.org/create.html >> The tool is for initial creation as it says in the first lines; but it >> doesn't harm to re-run it from scratch and ensure differences in the >> generated XML are as expected. >> >>> @Andrea: You are listed as project data maintainer, is this still >>> current? >> I can update it, sure. If I recall correctly, this used to be done at >> every release before we had a different way to track releases, so it's >> been a while since the last update. >> >> The updates I see now, as discussed, are: >> >> 1. Source from Git >> >> 2. ISO for ODF 1.2 (ISO/IEC 26300:2015) >> >> Anything else? Or I will just regenerate, check the diffs with respect >> to the current one, and commit. Of course, we can accommodate other >> suggestions at any time, generating/editing the file is quick. > Any news on this one? > > Regards, > > Matthias > >> Regards, >> Andrea. >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> smime.p7s Description: S/MIME Cryptographic Signature
Re: New Mirror Information (London, UK)
Don’t trust it. We know nothing about it. No one we know requested it. > On Jul 10, 2020, at 12:23 PM, Martin Groenescheij > wrote: > > Strange to receive this important information from someone who isn't > subscribed to the list. > Sounds like a Phishing email > > Should such information not come from Apache OpenOffice. > How can I trust this? > > On 09/07/2020 11:24, Get Hosted Online - Accounts, Billing and Technical > Support wrote: >> Hi >> >> This is to notify you of our intention to mirror your infrastructure as part >> of our commitment to open-source software. >> >> Points of access can be found below: >> HTTP: http://mirrors.gethosted.online/openoffice >> HTTPS: https://mirrors.gethosted.online/openoffice >> FTP: ftp://mirrors.gethosted.online/openoffice >> RSYNC: rsync://mirrors.gethosted.online/openoffice >> >> Please update your website and/or infrastructure accordingly. >> >> I trust this is satisfactory. >> >> Kind regards >> >> >> Get Hosted Online >> Telephone: +44 (0)1200 422533 >> Email: sales@gethosted.online >> Web: https://www.gethosted.online >> >> >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org > For additional commands, e-mail: users-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Hi Andrea, Am 13.04.20 um 17:26 schrieb Andrea Pescetti: > On 12/04/2020 Matthias Seidel wrote: >> https://svn.apache.org/repos/asf/openoffice/site/trunk/content/doap_openoffice.rdf >> >> I would like to have it updated, esp. for the repository change from >> Subversion to Git. >> >> There is a tool for creating such a file: >> https://projects.apache.org/create.html > > The tool is for initial creation as it says in the first lines; but it > doesn't harm to re-run it from scratch and ensure differences in the > generated XML are as expected. > >> @Andrea: You are listed as project data maintainer, is this still >> current? > > I can update it, sure. If I recall correctly, this used to be done at > every release before we had a different way to track releases, so it's > been a while since the last update. > > The updates I see now, as discussed, are: > > 1. Source from Git > > 2. ISO for ODF 1.2 (ISO/IEC 26300:2015) > > Anything else? Or I will just regenerate, check the diffs with respect > to the current one, and commit. Of course, we can accommodate other > suggestions at any time, generating/editing the file is quick. Any news on this one? Regards, Matthias > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > smime.p7s Description: S/MIME Cryptographic Signature
Re: Apache OpenOffice Project Information
Hi Andrea, Am 13.04.20 um 17:26 schrieb Andrea Pescetti: > On 12/04/2020 Matthias Seidel wrote: >> https://svn.apache.org/repos/asf/openoffice/site/trunk/content/doap_openoffice.rdf >> >> I would like to have it updated, esp. for the repository change from >> Subversion to Git. >> >> There is a tool for creating such a file: >> https://projects.apache.org/create.html > > The tool is for initial creation as it says in the first lines; but it > doesn't harm to re-run it from scratch and ensure differences in the > generated XML are as expected. > >> @Andrea: You are listed as project data maintainer, is this still >> current? > > I can update it, sure. If I recall correctly, this used to be done at > every release before we had a different way to track releases, so it's > been a while since the last update. Thanks! We still update it for every release [1] and I did manually change some links a while ago. But it was never really "overhauled". Regards, Matthias [1] https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release#HowtoCookaRelease-Apache'sprojectdata(DOAPRDFdata) > > The updates I see now, as discussed, are: > > 1. Source from Git > > 2. ISO for ODF 1.2 (ISO/IEC 26300:2015) > > Anything else? Or I will just regenerate, check the diffs with respect > to the current one, and commit. Of course, we can accommodate other > suggestions at any time, generating/editing the file is quick. > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Apache OpenOffice Project Information
On 12/04/2020 Matthias Seidel wrote: https://svn.apache.org/repos/asf/openoffice/site/trunk/content/doap_openoffice.rdf I would like to have it updated, esp. for the repository change from Subversion to Git. There is a tool for creating such a file: https://projects.apache.org/create.html The tool is for initial creation as it says in the first lines; but it doesn't harm to re-run it from scratch and ensure differences in the generated XML are as expected. @Andrea: You are listed as project data maintainer, is this still current? I can update it, sure. If I recall correctly, this used to be done at every release before we had a different way to track releases, so it's been a while since the last update. The updates I see now, as discussed, are: 1. Source from Git 2. ISO for ODF 1.2 (ISO/IEC 26300:2015) Anything else? Or I will just regenerate, check the diffs with respect to the current one, and commit. Of course, we can accommodate other suggestions at any time, generating/editing the file is quick. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: Apache OpenOffice Project Information
> -Original Message- > From: Marcus [mailto:marcus.m...@wtnet.de] > Sent: Monday, April 13, 2020 11:21 AM > To: dev@openoffice.apache.org > Subject: Re: Apache OpenOffice Project Information > >> In order to have some more context an addition like > "Apache OpenOffice > >> supports Open Document Format for Office Applications > (OpenDocument) > >> version 1.2 - ISO/IEC 26300-1:2015" or similar would be > interesting. ;-) > > > > That is already listed under "Implemented standards" for > ages. I don't > > think it belongs in a *description*. > > ah, I've overlooked the last entry in the XML file. However, "ISO/IEC > 26300-1:2006" means ODF v1.0. IMHO it's better to mention "ISO/IEC > 26300:2015" for ODF v1.2 like: +1 Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: Apache OpenOffice Project Information
> -Original Message- > From: Matthias Seidel [mailto:matthias.sei...@hamburg.de] > Sent: Monday, April 13, 2020 10:26 AM > To: dev@openoffice.apache.org > Subject: Re: Apache OpenOffice Project Information > > Hi Marcus, > > Am 13.04.20 um 09:53 schrieb Marcus: > > Am 13.04.20 um 09:31 schrieb Jörg Schmidt: > >>> -Original Message- > >>> From: Matthias Seidel [mailto:matthias.sei...@hamburg.de] > >>> Sent: Sunday, April 12, 2020 8:38 PM > >>> To: dev@openoffice.apache.org > >>> Subject: Apache OpenOffice Project Information > >>> > >>> Like every ASF projects we do have Project Informations: > >>> > >>> https://projects.apache.org/project.html?openoffice > >>> > >>> The data is taken from this file: > >>> > >>> https://svn.apache.org/repos/asf/openoffice/site/trunk/content > >>> /doap_openoffice.rdf > >>> > >>> I would like to have it updated, esp. for the repository > change from > >>> Subversion to Git. > >>> > >>> There is a tool for creating such a file: > >>> > >>> https://projects.apache.org/create.html > >>> > >>> Any Opinions? > >> > >> It would be good if it could be added that AOO also implements . > > > > sure. > > > > In order to have some more context an addition like "Apache > OpenOffice > > supports Open Document Format for Office Applications (OpenDocument) > > version 1.2 - ISO/IEC 26300-1:2015" or similar would be > interesting. ;-) > > That is already listed under "Implemented standards" for ages. I don't > think it belongs in a *description*. What exactly do you mean? Is Marcus' description too long? This may be possible, only for a short description the ISO standard and not the OASIS standard would be the more important information and therefore I would write in https://projects.apache.org/project.html?openoffice: Implemented standards: *ISO/IEC 26300-1:2015 or: Implemented standards: *ISO/IEC 26300-1:2015 *OASIS 26300:2006: OpenDocument Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Am 13.04.20 um 10:25 schrieb Matthias Seidel: Am 13.04.20 um 09:53 schrieb Marcus: Am 13.04.20 um 09:31 schrieb Jörg Schmidt: -Original Message- From: Matthias Seidel [mailto:matthias.sei...@hamburg.de] Sent: Sunday, April 12, 2020 8:38 PM To: dev@openoffice.apache.org Subject: Apache OpenOffice Project Information Like every ASF projects we do have Project Informations: https://projects.apache.org/project.html?openoffice The data is taken from this file: https://svn.apache.org/repos/asf/openoffice/site/trunk/content /doap_openoffice.rdf I would like to have it updated, esp. for the repository change from Subversion to Git. There is a tool for creating such a file: https://projects.apache.org/create.html Any Opinions? It would be good if it could be added that AOO also implements . sure. In order to have some more context an addition like "Apache OpenOffice supports Open Document Format for Office Applications (OpenDocument) version 1.2 - ISO/IEC 26300-1:2015" or similar would be interesting. ;-) That is already listed under "Implemented standards" for ages. I don't think it belongs in a *description*. ah, I've overlooked the last entry in the XML file. However, "ISO/IEC 26300-1:2006" means ODF v1.0. IMHO it's better to mention "ISO/IEC 26300:2015" for ODF v1.2 like: Title OpenDocument Format BodyOASIS ID 26300:2015 URL https://www.iso.org/standard/66363.html Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Am 13.04.20 um 10:27 schrieb Matthias Seidel: Am 13.04.20 um 10:12 schrieb Marcus: Am 12.04.20 um 23:59 schrieb Matthias Seidel: Am 12.04.20 um 23:49 schrieb Marcus: Am 12.04.20 um 22:13 schrieb Peter Kovacs: yea, the subversion should be changed. Maybe the summary could be checked, if we can use the project summary we give in the reports. this was also my idea. ;-) @Matthias: But why creating a new file? The existing one can be updated. The output would be the same? It is easier to create a new one than to "hack" the old one... OK, if it's easier for you than do it. Of course it is easier, but to be clear: I will not do it. ;-) sure, it's your decision. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Hi Marcus, Am 13.04.20 um 10:12 schrieb Marcus: > Am 12.04.20 um 23:59 schrieb Matthias Seidel: >> Am 12.04.20 um 23:49 schrieb Marcus: >>> Am 12.04.20 um 22:13 schrieb Peter Kovacs: yea, the subversion should be changed. Maybe the summary could be checked, if we can use the project summary we give in the reports. >>> >>> this was also my idea. ;-) >>> >>> @Matthias: >>> But why creating a new file? The existing one can be updated. >> >> The output would be the same? >> >> It is easier to create a new one than to "hack" the old one... > > OK, if it's easier for you than do it. Of course it is easier, but to be clear: I will not do it. ;-) Matthias > I just thought that exchanging 2 things is not that complex. However, > when I now look at the creating webpage [1] I think double-checking > the existing content is a good idea. ;-) > > Some suggestions: > > Category: > Content > Like it is today, all other doesn't make sense IMHO. > > License: > Need to be new as the current link is broken: > http://www.apache.org/licenses/LICENSE-2.0.html > > Short description: > Apache OpenOffice is an open-source, office-document productivity suite. > > Long description: > Apache OpenOffice is an open-source office-document productivity > suite. There are six productivity applications based around the > OpenDocument Format (ODF) that are Writer, Calc, Impress, Draw, Math, > Base. With limited support for many other file formats, OpenOffice > ships for Windows, macOS, Linux 64-bit (DEB + RPM), Linux 32-bit (DEB > + RPM) and in 41 languages. OpenOffice supports the Open Document > Format for Office Applications (ODF) version 1.2 - ISO/IEC 26300-1:2015. > > The remaining stuff can be left as it is today. > > You can verify the changes or new file with this tool [2]. > > [1] https://projects.apache.org/create.html > [2] https://www.w3.org/RDF/Validator/ > > HTH > > Marcus > > > Am 12.04.20 um 20:37 schrieb Matthias Seidel: > Like every ASF projects we do have Project Informations: > > https://projects.apache.org/project.html?openoffice > > The data is taken from this file: > > https://svn.apache.org/repos/asf/openoffice/site/trunk/content/doap_openoffice.rdf > > > > I would like to have it updated, esp. for the repository change from > Subversion to Git. > > There is a tool for creating such a file: > > https://projects.apache.org/create.html > > Any Opinions? Volunteers? ;-) > > @Andrea: You are listed as project data maintainer, is this still > current? > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Apache OpenOffice Project Information
Hi Marcus, Am 13.04.20 um 09:53 schrieb Marcus: > Am 13.04.20 um 09:31 schrieb Jörg Schmidt: >>> -Original Message- >>> From: Matthias Seidel [mailto:matthias.sei...@hamburg.de] >>> Sent: Sunday, April 12, 2020 8:38 PM >>> To: dev@openoffice.apache.org >>> Subject: Apache OpenOffice Project Information >>> >>> Like every ASF projects we do have Project Informations: >>> >>> https://projects.apache.org/project.html?openoffice >>> >>> The data is taken from this file: >>> >>> https://svn.apache.org/repos/asf/openoffice/site/trunk/content >>> /doap_openoffice.rdf >>> >>> I would like to have it updated, esp. for the repository change from >>> Subversion to Git. >>> >>> There is a tool for creating such a file: >>> >>> https://projects.apache.org/create.html >>> >>> Any Opinions? >> >> It would be good if it could be added that AOO also implements . > > sure. > > In order to have some more context an addition like "Apache OpenOffice > supports Open Document Format for Office Applications (OpenDocument) > version 1.2 - ISO/IEC 26300-1:2015" or similar would be interesting. ;-) That is already listed under "Implemented standards" for ages. I don't think it belongs in a *description*. Matthias > > Marcus > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Apache OpenOffice Project Information
Am 12.04.20 um 23:59 schrieb Matthias Seidel: Am 12.04.20 um 23:49 schrieb Marcus: Am 12.04.20 um 22:13 schrieb Peter Kovacs: yea, the subversion should be changed. Maybe the summary could be checked, if we can use the project summary we give in the reports. this was also my idea. ;-) @Matthias: But why creating a new file? The existing one can be updated. The output would be the same? It is easier to create a new one than to "hack" the old one... OK, if it's easier for you than do it. I just thought that exchanging 2 things is not that complex. However, when I now look at the creating webpage [1] I think double-checking the existing content is a good idea. ;-) Some suggestions: Category: Content Like it is today, all other doesn't make sense IMHO. License: Need to be new as the current link is broken: http://www.apache.org/licenses/LICENSE-2.0.html Short description: Apache OpenOffice is an open-source, office-document productivity suite. Long description: Apache OpenOffice is an open-source office-document productivity suite. There are six productivity applications based around the OpenDocument Format (ODF) that are Writer, Calc, Impress, Draw, Math, Base. With limited support for many other file formats, OpenOffice ships for Windows, macOS, Linux 64-bit (DEB + RPM), Linux 32-bit (DEB + RPM) and in 41 languages. OpenOffice supports the Open Document Format for Office Applications (ODF) version 1.2 - ISO/IEC 26300-1:2015. The remaining stuff can be left as it is today. You can verify the changes or new file with this tool [2]. [1] https://projects.apache.org/create.html [2] https://www.w3.org/RDF/Validator/ HTH Marcus Am 12.04.20 um 20:37 schrieb Matthias Seidel: Like every ASF projects we do have Project Informations: https://projects.apache.org/project.html?openoffice The data is taken from this file: https://svn.apache.org/repos/asf/openoffice/site/trunk/content/doap_openoffice.rdf I would like to have it updated, esp. for the repository change from Subversion to Git. There is a tool for creating such a file: https://projects.apache.org/create.html Any Opinions? Volunteers? ;-) @Andrea: You are listed as project data maintainer, is this still current? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Am 13.04.20 um 09:31 schrieb Jörg Schmidt: -Original Message- From: Matthias Seidel [mailto:matthias.sei...@hamburg.de] Sent: Sunday, April 12, 2020 8:38 PM To: dev@openoffice.apache.org Subject: Apache OpenOffice Project Information Like every ASF projects we do have Project Informations: https://projects.apache.org/project.html?openoffice The data is taken from this file: https://svn.apache.org/repos/asf/openoffice/site/trunk/content /doap_openoffice.rdf I would like to have it updated, esp. for the repository change from Subversion to Git. There is a tool for creating such a file: https://projects.apache.org/create.html Any Opinions? It would be good if it could be added that AOO also implements . sure. In order to have some more context an addition like "Apache OpenOffice supports Open Document Format for Office Applications (OpenDocument) version 1.2 - ISO/IEC 26300-1:2015" or similar would be interesting. ;-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: Apache OpenOffice Project Information
> -Original Message- > From: Matthias Seidel [mailto:matthias.sei...@hamburg.de] > Sent: Sunday, April 12, 2020 8:38 PM > To: dev@openoffice.apache.org > Subject: Apache OpenOffice Project Information > > Hi all, > > Like every ASF projects we do have Project Informations: > > https://projects.apache.org/project.html?openoffice > > The data is taken from this file: > > https://svn.apache.org/repos/asf/openoffice/site/trunk/content > /doap_openoffice.rdf > > I would like to have it updated, esp. for the repository change from > Subversion to Git. > > There is a tool for creating such a file: > > https://projects.apache.org/create.html > > Any Opinions? It would be good if it could be added that AOO also implements ISO/IEC 26300-1:2015. greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
Hi Marcus, Am 12.04.20 um 23:49 schrieb Marcus: > Am 12.04.20 um 22:13 schrieb Peter Kovacs: >> yea, the subversion should be changed. Maybe the summary could be >> checked, if we can use the project summary we give in the reports. > > this was also my idea. ;-) > > @Matthias: > But why creating a new file? The existing one can be updated. The output would be the same? It is easier to create a new one than to "hack" the old one... Matthias > > Marcus > > > >> Am 12.04.20 um 20:37 schrieb Matthias Seidel: >>> Like every ASF projects we do have Project Informations: >>> >>> https://projects.apache.org/project.html?openoffice >>> >>> The data is taken from this file: >>> >>> https://svn.apache.org/repos/asf/openoffice/site/trunk/content/doap_openoffice.rdf >>> >>> >>> I would like to have it updated, esp. for the repository change from >>> Subversion to Git. >>> >>> There is a tool for creating such a file: >>> >>> https://projects.apache.org/create.html >>> >>> Any Opinions? Volunteers? ;-) >>> >>> @Andrea: You are listed as project data maintainer, is this still >>> current? > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Apache OpenOffice Project Information
Am 12.04.20 um 22:13 schrieb Peter Kovacs: yea, the subversion should be changed. Maybe the summary could be checked, if we can use the project summary we give in the reports. this was also my idea. ;-) @Matthias: But why creating a new file? The existing one can be updated. Marcus Am 12.04.20 um 20:37 schrieb Matthias Seidel: Like every ASF projects we do have Project Informations: https://projects.apache.org/project.html?openoffice The data is taken from this file: https://svn.apache.org/repos/asf/openoffice/site/trunk/content/doap_openoffice.rdf I would like to have it updated, esp. for the repository change from Subversion to Git. There is a tool for creating such a file: https://projects.apache.org/create.html Any Opinions? Volunteers? ;-) @Andrea: You are listed as project data maintainer, is this still current? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Apache OpenOffice Project Information
yea, the subversion should be changed. Maybe the summary could be checked, if we can use the project summary we give in the reports. I am not volunteering. I am already on to many topics. Am 12.04.20 um 20:37 schrieb Matthias Seidel: Hi all, Like every ASF projects we do have Project Informations: https://projects.apache.org/project.html?openoffice The data is taken from this file: https://svn.apache.org/repos/asf/openoffice/site/trunk/content/doap_openoffice.rdf I would like to have it updated, esp. for the repository change from Subversion to Git. There is a tool for creating such a file: https://projects.apache.org/create.html Any Opinions? Volunteers? ;-) @Andrea: You are listed as project data maintainer, is this still current? Regards, Matthias - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Apache OpenOffice Project Information
Hi all, Like every ASF projects we do have Project Informations: https://projects.apache.org/project.html?openoffice The data is taken from this file: https://svn.apache.org/repos/asf/openoffice/site/trunk/content/doap_openoffice.rdf I would like to have it updated, esp. for the repository change from Subversion to Git. There is a tool for creating such a file: https://projects.apache.org/create.html Any Opinions? Volunteers? ;-) @Andrea: You are listed as project data maintainer, is this still current? Regards, Matthias smime.p7s Description: S/MIME Cryptographic Signature
Security bulletin information update.
Hello. Usually the information about fixed security vulnerabilities was published on https://www.openoffice.org/security/bulletin.html in few weeks after AOO new release. Or there just was mentioned that no fixes were made this time. Is it time to make this info pulic and update the information about fixed CVE in Apache OpenOffice 4.1.7? -- Sergey Torokhov - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OpenOffice 4.1.6 fixed security vulnerabilities information
Does anybody know what vulnerabilities were fixed in OpenOffice 4.1.6? When the appropriate information will be published? -- Sergey 29.12.2018, 03:08, "Torokhov Sergey" : > Hello. > > The page https://www.openoffice.org/security/bulletin.html states that > >> OpenOffice 4.1.6 fixes security vulnerabilities. As usual, details about >> fixed vulnerabilities will be made public a few weeks after release. > > Is it time to make this info public? > > Could anybody publish the information about fixed CVE? > > I'm interesting because in Gentoo the security team initially looked up the > OpenOffice before update the package in portage tree. > > -- > > Sergey > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
OpenOffice 4.1.6 fixed security vulnerabilities information
Hello. The page https://www.openoffice.org/security/bulletin.html states that > OpenOffice 4.1.6 fixes security vulnerabilities. As usual, details about > fixed vulnerabilities will be made public a few weeks after release. Is it time to make this info public? Could anybody publish the information about fixed CVE? I'm interesting because in Gentoo the security team initially looked up the OpenOffice before update the package in portage tree. -- Sergey - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Information about used MS Visual Studio versions?
Yes. On the 4.1.x series we are on Java 1.8. the 4.2.0 Series will support 1.9. Java is optional, but you would loose features. We also have some code that is written in Python I think. I think we use perl only in the build environment but I am not sure of this. On 9/14/18 11:30 PM, Howard Cary Morris wrote: Thought I saw in another email that JAVA was sometimes used. True? Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Matthias Seidel<mailto:matthias.sei...@hamburg.de> Sent: Friday, September 14, 2018 11:36 AM To: dev@openoffice.apache.org<mailto:dev@openoffice.apache.org> Subject: Re: Information about used MS Visual Studio versions? Hi Jörg, I can only speak for version 4.1.4 and 4.1.5, but those were built with MS Visual C++ Compilers 2008 Standard Edition: https://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.1.4/wntmsci/ReadMe.txt https://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.1.5/wntmsci/ReadMe.txt No changes for AOO 4.1.6 planned. Regards, Matthias Am 14.09.2018 um 09:33 schrieb Jörg Schmidt: Hello, Where can I get the information which (old) OOo/AOO versions were compiled against which concrete version of MS Visual Studio? The reason of my question is the current problems with Windows 10 and KB4343909, for example reported in: https://forum.openoffice.org/en/forum/viewtopic.php?f=15&t=94690 I hope to be able to select a suitable version of OpenOffice Portable that is immune to problems with KB4343909 by knowing version information (about the MS Visual Studio Version). greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: Information about used MS Visual Studio versions?
Thought I saw in another email that JAVA was sometimes used. True? Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Matthias Seidel<mailto:matthias.sei...@hamburg.de> Sent: Friday, September 14, 2018 11:36 AM To: dev@openoffice.apache.org<mailto:dev@openoffice.apache.org> Subject: Re: Information about used MS Visual Studio versions? Hi Jörg, I can only speak for version 4.1.4 and 4.1.5, but those were built with MS Visual C++ Compilers 2008 Standard Edition: https://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.1.4/wntmsci/ReadMe.txt https://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.1.5/wntmsci/ReadMe.txt No changes for AOO 4.1.6 planned. Regards, Matthias Am 14.09.2018 um 09:33 schrieb Jörg Schmidt: > Hello, > > Where can I get the information which (old) OOo/AOO versions were compiled > against which concrete version of MS Visual Studio? > > The reason of my question is the current problems with Windows 10 and > KB4343909, for example reported in: > https://forum.openoffice.org/en/forum/viewtopic.php?f=15&t=94690 > I hope to be able to select a suitable version of OpenOffice Portable that is > immune to problems with KB4343909 by knowing version information (about the > MS Visual Studio Version). > > > greetings, > Jörg > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org >
Re: Information about used MS Visual Studio versions?
Hi Jörg, I can only speak for version 4.1.4 and 4.1.5, but those were built with MS Visual C++ Compilers 2008 Standard Edition: https://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.1.4/wntmsci/ReadMe.txt https://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.1.5/wntmsci/ReadMe.txt No changes for AOO 4.1.6 planned. Regards, Matthias Am 14.09.2018 um 09:33 schrieb Jörg Schmidt: > Hello, > > Where can I get the information which (old) OOo/AOO versions were compiled > against which concrete version of MS Visual Studio? > > The reason of my question is the current problems with Windows 10 and > KB4343909, for example reported in: > https://forum.openoffice.org/en/forum/viewtopic.php?f=15&t=94690 > I hope to be able to select a suitable version of OpenOffice Portable that is > immune to problems with KB4343909 by knowing version information (about the > MS Visual Studio Version). > > > greetings, > Jörg > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Information about used MS Visual Studio versions?
Hi, We use Microsoft's Visual C++ 2008 SP1 for building current builds. Damjan has put some work in 4.2.0 so we can build with a newer Version ( I think it was 2015, but I am unsure) I think. There is a mail in archive. I think your Idea is best tested with 4.2.0. We could then think if backport to 4.1.6 is an option. The current requirements you find on https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_Windows Am 14. September 2018 09:33:35 MESZ schrieb "Jörg Schmidt" : >Hello, > >Where can I get the information which (old) OOo/AOO versions were >compiled against which concrete version of MS Visual Studio? > >The reason of my question is the current problems with Windows 10 and >KB4343909, for example reported in: >https://forum.openoffice.org/en/forum/viewtopic.php?f=15&t=94690 >I hope to be able to select a suitable version of OpenOffice Portable >that is immune to problems with KB4343909 by knowing version >information (about the MS Visual Studio Version). > > >greetings, >Jörg > > > >- >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Information about used MS Visual Studio versions?
Hello, Where can I get the information which (old) OOo/AOO versions were compiled against which concrete version of MS Visual Studio? The reason of my question is the current problems with Windows 10 and KB4343909, for example reported in: https://forum.openoffice.org/en/forum/viewtopic.php?f=15&t=94690 I hope to be able to select a suitable version of OpenOffice Portable that is immune to problems with KB4343909 by knowing version information (about the MS Visual Studio Version). greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Extention License information on the webinterface
On 4/27/18 12:49 PM, Dave Fisher wrote: > Hi - > >> On Apr 27, 2018, at 9:37 AM, Marcus wrote: >> >> Am 26.04.2018 um 07:45 schrieb Peter Kovacs: >>> I wonder if we could fuel the Extention information presented on the >>> website from the Information provided in the Extention itself. >>> In addition we store only rateings from users to the extention. >>> Is this a possible vision? >>> Where are the cave eats for this? >> >> at the moment I've no idea what you mean. Can you give an example *what* you >> would like to see ans *where*? Maybe it's then easier to imagine. ;-) > > AFAIK - the templates and extensions systems and data are managed by > SourceForge and they are Drupal based. > The extensions.openoffice.org and templates.openoffice.org sites are hosted on SourceForge infrastructure but not managed or developed by SourceForge. Some years ago there was a Drupal contractor that helped develop those sites, but that is no longer the case. Like all of SourceForge's project web hosting, it is general purpose hosting and the project (Apache OpenOffice) has full access and control and responsibility for the code and data; SourceForge just provides the infrastructure. SourceForge has done minor Drupal upgrades to ensure the sites stay secure, and can offer a helping hand to diagnose issues, etc from time to time. We also have Drupal admin login credentials for historical reasons, but would be happy to hand that over to OpenOffice members at any time. And any OpenOffice developer that wants to work on the sites to enhance them could do so. -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <>< signature.asc Description: OpenPGP digital signature
Re: Extention License information on the webinterface
On 04/27/2018 07:27 PM, Andrea Pescetti wrote: > But showing the license info would be useful and probably feasible. An issue I've run into, for both the LibO extension and template repositories, is that the license on the description page, and the license in the template/extension are completely different. (In one instance, the description page claimed GPL 3.0, but the license within the extension was _your rights removed_.) In other instances, the description page implies, if not outright claims it is gratis, but the extension/template itself lays out a fee schedule, with no classes being gratis. Licensing information, and cost would be useful additions, provided they are accurate. (I don't expect an extension whose price is demarcated in Euro's to have a dollar equivalent, or vice-versus.) On second thoughts, listing the cost would have to be run past Apache Legal, to ensure GDPR compliance, among other things. jonathon - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Extention License information on the webinterface
Peter Kovacs wrote:> Currently you have to download the extention in order to see the license. With OO 3.3 I have seen that you have to add the license in the extention description. You have to distinguish between an extension and a release. The same extension can have different releases with different licenses (like, some extensions released as "GPLv2 or later" became "GPLv3 or later" once GPLv3 was published). Example of an extension page (the Italian dictionary I maintain): https://extensions.openoffice.org/en/project/italian-dictionary-thesaurus-hyphenation-patterns (note: there seems to be a bug; the page used to contain download statistics but they are not shown now; this is possibly due to the new SourceForge counters) Example of a release page (here is where license info would go): https://extensions.openoffice.org/en/projectrelease/italian-dictionary-thesaurus-hyphenation-patterns-20160210 I wonder if we can read the extention description and use that for the extention page. It could help to clarify the user before downloading which condition he is expecting to agree to. Plus we could maybe add search functionality based on license information. It looks like you've never created or uploaded an OXT file: you may want to create one if you want to play with these concepts. The site does the processing, but indeed the license is not shown. And it wouldn't be useful for indexing as it is free text or link (if I remember correctly). So you can write "GPL3", "GPL 3", "GPLv3", "GPL version 3" or any link to the GPLv3 and it would be classified differently. But showing the license info would be useful and probably feasible. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Extention License information on the webinterface
Uups wrong topic. Currently you have to download the extention in order to see the license. With OO 3.3 I have seen that you have to add the license in the extention description. I wonder if we can read the extention description and use that for the extention page. It could help to clarify the user before downloading which condition he is expecting to agree to. Plus we could maybe add search functionality based on license information. If you think the step further we could use all the information stored in an extention to explain what the extention is about. Am 27. April 2018 19:41:54 MESZ schrieb Peter kovacs : >The basic Idea is to offer an extention multimedia functionality based >on Gstreamer 0.1.0 API and one extention on 1.0.0 API. > >The core OpenOffice would not ship the multimedia functionality by >default anymore. (As compiled without the gstreamer Flag) The user has >to install the extention. > >Depending on design of the extention itself maybe additional steps are >required like the install of gstreamer itself. On the other hand we >could also package gstreamer with the extention. >Maybe depending on OS we could provide different strategies. > > >Am 27. April 2018 18:37:51 MESZ schrieb Marcus : >>Am 26.04.2018 um 07:45 schrieb Peter Kovacs: >>> I wonder if we could fuel the Extention information presented on the > >>> website from the Information provided in the Extention itself. >>> In addition we store only rateings from users to the extention. >>> >>> Is this a possible vision? >>> Where are the cave eats for this? >> >>at the moment I've no idea what you mean. Can you give an example >>*what* >>you would like to see ans *where*? Maybe it's then easier to imagine. >>;-) >> >>Thanks >> >>Marcus >> >> >>- >>To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>For additional commands, e-mail: dev-h...@openoffice.apache.org > >- >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Extention License information on the webinterface
The basic Idea is to offer an extention multimedia functionality based on Gstreamer 0.1.0 API and one extention on 1.0.0 API. The core OpenOffice would not ship the multimedia functionality by default anymore. (As compiled without the gstreamer Flag) The user has to install the extention. Depending on design of the extention itself maybe additional steps are required like the install of gstreamer itself. On the other hand we could also package gstreamer with the extention. Maybe depending on OS we could provide different strategies. Am 27. April 2018 18:37:51 MESZ schrieb Marcus : >Am 26.04.2018 um 07:45 schrieb Peter Kovacs: >> I wonder if we could fuel the Extention information presented on the >> website from the Information provided in the Extention itself. >> In addition we store only rateings from users to the extention. >> >> Is this a possible vision? >> Where are the cave eats for this? > >at the moment I've no idea what you mean. Can you give an example >*what* >you would like to see ans *where*? Maybe it's then easier to imagine. >;-) > >Thanks > >Marcus > > >- >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Extention License information on the webinterface
Hi - > On Apr 27, 2018, at 9:37 AM, Marcus wrote: > > Am 26.04.2018 um 07:45 schrieb Peter Kovacs: >> I wonder if we could fuel the Extention information presented on the website >> from the Information provided in the Extention itself. >> In addition we store only rateings from users to the extention. >> Is this a possible vision? >> Where are the cave eats for this? > > at the moment I've no idea what you mean. Can you give an example *what* you > would like to see ans *where*? Maybe it's then easier to imagine. ;-) AFAIK - the templates and extensions systems and data are managed by SourceForge and they are Drupal based. Regards, Dave > > Thanks > > Marcus > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > signature.asc Description: Message signed with OpenPGP
Re: Extention License information on the webinterface
Am 26.04.2018 um 07:45 schrieb Peter Kovacs: I wonder if we could fuel the Extention information presented on the website from the Information provided in the Extention itself. In addition we store only rateings from users to the extention. Is this a possible vision? Where are the cave eats for this? at the moment I've no idea what you mean. Can you give an example *what* you would like to see ans *where*? Maybe it's then easier to imagine. ;-) Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Extention License information on the webinterface
Hi all, I wonder if we could fuel the Extention information presented on the website from the Information provided in the Extention itself. In addition we store only rateings from users to the extention. Is this a possible vision? Where are the cave eats for this? Thanks. All the best Peter - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Bugzilla information
I disagree. You have to make your point. Not to object will only strengthen other position because your view remains unheard. The best weapon against haters is love and dignity. Am 22. Mai 2017 18:32:39 MESZ schrieb esh1907 : >The way to treat such people: >1. Change our software license so any code sharing between us and them >becomes impossible. >2. Arrange legally for the brand name they so desire to be forever >unavailable even if our project will be terminated in the future. >3. Ignore them. > >On Sun, May 21, 2017 at 7:52 PM, Matthias Seidel >> wrote: > >> I sometimes wonder if these people monitoring our mailing list don't >> have a real life... >> >> I know such zealots for almost 30 years now. >> They do not understand that people are free to do what they want and >to >> use what they want. >> >> Matthias >> >> >> Am 21.05.2017 um 11:13 schrieb Marcus: >> > Am 20.05.2017 um 21:35 schrieb Meh: >> >> Hey I saw the bugzilla thread and thought I'd share some info; >> > >> > another attempt to tell a story that only specific people want to >> > know. How boring. >> > >> > Marcus >> > >> > >> > >> >> >> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re:Bugzilla information
It's a very good point Peter. Diversity in the office software space is good. And you're right; People aren't going to stop using AOO if the PMC decided to stop releasing new versions. Please note to others I'm not some TDF/LO stooge. I actually use MS Office for work and OnlyOffice for personal files (I have 3 computers I actually write on with different OS's and document compatibility/sync is important.) I do read TDF's planet and AOO's dev list because I started in 2013/14 when The Register did an article and I've found it interesting to see both projects develop (weird idiosyncrasy to check these really when it has nothing to do with my life). I have found TDF to be a more sophisticated organization and as I stated in my views I see it for the reasons I listed, based on what I've read. They literally have staff to nurture volunteers, and strategically I think they're working hard on making a FOSS alternative that works economically (To Jorg: I don't see why having indirect company control of a foundation is bad if there's ample representation by governments on the foundation as well. Never seen a foundation that wasn't under the thumb of something powerful. If it was just one company or a for-profit ogliopoly then I would agree. But also that's an ethical/philosophical position of having a blind eye to evil to get to where you want to be (which IMO is an office suite that is treated like a public good for businesses/people, like the internet). That doesn't mean I think LO is the best office suite (again, I think OnlyOffice will take the FOSS crown because they're moving faster in the direction that the connected user wants. Too much baggage on the LO side. (Seriously, who is using Base? How many actually use Math? Poor allocation of resources IMO.) But that's just me!) In my time watching I've become concerned at the state of the AOO project. Not because I want to see it fail, but I help older people with their computers from time to time and I see how little they know and how gullible they are to scams. The state of security on AOO concerns me and I hope you passionate people can get security releases out soon. But you raise a very good point I did not consider; Even if AOO stopped, millions of people would not stop using the software. It's definitely more pervasive of a brand than any of the other FOSS suites. So yes, you're right and you've changed my perspective a bit; the mature answer would be to continue to make bug fixes. I wish you and the AOO team well! P.S. - I think people are responsible for their actions, but I don't think this applies for technology (yet). In the last 30 years we went from DOS to Smart Phones. No one can keep up. There's a lot of misplaced trust right now in the tech world. 21.05.2017, 20:51, "Peter Kovacs" : > The other offices are doing well. And competition is awesomely great. > You have forgotten to mention some competitors that also put some awesome > offers on the table. > I like the diversity this is causing. > > I have joined in September last year and do not plan to swap project soon. > I joined the project because I don't want to see open Office retire. I have > some skill in doing what is required, and I will do this. > > So my position is total contrary to yours. And imho people are responsible > for their own actions. See wannacry attack. > > I think you can learn from that if we would retire people will not stop use > the software. So the only mature answer is to fix the bugs untill people are > save. > > All the best > Peter > > Am 20. Mai 2017 21:35:02 MESZ schrieb Meh : >
Re: Bugzilla information
The way to treat such people: 1. Change our software license so any code sharing between us and them becomes impossible. 2. Arrange legally for the brand name they so desire to be forever unavailable even if our project will be terminated in the future. 3. Ignore them. On Sun, May 21, 2017 at 7:52 PM, Matthias Seidel wrote: > I sometimes wonder if these people monitoring our mailing list don't > have a real life... > > I know such zealots for almost 30 years now. > They do not understand that people are free to do what they want and to > use what they want. > > Matthias > > > Am 21.05.2017 um 11:13 schrieb Marcus: > > Am 20.05.2017 um 21:35 schrieb Meh: > >> Hey I saw the bugzilla thread and thought I'd share some info; > > > > another attempt to tell a story that only specific people want to > > know. How boring. > > > > Marcus > > > > > > > > >
Re: Bugzilla information
The other offices are doing well. And competition is awesomely great. You have forgotten to mention some competitors that also put some awesome offers on the table. I like the diversity this is causing. I have joined in September last year and do not plan to swap project soon. I joined the project because I don't want to see open Office retire. I have some skill in doing what is required, and I will do this. So my position is total contrary to yours. And imho people are responsible for their own actions. See wannacry attack. I think you can learn from that if we would retire people will not stop use the software. So the only mature answer is to fix the bugs untill people are save. All the best Peter Am 20. Mai 2017 21:35:02 MESZ schrieb Meh : >Hey I saw the bugzilla thread and thought I'd share some info; > >There have been 3 attempts by Apache and OpenOffice members in the past >couple years to do a dignified retirement before the code rot creates >an unusable state for AOO and it becomes an embarrassment for the FOSS >community. > >The most recent was by David Hamilton, the previous PM. There was some >serious discussion around this until some people decided that they'd >rather go down with the ship due to long standing grudges against >people at The Document Foundation. (Really petty imo) > >The only reason AOO still exists is a community of people who >ideologically believe that GPL/LO is bad and unrestrictive licenses are >great. Nothing wrong with that, just very inefficient use of people's >time. > >There are 4 consumer friendly, actively developed open source office >suites in the market today: Abiword/Gnumeric, Libreoffice, Calligra, >and OnlyOffice. > >OnlyOffice and Libreoffice are actively pursuing cloud integration with >cloud hosting providers (nextcloud, file cloud (proprietary), Seafile, >Pydio, etc.). OnlyOffice was opensourced in 2015, and was built using a >HTML5 and JavaScript base. It's probably going to be the new popular >kid on the block for open source office software. > >The people who worked at Sun that still want to work on OOo now work on >the Libreoffice code. LO code is literally years ahead in coding >development, refactoring, rewriting, etc. You won't get them back. > >Google Fuzz identified 33 bugs in LO code and suggested a quarter of >them were security vulnerabilities. It's likely that AOO has these >vulnerabilities too but they won't be fixed. > >Most AOO volunteers arrive, see the state of the project and then drift >off to projects with larger communities. > >Large tech companies don't see a need to invest in desktop only >technology, if anything there will be more use of MPL licensed LO or >OnlyOffice (new OO) as companies like Collabora already have sales >account managers and developers making it an option for companies and >governments wanting to stay away from MS. > >TDF donations go directly and solely to LO project management and >volunteer recruitment. There's a recent blog post on their planet that >talks about how they use donated funds to fix things volunteers never >would find interesting. AOO never received funds directly, only to the >Apache Project. Apache distributes to what they think is important, and >right now that is big data. This is unfair but not illogical. > >There hasn't been a significant release in AOO for a few years now, >only minor bug fixes. Old people like it because it works the same way >it has for the 6 years. However there are significant security risks to >using AOO. > >It's a great accomplishment of OOo that the brand has embedded into >tech culture that people use the name when they think free office >suite. But there won't be any new development on the project. There are >too many new FOSS projects out there solving the same problems that AOO >wants to solve, and the AOO demographic is getting smaller every month. >Windows S will likely initiate a huge drop in CNET downloads and there >will be a shift to LO over the next few years as they adopt more MS >features. > >If AOO wanted to survive as a project it would need to not be under the >Apache Foundation, or there would need to be a company willing to spend >money redoing everything what LO has done. But they won't, because even >LO has competitors that do Base better (Kexi), Draw better (Inkscape), >Impress better (Prezi, etc.). > >TDF realises this and they've focused on writer, calc, and impress in >the cloud. They'll likely be able to continue because of the community >support, but I see OnlyOffice taking the FOSS crown. AOO? Maybe a >Shuttleworth will bankroll developers? But why wouldn't he start from >scratch with all the code rot? LO still hasn't finished translating the >german comments and they've been working on it for years. i guess if >you posted it all on Github devs might take notice? > >I'm writing this as an appeal to take a mature response to the state of >your project. You have huge branding power and millions of older people >u
Re: Bugzilla information
I sometimes wonder if these people monitoring our mailing list don't have a real life... I know such zealots for almost 30 years now. They do not understand that people are free to do what they want and to use what they want. Matthias Am 21.05.2017 um 11:13 schrieb Marcus: > Am 20.05.2017 um 21:35 schrieb Meh: >> Hey I saw the bugzilla thread and thought I'd share some info; > > another attempt to tell a story that only specific people want to > know. How boring. > > Marcus > > > smime.p7s Description: S/MIME Cryptographic Signature
Re: Bugzilla information
Am 20.05.2017 um 21:35 schrieb Meh: Hey I saw the bugzilla thread and thought I'd share some info; another attempt to tell a story that only specific people want to know. How boring. Marcus -- Ciao Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Bugzilla information
> From: Meh [mailto:espri...@yandex.ru] > The only reason AOO still exists is a community of people who > ideologically believe that GPL/LO is bad and unrestrictive > licenses are great. No, that is not correct. Here at AOO are also people who do not agree with the TDF, which is not a question of licenses. The people at OpenOffice.org once wanted an independent foundation, but the TSF is dependent on companies, exactly the same as OOo was dependent on Oracle or Sun. And let us not overlook the basic truth: LibreOffice is the fork, not AOO. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Bugzilla information
Hey I saw the bugzilla thread and thought I'd share some info; There have been 3 attempts by Apache and OpenOffice members in the past couple years to do a dignified retirement before the code rot creates an unusable state for AOO and it becomes an embarrassment for the FOSS community. The most recent was by David Hamilton, the previous PM. There was some serious discussion around this until some people decided that they'd rather go down with the ship due to long standing grudges against people at The Document Foundation. (Really petty imo) The only reason AOO still exists is a community of people who ideologically believe that GPL/LO is bad and unrestrictive licenses are great. Nothing wrong with that, just very inefficient use of people's time. There are 4 consumer friendly, actively developed open source office suites in the market today: Abiword/Gnumeric, Libreoffice, Calligra, and OnlyOffice. OnlyOffice and Libreoffice are actively pursuing cloud integration with cloud hosting providers (nextcloud, file cloud (proprietary), Seafile, Pydio, etc.). OnlyOffice was opensourced in 2015, and was built using a HTML5 and JavaScript base. It's probably going to be the new popular kid on the block for open source office software. The people who worked at Sun that still want to work on OOo now work on the Libreoffice code. LO code is literally years ahead in coding development, refactoring, rewriting, etc. You won't get them back. Google Fuzz identified 33 bugs in LO code and suggested a quarter of them were security vulnerabilities. It's likely that AOO has these vulnerabilities too but they won't be fixed. Most AOO volunteers arrive, see the state of the project and then drift off to projects with larger communities. Large tech companies don't see a need to invest in desktop only technology, if anything there will be more use of MPL licensed LO or OnlyOffice (new OO) as companies like Collabora already have sales account managers and developers making it an option for companies and governments wanting to stay away from MS. TDF donations go directly and solely to LO project management and volunteer recruitment. There's a recent blog post on their planet that talks about how they use donated funds to fix things volunteers never would find interesting. AOO never received funds directly, only to the Apache Project. Apache distributes to what they think is important, and right now that is big data. This is unfair but not illogical. There hasn't been a significant release in AOO for a few years now, only minor bug fixes. Old people like it because it works the same way it has for the 6 years. However there are significant security risks to using AOO. It's a great accomplishment of OOo that the brand has embedded into tech culture that people use the name when they think free office suite. But there won't be any new development on the project. There are too many new FOSS projects out there solving the same problems that AOO wants to solve, and the AOO demographic is getting smaller every month. Windows S will likely initiate a huge drop in CNET downloads and there will be a shift to LO over the next few years as they adopt more MS features. If AOO wanted to survive as a project it would need to not be under the Apache Foundation, or there would need to be a company willing to spend money redoing everything what LO has done. But they won't, because even LO has competitors that do Base better (Kexi), Draw better (Inkscape), Impress better (Prezi, etc.). TDF realises this and they've focused on writer, calc, and impress in the cloud. They'll likely be able to continue because of the community support, but I see OnlyOffice taking the FOSS crown. AOO? Maybe a Shuttleworth will bankroll developers? But why wouldn't he start from scratch with all the code rot? LO still hasn't finished translating the german comments and they've been working on it for years. i guess if you posted it all on Github devs might take notice? I'm writing this as an appeal to take a mature response to the state of your project. You have huge branding power and millions of older people use your project. It's dangerous for these people to continue using your software when it's susceptible to exploits that won't be fixed anytime soon. Please inform them as to the state of your project instead of pretending everything is hunky dory. When LO releases their Google Fuzz code fixes hackers will compare the changes to your code and people will have identity theft, lose files, etc. Just so you guys can say: "oh, you suck LO, our ideology is better!" Meanwhile people are comparing OnlyOffice to Libreoffice when they look at FOSS office software. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: More Buildbot Information
Most excellent. Thx!! > On Sep 17, 2016, at 7:50 AM, Gavin McDonald wrote: > > Hi All, > > For those wanting to follow along or assist in the ASF hosted Buildbot > builds, I created a > new wiki page with some info about the builds and their hosts, how to update, > trigger builds etc. > > https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info > > My work on migrating builds from old to new slaves is complete. > > Project debs should check for failed builds. (Most are passing currently) > > Gav… > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
More Buildbot Information
Hi All, For those wanting to follow along or assist in the ASF hosted Buildbot builds, I created a new wiki page with some info about the builds and their hosts, how to update, trigger builds etc. https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info My work on migrating builds from old to new slaves is complete. Project debs should check for failed builds. (Most are passing currently) Gav… - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: License information
License is not just about price, actually price is irrelevant is about who can gain access to the code and what uses can be used. Please read the license at: http://www.apache.org/licenses/LICENSE-2.0 However you are "free" to use it from our website without the need to make any payment s to us. Althought donations are encourage. On Tue, Sep 6, 2016 at 12:56 AM, Harkesh Yadav wrote: > Dear sir > I am just confirm for the license of *Apache open office *It’s a free or > chargeable software please provide the information > > > > > > > > > *Thanks & Regards Harkesh * > > * 9711087683* > -- Alexandro Colorado Apache OpenOffice Contributor 9060 55AB FFD2 2F02 0E1A 3409 599C 14FC 9450 D3CF
License information
Dear sir I am just confirm for the license of *Apache open office *It’s a free or chargeable software please provide the information *Thanks & Regards Harkesh * * 9711087683*
Re: Where to find information about *.xcu schema (extension, dev, toolbar)
>Where to find information about *.xcu schema (extension, dev, toolbar) Use this extension: http://wiki.services.openoffice.org/wiki/Extensions_Packager Easy to produce OXT - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Where to find information about *.xcu schema (extension, dev, toolbar)
On 04/07/2016 07:55 AM, Christian Giehl wrote: Hi, I'm currently working on a custom toolbar for my oo-extension. To create the visual appearance of the toolbar, I have to write an Addons.xcu file, which contains a custom xml. However, the tag names and attributes I found in the tutorial all across the www are not sufficient for my case and I stumbled accross tags I never encountered anywhere before, e.g. You can include 4 icons for the toolbar, these are for High Contrast. The big one should be 26 x 26 and the small one 16 x 16. Same for the two low contrast ones. or some attributes like oor:op="replace". Since I can't reliably figure out what these tags/attributes represent and how they are used I am in need for some kind of documentation. The only ref I've found so far is (https://wiki.openoffice.org/wiki/Documentation/DevGuide/WritingUNO/AddOns/Toolbars), but not all props/tags/attrs are listed there. I wonder if anyone of you guys can tell me how I can approach to these kinds of problems better. Is there a reference documentation I haven't found yet? How do I gain a clearer understanding of those tags without a documentation? I beg nobody says reverse engineering :D Thanks in advance! Chris Hi Chris, I'm not aware of a schema published anywhere but perhaps someone else may. In the mean time I generated a sample Addons.xcu with the NetBeans plugin with some examples filled in. To make it simpler I'll just post the text below.. -- http://openoffice.org/2001/registry"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; oor:name="Addons" oor:package="org.openoffice.Office"> AddOn Menu _self com.example.nbaddon:Command0 _self Command0 Dummy com.example.nbaddon:Command0 _self com.sun.star.frame.Bibliography,com.sun.star.chart.ChartDocument,com.sun.star.sdb.OfficeDatabaseDocument,com.sun.star.drawing.DrawingDocument,com.sun.star.formula.FormulaProperties,com.sun.star.presentation.PresentationDocument,com.sun.star.sheet.SpreadsheetDocument,com.sun.star.text.TextDocument,com.sun.star.text.GlobalDocument Command0 oor:op="replace"> com.example.nbaddon:Command0 %origin%/../../../../../images/edit-cut.png -- Please let me know if you have any questions. Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Where to find information about *.xcu schema (extension, dev, toolbar)
Hi, I'm currently working on a custom toolbar for my oo-extension. To create the visual appearance of the toolbar, I have to write an Addons.xcu file, which contains a custom xml. However, the tag names and attributes I found in the tutorial all across the www are not sufficient for my case and I stumbled accross tags I never encountered anywhere before, e.g. or some attributes like oor:op="replace". Since I can't reliably figure out what these tags/attributes represent and how they are used I am in need for some kind of documentation. The only ref I've found so far is (https://wiki.openoffice.org/wiki/Documentation/DevGuide/WritingUNO/AddOns/Toolbars), but not all props/tags/attrs are listed there. I wonder if anyone of you guys can tell me how I can approach to these kinds of problems better. Is there a reference documentation I haven't found yet? How do I gain a clearer understanding of those tags without a documentation? I beg nobody says reverse engineering :D Thanks in advance! Chris - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Fwd: FOSDEM: Practical information
Forwarding Daniel's excellent message in case someone plans to attend FOSDEM and is not on the dev@community list. I've updated https://cwiki.apache.org/confluence/display/COMDEV/FOSDEM+2016 with the information earlier discussed on this list. See you there! Andrea Forwarded Message Date: Thu, 28 Jan 2016 09:21:24 +0100 From: Daniel Gruno Hi folks! FOSDEM is now less than two days away, so here's some practical information, which you'll also find on the wiki: SETUP: The booth will be set up on Saturday between 9:00 and 10:00. The conference starts at 10:00. Anyone willing to help out here, please meet up at the K building a bit before 9. SWAG: Due to the new logo (and the uncertainty of whether we'd be able to use it or not), we have been pressed for time, as we had very few days to procure swag for this. Luckily, we had some awesome print shops help us out, and we have the following items available (IN SMALL QUANTITIES!): - t-shirts (various sizes/sexes) - mugs (veeery few, probably gonna use them for coffee at the booth) - key chains with LED lights - fridge magnets (lots of those, like...hundreds!) - round 3" powered-by stickers (loads of them) - pens with full color logo - small badges with logo (not a whole lot, 30-40 or so) - beer coasters - 180x80cm banner for the booth with a quadpod - Some other stickers that Sally doesn't like ;) I'll be very "Scottish" about this and divide it into two piles - one for saturday, one for sunday, and only bring half the swag from my hotel each day. SWAG RULES: No talk, no swag! If people want even a pen, it requires a conversation with us. Do they know what the ASF does? Can they name 3 projects? Do they know who our president is? etc etc. The more they talk, the better swag they'll get :) Please be very sparse with handing out swag, especially at first, or it'll be gone within 25 minutes. BOOTH SCHEDULE: See the wiki for exact project schedules. The booth is open Saturday from 10:00 till 19:00, and Sunday from 10:00 till 17:00. The schedule can be changed if more projects show up. Besides, we have nearly 4 meters of booth space, so... TEARDOWN: teardown is on Sunday at 17:00 and should be done before 17:30. This should be simple, but help is appreciated. Jimjag has dibs on the banner, so I'll mail it to him once we're done using it. Hope to see you there! With regards, Daniel. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Ian Lynch information needed
Hi Andrea, I didn't get the chance to read the memorial until now, I most say is a great piece. However they omit a big part of his life which was his professional one. As his linkedin page says ( https://uk.linkedin.com/pub/ian-lynch/0/a88/bb2) he was a Registered Inspector of schools accredited by Office for Standards in Education, and a lifetime educator in the British school system. I can understand that maybe the goal is not to be too acurate, and on a lighter note, he was a very good Ruby player and missed going to the 2010 OpenOffice.org Conference in Slovenia due to a broken leg. https://scontent-atl3-1.xx.fbcdn.net/hphotos-xpa1/v/t1.0-9/12036502_10154197872421978_233667787073901200_n.jpg?oh=3ab5dbcd8f1895bce374dc466e62d7bb&oe=565FCDB2 On Sat, Sep 19, 2015 at 2:56 PM, Andrea Pescetti wrote: > On 13/09/2015 Kay Schenk wrote: > >> Thank you. And it seems I mis-typed the year.in the memorial page. New >> revision attached. >> > > Thank you Kay. This final version is now published at > http://www.apache.org/memorials/ > > Regards, > Andrea. > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614
Re: Ian Lynch information needed
On 13/09/2015 Kay Schenk wrote: Thank you. And it seems I mis-typed the year.in the memorial page. New revision attached. Thank you Kay. This final version is now published at http://www.apache.org/memorials/ Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wrongful information on the Wikipedia
Phillip Rhodes wrote: All of the above said, maybe we should drop this whole discussion Well, it remains the fact that "OpenOffice moribund" is false. The primary sources cited in the article (all of which are clearly misinterpreted) are: - A message from Juergen saying that he won't be Release Manager for 4.1.2; release managers are appointed per-release, so this is not relevant to the health of the project (actually Juergen's mail is very well-written, and very hard to misinterpret if one read carefully) - A message from Kay saying that we had not found a new volunteer for Release Manager yet; this is obsolete as we have now had a Release Manager (me) for several weeks, but no account is given of this. - My January 2015 report to Board. I'm sure I never wrote that OpenOffice is moribund or anything similar. I announced my resignation in that report, but I resigned as I had been 2 years in the role, just like Dennis plans to stay one year and then resign. shipping code is more important than Wikipedia anyway, right? Yes, but it is also important that users and potential users are not scared away. So, what can I do to help with 4.1.2? I like your approach! Are you looking for coder or non-coder tasks? I suggest that you seek inspiration at https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2 but if you need more details just open a "What can I do to help with 4.1.2?" discussion and I'll be happy to give more details. In the meantime I could go to Wikipedia, write that Johnny Depp is moribund and provide as source a blog post by a fan who complains that she hasn't seen Johnny as handsome as usual in his last public appearance... but I'll spend my time on more productive activities instead. I understand Dennis' point that discussing actions of one individual on Wikipedia is off-topic on this list, but still I wanted to provide some feedback on how messages sent to this list are misused. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wrongful information on the Wikipedia
On 17/09/15 15:30, Phillip Rhodes wrote: > This is about Wikipedia being accurate, and the simple truth is, Wikipedia is not about accuracy, nor is it about truth. What it is about, is whether or not the delusions and hallucinations of the editors can be supported by an appeal to an external authority. jonathon - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wrongful information on the Wikipedia
All of the above said, maybe we should drop this whole discussion, and let David have his way, and focus on getting a 4.1.2 release out the door. That should settle the issue, and shipping code is more important than Wikipedia anyway, right? So, what can I do to help with 4.1.2? Phil This message optimized for indexing by NSA PRISM On Thu, Sep 17, 2015 at 11:30 AM, Phillip Rhodes wrote: > David, this has nothing to do with marketing, and I honestly feel like you > are the one acting in bad faith here. This is about Wikipedia being > accurate, and the simple truth is, on a question like "what's the status of > AOO" none of your "sources" are more accurate than a primary source like > the internal project timeline / roadmap that I cited. > > If you have a grudge against AOO for some reason that's fine, I don't give > a flying fuck and I doubt anybody else does either. But Wikipedia is not > the place for you to further some personal vendetta. > > > Phil > > > This message optimized for indexing by NSA PRISM > > On Thu, Sep 17, 2015 at 10:25 AM, David Gerard wrote: > >> On Wed, 16 Sep 2015 21:27:53 GMT, Rob Weir wrote: >> >> > Last word, in case the inference is unclear. We're dealing with a >> > sophisticated serial infringer on Wikipedia. Correcting erroneous >> > information, which is proper to do, is unlikely to be achieved via an >> > edit war. Don't bring a knife to a gunfight. Any progress would >> > only be made by showing Mr. Gerard's own conflict and his bad will >> > (not hard to do), and escalating it within the the formal Wikipedia >> > appeals process, patiently dealing with the ministerial types to whom >> > bureaucratic process is dear. Since Dennis does not want to discuss >> > this on the list, feel free to contact me offline if anyone wishes to >> > discuss this further. >> >> >> When you're putting together a plan for marketing efforts concerning a >> Wikipedia article, it may help if you don't leave prima facie evidence >> of your coordinated effort on a public mailing list. >> >> Editing with a conflict of interest is not specifically disallowed by >> Wikipedia policies, but ideally it should be avoided. Note example on >> the talk page, where a list participant properly noted his involvement >> when this was brought to his attention. >> >> Relevant guideline: >> https://en.wikipedia.org/wiki/Wikipedia:Conflict_of_interest >> >> You should note also that a "conflict of interest" does not mean a >> differing opinion, and also that improperly founded accusations of COI >> are held to constitute personal attacks and should ideally be avoided. >> >> There are those (e.g. Jimmy Wales) who believe public relations >> efforts on Wikipedia should work to the "bright line" standard, where >> you don't go near the article at all, and certainly don't try to >> coordinate an off-site attack on a Wikipedia contributor because you >> believe they are not helping your marketing. This is something the >> project, and the Foundation in general, should probably consider. >> >> Cheers! >> >> >> - d. >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> >
Re: Wrongful information on the Wikipedia
David, this has nothing to do with marketing, and I honestly feel like you are the one acting in bad faith here. This is about Wikipedia being accurate, and the simple truth is, on a question like "what's the status of AOO" none of your "sources" are more accurate than a primary source like the internal project timeline / roadmap that I cited. If you have a grudge against AOO for some reason that's fine, I don't give a flying fuck and I doubt anybody else does either. But Wikipedia is not the place for you to further some personal vendetta. Phil This message optimized for indexing by NSA PRISM On Thu, Sep 17, 2015 at 10:25 AM, David Gerard wrote: > On Wed, 16 Sep 2015 21:27:53 GMT, Rob Weir wrote: > > > Last word, in case the inference is unclear. We're dealing with a > > sophisticated serial infringer on Wikipedia. Correcting erroneous > > information, which is proper to do, is unlikely to be achieved via an > > edit war. Don't bring a knife to a gunfight. Any progress would > > only be made by showing Mr. Gerard's own conflict and his bad will > > (not hard to do), and escalating it within the the formal Wikipedia > > appeals process, patiently dealing with the ministerial types to whom > > bureaucratic process is dear. Since Dennis does not want to discuss > > this on the list, feel free to contact me offline if anyone wishes to > > discuss this further. > > > When you're putting together a plan for marketing efforts concerning a > Wikipedia article, it may help if you don't leave prima facie evidence > of your coordinated effort on a public mailing list. > > Editing with a conflict of interest is not specifically disallowed by > Wikipedia policies, but ideally it should be avoided. Note example on > the talk page, where a list participant properly noted his involvement > when this was brought to his attention. > > Relevant guideline: > https://en.wikipedia.org/wiki/Wikipedia:Conflict_of_interest > > You should note also that a "conflict of interest" does not mean a > differing opinion, and also that improperly founded accusations of COI > are held to constitute personal attacks and should ideally be avoided. > > There are those (e.g. Jimmy Wales) who believe public relations > efforts on Wikipedia should work to the "bright line" standard, where > you don't go near the article at all, and certainly don't try to > coordinate an off-site attack on a Wikipedia contributor because you > believe they are not helping your marketing. This is something the > project, and the Foundation in general, should probably consider. > > Cheers! > > > - d. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Wrongful information on the Wikipedia
On Thu, Sep 17, 2015 at 10:25 AM, David Gerard wrote: > On Wed, 16 Sep 2015 21:27:53 GMT, Rob Weir wrote: > >> Last word, in case the inference is unclear. We're dealing with a >> sophisticated serial infringer on Wikipedia. Correcting erroneous >> information, which is proper to do, is unlikely to be achieved via an >> edit war. Don't bring a knife to a gunfight. Any progress would >> only be made by showing Mr. Gerard's own conflict and his bad will >> (not hard to do), and escalating it within the the formal Wikipedia >> appeals process, patiently dealing with the ministerial types to whom >> bureaucratic process is dear. Since Dennis does not want to discuss >> this on the list, feel free to contact me offline if anyone wishes to >> discuss this further. > > > When you're putting together a plan for marketing efforts concerning a > Wikipedia article, it may help if you don't leave prima facie evidence > of your coordinated effort on a public mailing list. > > Editing with a conflict of interest is not specifically disallowed by > Wikipedia policies, but ideally it should be avoided. Note example on > the talk page, where a list participant properly noted his involvement > when this was brought to his attention. > > Relevant guideline: > https://en.wikipedia.org/wiki/Wikipedia:Conflict_of_interest > > You should note also that a "conflict of interest" does not mean a > differing opinion, and also that improperly founded accusations of COI > are held to constitute personal attacks and should ideally be avoided. > > There are those (e.g. Jimmy Wales) who believe public relations > efforts on Wikipedia should work to the "bright line" standard, where > you don't go near the article at all, and certainly don't try to > coordinate an off-site attack on a Wikipedia contributor because you > believe they are not helping your marketing. This is something the > project, and the Foundation in general, should probably consider. > You are not reading very well today, David. I'm not talking about, "a plan for marketing efforts concerning a Wikipedia article." I'm talking about an effort to bring together evidence of your conflict of interest as well as your tendentious editing (much of which I have already collected over the past few years) and use that to lodge an appeal, via official and public channels, to get a topic ban imposed on you on Wikipedia articles relevant to this infringement. Cheers. -Rob > Cheers! > > > - d. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wrongful information on the Wikipedia
On Wed, 16 Sep 2015 21:27:53 GMT, Rob Weir wrote: > Last word, in case the inference is unclear. We're dealing with a > sophisticated serial infringer on Wikipedia. Correcting erroneous > information, which is proper to do, is unlikely to be achieved via an > edit war. Don't bring a knife to a gunfight. Any progress would > only be made by showing Mr. Gerard's own conflict and his bad will > (not hard to do), and escalating it within the the formal Wikipedia > appeals process, patiently dealing with the ministerial types to whom > bureaucratic process is dear. Since Dennis does not want to discuss > this on the list, feel free to contact me offline if anyone wishes to > discuss this further. When you're putting together a plan for marketing efforts concerning a Wikipedia article, it may help if you don't leave prima facie evidence of your coordinated effort on a public mailing list. Editing with a conflict of interest is not specifically disallowed by Wikipedia policies, but ideally it should be avoided. Note example on the talk page, where a list participant properly noted his involvement when this was brought to his attention. Relevant guideline: https://en.wikipedia.org/wiki/Wikipedia:Conflict_of_interest You should note also that a "conflict of interest" does not mean a differing opinion, and also that improperly founded accusations of COI are held to constitute personal attacks and should ideally be avoided. There are those (e.g. Jimmy Wales) who believe public relations efforts on Wikipedia should work to the "bright line" standard, where you don't go near the article at all, and certainly don't try to coordinate an off-site attack on a Wikipedia contributor because you believe they are not helping your marketing. This is something the project, and the Foundation in general, should probably consider. Cheers! - d. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wrongful information on the Wikipedia
On 09/16/2015 02:32 PM, Louis Suárez-Potts wrote: > >> On 16 Sep 15, at 17:27, Rob Weir wrote: >> >> On Wed, Sep 16, 2015 at 5:04 PM, Rob Weir wrote: >>> On Wed, Sep 16, 2015 at 3:38 PM, Dennis E. Hamilton >>> wrote: >>>> Time, gentlemen, time. >>>> >>>> We're far across the ad hominem boundary and it is time to let >>>> this thread go night-night. >>>> >>>> Whatever is thought of about what happens on Wikipedia, it is >>>> not ASF and AOO business. We have our own business to attend >>>> to. If folks want to keep fussing about it, there are many >>>> better places to do that than here on dev@. >>>> >>> >>> Ad hominem? Excuse me? The web page has a record of Wikipedia >>> abuses attributed to Mr. Gerard and cites several cases where he >>> was sanction for it. One can talk about his actions without >>> slurring his person, especially when such acts are directly >>> relevant to the topic of this thread. >>> >> >> Last word, in case the inference is unclear. We're dealing with >> a sophisticated serial infringer on Wikipedia. Correcting >> erroneous information, which is proper to do, is unlikely to be >> achieved via an edit war. Don't bring a knife to a gunfight. Any >> progress would only be made by showing Mr. Gerard's own conflict >> and his bad will (not hard to do), and escalating it within the >> the formal Wikipedia appeals process, patiently dealing with the >> ministerial types to whom bureaucratic process is dear. Since >> Dennis does not want to discuss this on the list, feel free to >> contact me offline if anyone wishes to discuss this further. >> >> -Rob I love "serial infringer". :) >> > > But Dennis does not control the lists, just as King Canute did not > control the waves. :-/ > > Rob, your points are good; I was being too facetious, stunned by the > attitude of Mr Gerard. Clearly, unless we are reading him wrongly, he > would seem more likely to stick to his position, regardless of reason > and logic, than accept the ignominy of somebody else being right. > > louis > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > -- MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wrongful information on the Wikipedia
> On 16 Sep 15, at 17:27, Rob Weir wrote: > > On Wed, Sep 16, 2015 at 5:04 PM, Rob Weir wrote: >> On Wed, Sep 16, 2015 at 3:38 PM, Dennis E. Hamilton >> wrote: >>> Time, gentlemen, time. >>> >>> We're far across the ad hominem boundary and it is time to let this thread >>> go night-night. >>> >>> Whatever is thought of about what happens on Wikipedia, it is not ASF and >>> AOO business. We have our own business to attend to. If folks want to >>> keep fussing about it, there are many better places to do that than here on >>> dev@. >>> >> >> Ad hominem? Excuse me? The web page has a record of Wikipedia >> abuses attributed to Mr. Gerard and cites several cases where he was >> sanction for it. One can talk about his actions without slurring his >> person, especially when such acts are directly relevant to the topic >> of this thread. >> > > Last word, in case the inference is unclear. We're dealing with a > sophisticated serial infringer on Wikipedia. Correcting erroneous > information, which is proper to do, is unlikely to be achieved via an > edit war. Don't bring a knife to a gunfight. Any progress would > only be made by showing Mr. Gerard's own conflict and his bad will > (not hard to do), and escalating it within the the formal Wikipedia > appeals process, patiently dealing with the ministerial types to whom > bureaucratic process is dear. Since Dennis does not want to discuss > this on the list, feel free to contact me offline if anyone wishes to > discuss this further. > > -Rob > But Dennis does not control the lists, just as King Canute did not control the waves. :-/ Rob, your points are good; I was being too facetious, stunned by the attitude of Mr Gerard. Clearly, unless we are reading him wrongly, he would seem more likely to stick to his position, regardless of reason and logic, than accept the ignominy of somebody else being right. louis - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wrongful information on the Wikipedia
On Wed, Sep 16, 2015 at 5:04 PM, Rob Weir wrote: > On Wed, Sep 16, 2015 at 3:38 PM, Dennis E. Hamilton wrote: >> Time, gentlemen, time. >> >> We're far across the ad hominem boundary and it is time to let this thread >> go night-night. >> >> Whatever is thought of about what happens on Wikipedia, it is not ASF and >> AOO business. We have our own business to attend to. If folks want to keep >> fussing about it, there are many better places to do that than here on dev@. >> > > Ad hominem? Excuse me? The web page has a record of Wikipedia > abuses attributed to Mr. Gerard and cites several cases where he was > sanction for it. One can talk about his actions without slurring his > person, especially when such acts are directly relevant to the topic > of this thread. > Last word, in case the inference is unclear. We're dealing with a sophisticated serial infringer on Wikipedia. Correcting erroneous information, which is proper to do, is unlikely to be achieved via an edit war. Don't bring a knife to a gunfight. Any progress would only be made by showing Mr. Gerard's own conflict and his bad will (not hard to do), and escalating it within the the formal Wikipedia appeals process, patiently dealing with the ministerial types to whom bureaucratic process is dear. Since Dennis does not want to discuss this on the list, feel free to contact me offline if anyone wishes to discuss this further. -Rob > -Rob > >> - Dennis >> >> [ ... ] >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wrongful information on the Wikipedia
On Wed, Sep 16, 2015 at 3:38 PM, Dennis E. Hamilton wrote: > Time, gentlemen, time. > > We're far across the ad hominem boundary and it is time to let this thread go > night-night. > > Whatever is thought of about what happens on Wikipedia, it is not ASF and AOO > business. We have our own business to attend to. If folks want to keep > fussing about it, there are many better places to do that than here on dev@. > Ad hominem? Excuse me? The web page has a record of Wikipedia abuses attributed to Mr. Gerard and cites several cases where he was sanction for it. One can talk about his actions without slurring his person, especially when such acts are directly relevant to the topic of this thread. -Rob > - Dennis > > [ ... ] > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wrongful information on the Wikipedia
> On 16 Sep 15, at 15:38, Dennis E. Hamilton wrote: > > Time, gentlemen, time. > > We're far across the ad hominem boundary and it is time to let this thread go > night-night. > > Whatever is thought of about what happens on Wikipedia, it is not ASF and AOO > business. We have our own business to attend to. If folks want to keep > fussing about it, there are many better places to do that than here on dev@. > > - Dennis > > [ … ] ?? I don’t think this is a) a gentleman kind of thing, if only for gender reasons; b) I think I rather like Mr G. and hardly deem this to be an ad hominem event. If others are like me, once you read over Mr G’s bio, a *lot* gets forgiven. He’s a card, a character, a source of necessary comic inversion. No one is flaming anyone here and we are actually kind of having fun. Louis > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: Wrongful information on the Wikipedia
Time, gentlemen, time. We're far across the ad hominem boundary and it is time to let this thread go night-night. Whatever is thought of about what happens on Wikipedia, it is not ASF and AOO business. We have our own business to attend to. If folks want to keep fussing about it, there are many better places to do that than here on dev@. - Dennis [ ... ] - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org