-
Notifications
You must be signed in to change notification settings - Fork 5
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 #13 from atomgalaxy/patch-1
Update text of links and format the title
- Loading branch information
Showing
1 changed file
with
5 additions
and
3 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,7 +1,9 @@ | ||
#Choosing a Code of Conduct | ||
# Choosing a Code of Conduct | ||
|
||
C++ Conferences usually go with either the https://github.com/brycelelbach/cpp_code_of_conduct[C++ Code of Conduct] or the https://berlincodeofconduct.org/[Berlin Code of Conduct]. | ||
C++ Conferences usually go with either the https://github.com/brycelelbach/cpp_code_of_conduct[{cpp} Code of Conduct] or the https://berlincodeofconduct.org/[Berlin Code of Conduct]. | ||
|
||
The *Berlin Code of Conduct* emphasizes more inclusion, while the *C++ Code of Conduct* focuses more on anti-harassment. Both those Code of Conduct are equally trusted by the community and will send a strong signal to attendees from underrepresented group that you intend to protect them in case of problem. | ||
|
||
After choosing your Code of Conduct, keep in mind that you need to actually enforce it if the need arises. Make sure all organizers of your event are aware of it and in line with its interpretation. | ||
After choosing your Code of Conduct, keep in mind that you need to actually enforce it if the need arises. Make sure all organizers of your event are aware of it and in line with its interpretation. | ||
|
||
:cpp: C++ |