You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Andrea Pescetti <pe...@apache.org> on 2013/06/01 16:54:35 UTC
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
On 29/05/2013 Rob Weir wrote:
> On Fri, May 24, 2013 at 2:19 AM, Andrea Pescetti wrote:
>> http://svn.apache.org/viewvc/openoffice/trunk/main/readlicense_oo/docs/readme/readme.xrm?view=log
> I took a look. Two things that I noticed.
>
> 1) It refers the reader to this URL for the latest version of the README:
> http://www.openoffice.org/welcome/readme.html
> But that page does not appear to have been updated since OOo 3.0. Is
> that URL correct? If so I can enter a BZ issue so we remember to
> update the contents of that page with the latest README. On the other
> hand, shouldn't this really be a per-version readme file?
Yes, the web page must be updated before release. And, as for the
per-version URL (like readme-400.html), this is a tradeoff to decide
upon, since this requires manual changes at every release in all cases.
So: either we "archive" old READMEs and link them from
http://www.openoffice.org/welcome/readme.html or we use a specific URL.
Considering string freeze and translations, it's probably better to do
the former (archive the old ones) since it can be centralized and has a
lesser impact on contributors.
> 2) The README has many references to the Solaris platform, which is
> not supported in the release. Should that be migrated into a separate
> readme that would be distributed by the Solaris port?
The Solaris-specific strings are not displayed on other operating
systems (you will see CSS classes that are used to suppress them at the
above URL). That said, they are probably outdated and irrelevant indeed.
I didn't move strings since it might have had an impact on translation.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by FR web forum <oo...@free.fr>.
>> 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
Don't forget native language project.
Maybe an URL like:
www.openoffice.org/<**lang>/release/<**version>/README
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Kay Schenk <ka...@gmail.com>.
On Sat, Jun 8, 2013 at 12:46 PM, Andrea Pescetti <pe...@apache.org>wrote:
> On 01/06/2013 Rob Weir wrote:
>
>> 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
>>
>
> Sounds like a very good idea. I'm not sure we will be able to implement it
> in time for OpenOffice 4 (translations get in the way), but it could be
> setup with some basic information already for version 4 (and, if the
> hard-coded URLs in version 4 are different and cannot be changed at this
> stage, we could redirect them appropriately).
Maybe a quick and not too confusing fix for this for 4.0 --
redirect /welcome/readme.html (meta refresh, no need to do anything else)
-> (new) /welcome/readme_4.0.html
Make changes as appropriate to new doc.
>
>
> Regards,
> Andrea.
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<de...@openoffice.apache.org>
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
-------------------------------------------------------------------------------------------------
MzK
"Normal is not something to aspire to, it is something to get away from."
-- Jodie Foster
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Andrea Pescetti <pe...@apache.org>.
On 01/06/2013 Rob Weir wrote:
> 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
Sounds like a very good idea. I'm not sure we will be able to implement
it in time for OpenOffice 4 (translations get in the way), but it could
be setup with some basic information already for version 4 (and, if the
hard-coded URLs in version 4 are different and cannot be changed at this
stage, we could redirect them appropriately).
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by "Dennis E. Hamilton" <de...@acm.org>.
++++++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"
<de...@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
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Rob Weir <ra...@gmail.com>.
On Jun 1, 2013, at 3:55 PM, "Dennis E. Hamilton"
<de...@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
>
>
>
>>> 2) The README has many references to the Solaris platform, which is
>>> not supported in the release. Should that be migrated into a separate
>>> readme that would be distributed by the Solaris port?
>>
>> The Solaris-specific strings are not displayed on other operating systems (you will see CSS classes that are used to suppress them at the above URL). That said, they are probably outdated and irrelevant indeed. I didn't move strings since it might have had an impact on translation.
>>
>> Regards,
>> Andrea.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by "Dennis E. Hamilton" <de...@acm.org>.
+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.
- 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
>> 2) The README has many references to the Solaris platform, which is
>> not supported in the release. Should that be migrated into a separate
>> readme that would be distributed by the Solaris port?
>
> The Solaris-specific strings are not displayed on other operating systems (you will see CSS classes that are used to suppress them at the above URL). That said, they are probably outdated and irrelevant indeed. I didn't move strings since it might have had an impact on translation.
>
> Regards,
> Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Rob Weir <ra...@gmail.com>.
On Jun 1, 2013, at 10:55 AM, Andrea Pescetti <pe...@apache.org> wrote:
> On 29/05/2013 Rob Weir wrote:
>> On Fri, May 24, 2013 at 2:19 AM, Andrea Pescetti wrote:
>>> http://svn.apache.org/viewvc/openoffice/trunk/main/readlicense_oo/docs/readme/readme.xrm?view=log
>> I took a look. Two things that I noticed.
>>
>> 1) It refers the reader to this URL for the latest version of the README:
>> http://www.openoffice.org/welcome/readme.html
>> But that page does not appear to have been updated since OOo 3.0. Is
>> that URL correct? If so I can enter a BZ issue so we remember to
>> update the contents of that page with the latest README. On the other
>> hand, shouldn't this really be a per-version readme file?
>
> Yes, the web page must be updated before release. And, as for the per-version URL (like readme-400.html), this is a tradeoff to decide upon, since this requires manual changes at every release in all cases. So: either we "archive" old READMEs and link them from http://www.openoffice.org/welcome/readme.html or we use a specific URL. Considering string freeze and translations, it's probably better to do the former (archive the old ones) since it can be centralized and has a lesser impact on contributors.
>
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
>> 2) The README has many references to the Solaris platform, which is
>> not supported in the release. Should that be migrated into a separate
>> readme that would be distributed by the Solaris port?
>
> The Solaris-specific strings are not displayed on other operating systems (you will see CSS classes that are used to suppress them at the above URL). That said, they are probably outdated and irrelevant indeed. I didn't move strings since it might have had an impact on translation.
>
> Regards,
> Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org