Luis's notes:

• why are we here?
• what are we doing well/poorly w/ bugzilla?
  • mail duplication bits- finally kill the damn aliases
  • continued work on query pages
  • better mass manipulation- i.e., 'find all NEEDINFO bugs with no comments in past six months'
  • better API for sync, better processes
  • for company, you have to be hacking against HEAD for it to be basically useful
  • need to email bugmaster to add new versions and such- maybe fixable in 2.18?
• how can we reinvigorate bug days? Saturdays? evenings only? rolling global evenings? formally rotate announcements?
  • big problem is that there are only like 4-10 people who can/do actually do it
  • rotation of days has down and upside
  • shorter bug days? less than weekly, but bigger blowouts?
  • get better about theming bug days
  • continued etiquette training for maintainers and bugsquadders
  • 90% of bugs are easy to triage, 10% hard to triage- how do you deal with the hard to triage ones such that you don't scare them off?
• automated testing- how could we use it in a bugsquad context? paolo's stuff?
  • you'd want to tie it to bug-buddy, or alternately tie it into a build system process if output is sane enough
• testcase databases? if Novell open sourced their testcase database, could we usefully use it?
  • basically a combo database for test cases and databases
  • different questions: would it be useful to corporations who may or may not be working on head? would it be of interest to community members to do it?
• built binary rpms/debs/whatever- these are important, how can we do these again?
  • wouldn't necessary have to be binaries- jhbuild actually packaged/distributed with good instructions to get it log
  • packaging project could concievably be resurrected; can't have single points of failure- we must write things down