🔄 Synced file(s) with SymbiFlow/symbiflow-common-config

CODE_OF_CONDUCT.md

@@ -0,0 +1,65 @@
+# 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 orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* 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 advances
+* 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
+the project team at [[email protected]](mailto:[email protected]).
+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 [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/
+

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to Project U-Ray
+# Contributing to SymbiFlow Projects
 
-There are a couple of guidelines when contributing to Project U-Ray which are
+There are a couple of guidelines when contributing to SymbiFlow Projects which are
 listed here.
 
 ### Sending
@@ -11,8 +11,8 @@ All contributions should be sent as
 ### License
 
 All software (code, associated documentation, support files, etc) in the
-Project U-Ray repository are licensed under the very permissive
-[Apache-2.0 License](LICENSE). A copy can be found in the [`LICENSE`](LICENSE) file.
+Symbiflow repositories are licensed under the very permissive
+[ISC Licence](https://opensource.org/licenses/ISC). A copy can be found in the [`LICENSE`](LICENSE) file.
 
 All new contributions must also be released under this license.
 
@@ -78,20 +78,4 @@ You can add the signoff as part of your commit statement. For example:
 following command to add signoffs to all commits between you and the upstream
 master:
 
-    git rebase --signoff upstream/master
-
-### Contributing to the docs
-
-In addition to the above contribution guidelines, see the guide to
-[updating the Project U-Ray docs](UPDATING-THE-DOCS.md).
-
-
-
-
-
-
-----
-
-This file is generated from [README.md](README.md), please edit that file then
-run the `./.github/update-contributing.py`.
-
+    git rebase --signoff upstream/master