Rob Weir wrote: > On Wed, Feb 12, 2014 at 6:21 PM, Andrea Pescetti > <pescetti-1odqgaof3lkdnm+yrof...@public.gmane.org> wrote: >> Andrew Douglas Pitonyak wrote: >>> >>> If the intent is to change OOo to AOO, if I could change the pages at 3 >>> minutes per page, it would take 6 days of solid work to change them all. >>> Could this be done during a maintenance cycle? >> >> >> Sure, this is best done automatically, directly on the server. But I don't >> see a real reason for being so verbose and always using "Apache OpenOffice" >> instead of the normal "OpenOffice". >> >> I believe the internal product name is set to "OpenOffice", and we have a >> "long product name" set to "Apache OpenOffice" for some occurrences in the >> interface. >> >> Anyway, whatever is agreed upon, once we agree this is a task to be handled >> by a global "search and replace" in database. >> > > The problem we have is that outdated pages usually are outdated in > more than one. It is not just the product name that is wrong. It > could have incorrect email addresses, URLs, descriptions of project > organization, broken external links, etc. And then there is > information that is technically obsolete as well. > > An idea: mark all pages with two tags: > > 1) Needs branding review > 2) Need technical review > > (or names with similar meaning)
There currently is a template to do this it is called with the wiki
markup {{Documentation/NeedsRework}}. It marks it as needing checking
for both style and technical accuracy and adds it to the Category
NeedsRework.There is also on that marks it as checked for Technical
accuracy. Creating one to mark it as checked for style would be a fairly
simple task. Then as they get done an editor could check it and remove
the Templates which also removes the link to the category.
There are a wealth of templates already created; Many especially for
documentation are listed in the Wiki_Editing_Policy at
https://wiki.openoffice.org/wiki/Documentation/Dashboard/Wiki_Editing_Policy#List_of_Existing_Documentation_Templates
I can do any templates that are needed, but we need a Style Guide to
check against. That is not my field of expertise. There are a few pages
on the Wiki possibly could be used as a starting point.
Regards
Keith
> Then we can slowly, over time, review each of these pages and update
> them. When the branding review is done we remove the "Needs branding
> review" tag, for example. It would be possible, I assume, to have a
> page that simply lists all pages with a given tag, so we can review
> the (hopefully shrinking) list of pages needing review.
>
> This would yield tasks that any volunteer could work on, even with
> just an hour of free time.
>
> We could maintain a special page that lists the most common
> corrections, to make them easier to apply.
>
> -Rob
>
>
>> Regards,
>> Andrea.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> doc-unsubscribe-jnqqrfibojosbzieg410zs0vgnn6c...@public.gmane.org
>> For additional commands, e-mail:
>> doc-help-jnqqrfibojosbzieg410zs0vgnn6c...@public.gmane.org
>>
signature.asc
Description: OpenPGP digital signature
