Underline section titles.
Convert links to RST-style links. NB that the Communication Guide
link won't work ATM; this will be fixed when we convert that document
to RST.
Adjust the formatting for the list so that it's converted properly.
A couple of clean-ups:
* Expand the label for communication guidance, and convert the link to
the project governance to a named reference rather than an "embedded"
URI.
* Move all hyperlink targets to the bottom of the article, and put
them in the order they're linked.
No changes to the text.
Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxx>
---
...code-of-conduct.md => code-of-conduct.rst} | 39 ++++++++++++-------
source/conf.py | 2 +-
source/index.rst | 1 +
3 files changed, 27 insertions(+), 15 deletions(-)
rename source/{code-of-conduct.md => code-of-conduct.rst} (83%)
diff --git a/source/code-of-conduct.md b/source/code-of-conduct.rst
similarity index 83%
rename from source/code-of-conduct.md
rename to source/code-of-conduct.rst
index a6080cd..81efe04 100644
--- a/source/code-of-conduct.md
+++ b/source/code-of-conduct.rst
@@ -1,6 +1,8 @@
-# Xen Project Code of Conduct
+Xen Project Code of Conduct
+***************************
-## Our Pledge
+Our Pledge
+==========
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to make participation in our project and
@@ -9,12 +11,13 @@ size, disability, ethnicity, sex characteristics, gender
identity and
expression, level of experience, education, socio-economic status,
nationality,
personal appearance, race, religion, or sexual identity and orientation.
-## Our Standards
+Our Standards
+=============
We believe that a Code of Conduct can help create a harassment-free environment,
but is not sufficient to create a welcoming environment on its own: guidance
on
creating a welcoming environment, how to communicate in an effective and
-friendly way, etc. can be found [here][guidance]].
+friendly way, etc. can be found `here <Communication Guidance_>`_.
Examples of unacceptable behavior by participants include:
@@ -27,7 +30,8 @@ Examples of unacceptable behavior by participants include:
* Other conduct which could reasonably be considered inappropriate in a
professional setting
-## Our Responsibilities
+Our Responsibilities
+====================
Project leadership team members are responsible for clarifying the standards of
acceptable behavior and are expected to take appropriate and fair corrective
@@ -39,7 +43,8 @@ contributions that are not aligned to this Code of Conduct,
or to ban
temporarily or permanently any contributor for other behaviors that they deem
inappropriate, threatening, offensive, or harmful.
-## Scope
+Scope
+=====
This Code of Conduct applies within all project spaces of all sub-projects,
and it also applies when an individual is representing the project or its
@@ -49,7 +54,8 @@ media account, or acting as an appointed representative at an
online or offline
event. Representation of a project may be further defined and clarified by the
project leadership.
-## What to do if you witness or are subject to unacceptable behavior
+What to do if you witness or are subject to unacceptable behavior
+=================================================================
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting Conduct Team members at conduct@xxxxxxxxxxxxxx. All
@@ -67,25 +73,30 @@ Project leadership team members who do not follow or
enforce the Code of Conduct
in good faith may face temporary or permanent repercussions as determined by
other members of the project's leadership.
-## Conduct Team members
+Conduct Team members
+====================
+
Conduct Team members are project leadership team members from any
sub-project. The current list of Conduct Team members is:
+
* Lars Kurth <lars dot kurth at xenproject dot org>
