Bug management/Meeting preparations


 * Choose a topic
 * Talk to product directors/managers
 * The i18n team, for example, wants to do triages every second wednesday.
 * New products or features that have rolled out are a good choice
 * After the introduction of a particularly change-laden semi-weekly rollout, there may be lots of trouble.
 * General triage of village pump issues should be done every few weeks anyway.
 * Produce a list of bugs to cover
 * If you're familiar with the bug database and have some grasp of the topic, then this should not be too hard.
 * Unresolved village pump issues are natural issues to cover.
 * Set up an Etherpad
 * Lay out the list of bugs to cover in the order you think they should be covered.
 * Add any necessary description.
 * Link to the bug so that people can comment on them or quickly follow up during the triage.
 * Possibly meet up with one or two main stakeholders to do a pre-meeting
 * This will give you a chance to figure out which things may be non-issues.
 * Announce the triage on [WikiTech-l]
 * Update the triage calendar.
 * Hold the triage.