Return-Path: 
 <dev-return-36842-apmail-openoffice-dev-archive=openoffice.apache.org@openoffice.apache.org>
X-Original-To: apmail-openoffice-dev-archive@www.apache.org
Delivered-To: apmail-openoffice-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 0D7E89E64
	for <apmail-openoffice-dev-archive@www.apache.org>;
 Sun,  2 Jun 2013 15:27:04 +0000 (UTC)
Received: (qmail 56761 invoked by uid 500); 2 Jun 2013 15:27:03 -0000
Delivered-To: apmail-openoffice-dev-archive@openoffice.apache.org
Received: (qmail 56602 invoked by uid 500); 2 Jun 2013 15:27:03 -0000
Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@openoffice.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@openoffice.apache.org>
List-Post: <mailto:dev@openoffice.apache.org>
List-Id: <dev.openoffice.apache.org>
Reply-To: dev@openoffice.apache.org
Delivered-To: mailing list dev@openoffice.apache.org
Received: (qmail 56594 invoked by uid 99); 2 Jun 2013 15:27:03 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Jun 2013 15:27:03 +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 dennis.hamilton@acm.org
 designates 216.119.133.2 as permitted sender)
Received: from [216.119.133.2] (HELO a2s42.a2hosting.com) (216.119.133.2)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Jun 2013 15:26:57 +0000
Received: from 71-217-92-7.tukw.qwest.net ([71.217.92.7]:32849
 helo=Astraendo2)
	by a2s42.a2hosting.com with esmtpa (Exim 4.80)
	(envelope-from <dennis.hamilton@acm.org>)
	id 1UjAB1-003PBv-LQ
	for dev@openoffice.apache.org; Sun, 02 Jun 2013 11:26:35 -0400
Reply-To: <dennis.hamilton@acm.org>
From: "Dennis E. Hamilton" <dennis.hamilton@acm.org>
To: <dev@openoffice.apache.org>
References: <5190E97B.6080103@gmail.com> <51964BDE.7010809@gmail.com>
 <5198FDB8.2010604@apache.org>
 <3579970.17191.1369162536646.JavaMail.mobile-sync@vcbkh12>
 <-7808610423548947215@unknownmsgid>
 <23042581.59663.1369330912449.JavaMail.mobile-sync@vcat18>
 <1076340531837915469@unknownmsgid> <519E9016.5030504@apache.org>
 <CAP-ksohfTP=BTq=sp9PmLh556tVmpD3k9gpxs0X9Bn1Wfm1eqQ@mail.gmail.com>
 <51AA0B2B.1030002@apache.org> <2678159337378567478@unknownmsgid>
 <004e01ce5f01$dd4b51f0$97e1f5d0$@acm.org> <-8619287151358626900@unknownmsgid>
In-Reply-To: <-8619287151358626900@unknownmsgid>
Subject: RE: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Date: Sun, 2 Jun 2013 08:26:45 -0700
Organization: NuovoDoc
Message-ID: <00b001ce5fa5$97f4abc0$c7de0340$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: 
 AQJo3NQM+wfWkstPhm9Rimc02qf9sgEwVsamARkfVhcAeC35DwKsbKiKAafghYcCW//SDwI1ssInAYiVXAUCj9z15QEeunrBAkiOxFECGDhR4JdDlEZg
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse,
 please include it with any abuse report
X-AntiAbuse: Primary Hostname - a2s42.a2hosting.com
X-AntiAbuse: Original Domain - openoffice.apache.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - acm.org
X-Get-Message-Sender-Via: a2s42.a2hosting.com: authenticated_id:
 himself+orcmid.com/only user confirmed/virtual account not confirmed
X-Virus-Checked: Checked by ClamAV on apache.org

++++++1

One-click access, Yay!!

 - Dennis

-----Original Message-----
From: Rob Weir [mailto:rabastus@gmail.com]=20
Sent: Saturday, June 1, 2013 06:44 PM
To: dev@openoffice.apache.org
Subject: Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0

On Jun 1, 2013, at 3:55 PM, "Dennis E. Hamilton"
<dennis.hamilton@acm.org> wrote:

>
> +1
>
> The <version>-specific path on the site is also a fine way to locate =
the check-for-update target, since the release has its release =
<version>.  It can also have human-readable (and localized) pages that =
provide update information to someone who visits on-line.
>
> The default page at those locations could provide anything important =
about those particular versions, including obsolescence by security =
updates, what release replaced it, how to still obtain it, etc.
>

Good point, especially if there is access via the Help menu or other
prominent place in the UI.  It is a good way to reach out to our
users. If we had it with 3.4.1, for example, we could have added
updated information for things like the language updates or fixes for
the profile-related problems.

A strong form of online engagement with our users could be quite
powerful. Although we had 50 million downloads of AOO 3.4, engaged
users via the announcement list, Facebook, Twitter, etc., is only
around 15,000 users. Imagine if all 50 million had one click access to
the latest info on their installed AOO release?

-Rob


> - Dennis
>
>
> -----Original Message-----
> From: Rob Weir [mailto:rabastus@gmail.com]
> Sent: Saturday, June 1, 2013 08:55 AM
> To: dev@openoffice.apache.org
> Subject: Re: [RELEASE][TRANSLATION]: changes to the README file for =
4.0
>
> [ ... ]
>
> Crazy idea. What if we just made a sub domain for each release?  Or
> equivalently a path under  ooo-site.  Then we could have hard-coded
> standard paths in the code and other systems like:
>
>
> www.openoffice.org/release/<version>/README
>
> Could also do LICENSE, release notes, even the update notification XML =
files
>
> So a special website per release. Then when we do a new release we
> just do an svn copy to populate the new site, and update as needed.
> The code then points to appropriate dir based on build time version
> flag.
>
> -Rob
>
[ ... ]


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org