Browse files

Add code of conduct

  • Loading branch information...
1 parent d60e590 commit 160762e4ab447d2ea02c66fd2f35e493b698a026 @baldurk committed May 22, 2016
Showing with 86 additions and 17 deletions.
  1. +78 −0
  2. +0 −15
  3. +5 −0
  4. +3 −2
@@ -0,0 +1,78 @@
+I want RenderDoc to be an open and welcoming project, and for that reason I want to make sure that people feel secure joining the project by outlining and enforcing expected behaviour from members of the community. This code is used in many open source projects and embodies that spirit of inclusiveness well.
+The full text is listed below. Anywhere that 'the project maintainers' are referred to as a collective group, this currently refers just directly to me. If you have any queries or issues with the code of conduct, you can get in touch with me [directly via email](
+# Contributor Covenant Code of Conduct
+## Our Pledge
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+## Our Standards
+Examples of behavior that contributes to creating a positive environment
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+Examples of unacceptable behavior by participants include:
+* The use of sexualized language or imagery and unwelcome sexual attention or
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+## Our Responsibilities
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other 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
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social 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 project maintainers.
+## Enforcement
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting myself the project leader at []( All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+Project maintainers 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.
+## Attribution
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [][version]
@@ -1,11 +1,3 @@
-Each RenderDoc back-end is called a 'driver' and is under the renderdoc/driver/ folder. If you don't have the SDK or don't care about a particular API you can remove a driver from building - in the Makefile by editing LIBS= in renderdoc/Makefile, in VS by removing the project and the reference on the renderdoc reference. Be aware of dependencies, such as D3D11 expecting DXGI to be loaded too.
-Some shared code for handling shader formats used in multiple APIs such as DXBC and SPIR-V are in renderdoc/driver/shaders/ folder.
@@ -49,10 +41,3 @@ sudo pacman -S libx11 xcb-util-keysyms mesa mesa-libgl qt5-base qt5-x11extras
If you know the required packages for another distribution, please share (or pull request this file!)
-Official releases will get a github release made for them, nightly builds and beta are just marked with the hash of the commit they were built from.
-Please don't distribute releases marked with a version number and commit hash as it will confuse me with auto-submitted crashes since I won't have the symbols for them. If you distribute releases leave the version information as is (master is always marked as an unofficial non-versioned build).
@@ -30,6 +30,11 @@ Copyright / Contributor License Agreement
Any code you submit will become part of the repository and be distributed under the [RenderDoc license]( By submitting code to the project you agree that the code is your own work and that you have the ability to give it to the project. You also agree by submitting your code that you grant all transferrable rights to the code to the project maintainer, including for example re-licensing the code, modifying the code, distributing in source or binary forms.
+Code of Conduct
+I want to ensure that anyone can contribute to RenderDoc with only the next bug to worry about. For that reason the project has adopted the [contributor covenent]( as a code of conduct to be enforced for anyone taking part in RenderDoc development. If you have any queries in this regard you can get in touch with me [directly over email](
Code Explanation
@@ -12,10 +12,11 @@ Quick Links:
* **Downloads**:
* **Documentation**: renderdoc.chm in the build, or
* **Tutorials**: There are some video tutorials on Youtube:
-* **Email contact**:
+* **Email contact**: [](
* **IRC channel**: #renderdoc on freenode
* **Roadmap/future development**: [Roadmap](
* **Starting place for developing/contributing**: [](
+* **Code of Conduct**: [contributor covenent](
* **How to compile**: [](
@@ -69,5 +70,5 @@ Building RenderDoc is fairly straight forward. See []( for
Contributing & Development
-I've added some notes on how to contribute, as well as where to get started looking through the code in []( - check there for more details on how to set up to build renderdoc and where to start contributing to its development.
+I've added some notes on how to contribute, as well as where to get started looking through the code in []( - also look at []( for details on how to set up to build renderdoc.

0 comments on commit 160762e

Please sign in to comment.