There is a fundamental problem here, albeit one that is rooted in simple misunderstanding.
The burden of proof is on the originator of an idea (i.e., the ticket reporter). Arguments can be made against the idea in the ticket. Rebuttal is sent elsewhere. Regardless of the intention, this automatically creates contention (in some cases) because it appears as a double standard, as arbitrary discretion is used to draw a line in the sand (the point at which the discussion should be moved to the mailing list). The solution could be either: A) Allow for full discussion in a ticket (this may not be an option, based on the conversations I've read) or B) Disallow only technical (how to fix, code review, etc.) discussion in a ticket, and make it easy to get from a ticket to its discussion thread and back again. Option A allows for easier collaboration on business aspects by incorporating technical considerations into the conversation at the expense of extra noise. Option B allows for easier digestion of either tech or business at the expense of a lack of cohesion among both parties. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
