Hi,
I am interested in gaining experience in technical writing and wanted to
volunteer to create and maintain documentation for the OpenOffice project.
I would like to involved in tasks such as, updating the OpenOffice
Administration Guide, and/or writing other documentation. Can you tell me
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
> -Original Message-
> From: Dr. Michael Stehmann [mailto:anw...@rechtsanwalt-stehmann.de]
> Sent: Wednesday, August 31, 2016 22:04
> To: dev@openoffice.apache.org
> Subject: Re: Independent Entity to Develop and Further AOO
>
> Am 01.09.2016 um 00:59 schrieb Simon Phipps:
> > On Wed, Au
OK, thank you, Pedro. It came up in my search because it's not marked as
RESOLVED. So, I did that just now.
On Thu, Sep 1, 2016 at 8:34 AM, Pedro Giffuni wrote:
> Hello;
>
> FWIW, I fixed Issue 124091 a while ago. The commits are registered in
> Bugzilla.
>
> Pedro.
>
>
> ---
On Thu, 1 Sep 2016 09:58:04 -0700
"Dennis E. Hamilton" wrote:
>
>
> > -Original Message-
> > From: Dr. Michael Stehmann [mailto:anw...@rechtsanwalt-stehmann.de]
> > Sent: Wednesday, August 31, 2016 22:04
> > To: dev@openoffice.apache.org
> > Subject: Re: Independent Entity to Develop an
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 bec
[BCC to PMC]
When I offered myself as a candidate for Chair of the Apache OpenOffice Project
Management Committee (PMC), I emphasized that a key objective was to obtain
clarity on the status of the project and its moving parts.
>From my personal perspective, that has been accomplished.
What
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 Ope
Great to see that this issue is solved finally.
Thanks to everyone who was involved. I want to express a special thanks
to the developers Patricia, Damjan and Ariel for creating the binary
files and Dennis for his coordination.
:-)
Marcus
Am 08/30/2016 05:46 PM, schrieb Dennis E. Hamilton
On 07/11/2016 09:44 PM, Suminda Dharmasena wrote:
> This is exactly what I had in mind also.
>From the original post of:
http://mail-archives.apache.org/mod_mbox/openoffice-dev/201607.mbox/%3CCAAfFNYEBbXaTj5-qVy7V8Uj7uA3wCyo6O0fsHG7ESpmTG4qO3Q%40mail.gmail.com%3E
None of the approaches listed
On 29 Aug, Don Lewis wrote:
> When building OpenOffice trunk revsion r1758161 as a FreeBSD port on
> FreeBSD 12.0-CURRENT with clang 3.8.0, I get the following warnings.
> I'm mostly interested in the OpenOffice code and not the bundled
> external code, so I specifically built the FreeBSD port it u
I need a problem to work on. Would you like me to take a particular
compiler warning and try to sort it out?
On 9/1/2016 3:29 PM, Don Lewis wrote:
On 29 Aug, Don Lewis wrote:
When building OpenOffice trunk revsion r1758161 as a FreeBSD port on
FreeBSD 12.0-CURRENT with clang 3.8.0, I get the f
On 1 Sep, Patricia Shanahan wrote:
> I need a problem to work on. Would you like me to take a particular
> compiler warning and try to sort it out?
Here is one:
/wrkdirs/usr/ports/editors/openoffice-devel2/work/aoo-4.2.0/main/solver/420/unxfbsdx.pro/inc/osl/diagnose.hxx:65:25:
warning: 'osl_de
Here is what a careful retirement of Apache OpenOffice could look like.
A. PERSPECTIVE
B. WHAT RETIREMENT COULD LOOK LIKE
1. Code Base
2. Downloads
3. Development Support
4. Public-Project Community Int
On 1 Sep, To: Don Lewis wrote:
> One of the -Wunused-parameter warnings led me to this questionable bit
> of code in filter/source/xsltfilter/containerhelper.hxx:
>
> template
> inline void forEachMem(FuncType pFunc, ParamType aParam) const
> {
> forEach(
Hi Dennis,
I don't have objections to this topic, but I feel I need to make a few
suggestions before this thread is either ignored or a confused mess.
(1) a long, official policy statement like this is best put into a wiki page
where many can edit it and it can be an easy discussion and not a c
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 als
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
[BCC to PMC]
> -Original Message-
> From: Dave Fisher [mailto:dave2w...@comcast.net]
> Sent: Thursday, September 1, 2016 19:27
> To: priv...@openoffice.apache.org
> Cc: dev@openoffice.apache.org
> Subject: Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)
>
> Hi Dennis,
>
>
Wow, just wow. I have to say, I think even broaching this topic is a
mistake. "Self-fulfilling prophecy"? Not even that, it'll be a "3rd party
fulfilling prophecy" as soon as this hits the press. There are a lot of
people out there who seem to have it in for AOO and have for a while... now
you *
> (3) I think that working towards being able to release rather than patch
> as Patricia has suggested is our best way to solve the security issue. The
> quick patch is not much faster and has been proven to be more of a
> challenge then kick starting the broken build process.
>
Forgive me for be
> -Original Message-
> From: Phillip Rhodes [mailto:motley.crue@gmail.com]
> Sent: Thursday, September 1, 2016 21:16
> To: dev@openoffice.apache.org; orc...@apache.org
> Subject: Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)
>
> Wow, just wow. I have to say, I think e
>
>
> What alternative do you see?
>
>
>
There's no particular reason that I can see, that AOO shouldn't be able to
produce secure software, issue releases and
do all of those other things. We've done it in the past (and yeah, I feel
guilty about saying "we" since I haven't been very active. Mea c
> -Original Message-
> From: Phillip Rhodes [mailto:motley.crue@gmail.com]
> Sent: Thursday, September 1, 2016 21:23
> To: dev@openoffice.apache.org
> Cc: priv...@openoffice.apache.org
> Subject: Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)
>
> > (3) I think that wo
> -Original Message-
> From: Phillip Rhodes [mailto:motley.crue@gmail.com]
> Sent: Thursday, September 1, 2016 21:49
> To: dev@openoffice.apache.org; Dennis Hamilton
> Subject: Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)
>
> >
> >
> > What alternative do you see?
25 matches
Mail list logo
