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: 
 <CAGj3214jf8xhns0ELZnb7sA5cjn1EPURrxrmfbwJyfFOp0iviQ@mail.gmail.com>
References: 
 <CAGj3217wXHUJkHd80GCMRC7P2kuR_0hCAiyfRMXzXr-AfKL-TQ@mail.gmail.com>
	<90FE60CE-D08F-4282-A5F4-33709C069317@comcast.net>
	<4EB31242.5040603@cfl.rr.com>
	<CAGj3214b-Y8zjWFqpHuRokWQghDh1Erqx8yD0rhcM-cnzsGt+A@mail.gmail.com>
	<006601cc9a81$99de4080$cd9ac180$@acm.org>
	<CAGj3214jf8xhns0ELZnb7sA5cjn1EPURrxrmfbwJyfFOp0iviQ@mail.gmail.com>
Date: Thu, 10 Nov 2011 15:20:11 -0800
Message-ID: 
 <CAGj3217sMHykznAX0thbAnqBSUeUgcUFj+JsQKBznBa+=W7+bw@mail.gmail.com>
Subject: Re: [DISCUSS] easier access for N-L sites during staging process
From: Kay Schenk <kay.schenk@gmail.com>
To: ooo-dev@incubator.apache.org, dennis.hamilton@acm.org
Content-Type: multipart/alternative; boundary=0003255582166eb56f04b169a5ee

--0003255582166eb56f04b169a5ee
Content-Type: text/plain; charset=ISO-8859-1

OK, the status of things right now--

1. There is a new home page entry on
http://ooo-site.staging.apache.org/

so folks can at least navigate to the N-L sites page. This is NOT deemed to
be a "final" of anything just an easy access mechanism. I didn't even try
to deal with the style issues on the home page and merge what I did or make
new styles for this one additional item.

2. There is no problem button for any of the sites. I see there is another
conversation devoted entirely to what to do with them currently, so maybe
some of the "problems" should be addressed in that thread instead.

3. We have svn copies of the some sites by the sites are NOT displaying.
This could be due to the incorrect document charsets or some other issues
-- non-UNIX line terminators. These sites will need to be hand edited or
redone in some way. These sites are:

sq, bre, et, fur, hi, lo, lv, mk,pap

4. The following sites we do not have in the svn repository for some reason
(my initial bulk svn load failed and I didn't notice or redo them I guess),
and will need to be re-pulled:

hy, he ,ps, ro,  ta, tet, bo, uk

5. The following sites we have but are missing index.html pages, so what
you see is what you get:

ku, ml

My first priorities in dealing with the N-L sites are to re-pull the
missing entities -- #4, then deal with the "problem" areas #3 and maybe #5.

I FINALLY found a quick and easy way to publish the staging repository (one
you make changes to the the svn they go to:
http://ooo-site.staging.apache.org/)

by going to this page:

https://cms.apache.org/

and clicking on the "Publish ooo-site link"

Using the webgui for changes and publishing really isn't my cup of tea. I
like using my Eclipse svn environment.

On Fri, Nov 4, 2011 at 2:42 PM, Kay Schenk <kay.schenk@gmail.com> wrote:

>
>
> On Thu, Nov 3, 2011 at 4:37 PM, Dennis E. Hamilton <
> dennis.hamilton@acm.org> wrote:
>
>> ++++++1
>>
>> A little tuning, for what it is worth:
>>
>> It is not necessary to subscribe to any of these lists in order to ask
>> for help.  They will be moderated in.
>>
>> It might be nice if the mailto: entry specified a subject that would let
>> us know it is from the request link though.  That would emphasize that the
>> requester is probably not subscribed and a direct CC: on any response is
>> called for.
>>
>
> yes, of course...
>
>
>>
>> Also, ooo-users might be a better target than ooo-dev.
>>
>
> Why? These would be people reporting problems with the staging web site,
> not the product ????
>
>
>>
>> And, if within-site relative URLs are used for some cross-references,
>> they will work when the cut-over happens as if they were always links to
>> http:// *.openoffice.org URLs.  That way it is never necessary to expose
>> ooo-site.apache.org addresses.  (Cross references to the podling site
>> are different, of course and they will hopefully all be redirected on
>> graduation.)
>>
>> At some point, it should be fixed so http://ooo-site.apache.orgredirects to
>> http://openoffice.org (even though the pages are actually created at
>> you-know-where, that can be made to work without looping [;<).  It can also
>> be arranged that http://ooo-site.apache.org/es/ is served up as
>> http://es.openoffice.org, etc.
>>
>
> yes, that is right...
>
>>
>> -----Original Message-----
>> From: Kay Schenk [mailto:kay.schenk@gmail.com]
>> Sent: Thursday, November 03, 2011 15:22
>> To: ooo-dev@incubator.apache.org
>> Subject: Re: [DISCUSS] easier access for N-L sites during staging process
>>
>> On Thu, Nov 3, 2011 at 3:14 PM, TJ Frazier <tjfrazier@cfl.rr.com> wrote:
>>
>> > On 11/3/2011 17:59, Dave Fisher wrote:
>> >
>> >>
>> >> On Nov 3, 2011, at 2:39 PM, Kay Schenk wrote:
>> >>
>> >>  I'm thinking of changing the links on:
>> >>>
>> >>> http://ooo-site.apache.org/**projects/native-lang.html<
>> http://ooo-site.apache.org/projects/native-lang.html>
>> >>>
>> >>> to the format we're using at the staging site--
>> >>>
>> >>> http://ooo-site.apache.org/"**nl-abbreviation"
>> >>>
>> >>> and putting a link on the staging home page
>> >>>
>> >>> http://ooo-site.apache.org
>> >>>
>> >>> to the revised http://ooo-site.apache.org/**projects/native-lang.html
>> <http://ooo-site.apache.org/projects/native-lang.html>
>> >>> at the bottom of the menu with something called "Native Language
>> >>> Federation"
>> >>>
>> >>> to make it easier for folks to review the N-L sites.
>> >>>
>> >>> Due to the fact that we are now missing the navigating tabs on the
>> >>> staging
>> >>> site, we may want to deal with other areas like this as well for the
>> time
>> >>> being until a more in-depth discussion is had. This is merely for
>> >>> checking
>> >>> content accuracy for the time being.
>> >>>
>> >>> Are there any problems with this suggestion?
>> >>>
>> >>
>> >> +1000
>> >>
>> >> Regards,
>> >> Dave
>> >>
>> >>
>> >>> I can probably get this done over the coming weekend sometime.
>> >>>
>> >>>  Kay,
>> >
>> > You might consider a new column, which would have either a constant like
>> > "Review" or "New site" (with new link), or be empty for "not moved
>> yet". A
>> > sentence about "What do I do if I find a problem?" should be aimed at
>> > unsophisticated end-users.
>> >
>>
>> Well the thing is the sites "are moved" in the sense that they're in the
>> svn repository for the staging site. I'm not exactly sure what Dave is
>> doing at the moment in terms of preparation to tell you the truth, but I'm
>> fairly certain we've got everything that could be had "svn-ing" what was
>> publicly known .
>>
>> However, the  "What do I do if I find a problem?" link/page certainly has
>> merit. About the only thing I could suggest though is an e-mail to this
>> list (and they need to be subscibed first), and suggest an appropriate
>> subject title to them so we could spot these things easily. Would
>> something
>> as simple as that work or what were you thinking?
>>
>>
>>
>> > --
>> > /tj/
>> >
>> >
>>
>>
>> --
>>
>> ---------------------------------------------------------------------------------------
>> MzK
>>
>> "This is no social crisis
>>  Just another tricky day for you."
>>                 -- "Tricky Day", the Who
>>
>>
>
>
> --
>
> ---------------------------------------------------------------------------------------
> MzK
>
> "This is no social crisis
>  Just another tricky day for you."
>                  -- "Tricky Day", the Who
>
>


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

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

--0003255582166eb56f04b169a5ee--