-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/12/12 07:28, Frank Reininghaus wrote: > Hi Anne, > > 2012/12/10 Anne Wilson: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 10/12/12 09:50, Frank Reininghaus wrote: >>>> There is a perception that devs don't listen. This is not a >>>>> complaint, on my part, but a statement of fact. >>> Well, I can't speak for all developers, but on my side, there >>> is a perception that some people believe "If I have a good >>> idea, it will either be implemented by the maintainer of the >>> application, or it will not be implemented at all, and then the >>> maintainer has to provide an explanation why he/she won't >>> implement it". This is confirmed by... >>> >> I agree - there is a lot of misunderstanding. That's why I >> think that if we can come up with a simple acknowledgement >> (that's why I suggested something boilerplate) some of the >> misunderstanding can be avoided. > > Yes, I think that we all agree that the frustration that results > from such misunderstandings should be avoided. However, I would > say that the average wishlist report on bugs.kde.org can usually > not be responded to with a standard reply. But this might of course > be different for ideas which have already been discussed thoroughly > at KDE Brainstorm. > One thing I have wondered about is whether it is worth adding some flag to show which are brainstorm wishes, making it easier to assess whether they are in fact of a higher standard.
A point that comes to mind, is that I have seen wishes that are complex, being in reality a combination of several ideas, which may or may not work together. When such an idea comes up in brainstorm the writer is told that that is invalid. A brainstorm idea must be about a single issue. That makes it easier to direct discussion in a meaningful way, and helps the mods to see whether it is something worth passing upstream. If we could prove that brainstorm works better for all concerned we could make that the *normal* way of submitting wishes :-) Anne -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDHE4EACgkQj93fyh4cnBeDnACeNSWilA+qOTWi5ZnzXIF9d6e2 atsAnR0LDAwjp6r+kQE2t70PANJe7ZiQ =Zsn9 -----END PGP SIGNATURE----- >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<