Hi,
Enrique wrote:
Joerg Barfurth wrote:
Completely unmoderated communication between developers and a wider less techinalical audience often don't work well, as can be seen by the way issue commenting is often (ab)used in ways that are perceived as counterproductive by most developers.But currently the only way to comment on OOo development is through issues. That's where the voice is taken. The "official" advice in in these newsgroups is "file an issue or forget about seeing it in OO ever"
Issuezilla is seen as *the* channel for RFEs
Yes. That advice is correct.
But long discussions with loads of comments that verbosely say "me too", misplaced comments of the "btw, I also have another issue with this function ..." or comments demanding "I need this urgently, why does nothing happen" without understanding that assigned owner, status and target milestone together pretty clearly state whther and for what release an issue will be addressed don't belong into an issue. Similarly repeating twenty steps to reproduce the problem and attaching a dozen screenshots when the owner has long report that the issue could be reproduced and maybe even the fix is understood is not useful. And when this kind of unnessary and redundant information swamps the technical comments that developers (have to) make in the issues to communicate among themselves, then this becomes counterproductive.
Of course the problem is how to teach people the rules for handling issues that don't understand the underlying developement process without scaring them away from submitting issues at all.
Ciao, Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
