Documentation/GettingStartedDevelopers: Difference between revisions

Revision as of 01:50, 5 April 2011

You want to contribute code, documentation or patches to QEMU?

Then...

... you should probably first join the mailing list.

Wiki

Create yourselves an account in the QEMU wiki.
Start with reading the QEMU wiki.
Contribute to the QEMU wiki by adding new topics or improving and expanding existing topics. It should help you and others in the future.

Documentation

Continue with reading the existing documentation.

Be prepared that all written documentation might be invalid - either because it is too old or because it was never correct. And it is never complete...

If you find bugs in the documentation then fix them and send patches to the mailing list. See Contribute/ReportABug.

Code

Run the QEMU system and user mode emulation for different targets (x86, mips, powerpc, ...).
QEMU has a lot of different parts (hardware device emulation, target emulation, code generation for different hosts, configuration, ...).

Choose an interesting part and concentrate on it for some time and read the code. QEMU does not have a high level design description document.

If you find bugs in the code, then fix them and send a patch to the mailing list. See Contribute/ReportABug.

Bugs

Read the Bug Tracker.
Check for topics in it for which you feel capable of handling and try to fix the issue. Send patches.

@@ Line 17: / Line 17: @@
 * Run the QEMU system and user mode emulation for different targets (x86, mips, powerpc, ...).
 * QEMU has a lot of different parts (hardware device emulation, target emulation, code generation for different hosts, configuration, ...).
-:Choose an interesting part and concentrate on it for some time and read the code.
+:Choose an interesting part and concentrate on it for some time and read the code. QEMU does not have a high level design description document.
 * If you find bugs in the code, then fix them and send a patch to the mailing list. See [[Contribute/ReportABug]].