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: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=Qm/Ye6tZKG1iaMfbWxt2EzW+1nXTWZ2vDnJ/JCkjAAEAoSA7avvv69bpTDwgzRETooZ58ZFmj7FYFy+6VhLtVDKVl5R4FT5r7tUp6dtBI7KotVA4yjKM1GcRIRcQto+FIJqOXdfiL6agjUh8AutLfQkMW7jxd0lRoaxTAtLA9jI=;
References: <1322439624.71382.YahooMailClassic@web113503.mail.gq1.yahoo.com>
 <4EE4B81A.7030502@openoffice.org>
 <11CF9C89-5984-43FC-A344-ED0B30A19621@comcast.net>
 <CAP-ksoj-Lv3hpHOTLQpAH6zFan9jaAS3SV9VWi8uXeYZroa1bw@mail.gmail.com>
 <A3AA9247-E744-4138-84C7-73212D3B491D@comcast.net>
 <CAP-ksogx0=SBRcc6k3=DP4oo1KtU4u9fnjTm=dqtVyoHe9qDow@mail.gmail.com>
 <CAP-ksoiwV6s1ecs4H+fBmPzOW1__vJFgL7eTQVF0msL_EtBBBg@mail.gmail.com>
 <D63F859D-C2EE-4295-AD85-F692A391D3ED@comcast.net>
 <CAP-ksog2RHL+hiO15Du4gHNkzA3Yh+011miuwh3rm9u8O3DSCg@mail.gmail.com>
 <51E8516B-9473-4987-91FE-7CB2F6204F31@comcast.net>
 <CAP-ksojrT_asjA=51k7866WaUTktTioGxCm3Eo=TX9N6JP1edg@mail.gmail.com>
 <3964A6C7-CF99-4D30-B38A-9B41AC3043B3@comcast.net>
 <CAP-ksoiBef-gtT7WDVbJ2yMYfSLFo7v2V6uKdMzABTToDCZUmw@mail.gmail.com>
 <864D3EAD-5E14-4F20-A20F-3B66749969F2@comcast.net>
 <CAP-ksojfbedwjyoaO+2dRKHDB5aF9vzerPqze6SvJ8e6nAg0sw@mail.gmail.com>
 <A2A9A10C-B684-47E7-871A-D569F33DE993@comcast.net>
 <CAP-ksog6OtrdGcfXmvBR76pN4TyKCucWpsYyj
 3iri8SsZqA00g@mail.gmail.com>
Message-ID: <1323652673.55411.YahooMailNeo@web160901.mail.bf1.yahoo.com>
Date: Sun, 11 Dec 2011 17:17:53 -0800 (PST)
From: Joe Schaefer <joe_schaefer@yahoo.com>
Reply-To: Joe Schaefer <joe_schaefer@yahoo.com>
Subject: Re: Rationalizing two OpenOffice websites
To: "ooo-dev@incubator.apache.org" <ooo-dev@incubator.apache.org>
In-Reply-To: 
 <CAP-ksog6OtrdGcfXmvBR76pN4TyKCucWpsYyj3iri8SsZqA00g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Why don't you just decide to make the current ooo-site live,=0Aand tell inf=
ra to change dns for www.openoffice.org to point=0Aat it?=0A=0AI've made so=
me performance enhancements to the CMS today so=0Aweb checkouts will only t=
ake a few seconds as opposed to 30min.=0A=0AAlso I will be working on your =
site's build because it is in a=0Aterrible state, but that will take more t=
ime.=0A=0A=0A=0A----- Original Message -----=0A> From: Rob Weir <robweir@ap=
ache.org>=0A> To: ooo-dev@incubator.apache.org=0A> Cc: =0A> Sent: Sunday, D=
ecember 11, 2011 7:55 PM=0A> Subject: Re: Rationalizing two OpenOffice webs=
ites=0A> =0A> On Sun, Dec 11, 2011 at 6:15 PM, Dave Fisher <dave2wave@comca=
st.net> =0A> wrote:=0A>> =0A>>  On Dec 11, 2011, at 2:09 PM, Rob Weir wrote=
:=0A>> =0A>>>  On Sun, Dec 11, 2011 at 4:04 PM, Dave Fisher =0A> <dave2wave=
@comcast.net> wrote:=0A>>> =0A>>>  <snip>=0A>>> =0A>>>> =0A>>>>  I've alrea=
dy answered. I've been very clear. Nothing has =0A> stopped others from wor=
king on ooo-site.=0A>>>> =0A>>> =0A>>>  I apologize if I was not clear. =A0=
I'm not interested in editing=0A>>>  ooo-site.apache.org.=0A>> =0A>>  And I=
 happen to think that this is absolute nonsense. ooo-site will be =0A> www.=
openoffice.org when the time comes. Waiting is a bogus excuse.=0A>> =0A> =
=0A> To the extent that you continue to not understand what I am saying I=
=0A> will continue to repeat myself, attempting various ways of=0A> reformu=
lating my point.=0A> =0A> I want to update www.openoffice.org.=A0 I do not =
want to update only=0A> your test server.=A0 I want the changes I make now =
to be reflected on=0A> the public, user facing openoffice.org website after=
 a simple staging=0A> and publication stage, i.e., near real time, no more =
than a few=0A> minutes delay.=A0 That is what the project needs.=A0 This is=
 what we all=0A> need. The fact that we can can easily update ooo-site, a s=
taging=0A> website that no user actually ever sees is a partial success onl=
y.=0A> =0A> What I hear you saying is that we're free to update the data in=
=0A> /ooo-site and that will then appear on the test staging server.=A0 Tha=
t=0A> is nice.=A0 But the changes that you, me and others have made on that=
=0A> content is not being seen by real users.=A0 It is stuck in limbo.=A0 W=
e=0A> can invite committers to stick more content into limbo, of course, to=
=0A> queue it up for publication at some indeterminate point in the future.=
=0A> =A0 But I'm more interested in what we need to do to get the content o=
ut=0A> of limbo and live on www.openoffice.org.=A0 How do we complete this?=
=0A> =0A> So this is not about ooo-site.=A0 This is about the complete publ=
ication=0A> pipeline.=A0 That is=A0 what matters for the PPMC's ability to =
properly=0A> manage the www.openoffice.org website.=A0 Nothing is live unti=
l the PPMC=0A> can effectively update the real site.=0A> =0A> Remember, wha=
t our users have on www.openoffice.org is very wrong in=0A> many places.=A0=
 We're continuing every day to harm the project if that=0A> content remains=
 as-is and is not replaced by accurate project=0A> information.=A0  The fac=
t that some of the content is corrected in SVN=0A> or on ooo-site is not en=
ough.=0A> =0A> If at all possible, I'd urge us to take a "release early, re=
lease=0A> often" approach to the website migration rather than a "big bang=
=0A> integration" approach.=0A> =0A> What is the minimum that really needs =
to be done to make this site go=0A> live?=A0  And how can I, and anyone els=
e who is interested in=0A> accelerating this work, help?=0A> =0A> -Rob=0A>