openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <dennis.hamil...@acm.org>
Subject RE: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Date Sun, 02 Jun 2013 15:26:45 GMT
++++++1

One-click access, Yay!!

 - Dennis

-----Original Message-----
From: Rob Weir [mailto:rabastus@gmail.com] 
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


Mime
View raw message