On 2017-03-03 09:53, Miroslav Suchý wrote:
Dne 2.3.2017 v 15:17 Andreas Nilsson napsal(a):
> Excellent. That simplifies the UI a lot.
> Made these changes to the mockup:
I was thinking about the "Report" button and "Reported". The term
"report" is little bit overloaded as someone can
expect that it will in fact open a BZ issue. How we can emphasize the difference between
"File issue"? The fact that
"Report" button send just microreport to FAF (stripped of any private data)?
I was thinking about:
* "Send MicroReport" - too long
* "μReport" or "microReport" - too cryptic?
* leave it as is
I would welcome any other ideas.
Yeah, "Microreport" is probably a bit cryptic indeed, and very much an
implementation detail in my mind.
Looking at reporting functions from other systems, they are a bit more
explicit about where they send them.
* "Send to Apple" in MacOS
* "Tell Mozilla about this..."
* "Windows can send descriptions of problems on this server to
Microsoft..." (in the settings only) https://i.stack.imgur.com/lo6fC.png
Those are mostly concerned with who you're reporting this information
to, and doesn't worry too much about the distinction between the report
collector and the bug tracker.
One solution could be to give it a tooltip with a string like "Report to
Fedora Analysis Framework" or "Report to Fedora problem analysis
server". That addresses both the destination and difference to bugzilla.
I wouldn't put it directly in the button, since it's such a long string,
and it can become even longer in some languages.
How does it work in the cases of RHEL or CentOS? Does those problems get
publicly published in the same place, or do they have separate problem