Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of dave2wave@comcast.net
 designates 76.96.27.243 as permitted sender)
Subject: Re: Neutral / shared security list ...
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Dave Fisher <dave2wave@comcast.net>
In-Reply-To: <A4CD6A49-3214-47D3-A742-682AAAE80C85@webmink.com>
Date: Mon, 24 Oct 2011 16:25:59 -0700
Cc: Rob Weir <robweir@apache.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <34F3347E-B725-4C74-893F-2928417C448C@comcast.net>
References: <1319037389.83728.YahooMailMobile@web113502.mail.gq1.yahoo.com>
 <CAA4ffp8Ds25ExcE9O_GTR0h3id6m2ZCNMRxDne57kt-gtpvj_w@mail.gmail.com>
 <CAP-ksohpfGdgTGF1Ayswo8Gn2s9BQ_S7QdMx0eDjDDs3QRPX2A@mail.gmail.com>
 <A4CD6A49-3214-47D3-A742-682AAAE80C85@webmink.com>
To: ooo-dev@incubator.apache.org

Simon,

Please don't despair!

On Oct 24, 2011, at 3:32 PM, Simon Phipps wrote:

>=20
> On 23 Oct 2011, at 04:37, Rob Weir wrote:
>=20
>> Simon,
>>=20
>> I hope TDF members (and members of other related source projects) =
will
>> accept our hospitality and join us on the securityteam list.
>=20
> Your words show you missed the entire point of my proposal, Rob, and =
leave me too frustrated to want to discuss the matter with you any =
further; we were all so close to agreement when you were on vacation.  =
My attempted contribution on this list and at TDF is to envisage grounds =
for co-operation between these two divided parts of the legacy =
StarOffice/OpenOffice community. It is not to be a messenger for your =
alternative ideas.=20

I think that Rob is getting ahead of the situation. We need to reach a =
simple agreement about this single issue before bringing up other =
obvious places of overlap.  I think we may really be closer than we =
think.

Not sure how much this is like your original proposal, but maybe the =
following is acceptable:

(1) The securityteam@openoffice.org continues.

(2) The membership of securityteam ML should be open to individuals and =
forks/"downstreams" as selected by the ML membership.

(3) The securityteam ML moderators are selected from the individual =
membership of the securityteam ML.

(4) The securityteam ML is nominally under the governance of the ASF - =
either the AOOo podling PPMC, the Apache Security Team, or even the =
Foundation Board. I think the AOOo podling PPMC should be acceptable, =
but we can ask the other entities if that is not is not neutral enough. =
We may ask the TDF to neutrally host some component and it would make =
sense for each entity to trust the neutrality of the other entity (Rob's =
real point).

(5) No iCLAs are required.

(6) A set point for membership is determined when at least AOOo, TDF, =
and any other OOo fork/"downstreams" who might appear within a =
reasonably short time period. The deadline would need to be agreed.

(7) The securityteam@openoffice.org ML will be hosted by the ASF when =
the MX for openoffice.org is moved to ASF Infrastructure.

> I suggest you go to their mailing lists and make your proposals. Maybe =
you can earn TDF membership with your contributions?

This is a reasonable place to go to ask the TDF to host some component =
OOo by the TDF.

I'm currently curious if LO uses extensions.s.oo.o and templates.s.oo.o?

Regards,
Dave

>=20
> S.
>=20