Re: drop ressources (stlport, maybe beanshell)

[Pedro Giffuni]

Hi guys;

FWIW, I am involved in beanshell in my spare time, which is not plenty
lately. As mentioned previously it is in github now and a much improved
version will be released one day (no ETA).

While looking for candidates to remove stuff, consider stax. It is
included in Java since JDK5.

Pedro.


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

repository archeolo-git needed

[Pedro Giffuni]

Hi;

Apparently the old mercurial repository that the OOo team did in
bitbucket is no more, and we know that because the link in our sources
page is not there.

For those of you that were not around, Oracle wanted to transfer the
history from the repositories but the process to convert everything from
mercurial to subversion would take too long and we needed to get started
really soon so we sidestepped it. With git it would have been easy, but
at the time infra only offered subversion.

There was some interesting code there which we actually have the power
to relicense. There was a branch with an update to hsqldb, for example.

Somewhat later Herbert Duerr actually made an exercise of a faithful
translation :

https://archive.fosdem.org/2014/schedule/event/exploring_openoffice_history_using_git_grafts/

last time I talked to him, he mentioned the resulting file was at
minotaur but there was a 26G blob mirrored here:

https://dev-www.libreoffice.org/extern/HistOOory_v0.9.zip

It would be really nice to take the above and rebase our current
repository on top of it. Or perhaps, someone should pass the request to
infra.

Cheers,

Pedro.


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

Re: System-provided Python 3 support now committed

[Pedro Giffuni]

Hello;

For the record, I only did a small "scotch tape" fix, the heavy lifting
was done by Damjan. My public thanks to him as this is likely to save
AOO from deprecation (at least in FreeBSD).

I think in the future we may move to tauthon, as an interim step before
Python 3:

https://github.com/naftaliharris/tauthon

Cheers,

Pedro.


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

Re: Update to python-2.17

[Pedro Giffuni]

On 2020-01-10 13:24, Matthias Seidel wrote:
> Hi Pedro,
>
> Am 10.01.20 um 07:14 schrieb Pedro Giffuni:
>> Hi again;
>>
>> On 2020-01-04 05:16, Matthias Seidel wrote:
>>> Hi Pedro,
>>>
>>> Thanks!
>>>
>>> Unfortunately the build process just stops at some point (on Windows),
>>> no error codes I could give you.
>> The problems are usually related to getting the patches applied
>> correctly. There can be no hunks or mismatches.
>>
>> I tested them one by one and they should be OK now. Same place:
>>
>> https://people.apache.org/~pfg/patches/patch-python-2.17.diff
> When trying to apply this patch to trunk I get:
>
>   malformed patch at line 2048: Index:
> main/python/python-2.7.15-msvs9.patch
>
> (It would be nice if you could create a Pull Request on GitHub)

Indeed that patch causes issues due to Windows LF characters. I
overruled the issue in git and sent the Pull Request:

https://github.com/apache/openoffice/pull/23

Enjoy!

Pedro.



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

Re: Update to python-2.17

[Pedro Giffuni]

On 2020-01-10 14:53, Matthias Seidel wrote:
> Hi Pedro,
>
> Am 10.01.20 um 20:50 schrieb Pedro Giffuni:
>> On 2020-01-10 13:24, Matthias Seidel wrote:
>>> Hi Pedro,
>>>
>>> Am 10.01.20 um 07:14 schrieb Pedro Giffuni:
>>>> Hi again;
>>>>
>>>> On 2020-01-04 05:16, Matthias Seidel wrote:
>>>>> Hi Pedro,
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Unfortunately the build process just stops at some point (on Windows),
>>>>> no error codes I could give you.
>>>> The problems are usually related to getting the patches applied
>>>> correctly. There can be no hunks or mismatches.
>>>>
>>>> I tested them one by one and they should be OK now. Same place:
>>>>
>>>> https://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>> When trying to apply this patch to trunk I get:
>>>
>>>   malformed patch at line 2048: Index:
>>> main/python/python-2.7.15-msvs9.patch
>>>
>>> (It would be nice if you could create a Pull Request on GitHub)
>> Indeed that patch causes issues due to Windows LF characters. I
>> overruled the issue in git and sent the Pull Request:
>>
>> https://github.com/apache/openoffice/pull/23
> Thanks!
>
> What revision is this patch based on?
> I see a lot of commits that are already in trunk for longer time...
> (However, they should be ignored when merging?)

It's straight from recent git clone but I applied the changes manually.
Some crap crept into external_dps.lst but I cleaned them up with
successive commits.

Do feel free to ignore any irrelevant change that might have crept in.

Pedro.



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

Re: Update to python-2.17

[Pedro Giffuni]

On 2020-01-10 13:24, Matthias Seidel wrote:
> Hi Pedro,
>
> Am 10.01.20 um 07:14 schrieb Pedro Giffuni:
>> Hi again;
>>
>> On 2020-01-04 05:16, Matthias Seidel wrote:
>>> Hi Pedro,
>>>
>>> Thanks!
>>>
>>> Unfortunately the build process just stops at some point (on Windows),
>>> no error codes I could give you.
>> The problems are usually related to getting the patches applied
>> correctly. There can be no hunks or mismatches.
>>
>> I tested them one by one and they should be OK now. Same place:
>>
>> https://people.apache.org/~pfg/patches/patch-python-2.17.diff
> When trying to apply this patch to trunk I get:
>
>   malformed patch at line 2048: Index:
> main/python/python-2.7.15-msvs9.patch

This shouldn't happen because all -2.7.15 are removed in the patch and
replaced with 2.7.17 versions.

% ls python
makefile.mk
prj
python-2.7.17-msvs9-dir.patch
python-2.7.17-msvs9-no-host-python.patch
python-2.7.17-msvs9-python-path.patch
python-2.7.17-msvs9-subsystem.patch
python-2.7.17-msvs9-win64-target.patch
python-2.7.17-msvs9-win64.patch
python-2.7.17-msvs9.patch
python-2.7.17-nohardlink.patch
python-2.7.17-sysbase.patch
python-freebsd.patch
python-md5.patch
python-solaris.patch
python-solver-before-std.patch
python-ssl.patch
pyversion.mk
pyversion_dmake.mk

FWIW, I used "svn diff --patch-compatible", to generate the patch.

> (It would be nice if you could create a Pull Request on GitHub)

This would indeed by much easier for me. I'll do that!


Pedro.
> Regards,
>
>    Matthias
>
>>> According to https://www.python.org/downloads/release/python-2717/ this
>>> is the "penultimate" release, so maybe there will be a final 2.7.18?
>> Yes, there will be a final release in a couple of months, but most linux
>> distributions (and FreeBSD) are already deprecating py27 and anything
>> that depends on it.
>>
>> Thanks for your patience!
>>
>> Pedro.
>>
>>> Regards,
>>>
>>>    Matthias
>>>
>>> Am 04.01.20 um 02:41 schrieb Pedro Giffuni:
>>>> Hi Matthias;
>>>>
>>>> Sorry about that. I could've tested better the patch. I will fix the
>>>> obvious issues and will let you guys know.
>>>>
>>>>
>>>> Pedro.
>>>>
>>>> ps. It may take me a while though, I am getting busy very fast :(
>>>>
>>>> On 2020-01-01 21:30, Pedro Giffuni wrote:
>>>>> Hello AOO devs and best wishes for the New Year!
>>>>>
>>>>> Well ... time has passed and Python 2 is now deprecated!
>>>>>
>>>>> I have a patch here to update AOO 4.2's version of Python to the latest
>>>>> (perhaps last) release in that line:
>>>>>
>>>>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>>>
>>>>> This is a remake of the previous update that I had made for
>>>>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>>>>> with git so please someone else will have to test and commit.
>>>>>
>>>>> On the near term, we really should update to Python 3, but that will be
>>>>> challenging for the build system since it requires a newer version of
>>>>> the MS compiler.
>>>>>
>>>>> Building with an external python is also currently broken for python
>>>>> versions >= 3.6.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Pedro.
>>>>>

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

Re: Update to python-2.17

[Pedro Giffuni]

Hi again;

On 2020-01-04 05:16, Matthias Seidel wrote:
> Hi Pedro,
>
> Thanks!
>
> Unfortunately the build process just stops at some point (on Windows),
> no error codes I could give you.

The problems are usually related to getting the patches applied
correctly. There can be no hunks or mismatches.

I tested them one by one and they should be OK now. Same place:

https://people.apache.org/~pfg/patches/patch-python-2.17.diff

> According to https://www.python.org/downloads/release/python-2717/ this
> is the "penultimate" release, so maybe there will be a final 2.7.18?

Yes, there will be a final release in a couple of months, but most linux
distributions (and FreeBSD) are already deprecating py27 and anything
that depends on it.

Thanks for your patience!

Pedro.

> Regards,
>
>    Matthias
>
> Am 04.01.20 um 02:41 schrieb Pedro Giffuni:
>> Hi Matthias;
>>
>> Sorry about that. I could've tested better the patch. I will fix the
>> obvious issues and will let you guys know.
>>
>>
>> Pedro.
>>
>> ps. It may take me a while though, I am getting busy very fast :(
>>
>> On 2020-01-01 21:30, Pedro Giffuni wrote:
>>> Hello AOO devs and best wishes for the New Year!
>>>
>>> Well ... time has passed and Python 2 is now deprecated!
>>>
>>> I have a patch here to update AOO 4.2's version of Python to the latest
>>> (perhaps last) release in that line:
>>>
>>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>>>
>>> This is a remake of the previous update that I had made for
>>> cpython-2.16, but which no one tested ! I currently lack an AOO setup
>>> with git so please someone else will have to test and commit.
>>>
>>> On the near term, we really should update to Python 3, but that will be
>>> challenging for the build system since it requires a newer version of
>>> the MS compiler.
>>>
>>> Building with an external python is also currently broken for python
>>> versions >= 3.6.
>>>
>>> Regards,
>>>
>>> Pedro.
>>>

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

Re: Update to python-2.17

[Pedro Giffuni]

Hi Matthias;

Sorry about that. I could've tested better the patch. I will fix the
obvious issues and will let you guys know.


Pedro.

ps. It may take me a while though, I am getting busy very fast :(

On 2020-01-01 21:30, Pedro Giffuni wrote:
> Hello AOO devs and best wishes for the New Year!
>
> Well ... time has passed and Python 2 is now deprecated!
>
> I have a patch here to update AOO 4.2's version of Python to the latest
> (perhaps last) release in that line:
>
> http://people.apache.org/~pfg/patches/patch-python-2.17.diff
>
> This is a remake of the previous update that I had made for
> cpython-2.16, but which no one tested ! I currently lack an AOO setup
> with git so please someone else will have to test and commit.
>
> On the near term, we really should update to Python 3, but that will be
> challenging for the build system since it requires a newer version of
> the MS compiler.
>
> Building with an external python is also currently broken for python
> versions >= 3.6.
>
> Regards,
>
> Pedro.
>

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

Update to python-2.17

[Pedro Giffuni]

Hello AOO devs and best wishes for the New Year!

Well ... time has passed and Python 2 is now deprecated!

I have a patch here to update AOO 4.2's version of Python to the latest
(perhaps last) release in that line:

http://people.apache.org/~pfg/patches/patch-python-2.17.diff

This is a remake of the previous update that I had made for
cpython-2.16, but which no one tested ! I currently lack an AOO setup
with git so please someone else will have to test and commit.

On the near term, we really should update to Python 3, but that will be
challenging for the build system since it requires a newer version of
the MS compiler.

Building with an external python is also currently broken for python
versions >= 3.6.

Regards,

Pedro.


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

Re: C++ standard when building OpenOffice

[Pedro Giffuni]

Hi;

Some notes, which I don't expect will be particularly useful ...

- I recall one of the reasons for using Boost and not the native STL was 
that the old MSVC compiler (the one AOO still uses) is poor on standards 
compliance. It may be that the internal Boost can be updated a bit more 
but it has to be tested on the Windows build.


- Microsoft's STL implementation is now open source and clang is supported:

https://github.com/microsoft/STL

- While FreeBSD PowerPC is a moving target, the destination is clang, 
spending time on the GCC build there is probably a waste of time:


https://wiki.freebsd.org/powerpc/llvm-elfv2

- Rust is really interesting :).

Pedro.



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

Python 2.7.16 update

[Pedro Giffuni]

Hello guys;

I never had the time to test?? a minor update to Python.

From the update notes it doesn't seem urgent, but feel free to give it 
a spin and commit if ready:


http://people.apache.org/~pfg/patches/patch-python-2.16.diff

Cheers,

Pedro.



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

Re: get Revision from Git (short Hash)

[Pedro Giffuni]

Hello;

Unfortunately including the date breaks reproducible builds:

https://reproducible-builds.org/docs/timestamps/

I suggest to try using the the SOURCE_DATE_EPOCH environment variable 
if/when it is defined.


Thanks,

Pedro.


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

Re: beanshell

[Pedro Giffuni]

Hi 

Sorry for noticing late.

beanshell was relicensed under an Apache License starting with bsh 2.0b5.

Apparently I had something to do with breaking the beanshell build 
(thanks for fixing): on FreeBSD we use the external (prepackaged) 
beanshell which is 2.0b6.


Pedro.


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

Re: Future development discussion

[Pedro Giffuni]

Win64 is also making good progress behind the scenes. The uncommitted Win64
UNO bridge I've been coding (a lot of it in AMD64 assembly) should now be
able to call arbitrary C++ methods from UNO and UNO methods from C++ (not
tested yet), but the poorly documented internals of MSVC C++ exception
handling are still TODO.

I also played a bit with mingw-w64 (an independent and alternative
mingw-like project capable of producing both Win32 and Win64 binaries) as
an alternative C++ compiler on Windows, but its MSYS2 environment can't
easily replace Cygwin due to using /c instead of /cygdrive/c, so a
tremendous amount of patching configure.ac, set_soenv.in, and many Perl
scripts that assume /cygdrive would be required. Using Cygwin instead of
MSYS2 might be more successful, but since GCC has different exception
handling to MSVC, Windows builds would need to be debugged with gdb instead
of Visual Studio, and AOO extensions would need to be built with mingw and
would be incompatible with the MSVC extensions. Also either we would need
the ship the GCC C and C++ runtimes, or link them statically and have
bloated binaries. It's worth noting LO gave up on mingw.

Where mingw could really help though, is building Windows binaries quickly
for testing purposes. Since Windows builds very slowly, and *nix builds
quickly, we could build a Windows version on *nix at *nix speeds by
compiling it in this setup:
mingw
Cygwin
Wine
*nix
;-)

We could also try a more ambitious setup of Windows Platform SDK in place
of mingw there, but how well it works on Wine is an open question.

FWIW, clang-cl from LLVM is really easy to install:

http://www.llvm.org/builds/

The thing is, libc++ hasn't been ported yet to Windows, so it depends on 
the Visual Studio libraries for everything.


All in all it is likely a better option than mingw, or cygwin.

Pedro.

Future development discussion

[Pedro Giffuni]

Hi again;

I just wanted to stop by and share some ideas of things that need to be 
done in AOO after 4.2.


Easier things:

OpenSSL has to be updated, yet again, and while the future versions will 
be under an Apache License, making things nicer for us, the API has been 
changing so we may need some adaptations to work with future versions.


Python 3: our compiler toolchain for MS-Windows is ancient enough that 
it is difficult to update internally to a recent Python 3 version. We 
have been supporting python 3 through external packages: configuring the 
AOO to build with Python 3 worked but, as found be FreeBSD's builds, it 
recently broke. I don't have more details this needs more investigation 
(and fixing).


And now the tougher thing:

I absolutely appreciate the huge effort Damjan has been doing with the 
build system: getting rid of Dmake is a viable objective that needs to 
be pushed forward.


I have been playing a bit with clang-cl, which appears to be the only 
opensource compiler that can work with native windows binaries: it 
integrates into MS-Visual Studio but it requires CMake. I also happen to 
have met a developer of the Bazel build system which seems interesting 
and would suit our purposes in many ways but I have no interest in 
having long discussions about build systems. The central thing that we 
*have* to do is update the windows toolchain: MSVisual Studio 2015 seems 
to be the minimum that is suficiently popular and basically required 
nowadays.


After that, there is a huge technical debt. Of course, pivot charts, 
newer ODF and better docx support would be very nice to have but without 
the proper tooling, especially on Windows, we have one hand tied.


All just my 0.02$.

Pedro.



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

Re: AOO 4.2.x development branch created

[Pedro Giffuni]

Hey guys!

Thank you to everyone getting involved in the new release. It is very 
much needed and I was really tired of the continuous revamping of the 
4.1 releases. It is now clear that we are also doing proper branching of 
the releases.


Some of the issues off the top of my head that you may want to mention 
on the Release Notes:


- All the fonts have been updated. We also added two fonts Caladea and 
Carlito which are geometrically compatible to Microsoft Cambria and 
Calibre.


- Python was updated to 2.7.15. Hunspell was updated to 1.3.3.

- Cleanups for many, many typos everywhere.

- Fixed many issues detected by Coverity scan.

There are many more changes that I surely forgot about.

Pedro.

[HEADS UP] Python update coming to trunk.

[Pedro Giffuni]

Hello guys;
I have an update to the internal python 2.7.14 -->2.7.15 that will likely hit 
the tree later today.The change is not major but it is important due to 
security updates.
 So far it has only been tested on FreeBSD. I don't expect major adjustments 
for other platforms: In AOO we generally only touch some old files related to 
the msvc9 build. 
Still, the win64 patches are somewhat more difficult to follow since they apply 
on top of other patches so I will make no claims.
Builders beware, keep calmed tone when reporting .. and be patient ... 
otherwise, just enjoy.

Pedro.

Re: Memory management strategy

[Pedro Giffuni]

On 3/25/2018 10:44 AM, Pedro Giffuni wrote:
> Somewhat related ...
> 
> I have been considering the use of APR pools:
> 
> http://www.apachetutor.org/dev/pools
> 
> It would be great to have the memory managed by the same technology used 
> in Apache httpd.


I need to think about this. It seems very appropriate for transaction
processing. I am not so sure it is a good fit for AOO.


We do a lot of different memory processing in AOO: in some cases it may 
be more useful that in others.


For the time being I was only looking at using pools to replace some 
malloc()/calloc()s in SAL but I haven't found time to do a PoC.


Pedro.

Re: First steps in building with MSVC 14 / Visual Studio 2015

[Pedro Giffuni]

Hi again;

On 03/13/18 13:10, Pedro Giffuni wrote:

Hi Damjan;

Glad to see this progress! To build python with newer versions of 
MSVC, you may have to change the BUILD_DIR to "PCbuild".


Look at main/python/makefile.mk line 125.



I committed a small adjustment in r1826694, to clarify better the situation.

I don't have a way of testing the windows build so feel free to revert 
if I managed to break things in some spectacular way :-/.


Cheers,

Pedro.


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

Re: First steps in building with MSVC 14 / Visual Studio 2015

[Pedro Giffuni]

Hi Damjan;

Glad to see this progress! To build python with newer versions of MSVC, 
you may have to change the BUILD_DIR to "PCbuild".


Look at main/python/makefile.mk line 125.

Cheers,

Pedro.

ps. As a reminder, the ASF has access to MSDN in case someone wants to help.


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

Re: Win64 port started, and how building 32 bit AOO on Win64 could break soon

[Pedro Giffuni]

Hi Damjan;

I personally think it would be better to start by upgrading MSVC, but in 
any case...

Here are some hints from LibreOffice:

http://tml-blog.blogspot.com.co/2011/03/

Cheers,

Pedro.


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

Re: Ubuntu 14.04

[Pedro Giffuni]

Hi Jim,


Playing around w/ building 4.1.5 and 4.2.0 on Ubuntu 14.04...
Will update the wiki as required (already found 2 dependencies
we were missing)


This is good news, as this is the platform used by travis-ci:

https://docs.travis-ci.com/user/reference/overview/

Any chance you could get to setup the github repo to do the automated 
builds?


This would be a good step to get back into coverity, eventually.

Pedro.


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

Re: A more sane way to build - SCons, deCygwination and other hopes

[Pedro Giffuni]

Hello everyone!

Just my $0.02


Hi

After days of failing to add a few new simple features to gbuild, I've now
reached my limits, and have begun experimenting with the SCons build system
instead.

It's starting to work. Having ported some of gbuild.mk, LinkTarget.mk and
platform/freebsd.mk to SCons, as well as a module's local gbuild files, I
can now compile files and (badly) link them into libraries, and clean the
build.


I am fine with bringing yet another build system, specially since we 
need this one to update Apache serf.


Of course the objective should still be to remove dmake, so my request 
to Damjan, would be to move python ASAP to  gbuild. I can understand us 
needing gbuild and Scons but we should be able to build SCons, and any 
other build system, without dmake.


Regards,

Pedro.

Re: [VOTE] Release Apache OpenOffice 4.1.4-RC4 as GA

[Pedro Giffuni]

+1 (non binding)

It’s about time ;).

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

report builder jar files

[Pedro Giffuni]

Hi Don;

> I'm attempting to update the FreeBSD openoffice-devel port, which is a
> snapshot of trunk, and add an option to enable the report builder
> extension.  That requires a whole bunch of .jar files.  Where should I
> get those?
…

Sometime ago I preventively copied them to our ooo-extras sourceforge mirror:

https://sourceforge.net/projects/oooextras.mirror/files/

I have no idea if I got them all, and the files appear to have never been 
downloaded, so it’s all untested.
Perhaps someone in the community, more used to that extension can check ?

Regards,

Pedro.

Re: Increase minimum Java version from 5 to 7/8 ?

[Pedro Giffuni]

Hello guys;

While updating the java requirements, please someone remove StaX API 
(main/stax) from the build. I recall it was only used for Java versions < 5.


Pedro.


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

Merge wish list for AOO 4.1.4

[Pedro Giffuni]

Hello;

Well I haven't hidden my lack of love for AOO 4.1.4: it's been like two 
years of development in trunk with none of it finding it's way into the 
release.


Last year I sort of went on with it because 4.1.4 was supposed to be 
inminent, but since it's taking so long I made a list of merges from 
trunk that I'd like to suggest. The idea is not to match 4.2.0 or even 
to modernize AOO, but at least to provide some incremental value against 
4.1.3.


Fonts

Proposal: Update ChromeOS fonts from 1.21.0 to version 1.23.0 (trunk has 
1.31.0)


Merge r1651397 (if feeling adventurous trunk has updated all fonts and 
added new ones).


OpenSSL

Proposal: Update it from 0.9.8zg to 0.9.8zh (trunk has 1.0.2h)

Merge: r178, r1722238, r1722239

Python

Proposal: Update it from 2.7.6 to 2.7.8 (trunk has 2.7.13)

Merge: r1722635

Misc fixes

r1779672, r1779758 fixes issues found with clang 4.

r1779875 permits building AOO with newer hunspell.

_

This is just off the top of my head, trunk/4.2 has many other nice 
fixes/updates than I can't list here.


Pedro.


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

Re: Please someone release 4.2.0 (or something else ...)

[Pedro Giffuni]

Hello;

Testing on the Mac is specially welcome. I am not sure the gbuild 
changes have been tested well there, so that's something to look at.


I think it may be a good idea to use "--with-alloc=system",and that
applies to 4.1.x as well.

Pedro.


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

Please someone release 4.2.0 (or something else ...)

[Pedro Giffuni]

Hi guys;

It seems like the imminent release of 4.1.4 got stuck and it is not
clear if it will happen or when. Sadly, I don't really see anything 
interesting that 4.1.4 will add to 4.1.3.


I find it terribly demotivating to spend time on AOO's trunk when it's
not clear if it will see the light of a release and there is basically
no chance to merge the interesting updates (or even the fonts) to 4.1.4.

Can you please reconsider releasing 4.2.0? It doesn't really matter if
you want to take longer for the release cycle but at least we would all
be on the same page.

Pedro.


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

Re: OpenOffice Windows builds

[Pedro Giffuni]

FWIW,

Porting OpenOffice to MSVC 2015 is not an easy task, porting to MSVC 
2010, OTOH should be reasonably simpler and likely doable.


I am not volunteering though :-P.

Pedro.


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

Re: Access to the OpenOffice Buildbot boxes

[Pedro Giffuni]

Hello;

Just IMHO.. it would be very valuable for our build experts to take a 
look at travis-ci (through github) and getting Coverity back up.


Pedro.

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

Re: AOO now builds with Clang on Linux

[Pedro Giffuni]

Hi Damjan;

Looking at the log I was wondering what exactly clang 1.8 was and
I took the liberty of fixing the mismatch ;).

FWIW, AOO should now work fine with clang 3.9.1. Clang 4 reveals
allocation issues. If someone is wondering why we/you should be using
clang, note that the FreeBSD buildbot takes 4 hours to build AOO,
while the linux buildbot takes 10.

Regards,

Pedro.

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

Re: [lazy consensus] FreeBSD as a new supported platform?

[Pedro Giffuni]

Some misc. comments:

In reply to Peter Kovacs;


Would it be more wise to go for BSD as OS instead of one distribution
FreeBSD? Or are BSD variants incompatible to each other?


BSD variants are certainly incompatible with each other as the result
of about 25 years of divergence.

AFAICT, the only two BSD variants that currently can build AOO are
FreeBSD and Darwin (AKA MacOSX), which happens to be a FreeBSD
derivative. We have some build support for NetBSD but it hasn't been
tested in ages.

I wonder, do we really support all linux variants? I think the buildbots 
cover very old versions of CentOS, do we have confidence with such level 
of testing?


In reply to Marcus (and orcmid);


And it is crucial that the hashes and signature files *not* be mirrored.  
Having them

only available at dist.apache.org is the secure way to detect that the 
mirror-downloaded binary
is authentic and unaltered.

right, we as OpenOffice project we should make sure that we refer only
to our own files and servers. So, I hope that there is no faulty link. ;-)


I find the notion of depending on your own servers and hashes to certify 
binaries rather outdated. The correct approach is having

reproducible builds so that *anyone* building a given source revision
can verify that neither the server nor the code suppliers have been
compromised. See:

https://reproducible-builds.org/ (and look for the wonderful talks
in youtube, involving demos with compromised compilers or 1 bit
changes that involve backdoors).

This does depend up to a certain level on the OS build environment
supporting it.

BTW, I updated the log in r1780202, to note there is an ongoing discussion.

Pedro.

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

Re: svn commit: r1780202 - /openoffice/trunk/main/README

[Pedro Giffuni]

Hi Marcus;

On 01/25/17 23:41, Marcus wrote:



In general the addition is OK. However, there is not yet agreement what
"supported" means. So, just to add FreeBSD to the list doesn't work as
it's not the same as for Win, Linux, Mac where we have a different
definition.

Marcus


I avoided making comments on things that have not been decided (and
that may even not ever be decided).

I think there is clear consensus that FreeBSD is in some way supported
and that Windows deserves to be in the top of the list.

For all I know we do more testing on FreeBSD than on MacOS so I placed 
it there but I admitted it is something subjective.


Feel free to make any other adjustment or clarification before 4.2.0
is released.

Regards,

Pedro.

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

Re: [lazy consensus] FreeBSD as a new supported platform?

[Pedro Giffuni]

On 01/24/17 , Marcus wrote:

Am 24.01.2017 um 22:47 schrieb Pedro Giffuni:

Our README states that currently supported platforms include: Windows,
MacOS X, Linux variants and OS/2. I would like to add FreeBSD to the
list. I have no idea if such status requires some formal procedure so I
will ask here:


I don't know every ASF policy. But I would guess it's up to the PMC to
define it. And we don't have a formal procedure.



Yes, I was wondering if there was some OOo guidelines we could follow.


But I think we should agree commonly what "supported platform" means and
what we understand. So, a short list of requirements would be helpful.
This will then be put into the Wiki for future reference.


FreeBSD is AFAICT, the only OS that ships AOO in it's official releases,
we have also been adding new features including (recently) support for
the PowerPC. This would not imply the ASF doing binary releases,
although we have a buildbot and I would expect, and it fact it happens,
that there is developer diligence in fixing breakages it detects.


Here I see some points for the requirements list. And "supported" could
mean it's not automatically available for download.



Well, I understand Apache Projects define binaries as release
"artifacts" and not part of a  a release itself. What matters is the
sourcecode release, so technically speaking binary releases are not 
critical.


There's also the issue that we don't (yet) support reproducible builds,
so even if we sign binaries, our binaries are not trustable.


Would anyone have some insight about any particular policy within the
project, or perhaps can I go ahead and add FreeBSD to the list for 4.2?


I see it as what Andrea and Matthias wrote so far. But I would say,
let's discuss what we want.



I agree with Andrea that there are different levels of what one could 
consider "support". If we just consider our capacity to generate

binaries and test them, I would say both OS/2 an MacOS X are under risk
of becoming unsupported in the near future.


BTW:
Offering binary builds for FreeBSD doesn't make sense as the normal way
would be to get the OpenOffice as source (the so-called ports) from a
FreeBSD server, compile it yourself and then just use it. So,
downloading and installing binaries is not the normal way. Do I remember
right?



I certainly don't want/need binary releases for FreeBSD. "Support" in 
FreeBSD's case would be something mostly symbolical, an indication

that OpenOffice in FreeBSD is expected to perform as well as in linux.

A parallel question is what supporting officially a platform involves:
it would mean we are willing to issue CVE's if the platform is affected,
and perhaps also that an error on such selected platforms may be 
considered a release blocker. We don't really follow any of those

criteria for OS/2, and when 4.2.0 was discussed we were about to
overrule the later for MacOS X.

As food for thought: my guess is that supporting officially a platform
should also merit some specific field when reporting bugs in bugzilla.

Just my $0.02,

Pedro.

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

[lazy consensus] FreeBSD as a new supported platform?

[Pedro Giffuni]

Hello;

Our README states that currently supported platforms include: Windows, 
MacOS X, Linux variants and OS/2. I would like to add FreeBSD to the 
list. I have no idea if such status requires some formal procedure so I 
will ask here:


FreeBSD is AFAICT, the only OS that ships AOO in it's official releases, 
we have also been adding new features including (recently) support for 
the PowerPC. This would not imply the ASF doing binary releases, 
although we have a buildbot and I would expect, and it fact it happens, 
that there is developer diligence in fixing breakages it detects.


Would anyone have some insight about any particular policy within the 
project, or perhaps can I go ahead and add FreeBSD to the list for 4.2?


Regards,

Pedro.



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

Re: Google Summer Of Code 2017

[Pedro Giffuni]

BTW, JFYI ...

Last time I tried to mentor for the ASF, I was told I had to ask the PMC
and get their OK first.

Pedro.

On 01/22/17 20:38, Pedro Giffuni wrote:

Hi Yakov;

I have mentored previously for other organizations. I could consider
mentoring this year if there is an interesting project.

Regards,

Pedro.


Is it planned in this season participated Apache Open Office in Google
Summer Of Code ?
https://opensource.googleblog.com/2017/01/now-accepting-organization-applications.html


--
Yakov Reztsov


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

Re: Google Summer Of Code 2017

[Pedro Giffuni]

Hi Yakov;

I have mentored previously for other organizations. I could consider 
mentoring this year if there is an interesting project.


Regards,

Pedro.


Is it planned in this season participated Apache Open Office in Google Summer 
Of Code ?
https://opensource.googleblog.com/2017/01/now-accepting-organization-applications.html

--
Yakov Reztsov


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

Re: Jars for Report Builder: where to get them ?

[Pedro Giffuni]

Nevermind .. I found them.

On 01/14/17 11:05, Pedro Giffuni wrote:

Hi;

Anyone has the jars required by the report builder [1]?

I think we should upload them to a folder in ooo-extras.

Regards,

Pedro.

[1]
http://openoffice.2283327.n4.nabble.com/About-reportbuilder-source-code-td4672788.html



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

Jars for Report Builder: where to get them ?

[Pedro Giffuni]

Hi;

Anyone has the jars required by the report builder [1]?

I think we should upload them to a folder in ooo-extras.

Regards,

Pedro.

[1]
http://openoffice.2283327.n4.nabble.com/About-reportbuilder-source-code-td4672788.html

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

Re: future of OpenOffice

[Pedro Giffuni]

Quoted from the posting from Simon Phipps dated 12 Jan 2017:
...


The Document Foundation takes much of the Apache OpenOffice AL2 licensed
software and rebases LO on it. This allows integration of OpenSymphony
code. Completely permissible under the AL2. They re-did the license of all
the source as MPL2 changing the headers. Some think that this is shady
although permitted. In effect this prevents LO updates from being
contributed back to AOO.


Ignoring the tricky wording, I should clarify that TDF has no power to 
"redo" any licensing. The attempt to re-license was evidently done by a 
non-lawyer and checking the git history you don't have to be a legal

genius to notice it.

I will go on and claim, without this being legal advice b/c IANAL, that 
the license situation of LO is unclear, rather risky and even very

likely to be unenforceable. So no, it is simply impossible for an
Apache project to take any significant code under such conditions.

Even within the ASF, where we have clear methodologies to manage the IP
consistently, the licensing was not completely clean until recently.

This said, end users don't really care much about licensing as
long as the code does what they need. The code in OpenOffice is not very 
nice to work with and, while I don't follow closely, I think they have 
been doing a tremendous effort to clean it up, they have passed their 
code through sanitizers and other practices that are really

important before doing more mature work. I suspect I will need an Office
suite for arm64 in the future so I may end up using it although not
developing it.

Just my $0.02, I don't care much about this thread.

Pedro.

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

Re: svn commit: r1777198 - /openoffice/trunk/main/configure.ac

[Pedro Giffuni]

Hi Don;


On  3 Jan, p...@apache.org wrote:
> Author: pfg
> Date: Tue Jan  3 18:37:15 2017
> New Revision: 1777198
>
> URL: http://svn.apache.org/viewvc?rev=1777198=rev
> Log:
> Ignore the OS when checking for the ARM target.
>
> Linux is not the only ARM target - see i117017.

Won't we also need FreeBSD/ARM bridges code?


Since r1777057 we have (untested) FreeBSD/ARM bridges code :).

Pedro.


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

FYI: github mirror is broken

[Pedro Giffuni]

FWIW,

The github mirror stopped updating the source tree over 10 months ago.

Cheers,

Pedro.

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

Re: Reproducible builds ...

[Pedro Giffuni]

Hi;

On 12/21/16 11:54, Pedro Giffuni wrote:

Hello;

It would be important to work on Reproducible builds:

https://reproducible-builds.org/

The first issue to be resolved is that the executable should NOT carry
the date it was built. We could carry the SVN revision value instead.

Perhaps someone may be interested in hunting down here the date is
introduced in the "About" box?



I hunted it down with some patience and it ended up being not difficult
after all. After r1775936 we should not be embedding dates anymore.

I can't really claim we are within reproducible builds though, someone
has to build it a couple of times and run a binary diff over the
packages.

Merry Christmas!

Pedro.


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

Reproducible builds ...

[Pedro Giffuni]

Hello;

It would be important to work on Reproducible builds:

https://reproducible-builds.org/

The first issue to be resolved is that the executable should NOT carry 
the date it was built. We could carry the SVN revision value instead.


Perhaps someone may be interested in hunting down here the date is 
introduced in the "About" box?


Regards,

Pedro.

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

Re: OpenOffice on KDE 4 issues

[Pedro Giffuni]

Hello;

Interesting (I use KDE but have never enabled the KDE option).

FWIW, there is/was a KDE4 CWS in the archive:

https://bitbucket.org/mst/ooo340/branch/default?head=4cb6c97c0ec77613a9501fca04793f23a982adbb

Regards,

Pedro.

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

Re: SVN broken and unable to revert bad commit

[Pedro Giffuni]

Hi Damjan;

Strange ... I just made the revert for you, without any problem.

Pedro.

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

Re: Is there still someone who build for Solaris/Openindiana

[Pedro Giffuni]

-1
I doubt the "simplifications" are sufficient to make the code any more 
readable.

Much better to spend time on something else, like updating hunspell.

Pedro.

On 06.12.2016 18:31, Patricia Shanahan wrote:

On 12/6/2016 1:55 AM, Raphael Bircher wrote:

Hi all

I'm going to the configure script and I recognize that there are still
parts for solaris. As far as I know, the last version who build with
solaris was the AOO 3.4.x. My question is, if we should ride off the
Solaris stuff or we should keep it. Well it won't hurt to keep it, but
it makes also no sense to keep a platform no one build.


I did make some moves towards Solaris building, but I feel at this
time that learning AOO internals and working on debug is a better use
of my AOO time.

I tend to assume that anything that is not being actively maintained
and tested does not work. We need to simplify the build process. I
suggest getting rid of the Solaris stuff, as a separate commit with
"Solaris" in the log message. That way, if anyone decides to pick it
up they will be able to find the last state easily.


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

Re: Is there still someone who build for Solaris/Openindiana

[Pedro Giffuni]

FWIW;

I think OpenIndiana still ships an older version of AOO:

https://www.openindiana.org/

You may ask Alexander Pyhalov: I did merge a bunch of his patches (with 
changes) into AOO so it may be easier to build nowadays although it is 
surely a bumpy road.


Pedro.

Re: Meson: yet another build system

[Pedro Giffuni]

Objective C? Yacc? Cygwin? Custom compiler flags to disable C++ exception
handling, build some files with optimizations disabled?

Our build systems are not our biggest problem. Meson, or SCons, or others,
could be good if we were starting a new project. We aren't. We are
maintaining one we poorly understand.



I agree the build system is not our biggest problem.


Porting to Meson will not be any easier than porting to gbuild. Writing
gbuild code becomes easy with practice. *Understanding* dmake / build.lst /
d.lst is hard...



So you are now a fan of gbuild? ;).

Moving python would be a huge step forward towards getting rid of dmake
as it seems to be required for any alternative build system (other than 
gbuild which of course would require it to build with gbuild anyways).



I've spend the last day trying to port several more modules to gbuild. I've
succeeded with main/fileaccess, main/io and main/package, but ran into
walls with main/rdbmaker and main/store. Dmake apparently has ways to name
libraries that gbuild can neither produce nor find (eg. libstore.so.3,
libreg.so.3). These culprits use the evil UNIXVERSIONNAMES setting which
generates such names:

cppu
cppuhelper
jvmaccess
jvmfwk
registry
salhelper
sal
store




Jikes.

Pedro.



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

Re: serf has wrong download link in the bootstrap

[Pedro Giffuni]

Fixed in r1772065.

FWIW, I think it was not visible, as in breaking the build, because it
was falling back to the sourceforge site.

Pedro.

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

Meson: yet another build system

[Pedro Giffuni]

http://mesonbuild.com/


 Features

 * multiplatform support for Linux, OSX, Windows, Gcc, Clang, Visual
   Studio and others
 * supported languages include C, C++, Fortran, Java, Rust
 * build definitions in a very readable and user friendly non-turing
   complete DSL
 * cross compilation for many operating systems as well as bare metal
 * optimized for extremely fast full and incremental builds without
   sacrificing correctness
 * built-in multiplatform dependency provider that works together with
   distro packages
 * fun!

Re: Building with the latest SDK on Windows

[Pedro Giffuni]

Hi Raphael;

I would expect trouble building with the latest MSVC: at least python
requires some changes in the build support and it may also involve
losing support for Windows XP.

I think it should be possible, and advantageous, to update to MSVC 2010
first. Note that Apache committers have access to the MSDN but the
process to get access to it has changed a couple of times. Someone in
the PMC should know ;).

Pedro.

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

Re: Code signing available for OpenOffice

[Pedro Giffuni]

FWIW,

I attended the code signing related talk at ApacheConEU 2014.

While it only applied to Windows, I think it is important to
sign binaries: AOO is a wide target for the wares sites and
it's a matter of fact they may add spyware.

I suspect the App Store won't be available to us since they
usually ask for sandboxing and we would not be able to access
Java or provide Python.

Pedro.

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

Discussion for ApacheConEU

[Pedro Giffuni]

Hello;

At this time I can say I will very likely be at ApacheConEU, 
independently of my talk being accepted or not (thanks to TAC!).


Depending on how many of us attend, I think we should take the
chance to have a round-table discussion, similar to the one we had
at ApacheconEU 2012. The idea is NOT a closed-door discussion about
how we will take over the world yet again, or how we will coerce
other projects to see the light, but it is generally more fluid
to have direct face to face discussion and planning and we get
few chances that are better at that than ApacheConEU.

I won't have much time to prepare anything formal, and we regularly
don't take decisions off-line anyways, so I would propose to
consider moving into a tighter integration with github:

https://blogs.apache.org/infra/entry/improved_integration_between_apache_and

We should also move to JIRA as infra has worked tighter with the 
integration.  This would also mean enabling travis-ci and Coverity

in addition to the regular infra services.

The idea is simply to make the code easier to fork and develop 
independently, which will also incentivize further development

and cooperation with third-parties, something we haven't seen much
lately.

From a development POV, I consider it is critical for the project
to support newer MSVC versions.

I am personally not working on the future dot releases, but that
is something that may be discussed as well.

Regards,

Pedro.

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

Re: Fwd: [Issue 125147] CRASH applying styles to text

[Pedro Giffuni]

Hello;

I have no intent of getting in the way of 4.1.x (x >=3), I understand it 
is important for the project to show it's capacity to push out a new 
release in a short time.


OTOH, we were caught unprepared, as we had abandoned the 41 branch 
completely about 11 months ago.


Given this is already late you should probably reconsider bringing in 
some fixes to known bugs. If the idea is just that 4.1.3 = 4.1.2 + 
CVE-2016-15-13, then it seems to be a huge waste of bandwidth for both 
mirrors and end users.


All just IMHO,

Pedro.


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

Access denied on bugzilla ...

[Pedro Giffuni]

FWIW ...
I just tried to access BZ 127117, which I created in the first place, and now I 
got
"You are not authorized to access issue #127117."
It is only a very minor update to openssl, and I wanted to submit the patch to 
do it.(AOO bugzilla and I have never been in a good relationship).
While here I shall explain the intent of the two recent requests: it is clear 
that we won't release soon updated, and hopefully secure, versions of some very 
basic support libraries/utilities. At least doing some minor low-hanging-fruit 
updates should save some pain to our users and some embarrassment to the 
project. The changes are very conservative and have been tested for a while in 
trunk but are superseded by the versions in trunk.
I will let the RM and the security team determine if they are worth it.
Regards,
Pedro.

Re: 4.1.4 Release Manager?

[Pedro Giffuni]

Hi Patricia;

I am rather amazed by the idea of 4.1.4, shouldn't we release
4.2.0 instead? I mean ...

- I thought the idea behind 4.1.3 was to make a quick fix for
  4.1.2 and to give more time for the 4.2.0 release process.
- the code in trunk has over two years of development and is
  more secure than what lives in the 41* branch. It is rather
  disappointing to not see the code out sooner.

I believe you should continue as Release Manager for 4.1.4,
or 4.2.0; the changes for 4.1.3 will already have to be
included in future releases and we could benefit from the
momentum of the dot release. Your vacations should also
not be a problem as other people are likely to be in
vacations during December as well.

Pedro.


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

Re: Last call for 4.1.3 patches

[Pedro Giffuni]

In response to truckman;
>

On 14 Sep, Patricia Shanahan wrote:

Should this go in 4.1.3 or in 4.1.4?

4.1.3 will not be able to move on to building and testing unless we cut
off additions at some point. I think that point has already passed, but
I'm open to arguments.


Have all of the necessary download site changes made it from trunk to
4.1.3?  The released source tarball for 4.1.3 won't include anything in
ext_sources that comes from svn, so we need to verify that bootstrap
succeeds with an empty ext_sources directory.



The content of ext_sources should be irrelevant.  We temporarily used 
that directory when the project was in incubation but the idea was to

deprecate it much sooner. The dependencies were always meant to be
downloaded as part as the build process.



It would also be nice to merge r1758093 from trunk to update
configure.ac to suggest the proper download URL for the dmake source.
The old URL no longer works.


Yes, that certainly should be done.

Pedro.

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

Re: Differentiate or Die

[Pedro Giffuni]

Hi Jörg;

...

> From: Pedro Giffuni [mailto:p...@apache.org]

> The thing about so-called "marketing gurus" is that their assumptions
> about how the markets work may break down when we are talking about
> software that has zero cost.
>
> I will simplify the marketing issue making a bold statement: "We have
> millions of users because we do 80% of what the market leader
> does but
> with 0% of the price."


No, the success of free software is not a question of price.


The success of free software is based on many things, of which price is 
only one of them. In the case of OpenOffice I sustain that the main 
factor for success is that end-users perceive it as free as in price. 
That and not the fact that we have less developers than other projects 
or that we are not being distributed in major linux distributions 
accounts for the project being successful today.




The development model of free software is something else, but it's not free. 
That is not the
goal.

read:
https://www.gnu.org/philosophy/selling.en.html


The GNU copyleftists have always struggled with economics but that is 
rather off-topic.


The notion of living on distribution costs is a dead end from a gone 
era. Distribution costs have diminished hugely with the Internet, in 
such a way that even commercial producers sell more software online than 
on CDs. Have you ever paid for using GCC, or do you know anyone that 
would prefer clang because it's cheaper to download?


Nowadays, support is likely the mayor source of revenue for independent 
developers and publicity is the mayor source of revenue for content 
producers.




Furthermore:
The development and use of OpenOffice is not free, because developers have to 
be paid by their
companies or donate their own time. Users have cost for installation, 
maintenance and staff
training.
Absolutely, just compiling the code involves electricity costs, but the 
end user doesn't have to carry the burden. Many don't even know or have 
to be aware of the costs involved.


No one has really quantified the real cost of producing OpenOffice and 
then if we charged even just $1 we would more than cover what we spend 
in development (100 million in budget.. yay!).




The work of Apache is also not free, because Apache needs donations to be able 
to work.

For example see:
https://www.apache.org/foundation/sponsorship.html

on:
http://www.apache.org/foundation/thanks.html

you can see that the sum of the sponsorship is (currently, per year):

Platinum: 700,000$
Gold: 320,000$
Silver: 260,000$
Bronze: 90,000$



Such costs existed before OpenOffice was an Apache Project, and we can't 
at all quantify how much OpenOffice's value is for the Apache Software 
Foundation.


Have there been more donations thanks to OpenOffice? And then .. if 
Microsoft or Google make a donation to the ASF does it mean either of 
them is in direct support of OpenOffice?


Part of the appeal of the ASF is making use of Foundation resources like 
buildbots and mailinglists but noways anyone can fork they own codebase 
on github, enable travis-ci and distribute the code through other means. 
Money is important everywhere but it is not an absolute truth that 
opensource necessarily obeys market rules.


Pedro.

Re: Differentiate or Die

[Pedro Giffuni]

Hi Phillip;

The thing about so-called "marketing gurus" is that their assumptions 
about how the markets work may break down when we are talking about 
software that has zero cost.


I will simplify the marketing issue making a bold statement: "We have 
millions of users because we do 80% of what the market leader does but 
with 0% of the price." Yes, there are other software packages that 
comply with the same criteria and may even be better in some place, but 
we keep the same consistent interface and branding that people have come 
to love.


We *can* indeed still differentiate from *other-name*Office as long as 
we keep the application consistent with what our current users have come 
to love. In other words, we have to play conservative but we can 
innovate in the things that people don't see easily. OOXML is in that list.


About the license, it is certainly a strength. Not only it is finely 
recognized and permissive license, it is *one* license (well there are 
some minor pieces under other licenses but they are all permissively 
compatible). This quite honestly makes a difference as a starting point 
for other projects. LibreOffice, from the last time I looked, opted to 
obfuscate the parts of the code that are under ALv2 by just slapping 
MPLv2 on everything. This said, and IANAL so don't take this as legal 
advice, after the linux-vmware law suit it seems clear that restrictive 
licenses will be very difficult to enforce unless someone that ewants to 
enforce the licnese is getting copyright assignment.


If I had some resources, I think I would focus on the plugin mechanism, 
perhaps port some of LibreOffice features as extensions and encourage 
special purpose forks (I have also considered a personal closed-source 
fork as well). It would also be important to have some sandboxing 
capability there.


I just don't have resources for that, so for the time being I am toying 
with the idea of using APR to hijack the SAL layer, which would make AOO 
consistent with other Apache projects.


Pedro.


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

Re: OOo extras

[Pedro Giffuni]

On 09/03/16 11:07, Pedro Giffuni wrote:

Hello;

FWIW, the apache-extras.org site that carried the OOo extras tarballs
has been redirected to the sourceforge site. The oooextras.mirror site
at sourceforge has a circular reference to the OOO Extras Web Site that
is now redundant.

Someone with access, please upload the Python-2.7.12 tar ball for extra
safety.



And while there, the dejavu fonts version 2.37 may be a good idea too.

:)

Pedro.

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

Re: Presence at ApacheCon Europe, November

[Pedro Giffuni]

Hi Andrea;


Pedro Giffuni wrote:

I had already submitted a talk for this year's ApacheConEU


Ah, nice! An OpenOffice-specific talk or a generic one? I mean, would it
fit into a (hypothetical, of course; everything depends on reviewers)
OpenOffice track or not?



It is about random number generation, based on the OpenOffice 
implementation (and I may find time for some further improvements

in the following weeks).

I think I may give another one on a different subject as well, but this 
one would be unrelated to AOO.


Pedro.

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

OOo extras

[Pedro Giffuni]

Hello;

FWIW, the apache-extras.org site that carried the OOo extras tarballs 
has been redirected to the sourceforge site. The oooextras.mirror site 
at sourceforge has a circular reference to the OOO Extras Web Site that 
is now redundant.


Someone with access, please upload the Python-2.7.12 tar ball for extra 
safety.


Regards,

Pedro.


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

Re: Presence at ApacheCon Europe, November

[Pedro Giffuni]

> Hello guys;
>
> Before "the dramatic events of the last hours" I had already submitted a
> talk for this year's ApacheConEU (Sevilla is such a nice city to have a
> conference!).
>
> I understand that AOO people may feel discouraged now to attend but I
> don't really believe any form of boycott will serve the purpose of
> strengthening OpenOffice within the Apache Software Foundation. The best
> way to show support for the project is to engage with the wider ASF
> community, meet member of the Board and tell them that Apache OpenOffice
> is important. What the heck ... if we can't convince them ... get them
> drunk ;).
>
> I hereby suggest, and it's the easiest way to "save" the project AFAICT,
> that we release Apache OpenOffice 4.2.0 *during* ApacheConEU 2016.
>
> Just IMHO, with the latest updates (thanks truckman for the help) I
> think we are in pretty good shape for a Release; we could start making
> Release Candidates really soon now and make it so that we release the
> new version on November 16. Maybe it's a tight schedule but I also think
> we have been adding a lot of red tape to the process of making a
> release, which in theory is just a vote.

According to ASF release approval policy,
http://www.apache.org/dev/release#approving-a-release, "Before voting +1
PMC members are required to download the signed source code package,
compile it as provided, and test the resulting executable on their own
platform, along with also verifying that the package meets the
requirements of the ASF policy on releases."

That takes a bit more effort than "just a vote".


The requirement is obvious. I am not a PMC member but I run the openoffice
development version in my desktop. I would expect someone in the PMC should
be doing the same.

We usually go beyond that for AOO, so the process takes months.



To some extent, it may conflict with ApacheConEU attendance, because
that will take PMC members away from their own platforms. Ideally, we
need to get the voting process done before those attending leave home.

Even though there is some publicity advantage to announcing at the
event, I would rather get the release out ASAP.


Well, before the event is fine, ASAP works for me as long as it is 
before the event(?).


Pedro.

Re: What would OpenOffice NON-retirement involve?

[Pedro Giffuni]

Hello;

At this time I am unsure what the Board wants from the project. They 
probably want to see more activity and may recur to artificial numbers 
like number of commits, number of active developers, or releases.


I very much doubt actions from the Board will solve anything, it's the 
PMC and the developers that do the effective changes in a project.


If we make a release in the following weeks we may take the Board from 
our backs and get time to work on the things that matter.


I have to say that thanks to the brave work of Damjan the project is a
LOT more sustainable than some months ago. We have a testsuite back and
the build environment has improved substantially. Also Don has been 
doing some important cleanups and updates.


Still the problems are:

- Developers: the issue is not actually the number of them but the 
know-how that AOO requires. The majority of the experienced developers

are either still at IBM but with a lot of unrelated work, or have
gravitated slowly to LibreOffice (as in paid to do so).

- A Win64 port: 80% of our users are Windows users.

- The code is just ugly .. really, and that is true for LibreOffice as well.

There are plans (rewrite a lot in Java, more use of APR), but we just
have to be realistic and understand that big changes in the codebase
are not going to happen soon. AOO 5.0 may take at least two years.

Pedro.

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

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

[Pedro Giffuni]

Hmm ... the discussion sounds a bit like Brexit ...

With the important difference that it is now evident that Brexit
didn't have a plan.

Having a retirement plan is important for our users and for the ASF
and while I think the discussion is sane and important I think we should 
focus now on the next release. It is clear to me that

even if AOO were to be retired, we still have to push out a
new release mainly because we do have stuff that should see
the light of a release.

For the release we are certainly seeing some deficiencies:

- Can we responsibly deliver AOO 4.2.0 for the Mac? If the base/java
issue is as serious as it sounds and since we don't have much developer
feedback or even a buildbot, we may have to release 4.2.0 with a Mac
version!

After the release there are certainly much more things to discuss.

Pedro.


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

Re: Python update for testing

[Pedro Giffuni]

On 09/01/2016 Kay Schenk wrote:


On 09/01/2016 11:17 AM, Pedro Giffuni wrote:

Hello;

The python we are carrying for AOO 4.2.0 (2.7.8) has many security
vulnerabilities which may or may not have an effect on AOO.

In order to make future updates and particularly for Python 2.7.9, in
fact, we also needed to update OpenSSL, so now that Don updated
OpenSSL the basic update became possible. I tested the update
on FreeBSD but I had to hack for Windows buildfiles and this requires
testing.

People that regularly build windows please try this patch:

http://people.apache.org/~pfg/patches/python-update.diff

If there is no feedback I could try committing the change and keep an
eye on the buildbots, although this is certainly not too elegant.


The issue is if we can get a newer version of Python from a reputable
repo for CentOS 5.11 for i386 and x86_64 which will be our build
environment for *nix systems.

So, we need to investigate this first. I'm using python 2.7.10 on CentOS
6.8 but I don't remember where I got it. :/


Hmm ...

I don't think I understand very well what you are meaning here:

If you are using a pre-packaged python to build AOO, then the AOO
embedded python version is of no concern. If you are building the
internal python in AOO then it's in your best interest to have
something at least as up to date as the one that regularly comes
with your OS.

I don't really care very much about the python version used in BSD/Linux
/MacOS as it is likely users in those systems will have an up-to-date 
python version. Windows, on the other hand, depends on the specific 
python we are delivering.


Pedro.

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

Python update for testing

[Pedro Giffuni]

Hello;

The python we are carrying for AOO 4.2.0 (2.7.8) has many security
vulnerabilities which may or may not have an effect on AOO.

In order to make future updates and particularly for Python 2.7.9, in
fact, we also needed to update OpenSSL, so now that Don updated
OpenSSL the basic update became possible. I tested the update
on FreeBSD but I had to hack for Windows buildfiles and this requires
testing.

People that regularly build windows please try this patch:

http://people.apache.org/~pfg/patches/python-update.diff

If there is no feedback I could try committing the change and keep an
eye on the buildbots, although this is certainly not too elegant.

Once this change is done, it may be relatively easy to update Python
all the way to 2.7.12, the only big change to be aware of is a path
change for the Windows build files.

Pedro.

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

Re: Release 4.2: Regressions for investigation

[Pedro Giffuni]

Hello;

FWIW, I fixed Issue 124091 a while ago. The commits are registered in 
Bugzilla.


Pedro.


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

Re: Putting Windows First ( was RE: null)

[Pedro Giffuni]

Hi Patricia;

I, for one, appreciate the idea: 80% of the users are Windows people and 
the project should be focusing on improving the experience on that platform.


OTOH, most of the active developers work on UNIX variant (and I suspect 
FreeBSD is the majority lately). I conceptually understand the Windows 
port is critical and would like to see it improve but I don't have the 
time or expertise to work on a platform different than the one I am 
using now.


May I say this shouldn't stop you: just create a branch and fork a more 
windows-friendly
port, we can cross-merge features between both branches. Also the 
capstone2013

branch, while badly outdated, may give new hints for a Windows build system.

Pedro.

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

Re: dmake

[Pedro Giffuni]

On 28 Aug, Gav wrote:

when did you try that last Don?

That url comes up oops 404


I last tried that in the last few weeks, but have been using a cached
copy since then.

This page lists lots of mirrored copies:


It looks like development has moved to GitHub:



and this is exactly what I was going to say ...

With the demise of Google code the project moved to github and is under 
a new maintainer (FreeBSD uses the new github version).


Perhaps we should mirror dmake-4.12.2, which was the last version 
released on apache-extras, on sourceforge and update the build link.


Pedro.

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

Re: [DISCUSS] Release 4.2: General Topics

[Pedro Giffuni]

Hi  again;
...

I did update most of the components you mention and even gave a talk
about it ;).


It looks like the others are:
ucpp


We are using the latest version.


Hmn, I wonder why the FreeBSD port is using the bundled one.


I think we just don't have an option in AOO to use an external
cpp.

I actually asked for one, but Jürgen Schmidt, considered it
unnecessary since the code is so small (he was probably right).

Pedro.

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

Re: [DISCUSS] Release 4.2: General Topics

[Pedro Giffuni]

Hi Don;


On 24 Aug, Pedro Giffuni wrote:



On 08/24/16 10:34, Pedro Giffuni wrote:

Hello;


...




  * [low priority] Updated bundled CoinMP.  There has been an API
change, which prevents the FreeBSD port from using the system
version.  Difficulty unknown ...



This is important, I was unaware of it. Sadly, I don't think I will
have time for it before the release.



A quick look at this ... FreeBSD is using version 1.8.3 which appears
to be the latest.

AOO could use the same version by default, it's just a matter of getting
the new version to build on all platforms. I think.


Unfortunately it is not that easy.  When I was cleaning up the the
FreeBSD port a while back, I went through all of the --with-system knobs
and CoinMP was one that did not work and broke the build.  My memory is
fuzzy, but I think there was an incompatible API change.



Hmm ... I just looked and the openoffice-devel FreeBSD port is using
the system coinmp. Actually CoinMP is only a wrapper around the core
Coin libraries. I have always considered using the core libraries 
directly as that provides more powerful options but I haven't found

the time and motivation to work on it.

I did try updating the CoinMP patches and it was not easy/fun. The Mac
changes are likely to be troublesome.


There are some other bundled bits that have the same problem, but CoinMP
is big and takes a while to build, which is my main motivation in this
case.  ICU also falls into this category, but I already know that it is
too difficult.



Yes, that one is difficult and while Symphony has a most of what we may 
need, the problem is that it has to be tested "multilingually".


I did update most of the components you mention and even gave a talk 
about it ;).



It looks like the others are:
ucpp


We are using the latest version.


mdds


The developer behind it broke compatibility with the AOO code (on
purpose, for all I know). The code is actually calling for a replacement 
but since it works we are leaving it untouched.



hsqldb


SUN had a branch with the required changes. I have some WIP patch for 
that but there are other issues, like the database format is 
incompatible. I have to spend more time on that but the change is

worth the rescue.


libxmlsec


AOO uses a heavily modified version. Updating it requires a lot of 
effort, basically forking libxmlsec.



stax


This is actually unused and can be thrown away, unless you are still
using something older than Java 5.


rhino


Oh yes, we updated this once but it's category B so there's not a lot of 
motivation to work on it. Newer java has functionality that can replace it.



xsltml


I don't remember well this one. I think it depended on something else 
and ultimately I was just happy about using the system version.



saxon


The latest versions (saxon-he) lack the functionality AOO requires.
We need to use saxon-B, and there is indeed a newer version but the
packaging is different to what AOO carries. FreeBSD was using the system 
one but we stopped using it due to conflicts with the saxon

from another important package (Scilab),


icc


I think Giuseppe Castagno said it wasn't worth the effort and since
he did the OOo related stuff I didn't look further. I like excuses to
be lazy :).


I do know that saxon is sort of funny case.


It is only used for very old MS-Office formats. It is probably not worth 
the effort anyways. LibreOffice replaced it with C code and the author 
actually offered to relicense it for us but I lost trace of him

afterwards.

Hope that helps,


Pedro.

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

Re: [DISCUSS] Release 4.2: General Topics

[Pedro Giffuni]

On 08/24/16 10:34, Pedro Giffuni wrote:

Hello;


...




  * [low priority] Updated bundled CoinMP.  There has been an API
change, which prevents the FreeBSD port from using the system
version.  Difficulty unknown ...



This is important, I was unaware of it. Sadly, I don't think I will
have time for it before the release.



A quick look at this ... FreeBSD is using version 1.8.3 which appears
to be the latest.

AOO could use the same version by default, it's just a matter of getting 
the new version to build on all platforms. I think.


Pedro.

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

Re: [DISCUSS] Release 4.2: General Topics

[Pedro Giffuni]

Hello;


Here is my list:

  * Update bundled redland / rasqal / raptor to fix a CVE.  This is
currently in progress.  The FreeBSD port has been using the system
versions of the latest and greatest.




This is difficult because of dependencies between the three and the way
the configure scripts are tied together :(.



  * Updated bundled serf to fix a CVE and a WebDAV issue.  The FreeBSD
port has been using the system version of the latest and greatest.



Agreed, this is important.


  * [low priority] Update bundled vigra.  This version is no longer
available upstream.  It is used by the basebmp module, but I don't
know what it is used for or how to test it.  I believe only the
headers are used.  The FreeBSD port uses the latest and greatest
version and I haven't heard of any problems.



We are using the latest version that does NOT use CMake. TBH, the
update is probably not worth it.



  * [low priority] Updated bundled CoinMP.  There has been an API
change, which prevents the FreeBSD port from using the system
version.  Difficulty unknown ...



This is important, I was unaware of it. Sadly, I don't think I will
have time for it before the release.

While here ... In Kay's list there is BZ 123975, an update to Python 3.
As stated in the BZ issue, this is not convenient at this time: we
have tried hard to keep compatibility with OpenOffice.org and updating
further would put that at risk.

Also the new Python versions upgraded the build scripts for Windows,
which may require more work for our build system.

Somewhere in the distant future... we should also update ICU.

Pedro.

Pedro.

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

Re: [DISCUSS] Release 4.2: General Topics

[Pedro Giffuni]

First of all ... huge thanks to Kay for taking over as Release Engineer.


On 8/23/2016 12:14 PM, Kay sch...@apache.org wrote:
...
> 2. Update Java requirement from Java 1.5 to *at least* Java 1.7
>
> I am rather adamant that we change our building requirement to Java 1.7
> for all platforms. I will be changing that in our Building Guide today.
> Java 1.5 went out of support by Oracle in November, 2009. We use OpenJDK
> but I'm sure updates for Java 1.5 through that channel are also no
> longer available.
> Even Java 1.7 has reached end of life by Oracle for public support as of
> April, 2015. To avoid undue issues for some of our current users on
> older platforms, I am "OK" with java 1.7. I am fairly confident ALL
> users can obtain this for whatever platform they are using.
...

The more important, and more difficult, issue is 32-bit vs 64-bit Java.


FWIW, I suspect 32 vs 64 is a non-issue from a release point of view:

Can AOO be built with 64-bit Java? If it doesn't then I guess it's not 
an option but in any case AOO is expected to work on 32 bit systems so 
we will have to release with the 32-bit Java in addition to the 64-bit Java.


BTW, Will java 1.7 attempt to update itself to Java 1.8? (I haven't used 
java on Windows in a long time ...)


Pedro.



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

Re: upgrading bundled openssl

[Pedro Giffuni]

Hi Don;

Thanks for working on this!

Two crazy ideas here:

1) Perhaps bundling libressl instead of openssl make sense?

2) It would be really nice if we were able to use encryption in other 
components: apr-utils and curl, for example.


Pedro.

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

Buildbot wishlist ... Fwd: [GitHub] The Apache Software Foundation has approved a third-party application that you use

[Pedro Giffuni]

Hello;

This is interesting but I have no time to investigate it.

There's also travis-ci which would be a nice-to-have alternative to the
ASF buildbots and I think they also support MacOS X.

Pedro.

 Forwarded Message 
Subject: [GitHub] The Apache Software Foundation has approved a 
third-party application that you use

Date: Mon, 08 Aug 2016 19:39:46 -0700
From: The Apache Software Foundation 
To:

An organization owner has approved the following application to access 
private data in the The Apache Software Foundation organization:


  "Coverity Scan" from Coverity Scan

Because you are a member of the The Apache Software Foundation 
organization and have already granted this application access to your 
personal account, Coverity Scan can now access The Apache Software 
Foundation organization resources on your behalf.


You can always see the full list of applications that have access to 
your account here:


  https://github.com/settings/applications

If you choose to stop using one of those applications, you can revoke 
its access at any time.


Thanks,
The GitHub Team

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

buildbot wish ... Fwd: [GitHub] The Apache Software Foundation has approved a third-party application that you use

[Pedro Giffuni]

(Reposting from my @apache address so it gets through easier)

Hello;

This (running coverity from github) is interesting but I have no time
to investigate.

There's also travis-ci which would be a nice-to-have alternative to the
ASF buildbots and I think they also support MacOS X.

Pedro.

 Forwarded Message 
Subject: [GitHub] The Apache Software Foundation has approved a 
third-party application that you use

Date: Mon, 08 Aug 2016 19:39:46 -0700
From: The Apache Software Foundation <nore...@github.com>
To: Pedro Giffuni <p...@freebsd.org>

An organization owner has approved the following application to access 
private data in the The Apache Software Foundation organization:


  "Coverity Scan" from Coverity Scan

Because you are a member of the The Apache Software Foundation 
organization and have already granted this application access to your 
personal account, Coverity Scan can now access The Apache Software 
Foundation organization resources on your behalf.


You can always see the full list of applications that have access to 
your account here:


  https://github.com/settings/applications

If you choose to stop using one of those applications, you can revoke 
its access at any time.


Thanks,
The GitHub Team

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

Re: Merge with LibreOffice?

[Pedro Giffuni]

On Aug 3, 2016 10:00 AM, "Christoph Reg"  wrote:
> Regardless of why or how,
> when it comes to development, it's clear that LO has won. Hands down.
> LO gets more commits in one or two days than AOO had since the
> beginning of the year.

The second part of the claim is probably true, but the first part of the 
claim is totally irrelevant, in the sense that this is not
really a competition. I don't think anyone of us here in AOO has any 
desire to "beat" another opensource project and at least I don't

really make money from OpenOffice.

> Are there any reasons why [merging AOO and LO] is not feasible?

That's something I have personally never considered. What would
"merging" mean? from the rest of the posting, I guess that would
mean closing the Apache project (we can't assign the name "Apache 
OpenOffice" to something we don't develop) and conceding the

good will to LibreOffice.

They are evidently still finding value from our patches ... in fact,
I have been spammed by member of the Document Foundation, which I
thought knew better, about my "contributions", so I guess stopping
my development would hurt them in some way.

I personally don't find their development methodology or their community 
attractive. I have never used LO, but if their project

has advanced so much, why would the need us to shut down?

Pedro.

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

Re: FW: buildbot success in on aoo-win7

[Pedro Giffuni]

Congratulations to Damjan!!

Now .. if we could just find a way to cut down the red tape and push
out a new release we would be just fine.

Pedro.

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

Re: Any chance to merge the gbuild branch rather soonish?

[Pedro Giffuni]

Hi Damjan;

I am back to gbuild, have moved my Windows VM's disk to the faster ext3
filesystem, and have begun doing the only thing I can think of to debug
this: manually "bisection testing" the gbuild-reintegration branch to try
isolate which patch causes the build performance regression.

There is 136 patches ported from the branches/gbuild branch that have been
merged in batches to branches/gbuild-reintegration.
Patch 129 builds in 341 minutes.
Patch 43 builds in 335 minutes.

So it must be one of the 42 most recent patches.
Currently compiling patch 16.



Nice! I was thinking perhaps we should consider having a different build 
system for windows (capstone?) but if gbuild works that would be fine.


Can you please sync the gbuild-reintegration branch with trunk? There 
have been some library updates and it would be good to have all those 
changes together.


Pedro.

GPL vs Apple Store (was Re: null)

[Pedro Giffuni]

Hi Damjan;
...

GPL apps are apparently not allowed in the Apple App Store (
http://www.zdnet.com/article/no-gpl-apps-for-apples-app-store/), and if the
source code is under the GPL, it doesn't stop being so in binary form, so
I'd love to know how they get away with it.

Damjan


The GPL vs Apple thing is pure propaganda: as long as the copyright 
owners don't complain Apple will not pull down the application.


In the VLC case one of the copyright owners complained so the community
ended up relicensing the code[1] and now the application is back.

The Battle of Wesnoth is another case where the game is GPLv2 and 
available (for money) on iOS. There is some internal agreement the

resulting money helps someone in the community and the sourcecode
is available.

NeoOffice does ship in the Apple store and the source code is rather
hard to get by (they use a private CVS, I think). They (ab)use the fact
that the copyright owners don't really care about making money from OOo
anymore.

They use code from LibreOffice but TDF doesn't have much control over 
the complete codebase. I think the ASF could stop it from being

distributed but we are not in the business of enforcing the GPL.

This said, the NeoOffice app store version seems to have way
too many limitations, and this is something that tends to happen with
all such "app stores" that expect some sort of sandboxing.

Just my $0.02,

Pedro.

[1] http://www.videolan.org/press/lgpl-libvlc.html


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

ApacheConEU 2016

[Pedro Giffuni]

Hello;

There was already a Call for Papers but this year I have seen very 
little publicity around ApacheConEU, so let me point you directly to the 
site:


http://events.linuxfoundation.org/events/apachecon-europe

November 16-18 Seville, Spain.

It sounds like a wonderful place to discuss future  Apache OpenOffice 
developments!


Pedro.




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

Re: [QUESTION] Dependency on OpenSSL

[Pedro Giffuni]

Hi Dennis;


I recall discussions of OpenSSL and updating our dependency on it to a 
better/patched version.

What I don't know is whether the binaries that are built and distributed 
directly by the project
incorporate OpenSSL in any manner?

Can anyone clear that up?

  1. Do our built binaries depend on and distribute OpenSSL in some manner?

  2. Is this for all platforms or only some of them?



While your questions are interesting, and we really must keep OpenSSL 
updated, it would seems like you want to limit the impact of what could 
be considered a liability. I think in our modern world the opposite 
approach is necessary: we should be looking at considering encryption 
more as an opportunity than a threat.


It looks like we have been avoiding including openssl where we should 
have: the general build *should* depend on OpenSSL for APR, curl, and 
python. I have never really worried about it because my primary platform 
(FreeBSD .. yeah!) uses the pre-packaged dependencies by default and 
those depend on OpenSSL.


So, my answers to your questions are:

1) I hope so, and if we are not, we have to fix that.

2) We absolutely must keep all platforms consistent.


Pedro.

Re: [PROPOSAL] Removing all tracking from AOO sites

[Pedro Giffuni]

Any news on this?



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

Re: Updating APR ...

[Pedro Giffuni]

Hi Dennis;



Pedro,

Please say more about what it means to "update APR support carried in AOO."

 1. Since APR is from an Apache Project, are you talking about relying on it 
more and/or contributing
improvements upstream?  <https://apr.apache.org/>

 2. Are you talking about using APR in implementations of more SAL components?

 3. Are you considering the replacement of (some) usage of the SAL API with APR 
API usage
instead?

 4. Finally, for (1-2), are there not rather important plumbing-architecture 
matters concerning
storage and lifecycle manage of components now handled at the SAL, UNO, etc., 
layers?

 5. Also, how does this intersect with efforts designed to make AOO into a 
Java-based application?
 I suppose some current concerns about multi-threading and synchronization, 
mutexes, etc.,
might also come into play.

It would be valuable to have a roadmap that allows work to be shared and 
reviewed and with
all of the testing and documentation that will be called for, across platform 
builds as handled
for AOO.

Perhaps I am reading too much into what you are proposing.  I look forward to 
your clarification.

 - Dennis



Hi Dennis,

You are reading too much ;).

All I will do is update a couple of tarballs:

apr 1.4.5  --> apr-1.5.2
apr-util-1.4.1 --> apr-util-1.5.4


In the near future I will reap out the core of rtl_random() and replace
the implementation with the APR equivalent. This will be within SAL, the 
API will remain untouched and the rest of AOO, you won't even notice the 
change.


I am hoping to prepare a presentation about it for the next ApacheConEU.

APR has some nice stuff used by apache-httpd and is very portable:
I think the mutex and pools goodies are good candidates to do the same, 
but this is progressive work and pretty much depends on my spare time.


If the Java replacement plans advance sufficiently to get rid of SAL
then ... great!

Pedro.

On 05/24/16 12:20, Pedro Giffuni wrote:

Hello;

As part of some enhancements I am preparing to generate better random
numbers, I took a look at the random number generator in SAL and
I found it's very limited.

I think even the "regular" KISS PRNG I implemented in Calc does a
better job generating random numbers but instead of moving my PRNG
to SAL I will be using the one in APR.

Looking at the SAL APIs I also think APR can replace much of that
functionality as well.

So, just to let you know, I am in the process of updating the APR
support we carry in AOO: it should be also useful for serf, and we
could use it for tomcat, which we may want to upgrade and use more
extensively in the future as well.

Pedro.


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

Updating APR ...

[Pedro Giffuni]

Hello;

As part of some enhancements I am preparing to generate better random
numbers, I took a look at the random number generator in SAL and
I found it's very limited.

I think even the "regular" KISS PRNG I implemented in Calc does a
better job generating random numbers but instead of moving my PRNG
to SAL I will be using the one in APR.

Looking at the SAL APIs I also think APR can replace much of that 
functionality as well.


So, just to let you know, I am in the process of updating the APR
support we carry in AOO: it should be also useful for serf, and we
could use it for tomcat, which we may want to upgrade and use more
extensively in the future as well.

Pedro.

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

RE: svn commit: r1745006 [3/9] - in /openoffice/trunk/main

[Pedro Giffuni]

Hi Dennis;

So you noticed such changes are burdensome ...

The situation is more or less this so that you understand:

- I have had those changes in my HD for a least a couple of months
now, I was tired of them,
- I considered dropping them but it was quite some effort (time),
and the changes I did to codespell are not public yet.
- While most of them are just comments, some of the strings are user 
visible and have a real effect.

When your software breaks in some evil way and then reports
"Unkown error" you know you can't expect much from the product.
- I of course ran a local build to make sure no breakage was caused.
- This stuff was getting in the way of more a more important
project that I am starting (Can't share the details right now).
So, either I shared it, or I threw it away: if you prefer I just threw
it away, then just say and we can revert it(!).
- There is no code review system in Apache OO to handle such changes.
Trust me: bugzilla won't handle this.
- This type of changes may be big but are pretty non-invasive: even
if we had a *real* code review system (something like phabricator),
someone has to take care of the final changes.

While there are some bogus changes, I do think there was an overall
improvement. It appears you got tired of reviewing the changes
(won't blame you) ... may I suggest you just go ahead and *commit*
your reviews?

Maybe I should have created a branch.. but with the high level of
activity in SVN, I think we could handle it ;).

Subversion is made for collaboration and we are seriously 
under-utilizing it. Let's use subversion for what it's meant to do.

Really, I just wish other committers were more active even when
what most of them do is not all that technical.

Pedro.

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

Re: [PROPOSAL] Removing all tracking from AOO sites

[Pedro Giffuni]

In reply to Kay;
...


Ever heard of Big Data? This information will be correlated along with
the latest
searches and will be sold for commercial value to other companies and
will also
likely be available to the governments of the world at request. For
whatever
Mr. Trump may find it useful is another matter.


I understand broadly what your concerns are. But really, in this day and
age, almost ANY website you visit has some sort of tracking mechanisnm
in place. Next time you "visit" anywhere, you might want to check this.



That others do it, doesn't mean we should. Do we at least respect the 
"do not track" settings in the browser?




Worst of all, we are not getting any value from this tracking ... let's
stop it now.


Well this last statement is NOT true. For the download page especially,
it is valuable because we can find out generally what OS the user is
using, complete with version information. I mean in a bulk sense.



How valuable is that? How does us it bring us any nearer towards having
an Android/iOS port? We already have counts from downloads statistics
and we know at least 80% of our users get the Windows port.

Pedro.

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

Re: [PROPOSAL] Removing all tracking from AOO sites

[Pedro Giffuni]

Guys, please ...


I just wanted to give a short update into my investigation of our Google
Analytics usage.

...

* There IS general individual usage collection in some reports but the
"user" information is translated into something called a "client id" -- so
not by IP.


Let's just not be naive here. We are giving direct information about our 
users to

a company that has ample power to tie this information to specific users and
that already may own the content of your emails and navigation history.

Ever heard of Big Data? This information will be correlated along with 
the latest
searches and will be sold for commercial value to other companies and 
will also

likely be available to the governments of the world at request. For whatever
Mr. Trump may find it useful is another matter.

Worst of all, we are not getting any value from this tracking ... let's 
stop it now.


Pedro.

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

RE: images

[Pedro Giffuni]

FWIW;


The Galleries are not produced and maintained by Apache OpenOffice.  The 
catalog and collection
of clipart downloads are maintained as a service between Apache OpenOffice and 
SourceForge.

The images are from third parties.  Gallery sets/extensions are offered under 
licenses specified
by their originators.  There is no blanket license.
I recall at least the galleries donated by IBM's Symphony and those that 
came from SUN are

under an Apache License.

Pedro.

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

RE: [PROPOSAL] Removing all tracking from AOO sites

[Pedro Giffuni]

+1

I should note, I used to have access to the Google Analytics stuff
when I was in the PMC. It was set up by Rob Weir under consensus.

It is certainly a form of tracking and, at least I, have no idea what 
purpose it has served. From some time I have had no access it as it

mysteriously disappeared from my list of GA sites.

Thanks so much for bringing up this subject, I always meant to bring
it up but forgot.

Pedro.

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

Re: Development updates

[Pedro Giffuni]

Hello Damjan;

I have been focusing on my other favorite open-source project lately,
which has been just fantastic but completely unrelated. I won’t get
you guys bored with the details ;).

Coincidentally, I do have a patch with the hsqldb2 update, based on the
older CWS from SUN, and I have a HUGE patch to fix spelling errors
in AOO. All is pending more time to give it a final kick.

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

Re: Any chance to merge the gbuild branch rather soonish?

[Pedro Giffuni]

Thank you for the report Damjan :(

Pedro.

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

Any chance to merge the gbuild branch rather soonish?

[Pedro Giffuni]

Hello;

FWIW, I am preparing a second round of spelling fixes ... it's a
quite big change. I would prefer to do such changes *after* the
new build system is in place though.

I can deal easily with any breakage caused by the spelling fixes but
it may not be very fun to have to fix again the build issues so I
would really prefer to chose the battle field ahead of time ;).

Pedro.

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

Re: 5. Any system which depends on human reliability is unreliable

[Pedro Giffuni]

IMHO,

The affirmation is worthless BS. Computers are designed by unreliable
humans and are therefore unreliable. Software is absolutely unreliable.

We measure the laws of physics and science based on what we observe. but
we cannot observe reliably so our conclusions are unreliable ... oh and
if new observations contradict theory we will certainly have to update
the laws of science for the new phenomena.

This email is unreliable, BTW. ;)

Pedro.

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

Re: Release Manager for 4.2.0?

[Pedro Giffuni]

Hi Don;


On 28 Mar, Pedro Giffuni wrote:
> In reply to Don,

>> The versions of openssl and curl badly need updating for the same
>> reason, and there is one CVE for serf.
>
> FreeBSD casually keeps some backported updates for the same openssl
> version AOO uses:
>
> https://svnweb.freebsd.org/base/stable/9/crypto/openssl/?view=log
>
> It should be pretty straightforward to take them from there and use 
them

> into
> main/openssl with minor adaptions.

That would fix only part of the problem.  The other part of the problem
is that the version of openssl that we currently bundle doesn't
implement the newer and more secure protocols and ciphers.  The older
and less secure ones are gradually getting disabled on the server side.

For instance, my only copy of Windows is XP, and the last version of IE
released for XP can no longer connect to some web sites because they
have disabled all of the protocols that IE supports.



That is a valid concern, however I am unsure about what in OpenOffice
uses the new cyphers. I think OpenSSL is used for signing documents:
when we update OpenSSL will AOO automatically accept more signing
options? I would expect browsers will bring their own SSL
implementations.

TBH, when I updated OpenSSL in AOO, I intentionally didn't upgrade it
further because the newer versions have more code but also more
vulnerabilities, therefore the expected maintenance cost would be
higher.  The FreeBSD 9.x updates are only a temporary workaround.
Now that upstream is not maintaining the older 0.9.8 version
it probably makes sense to reconsider upgrading.

Pedro.


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

Re: Release Manager for 4.2.0?

[Pedro Giffuni]

In reply to Don,

FWIW, On the topic of updates
...

Some of the external software that is bundled has security issues.  I
put together a patch for nss here:
.

The version of libxml currently bundled also has a lot of known
vulnerabilities.  I'm currently testing a patch.

These both need review and testing.

The versions of openssl and curl badly need updating for the same
reason, and there is one CVE for serf.


FreeBSD casually keeps some backported updates for the same openssl 
version AOO uses:


https://svnweb.freebsd.org/base/stable/9/crypto/openssl/?view=log

It should be pretty straightforward to take them from there and use them 
into

main/openssl with minor adaptions.

Pedro.

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