Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Hi Robinson
Le 22 août 2014 20:57, "Robinson Tryon" <bishop.robinson@gmail.com> a écrit
:

On Fri, Aug 22, 2014 at 2:21 PM, Florian Effenberger
<floeff@documentfoundation.org> wrote:
Robinson Tryon schrieb am 2014-08-22 um 20:02:
1) Should bugs re: content go to the same place as bugs re:
infrastructure? (Redmine -> Infra -> Help Wiki)

Clearly not, it's a totally different area. :) Only file as infra bug
if it
affects the wiki software per se.

Fair enough. For now, I'll indicate that content bugs should go to
Bugzilla with Component: 'Documentation' and prefix "WIKIHELP:". IIRC
the Documentation Team doesn't interact with Wikihelp, so that might
be our next issue to resolve.

For now this is the l10n team who is taking care of the help files and the
en_US version but it has no time for BZ so bug reports should be directed
to the l10n list. However as I said this is a process we are working on
together with kendy and moggi, discussion is happening on the l10n list.
Cheers
Sophie

-- 
To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.