openbmc bug management

[Andrew Geissler]

Currently we mostly open bugs against openbmc/openbmc.  This is nice
in that it provides a single location to search for all bugs related
to openbmc, but it doesn't provide any clear ownership for someone to
drive the bug, and it becomes more and more unmanageable as the
openbmc project continues to grow.

Per the community call topic today, we'd like to start having bugs
assigned to the specific repo that will provide the fix to the bug.
The main concern with this is that if someone is unsure on where the
bug should go and takes a best guess, if the guess is wrong, how do we
ensure the bug gets routed correctly?  The idea was that it's the
responsibility of the creator of the bug, so the repo owner says
something to the affect of "not my problem" (with some guidance on
who's it is if they know) and the bug submitter will then use the
zenhub option "Move Issue" to close it in the current repo and copy it
over to the new repo.

Thoughts or concerns?
Andrew