Hm, let me make sure I understand this.
You ask for an important change, want it to be motivated by *voting* (instead of an educated decision on sound technical base and estimation of impact) -- and you feel you're not able to provide summaries of existing problems?
Note, Greg didn't ask you to reproduce the existing bugs, he merely suggested that you have a look onto the tracked issues in order to help with getting an overview, which is a very useful suggestion in my mind, because it is something that everybody can help with; it doesn't require programming skills. It would be very constructive, IMO, and a very valuable form of contribution.
Probably you don't know that this is going on on bugzilla, as suggested by Takashi. I'm collecting the information on how to eventually proceed, and I'll open two trackers, one for GNOME and one for KDE, soon. A summary of a problem is simply its description: it might be the title of bugreport. I can surely do that. The question is: would it be of any use to fix problems? In my answer I meant that that summary would be of very limited use to fix those problems, which is what Greg wants to try to do. I can write that "User X has the problem Y on hardware Z", but if I don't have the hardware Z and user X doesn't provide feedback himself, you have no real advantage from the summary. It might help to decide what to do though, that's granted. Regards, A. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org