Re: Volunteer to implement data mining functionality for OpenOffice

[Peter Kovacs]

Hi Hao,


sorry for the late reply. I am not sure what you want to do. Data Mining 
/ analytics is a wide field.


OpenOffice can integrate python3. I think this is the way to go for all 
data analytics stuff. More about Python at [2].


I would recommend if you want to add features to start add them as 
extensions [1].




All the best

Peter

[1] 
https://wiki.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions


[2] https://wiki.openoffice.org/wiki/Python

On 25.11.21 03:34, Hao Wang wrote:

Dear Devs:

I noticed neither WPS nor OpenOffice have data mining functionality (Microsoft 
Office does have it). I'm proposing to implement data mining functionality for 
OpenOffice, but I need some help for integration.

Bravo!
Hao Wang


--
This is the Way! http://www.apache.org/theapacheway/index.html

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: I want to volunteer.

[Peter Kovacs]

Hi Gabriel,

sorry for the late reply.

It is a good thinking to start of with submitting bug problem reports 
for starters. However I would like to improve on your idea.


Website Issues:

If you see an Issue on our website we would rather like you to send 
directly a proposal. Or in case of the wiki, just go and fix what you 
want to change. If the community does not agree, we can discuss it. 
Every change is tracked and we can role back in case of need. So in 
order to work on the website all you need is a github account. See our 
guide at [1] for further explainations


Bugzilla:

For working on Bugzilla [2], you need to request a Bugzilla Account. For 
this you write a mail to this list with your request, a prefered user 
name and a n email you own. You can of course still add further bugs to 
the over 10K open Bugs we have. In my opinion if you want to work on 
Bugzilla, it would be more helpfull top check if the reported ones are 
still valid. And in case there is no Test description add a comment how 
to test this case.


Bugzilla Example [3]

In this Bug we see it is on Accepted, which means the report is not only 
open but confirmed. Version it says 619, which is old...


Latest Confirmation is --- Which says we do not know if this is still 
valid. So if you test this one and find out it is still valid. then you 
select the version you have tested with (preferable 4.1.11)


If it is not valid anymore you can close it.


If you could think on my suggestion and provide feedback this would be 
awesome :-)



All the best

Peter


[1] https://openoffice.apache.org/website-local.html

[2] https://bz.apache.org/ooo/

[3] https://bz.apache.org/ooo/show_bug.cgi?id=595


On 03.12.21 01:57, Gabriel Borba wrote:

Hello, my name is Gabriel Borba, I’m 19, and I’m looking to volunteer to submit 
problem reports about the product or website(s).
I already read the guide “How to file a good Issue”, however I’m open to learn 
more about what I need to do, so I can perform a better job

Sent from Mail for Windows



--
This is the Way! http://www.apache.org/theapacheway/index.html

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Openssl, serf and curl

[Pedro Lino]

Hi Matthias

> On 12/09/2021 3:20 PM Matthias Seidel  wrote:

> Is this a real machine or a VM?

It is a real machine
 
> I ask, because I have seen the Update Feed fail on Ubuntu in a VM when
> it definitely worked on my Laptop.

There were a lot of errors during unpack, as I said. 

If Arigo can send me the deb installer, I can try it again.

Regards,
Pedro

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Openssl, serf and curl

[Matthias Seidel]

Hi Pedro,

Am 08.12.21 um 22:55 schrieb Pedro Lino:
> Hi Arrigo
>
> I got some errors while unpacking the tar.bz2 file so I'm not sure it is 
> working as expected. It did run and it still reported "Checking for an update 
> failed."
> I'm running Ubuntu 18.04 x64

Is this a real machine or a VM?

I ask, because I have seen the Update Feed fail on Ubuntu in a VM when
it definitely worked on my Laptop.

Regards,

   Matthias

>
> Regards,
> Pedro
>
>> On 12/08/2021 7:08 PM Matthias Seidel  wrote:
>>
>>  
>> Hi Arrigo,
>>
>> Am 07.12.21 um 22:05 schrieb Arrigo Marchiori:
>>> Dear All,
>>>
>>> we are getting somewhere! I am replying myself again below.
>>>
>>> On Fri, Nov 26, 2021 at 08:26:55PM +0100, Arrigo Marchiori wrote:
>>>
 Dear All,

 On Sun, Nov 21, 2021 at 09:29:18PM +0100, Arrigo Marchiori wrote:

> Hello All,
>
> just a little update.
>
> On Sat, Nov 20, 2021 at 01:44:43PM +0100, Arrigo Marchiori wrote:
>
>> Hello Matthias, All,
>>
>> On Fri, Nov 19, 2021 at 12:26:37AM +0100, Matthias Seidel wrote:
>>
>>> Hi Arrigo,
>>>
>>> Am 17.11.21 um 08:16 schrieb Arrigo Marchiori:
 Dear All,

 I pushed a new branch "serf", that contains the OpenSSL upgrade
 commits (I reverted the reverts ;-) plus a tentative upgrade of the
 serf library to 1.3.9.

 A small patch is included to allow building with Python3-based SCons.

 The oox module also needed minor patching because it uses some OpenSSL
 functions that were refactored since OpenSSL 1.1.0.

 I tested it under Linux with Peter's Docker image (adding SCons). It
 builds and runs, but I am not sure how to verify if the SSL related
 problems are solved.

 I could not yet test if it builds under Windows and Mac. Any help
 would be appreciated. Please note that the "serf" branch derives from
 trunk.
>>> I cannot get it to build on Windows.
>>>
>>> The build just stops at a certain point. No error messages.
>> I had not tested it under Windows, when I commited it. Sorry.
>>
>> The build stops because the existing patch to OpenSSL does not apply.
>>
>> If we disable it, we face another challenge: OpenSSL does not build
>> with Cygwin's Perl!
>> https://github.com/openssl/openssl/issues/9048
>>
>> I will investigate if we need Strawberry Perl as suggested in the
>> above link. It's sure this is getting more complex than expected.
> I could patch the configure scripts to use Windows and Cygwin paths as
> necessary. Now the compilation is failing because of missing symbols,
> at link time.
>
> As soon as I have something almost usable, I will commit it.
 I think I fixed the OpenSSL module and the depending Python.
>>> Not yet... there were more places in which the libraries were named,
>>> and more fixes were necessary.
>>>
 Serf is now posing another challenge.

 Apparently, SCons needs to access the Windows registry in order to
 detect the presence of Visual Studio. This is reasonable: also our
 "oowintool" script does so.

 Python scripts can access the Windows registry using the "winreg"
 module. The problem is that such module _is not included_ in Cygwin's
 Python distribution!

 There is a "cygwinreg" module available, but it does not seem to work.

 So instead of using an ``external'' Perl, we will need to use an
 ``external'' Python.
>>> We will need an ``external'' SCons. I added the configure script
>>> option "--with-scons" that must be used under Windows to point to a
>>> ``native'' SCons.exe
>>>
>>> I added a minimal SConscript that checks the validity of the indicated
>>> SCons.
>>>
>>> Unix users should just need to install SCons in some ways (either
>>> using pip or the distribution's package) and it will be auto-detected
>>> by the configure script.
>>>
>>>  - Linux build:
>>>
>>> http://home.apache.org/~ardovm/openoffice/linux/openoffice4-2021-12-07-x86_64-installed.tar.bz2
>>>
>>>  - Windows build:
>>>
>>> https://home.apache.org/~ardovm/openoffice/windows/Apache_OpenOffice-2021-12-06_Win_x86_install_en-US.exe
>>>
>>> Do they work as expected?
>> I tested on Windows, it works as expected.
>>
>> The main problem on Linux was the update feed...
>>
>> Regards,
>>
>>    Matthias
>>
>>> Best regards,
> -
> 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