Thread:Talk:Groups/Proposals/Bug Squad/How to evaluate Bug Days?/reply

The parameters depend on what our aims for bugdays are -- not sure how quantifiable that is. My personal aims are probably to hang around with some great people (triagers and developers), to get to know new great people, try to keep everybody around and involved in our community (they often might move on from triaging to something else), and as the actual short term actions: discussing some bug reports and "resurrecting" them while everybody learns something from each other while having fun. That's hard to put into numbers. :)


 * How many people involved sounds like a good argument, but maybe also in which channels we announced a bugday and in which time(zone) it took place, assuming we want to use numbers to steadily improve our outreach.
 * Number of reports acted on feels less relevant if we spend time explaining triage to people and try to make connections. If I explain a lot of basics, I triage less, still it can feel like a successful bugday.
 * "How did newcomers found out about it?" which translates to "Which communication channels are important?", e.g. one newcomer from the last bugday found out because of the message on [en.wikipedia.org/wiki/Wikipedia:Village_pump|English Wikipedia's Village Pump].