Bug 60059 - BUGZILLAASSISTANT: Improve Wording "Sub Component"
Summary: BUGZILLAASSISTANT: Improve Wording "Sub Component"
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: WWW (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-30 07:37 UTC by Rainer Bielefeld Retired
Modified: 2013-04-21 15:15 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Bielefeld Retired 2013-01-30 07:37:06 UTC
For historic reasons we created some some Sub components with a similar function as the "Component" in AOOo.

This is useful and no discussion is needed, but I believe these key words should get a new name encouraging for a more liberal use in the summary line, what would lead to more useful summaries without duplicate words. I often See summaries like 
"FILEOPEN: Crash when open file", where I would prefer 
"CRASH when FILEOPEN" (what saves space for other useful info)
or 
"FILEOPEN FORMATTING PIVOTTABLE: When I open a document with conditional formatting in the data pilot libreOffice crashes", where I would prefer 
CRASH when FILEOPEN document with CONDITIONAL FORMATTING in PIVOTTABLE

Although I believe that currently there is no alternative for the BSA to start the summary with the most important key word (AKA "Sub component), here and in Wiki explications in future we should find a better name showing that those words in capital letters are key words to ease queries and to show most important parts of the summary. But the are no sanctum what have to be used without integration into rest of summary text.

I believe we should encourage users to use those key words (AKA "Sub component) in summary for telegram style sentences (without integrating too many ones) like

May be this needs some discussion on QA mailing list?
Comment 1 Marc Pare 2013-02-10 12:36:58 UTC
Hi Rainer,

I don't think this should be in Bugzilla. This should be on the discussion list where it can be discussed and come to a conclusion. Could you take it up there instead?

Some of the working in EN could become confusing to a newcomer and even an EN user/member. 

But, again, this should better be discussed on the discussion list.

Cheers,

Marc
Comment 2 Rainer Bielefeld Retired 2013-02-10 15:52:52 UTC
(In reply to comment #1)
> May be this needs some discussion on QA mailing list?

If nobody else starts a discussion I will do (end of February or so).
Comment 3 Florian Reisinger 2013-04-21 15:15:59 UTC
@Rainer: I seem to have this discussion missed....