Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of kay.schenk@gmail.com designates
 209.85.214.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1323658764.97060.YahooMailNeo@web160903.mail.bf1.yahoo.com>
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>
	<1323652673.55411.YahooMailNeo@web160901.mail.bf1.yahoo.com>
	<140612E5-AAC5-41C3-8188-F9F427A23509@comcast.net>
	<1323654349.73271.YahooMailNeo@web160904.mail.bf1.yahoo.com>
	<1323658764.97060.YahooMailNeo@web160903.mail.bf1.yahoo.com>
Date: Mon, 12 Dec 2011 15:09:44 -0800
Message-ID: 
 <CAGj3215DkLyeEGqjZ-gjz1qDOnf+ZNWi=_PZa_0jJ5_hC6EeDg@mail.gmail.com>
Subject: Re: Rationalizing two OpenOffice websites
From: Kay Schenk <kay.schenk@gmail.com>
To: ooo-dev@incubator.apache.org, Joe Schaefer <joe_schaefer@yahoo.com>
Content-Type: multipart/alternative; boundary=000e0ce0d47ef96b8704b3ed3a64

--000e0ce0d47ef96b8704b3ed3a64
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Dec 11, 2011 at 6:59 PM, Joe Schaefer <joe_schaefer@yahoo.com>wrote:

> All set. Just did a full site build and it went thru no trouble.
>

YAY! I did see this am that all seemed to be in good order...I'm not sure
WHAT happened yesterday. Right after I did a commit, I couldn't even get
this page to load:

https://cms.apache.org/

so I was sure the CMS was having problems.

I'm happy to hear things are good now, and will hopefully remain so.


>
>
>
> ----- Original Message -----
> > From: Joe Schaefer <joe_schaefer@yahoo.com>
> > To: "ooo-dev@incubator.apache.org" <ooo-dev@incubator.apache.org>
> > Cc:
> > Sent: Sunday, December 11, 2011 8:45 PM
> > Subject: Re: Rationalizing two OpenOffice websites
> >
> > I'm working with Gav to get the timeout upped as that's what's
> > causing the builds to fail (long delays when the built site gets
> > checked back in).  I will let you know once I have things ready
> > for you to make mass changes to the ooo-site.
> >
> >
> >
> > ----- Original Message -----
> >>  From: Dave Fisher <dave2wave@comcast.net>
> >>  To: ooo-dev@incubator.apache.org
> >>  Cc:
> >>  Sent: Sunday, December 11, 2011 8:32 PM
> >>  Subject: Re: Rationalizing two OpenOffice websites
> >>
> >>
> >>  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
> >>
> >>>
> >>>
> >>>
> >>>   ----- Original Message -----
> >>>>   From: Rob Weir <robweir@apache.org>
> >>>>   To: ooo-dev@incubator.apache.org
> >>>>   Cc:
> >>>>   Sent: Sunday, December 11, 2011 7:55 PM
> >>>>   Subject: Re: Rationalizing two OpenOffice websites
> >>>>
> >>>>   On Sun, Dec 11, 2011 at 6:15 PM, Dave Fisher
> >>  <dave2wave@comcast.net>
> >>>>   wrote:
> >>>>>
> >>>>>   On Dec 11, 2011, at 2:09 PM, Rob Weir wrote:
> >>>>>
> >>>>>>   On Sun, Dec 11, 2011 at 4:04 PM, Dave Fisher
> >>>>   <dave2wave@comcast.net> wrote:
> >>>>>>
> >>>>>>   <snip>
> >>>>>>
> >>>>>>>
> >>>>>>>   I've already answered. I've been very clear.
> >>  Nothing has
> >>>>   stopped others from working on ooo-site.
> >>>>>>>
> >>>>>>
> >>>>>>   I apologize if I was not clear.  I'm not interested in
> >
> >>  editing
> >>>>>>   ooo-site.apache.org.
> >>>>>
> >>>>>   And I happen to think that this is absolute nonsense. ooo-site
> > will
> >>  be
> >>>>   www.openoffice.org when the time comes. Waiting is a bogus excuse.
> >>>>>
> >>>>
> >>>>   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.
> >>>>
> >>>>   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.
> >>>>
> >>>>   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?
> >>>>
> >>>>   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.
> >>>>
> >>>>   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.
> >>>>
> >>>>   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.
> >>>>
> >>>>   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?
> >>>>
> >>>>   -Rob
> >>>>
> >>
> >
>


-- 
----------------------------------------------------------------------------------------
MzK

"The greatness of a nation and its moral progress can be judged
 by the way its animals are treated."
                              -- Mohandas Gandhi

--000e0ce0d47ef96b8704b3ed3a64--