Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <4E968C92.2070701@apache.org>
References: <1318434476.30811.YahooMailClassic@web113505.mail.gq1.yahoo.com>
	<4E968C92.2070701@apache.org>
Date: Thu, 13 Oct 2011 07:44:49 -0400
Message-ID: 
 <CAP-ksogpV1zMwZv5XwP4r8CfM5cRf0QOArkoMN4nW2SqEgupeA@mail.gmail.com>
Subject: Re: [PATCH] Fix for #118485#, #108221#, #67705#
From: Rob Weir <robweir@apache.org>
To: ooo-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8

On Thu, Oct 13, 2011 at 3:00 AM, Herbert Duerr <hdu@apache.org> wrote:
> On 10/12/2011 05:47 PM, Pedro Giffuni wrote:
>> [...]
>>
>> Oh yes, it was not that big, but it touched a lot of files
>> which made it difficult to get the context. In any case
>> big patches are sometimes necessary and I was confident
>> this wouldn't go bad: it was my way of saying "this guy
>> should be a committer so he can fix the stuff he breaks"
>> :),
>
> Armin should definitely become a committer soon. I'm no longer sure how that
> process works. I had sent a vote request regarding Ariel to the private list
> but for some reason it did not get there. I even sent it through the apache
> SMTP using my @apache.org email address, but it still didn't suffice to let
> it through.
>

Are you subscribed to the ooo-private list?  Notes from subscribers,
sent from the address they subscribed from, are not moderated.

Notes sent from non-subscribers are forwarded to the moderators, but
that should only introduce a short delay, at most a few hours.

The process for voting in a new committer is described in the Podling
Guide here:

http://incubator.apache.org/guides/ppmc.html

-Rob

>> Another thing is that we should be focusing on removing
>> copyleft components and perhaps some cleanups before
>> doing enhancements. I specifically want to avoid the
>> situation in LO where the code and the configuration
>> options keep growing and growing without control to
>> the point where patches occasionally make gcc run
>> out of memory.
>
> yes.
>
>> [...]
>> - Use of OpenSSL instead of nss for AES encryption.
>
> I'm looking into replacing nss by openssl for encryption and signing of
> documents. NSS is currently also responsible for key and certificate
> management and replacing that seems to be the really tricky part...
>
> Herbert
>