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 8C0C67CA4 for ; Fri, 2 Sep 2011 14:48:16 +0000 (UTC) Received: (qmail 56826 invoked by uid 500); 2 Sep 2011 14:48:16 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 56750 invoked by uid 500); 2 Sep 2011 14:48:15 -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 56742 invoked by uid 99); 2 Sep 2011 14:48:15 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2011 14:48:15 +0000 Received: from localhost (HELO mail-ey0-f173.google.com) (127.0.0.1) (smtp-auth username robweir, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2011 14:48:15 +0000 Received: by eyb7 with SMTP id 7so2547706eyb.18 for ; Fri, 02 Sep 2011 07:48:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.14.2.148 with SMTP id 20mr339573eef.125.1314974893360; Fri, 02 Sep 2011 07:48:13 -0700 (PDT) Received: by 10.14.188.2 with HTTP; Fri, 2 Sep 2011 07:48:13 -0700 (PDT) In-Reply-To: <008401cc697e$cca4cd10$65ee6730$@acm.org> References: <4E5FB6F0.2060504@ellisons.org.uk> <4E5FC756.5010106@ellisons.org.uk> <4E5FD55C.40207@ellisons.org.uk> <4E5FE090.2020506@apache.org> <014801cc68e5$d5fd5290$81f7f7b0$@acm.org> <1314911707.1938.55.camel@sybil> <4E60193C.4090304@shanecurcuru.org> <4E606C19.40005@ellisons.org.uk> <4E60E6DF.6050006@shanecurcuru.org> <008401cc697e$cca4cd10$65ee6730$@acm.org> Date: Fri, 2 Sep 2011 10:48:13 -0400 Message-ID: Subject: Re: Apache Way community moderation rationale From: Rob Weir To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable OpenOffice.org is an Apache domain. It will have Apache branding, etc. We can't pretend that site is at arm's length. -Rob On Fri, Sep 2, 2011 at 10:44 AM, Dennis E. Hamilton wrote: > +1 > > I completely support the high-level migration road-map you sketch for art= ifacts and services currently in custody of the openoffice.org domain sites= and not part of the Oracle SGA. > > In the final paragraph, though, perhaps you meant to say > > " Given the past history and the fact that this > non-code content is not currently under an *apache.org* domain, it is > possible to technically migrate a lot of stuff without having finalized > the policy issues. =C2=A0(Note: source code and items under apache.org > domains are different, and should discuss policy issues sooner rather > than later)." > > -----Original Message----- > From: Shane Curcuru [mailto:asf@shanecurcuru.org] > Sent: Friday, September 02, 2011 07:23 > To: ooo-dev@incubator.apache.org > Subject: Apache Way community moderation rationale > > [ ... ] > > ---- > NOTE: OOo is a huge project with a very diverse set of well-known > services, and, like, a LOT of users. =C2=A0To graduate to a top level pro= ject > will require significant changes to how some of these services are > provided in the future under any Apache marks or domain names. > > Given the scale and breadth of services, and the changes in community, I > think it's appropriate to plan on plenty of time to make the complete > migrations of these services. =C2=A0Likewise, I believe it may be permiss= ible > to take over hosting some services in the technical sense under the > openoffice.org domain - in the short term - that we might not normally > consider as managed fully by the Apache Way yet. > > One way to think about services migration - to separate out policy > dependencies from technical ones - is: > > - Ensure several PPMC members have root / admin / whatever level of > access is required to give them oversight, so they can review behavior > on the service. (first!) > > - Technically port the service to apache hardware (but not under an > apache.org domain yet) > > - Apply branding updates to the service > > - Decide final policy issues for moderation, etc. for the service > > Does that make sense? =C2=A0Given the past history and the fact that this > non-code content is not currently under an openoffice.org domain, it is > possible to technically migrate a lot of stuff without having finalized > the policy issues. =C2=A0(Note: source code and items under apache.org > domains are different, and should discuss policy issues sooner rather > than later) > > - Shane > >