Hi; this is something of a survey question. I'm particularly
interested in answers from people who've recently had to go through
the process of getting up to speed with working on QEMU, so
I've cc'd our current Outreachy and GSoC students, but input
from anybody is welcome.

* If we did one thing to make it easier for new contributors to get
  started, what should it be?

Very wide focus -- could be anything, better documentation, better
processes, test infrastructure, code changes, whatever.
Some possible things I've thought of:
  * better documentation of top-level qemu internals, like a
    source layout roadmap?
  * specific "missing pieces" that trip people up (eg not having
    a good intro to how to write QOM/qdev devices)?
  * better curation of 'bite sized tasks' list?
But I've been working on QEMU for years, so my impressions could
well be wrong. I'm hoping we can come up with a top 2 or 3 things
to work on improving/fixing, to try to make a difference for future
new contributors...

thanks in advance
-- PMM

Reply via email to