From ooo-dev-return-10339-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org Mon Dec 12 01:33:18 2011 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 CE6177D89 for ; Mon, 12 Dec 2011 01:33:18 +0000 (UTC) Received: (qmail 52590 invoked by uid 500); 12 Dec 2011 01:33:18 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 52551 invoked by uid 500); 12 Dec 2011 01:33:18 -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 52543 invoked by uid 99); 12 Dec 2011 01:33:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Dec 2011 01:33:18 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dave2wave@comcast.net designates 76.96.30.40 as permitted sender) Received: from [76.96.30.40] (HELO qmta04.emeryville.ca.mail.comcast.net) (76.96.30.40) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Dec 2011 01:33:08 +0000 Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta04.emeryville.ca.mail.comcast.net with comcast id 80zu1i0031wfjNsA41Ygcj; Mon, 12 Dec 2011 01:32:40 +0000 Received: from [192.168.1.7] ([67.180.51.144]) by omta23.emeryville.ca.mail.comcast.net with comcast id 81RF1i00d36gVt78j1RGvm; Mon, 12 Dec 2011 01:25:16 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: Rationalizing two OpenOffice websites From: Dave Fisher In-Reply-To: <1323652673.55411.YahooMailNeo@web160901.mail.bf1.yahoo.com> Date: Sun, 11 Dec 2011 17:32:45 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <140612E5-AAC5-41C3-8188-F9F427A23509@comcast.net> References: <1322439624.71382.YahooMailClassic@web113503.mail.gq1.yahoo.com> <4EE4B81A.7030502@openoffice.org> <11CF9C89-5984-43FC-A344-ED0B30A19621@comcast.net> <51E8516B-9473-4987-91FE-7CB2F6204F31@comcast.net> <3964A6C7-CF99-4D30-B38A-9B41AC3043B3@comcast.net> <864D3EAD-5E14-4F20-A20F-3B66749969F2@comcast.net> <1323652673.55411.YahooMailNeo@web160901.mail.bf1.yahoo.com> To: ooo-dev@incubator.apache.org X-Mailer: Apple Mail (2.1084) X-Virus-Checked: Checked by ClamAV on apache.org On Dec 11, 2011, at 5:17 PM, Joe Schaefer wrote: > Why don't you just decide to make the current ooo-site live, > and tell infra to change dns for www.openoffice.org to point > at it? There is an outstanding question about exactly how the extensions and = templates authenticate users. It is being investigated. Also the subdomain map needs to be built. > I've made some performance enhancements to the CMS today so > web checkouts will only take a few seconds as opposed to 30min. That's wonderful! > Also I will be working on your site's build because it is in a > terrible state, but that will take more time. Too much was committed at once. So, we don't collide let me know if you are working with templates or = lib, I am (or was) about to play with that part. I am really effin, = tired of being yelled at at repeatedly by Rob. When I'm done with my plan nearly every html file in ooo-site will be = updated, how do you want to co-ordinate that? Regards, Dave >=20 >=20 >=20 > ----- Original Message ----- >> From: Rob Weir >> To: ooo-dev@incubator.apache.org >> Cc:=20 >> Sent: Sunday, December 11, 2011 7:55 PM >> Subject: Re: Rationalizing two OpenOffice websites >>=20 >> On Sun, Dec 11, 2011 at 6:15 PM, Dave Fisher =20= >> wrote: >>>=20 >>> On Dec 11, 2011, at 2:09 PM, Rob Weir wrote: >>>=20 >>>> On Sun, Dec 11, 2011 at 4:04 PM, Dave Fisher=20 >> wrote: >>>>=20 >>>> >>>>=20 >>>>>=20 >>>>> I've already answered. I've been very clear. Nothing has=20 >> stopped others from working on ooo-site. >>>>>=20 >>>>=20 >>>> I apologize if I was not clear. I'm not interested in editing >>>> ooo-site.apache.org. >>>=20 >>> And I happen to think that this is absolute nonsense. ooo-site will = be=20 >> www.openoffice.org when the time comes. Waiting is a bogus excuse. >>>=20 >>=20 >> To the extent that you continue to not understand what I am saying I >> will continue to repeat myself, attempting various ways of >> reformulating my point. >>=20 >> I want to update www.openoffice.org. I do not want to update only >> your test server. I want the changes I make now to be reflected on >> the public, user facing openoffice.org website after a simple staging >> and publication stage, i.e., near real time, no more than a few >> minutes delay. That is what the project needs. This is what we all >> need. The fact that we can can easily update ooo-site, a staging >> website that no user actually ever sees is a partial success only. >>=20 >> What I hear you saying is that we're free to update the data in >> /ooo-site and that will then appear on the test staging server. That >> is nice. But the changes that you, me and others have made on that >> content is not being seen by real users. It is stuck in limbo. We >> can invite committers to stick more content into limbo, of course, to >> queue it up for publication at some indeterminate point in the = future. >> But I'm more interested in what we need to do to get the content = out >> of limbo and live on www.openoffice.org. How do we complete this? >>=20 >> So this is not about ooo-site. This is about the complete = publication >> pipeline. That is what matters for the PPMC's ability to properly >> manage the www.openoffice.org website. Nothing is live until the = PPMC >> can effectively update the real site. >>=20 >> Remember, what our users have on www.openoffice.org is very wrong in >> many places. We're continuing every day to harm the project if that >> content remains as-is and is not replaced by accurate project >> information. The fact that some of the content is corrected in SVN >> or on ooo-site is not enough. >>=20 >> If at all possible, I'd urge us to take a "release early, release >> often" approach to the website migration rather than a "big bang >> integration" approach. >>=20 >> What is the minimum that really needs to be done to make this site go >> live? And how can I, and anyone else who is interested in >> accelerating this work, help? >>=20 >> -Rob >>=20