Add Code of Conduct

This adds a code of conduct based on Django's to the project.
It is using a symlink for the COC file for the mdbook as mdbook doesn't
seem to handle mdfiles in parent directories

CODE_OF_CONDUCT.md

@@ -0,0 +1,78 @@
+RIOT-rs Code of Conduct
+=======================
+
+RIOT-rs, like so many other free and open source software projects, is made up of a
+mixed group of professionals and volunteers from all over the world, working on
+every aspect of our goals - including teaching, steering, and connecting people.
+
+We want diversity to be one of our greatest strengths, but it can also lead to
+communication issues and unhappiness. This is why we ask people to adhere to a
+few ground rules. They apply equally to founders, maintainers, contributors and
+those seeking help and guidance.
+
+This is not meant to be an exhaustive list of things you are not allowed to do.
+We rather would like you to think of it as a guide to enrich our community and
+the technical community in general with new knowledge and perspectives by
+allowing everyone to participate.
+
+This code of conduct applies to all spaces managed by the RIOT-rs community. This
+includes Matrix, the mailing lists, our GitHub projects, face to face events, and
+any other forums created by the community for communication within the
+community. In addition, violations of this code outside these spaces may also
+affect a person's ability to participate within them.
+
+If you believe someone is violating the code of conduct, we ask that you report
+it by emailing <conduct@riot-os.org>. For more details please see our [Reporting
+Guidelines](https://future-proof-iot.github.io/RIOT-rs/dev/CoC_reporting.html).
+
+-   **Be friendly and patient.**
+-   **Be welcoming.** We strive to be a community that welcomes and supports
+    people of all backgrounds and identities. This includes, but is not limited
+    to members of any race, ethnicity, culture, national origin, colour,
+    immigration status, social and economic class, educational level, sex,
+    sexual orientation, gender identity and expression, age, size, family
+    status, political belief, religion, and mental and physical ability.
+-   **Be considerate.** Your work will be used by other people, and you in turn
+    will depend on the work of others. Any decision you take will affect users
+    and colleagues, and you should take those consequences into account when
+    making decisions. Remember that we're a world-wide community, so you might
+    not be communicating in someone else's primary language.
+-   **Be respectful.** Not all of us will agree all the time, but disagreement
+    is no excuse for poor behavior and poor manners. We might all experience
+    some frustration now and then, but we cannot allow that frustration to turn
+    into a personal attack. It’s important to remember that a community where
+    people feel uncomfortable or threatened is not a productive one. Members of
+    the RIOT-rs community should be respectful when dealing with other members as
+    well as with people outside the RIOT-rs community.
+-   **Be careful in the words that you choose.** We are a community of
+    professionals, and we conduct ourselves professionally. Be kind to others.
+    Do not insult or put down other participants. Harassment and other
+    exclusionary behavior aren't acceptable. This includes, but is not limited
+    to:
+    -   Violent threats or language directed against another person.
+    -   Discriminatory jokes and language.
+    -   Posting sexually explicit or violent material.
+    -   Posting (or threatening to post) other people's personally identifying
+        information ("doxing").
+    -   Personal insults, especially those using racist or sexist terms.
+    -   Unwelcome sexual attention.
+    -   Advocating for, or encouraging, any of the above behavior.
+    -   Repeated harassment of others. In general, if someone asks you to stop,
+        then stop.
+-   **When we disagree, try to understand why.** Disagreements, both social and
+    technical, happen all the time and RIOT-rs is no exception. It is important
+    that we resolve disagreements and differing views constructively. Remember
+    that we’re different. The strength of RIOT-rs comes from its varied community,
+    people from a wide range of backgrounds. Different people have different
+    perspectives on issues. Being unable to understand why someone holds a
+    viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to
+    err and blaming each other doesn’t get us anywhere. Instead, focus on
+    helping to resolve issues and learning from mistakes.
+
+Text based on the Code of Conduct of the [Django
+community](https://www.djangoproject.com/conduct/).
+
+Questions?
+----------
+
+If you have questions, please feel free to [contact us](mailto:conduct@riot-os.org).

book/src/COC_reporting.md

@@ -0,0 +1,74 @@
+If you believe someone is violating the code of conduct we ask that you
+report it to us by emailing <conduct@riot-os.org>.
+
+**All reports will be kept confidential.** In some cases we may determine that a
+public statement will need to be made. If that's the case, the identities of all
+victims and reporters will remain confidential unless those individuals instruct
+us otherwise.
+
+**If you believe anyone is in physical danger, please notify appropriate law
+enforcement first.** If you are unsure what law enforcement agency is
+appropriate, please include this in your report and we will attempt to notify
+them.
+
+If you are unsure whether the incident is a violation, or whether the space
+where it happened is covered by this Code of Conduct, we encourage you to still
+report it. We would much rather have a few extra reports where we decide to take
+no action, rather than miss a report of an actual violation. We do not look
+negatively on you if we find the incident is not a violation. And knowing about
+incidents that are not violations, or happen outside our spaces, can also help
+us to improve the Code of Conduct or the processes surrounding it.
+
+In your report please include:
+
+-   Your contact info (so we can get in touch with you if we need to follow up)
+-   Names (real, nicknames, or pseudonyms) of any individuals involved. If there
+    were other witnesses besides you, please try to include them as well.
+-   When and where the incident occurred. Please be as specific as possible.
+-   Your account of what occurred. If there is a publicly available record (e.g.
+    a mailing list archive or a public Matrix logger) please include a link.
+-   Any extra context you believe existed for the incident.
+-   If you believe this incident is ongoing.
+-   Any other information you believe we should have.
+
+### What happens after you file a report?
+
+You will receive an email from one of the core community members as soon as
+possible. We promise to acknowledge receipt within 24 hours (and will aim for
+much quicker than that).
+
+They will review the incident and determine:
+
+-   What happened.
+-   Whether this event constitutes a code of conduct violation.
+-   Who the bad actor was.
+-   Whether this is an ongoing situation, or if there is a threat to anyone's
+    physical safety.
+
+If this is determined to be an ongoing incident or a threat to physical safety,
+their immediate priority will be to protect everyone involved.
+This means we may delay an "official" response until we believe that the
+situation has ended and that everyone is physically safe.
+
+Once the working group has a complete account of the events they will make a
+decision as to how to response. Responses may include:
+
+-   Nothing (if we determine no violation occurred).
+-   A private reprimand from us to the individual(s) involved.
+-   A public reprimand.
+-   An imposed vacation (i.e. asking someone to "take a week off" from a mailing
+    list or Matrix).
+-   A permanent or temporary ban from some or all RIOT-rs spaces (mailing lists,
+    Matrix, etc.)
+-   A request for a public or private apology.
+
+We'll respond within one week to the person who filed the report with either a
+resolution or an explanation of why the situation is not yet resolved.
+
+Once we've determined our final action, we'll contact the original reporter to
+let them know what action (if any) we'll be taking. We'll take into account
+feedback from the reporter on the appropriateness of our response, but we don't
+guarantee we'll act on it.
+
+#### Reference
+These reporting guidelines were adapted from the [Django reporting guidelines](https://www.djangoproject.com/conduct/reporting/)

book/src/CODE_OF_CONDUCT.md

@@ -0,0 +1 @@
+../../CODE_OF_CONDUCT.md

book/src/SUMMARY.md

@@ -2,6 +2,8 @@
 
 - [Manifesto](./manifesto.md)
 - [Introduction](./introduction.md)
+- [Code of Conduct](./CODE_OF_CONDUCT.md)
+  - [Reporting Guidelines](./COC_reporting.md)
 
 # User Guide