Contributing
The PyCon Korea Code of Conduct may be modified to better convey its intentions, purposes, and values. Your contributions can help the PyCon Korea Code of Conduct continue to evolve.
References
The contents of the PyCon Korea Code of Conduct are continuously updated based on the thoughts of those who have considered these issues beforehand.
Documents Referenced
- FEConf 2024 CoC (2024)
- DebConf CoC (2024)
- Debian Code of Conduct (2024)
- AWS Code of Conduct (2024)
- C++Korea Code of Conduct (2024)
- Inflearn 2024 - What to Keep (2024)
- Google Cloud Next 24 Event Conduct (2024)
- DEFCON Code of Conduct (2021)
- OpenInfra Code of Conduct (2020)
- Elastic Community Code of Conduct (2019)
- GitHub Open Source Guides Code of Conduct (2019)
- JSConf EU 2019 Code of Conduct (2019)
- JSConf Korea 2019 Code of Conduct (2019)
- PyCon US 2019 Code of Conduct (2019)
- Spoqa Creator Code of Conduct (2018)
- How and Why We Improved DjangoCon Europe’s Code of Conduct (2018)
Suggestions Welcome
The PyCon Korea Code of Conduct is continuously evolving for a better community. Despite the efforts of the PyCon Korea organizing committee and many others, there is still room for improvement in this Code of Conduct.
You can also participate in the process of improving the Code of Conduct. Feel free to send any suggestions, comments, or relevant content at any time to coc@pycon.kr. Your feedback will be carefully reviewed by the committee.
The PyCon Korea organizing committee believes in the values of transparency and record-keeping. If there are changes to the Code of Conduct, all details will be documented and made available on the website.
Release Notes
- This Code of Conduct was created by the PyCon Korea 2019 organizing committee with the advice of external experts.
- The PyCon Korea 2020 organizing committee modified some contents to suit an online event.