subject:"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

2023-03-04 Thread 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

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

2023-03-04 Thread 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?

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

2022-11-20 Thread GitBox



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

2022-11-12 Thread GitBox



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

2022-11-12 Thread GitBox



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)

2022-06-08 Thread Peter Kovacs


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)

2022-06-08 Thread Rony G. Flatscher (Apache)

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)

2022-06-06 Thread Carl Marcum


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)

2022-06-06 Thread Rony G. Flatscher (Apache)

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)

2022-06-06 Thread Rony G. Flatscher (Apache)

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)

2022-06-04 Thread Carl Marcum


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)

2022-06-03 Thread Peter Kovacs


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)

2022-01-16 Thread Matthias Seidel

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)

2022-01-16 Thread 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.


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)

2022-01-15 Thread Matthias Seidel

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)

2021-10-03 Thread 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

What information do we know about the market penetration of AOO?

2021-08-01 Thread Jörg Schmidt

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

2020-11-15 Thread 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.


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

2020-11-15 Thread Marcus


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

2020-11-15 Thread 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.


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

2020-11-14 Thread 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.


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

2020-11-14 Thread Dave Fisher

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

2020-11-14 Thread Matthias Seidel

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)

2020-07-10 Thread Dave Fisher

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

2020-04-25 Thread 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: Apache OpenOffice Project Information

2020-04-13 Thread 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.

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

2020-04-13 Thread 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.


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

2020-04-13 Thread Jörg Schmidt

 

> -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

2020-04-13 Thread Jörg Schmidt

 

> -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

2020-04-13 Thread Matthias Seidel

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

2020-04-13 Thread Matthias Seidel

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