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


On Thu, May 9, 2013 at 3:01 PM, klaus-jürgen weghorn ol
<ol@sophia-louise.de> wrote:

If we talk about this:
Do the QA-Team need all the BugzAssHlp-templates?
Or maybe we can make one page with all the content?

The BugzAssHlp templates exist to factor-out shared information
between 'Help' and 'Extended Help' pages used by both the BSA and
Bugzilla on FDO. We could make a 'BugzAssHlp sub-category, if that
would help to organize the pages...

I prefer to put all in one category. And for this in the one called
Category:Template because it is the same structure as Template:xxxx.

I guess that MediaWiki could have named the namespace "Templates:",
but perhaps they thought that "Templates:SomethingSomething" might
imply more than a single template.

Anyhow, my preference would be to use the plural consistently
("Features and Enhancements", "Mailing Lists", "Events", "EasyHacks",
"Templates for links", etc..). But if there's strong opposition, then
I understand.

--R

-- 
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.