Notes:
community: Andrew talked about recognizing bug reporters. That is important; we have at times regularly recognized bug reporters in a variety of ways. But other things are important to- mentoring (like kernel janitors), recruitment, and other things can all happen.
triage: if at all possible, don't make developers think about whether or not something is important. Heck, ideally, they shouldn't think about bugs at all – be there for developers to do whatever scutwork they require.
big picture: 'holistic' is a sucky word, but I'll use it anyway- good programmers are good at the details in front of them, and the grand sweep of their architecture. They aren't necessarily good at understanding how much of their own software works.