c81cfb89bc
In an ideal world, we would all get along together very well, always be polite and never end up in huge conflicts. And even if there are conflicts, we would always handle each other fair and respectfully. Unfortunately, this is not an ideal world and sometimes people forget how to interact with each other in a professional and respectful way. Fortunately, this seldom happens in the QEMU community, but for such rare cases it is preferrable to have a basic code of conduct document available to show to people who are misbehaving. In case that does not help yet, we should also have a conflict resolution policy ready that can be applied in the worst case. The Code of Conduct document tries to be short and to the point while trying to remain friendly and welcoming; it is based on the Fedora Code of Conduct[1] with extra detail added based on the Contributor Covenant 1.3.0[2]. Other proposals included the Contributor Covenant 1.3.0 itself or the Django Code of Conduct[3] (which is also a derivative of Fedora's) but, in any case, there was agreement on keeping the conflict resolution policy separate from the CoC itself. An important point is whether to apply the code of conduct to violations that occur outside public spaces. The text herein restricts that to individuals acting as a representative or a member of the project or its community. This is intermediate between the Contributor Covenant (which only mentions representatives of the community, for example using an official project e-mail address or posting via an official social media account), and the Django Code of Conduct, which says that violations of this code outside these spaces "may" be considered but otherwise applies no limit. The conflict resolution policy is based on the Drupal Conflict Resolution Policy[4] and its derivative, the Mozilla Consequence Ladder[5]. [1] https://www.fedoraproject.com/code-of-conduct/ [2] https://www.contributor-covenant.org/version/1/3/0/code-of-conduct/ [3] https://www.djangoproject.com/conduct/ [4] https://www.drupal.org/conflict-resolution [5] https://github.com/mozilla/diversity/blob/master/code-of-conduct-enforcement/consequence-ladder.md Co-developed-by: Thomas Huth <thuth@redhat.com> Reviewed-by: David Edmondson <david.edmondson@oracle.com> Reviewed-by: Alex Bennée <alex.bennee@linaro.org> Reviewed-by: Thomas Huth <thuth@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
45 lines
725 B
ReStructuredText
45 lines
725 B
ReStructuredText
.. This is the top level page for the 'devel' manual.
|
|
|
|
|
|
QEMU Developer's Guide
|
|
======================
|
|
|
|
This manual documents various parts of the internals of QEMU.
|
|
You only need to read it if you are interested in reading or
|
|
modifying QEMU's source code.
|
|
|
|
Contents:
|
|
|
|
.. toctree::
|
|
:maxdepth: 2
|
|
:includehidden:
|
|
|
|
code-of-conduct
|
|
conflict-resolution
|
|
build-system
|
|
style
|
|
kconfig
|
|
testing
|
|
fuzzing
|
|
control-flow-integrity
|
|
loads-stores
|
|
memory
|
|
migration
|
|
atomics
|
|
stable-process
|
|
qtest
|
|
decodetree
|
|
secure-coding-practices
|
|
tcg
|
|
tcg-icount
|
|
tracing
|
|
multi-thread-tcg
|
|
tcg-plugins
|
|
bitops
|
|
reset
|
|
s390-dasd-ipl
|
|
clocks
|
|
qom
|
|
block-coroutine-wrapper
|
|
multi-process
|