Some bugs are hard to triage and collect large amounts of comments before they are fully grasped. This makes it hard for a developer get a grip quickly what the status quo of a bug is.

This QA EasyHack asks you to:
1/ take a look at these unresolved bugs that have more than 20 comments:

   http://goo.gl/6bRh8T (*)

2/ Summarize all the provided information in the comments, discarding pointless "affects me too" or "why is this not fixed yet?" noise in one short overview
   (best referencing the comments that provided the interesting bits)

3/ Edit the summary of the line and add "summary in comment #XYZ" as e.g. in
   https://bugs.freedesktop.org/show_bug.cgi?id=46447

4/ Add "SummaryUpdate" to whiteboard status. This will make the bug disappear from the query from 1/.

5/ Please try to submit all changes at once, as otherwise people will get a lot of mails.


Developers might remove the SummaryUpdate tag in whiteboard status if there are more comments after the initial summary, that need to be included in another update of the summary.


(*) full query: https://bugs.freedesktop.org/buglist.cgi?f1=longdescs.count&list_id=386322&o1=greaterthaneq&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&v1=20&v2=SummaryUpdate&product=LibreOffice