-
Notifications
You must be signed in to change notification settings - Fork 157
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1319 from openziti/fix-coc
Fix code of conduct spelling errors
- Loading branch information
Showing
1 changed file
with
1 addition
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,17 +1 @@ | ||
# Code of Conduct | ||
|
||
All open source projects managed by NetFoundry share a common [code of | ||
conduct](https://netfoundry.github.io/policies/CODE_OF_CONDUCT.html) which all contributors are expected to follow. | ||
Please be sure you read, understand and adhere to the thoughts expressed therein. | ||
|
||
Individuals acting in any way that is considered in violation of the Code of Conduct will receive corrective actions | ||
appropriate for the violation. It is possible to act in ways which technically do not violate the Code of Conduct but | ||
are clearly against the spirit of the project. These situations will also be considered on a case by case basis and if | ||
necessary the Code of Conduct will be revised accordingly and approrpiate notifications will be made to the community | ||
and to the violator. | ||
|
||
## Violations | ||
|
||
Contributors violating the Code of Conduct will receive public notification of the violation. Contined violations or | ||
aggregious violations of the Code of Conduct will result in the contributor being removed from the contributors list as | ||
well as further contributions being declined. | ||
All open source projects managed by OpenZiti share a common [code of conduct](https://docs.openziti.io/policies/CODE_OF_CONDUCT.html) which all contributors are expected to follow. Please be sure you read, understand and adhere to the guidelines expressed therein. |