Hence the quote, "Issue queue or it didn't happen." That was Drupal's idiom and it still applies to projects in general.
> While all of these other communication mechanisms are great, esp. for hashing things out more effectively in real time, it's absolutely critical that a summary of what was talked about make its way back here for the benefit of those who couldn't be there, including Google, and yourself 2 weeks later when you totally forget what you talked about. :P There needs to be a URL to point people at who have questions later on. However. As a text-based medium, the issue queues are an ABSOLUTELY HORRIBLE medium through which to have a heated discussion about whatever. For that you turn to one of the others.
> While all of these other communication mechanisms are great, esp. for hashing things out more effectively in real time, it's absolutely critical that a summary of what was talked about make its way back here for the benefit of those who couldn't be there, including Google, and yourself 2 weeks later when you totally forget what you talked about. :P There needs to be a URL to point people at who have questions later on. However. As a text-based medium, the issue queues are an ABSOLUTELY HORRIBLE medium through which to have a heated discussion about whatever. For that you turn to one of the others.
https://www.reddit.com/r/drupal/comments/1qz9l9/i_am_angie_w...