A desire to contribute to Drupal. No programming knowledge required; the talk will be from the perspective of a programmer, but a lot of information is universal and applies to non-programming issues as well.
Let's dive into the Drupal issue queue. What do you do when you encounter an issue in a community component or have an idea for improving Drupal or one of the many contributed projects? Creating issues (and when not to), issue statuses and priorities, creating and rerolling patches and following up. Also, a peak at the future (boo patches!)
This is not specific to frontend or backend developers, and even if you're not a coder but want to contribute in other ways it is good to know how the issue queue works.