Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E864E7964 for ; Thu, 6 Oct 2011 12:41:00 +0000 (UTC) Received: (qmail 78329 invoked by uid 500); 6 Oct 2011 12:41:00 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 78284 invoked by uid 500); 6 Oct 2011 12:41:00 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 78276 invoked by uid 99); 6 Oct 2011 12:41:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Oct 2011 12:41:00 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jogischmidt@googlemail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bw0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Oct 2011 12:40:54 +0000 Received: by bke11 with SMTP id 11so3534923bke.6 for ; Thu, 06 Oct 2011 05:40:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=lW3BBnK2edHDuiksGHYiZkbsVtdyV4ZzN3IcB4/d+LI=; b=vQUJ8oKFWQbiWOw3yX0yDhivrdIWJr7TODRVJg6Nvu4iyTz/nQoVa9uvIHeA+YVdKb gFCEkoejYfL3b7m3x7rdZEKiCmgoVbB+qO8LJItrwmC/StDZrE9vkhCqLQ0iHeBt/dpD m0+d4gAWsyfb7zZHpO8IfXiwf6TUyHrZU0178= MIME-Version: 1.0 Received: by 10.204.131.217 with SMTP id y25mr525788bks.281.1317904834002; Thu, 06 Oct 2011 05:40:34 -0700 (PDT) Received: by 10.204.141.75 with HTTP; Thu, 6 Oct 2011 05:40:33 -0700 (PDT) In-Reply-To: <4E8D959C.1010009@documentfoundation.org> References: <00e601cc8396$a4eeaca0$eecc05e0$@apache.org> <6AA74BAB-B366-4B88-9472-D78FA94DD599@webmink.com> <00ed01cc839c$70bd9030$5238b090$@apache.org> <4E001CA5-762B-4C3B-BF51-FC0BD26C06F8@comcast.net> <012601cc83b6$22112fe0$66338fa0$@acm.org> <4E8D959C.1010009@documentfoundation.org> Date: Thu, 6 Oct 2011 14:40:33 +0200 Message-ID: Subject: Re: Vulnerability fixed in LibreOffice From: =?UTF-8?Q?J=C3=BCrgen_Schmidt?= To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=001517447ec67a808f04aea0a141 X-Virus-Checked: Checked by ClamAV on apache.org --001517447ec67a808f04aea0a141 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Oct 6, 2011 at 1:48 PM, Florian Effenberger < floeff@documentfoundation.org> wrote: > Hi, > > J=C3=BCrgen Schmidt wrote on 2011-10-06 13:18: > >> If a TDF or ASF list is secondary for me but i would volunteer to join >> this >> mailing list to help on this topic in the future. But maybe we should tr= y >> to >> keep the existing and knownsecurityteam@openoffice.**org mailing list and I >> >> see no reason why it shouldn't work. I think it is probably more a probl= em >> of the people on this list and missing communication. I assume that peop= le >> on this list have now other priorities and are not so responsive which o= f >> course is natural if they have a new job or moved into other projects ..= . >> > > from what I understood, we were told that things at Apache are "different= ". > IMHO, there is an Apache security list, but only a few selected people ca= n > be on it, and IMHO they have to be Apache contributors. > a further Apache specific list is independent of the shared and collaborative list securityteam@openoffice.orgwhere we want work together. My idea is to simply use the existing securityteam@openoffice.org list for collaborative work on this topic. LibreOffice has also a separate security list, right. So i don't see your point here. > Guess what I think about the fact that the well established communication > channel is about to vanish... > i don't think so, it is up to us to keep it working. We shouldn't mix the past (confusing, demotivating) 6 month with the future when things have settled down and everything is working here. We know that we still have a lot of things to do but that shouldn't prevent us from working together on this important security topic. Juergen --001517447ec67a808f04aea0a141--