Set up the environment and add organize/coc.md

.gitignore

@@ -0,0 +1,221 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm-project.org/#use-with-ide
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+### macOS ###
+# General
+.DS_Store
+.AppleDouble
+.LSOverride
+
+# Icon must end with two \r
+Icon
+
+
+# Thumbnails
+._*
+
+# Files that might appear in the root of a volume
+.DocumentRevisions-V100
+.fseventsd
+.Spotlight-V100
+.TemporaryItems
+.Trashes
+.VolumeIcon.icns
+.com.apple.timemachine.donotpresent
+
+# Directories potentially created on remote AFP share
+.AppleDB
+.AppleDesktop
+Network Trash Folder
+Temporary Items
+.apdisk
+
+### macOS Patch ###
+# iCloud generated files
+*.icloud
+
+### Windows ###
+# Windows thumbnail cache files
+Thumbs.db
+Thumbs.db:encryptable
+ehthumbs.db
+ehthumbs_vista.db
+
+# Dump file
+*.stackdump
+
+# Folder config file
+[Dd]esktop.ini
+
+# Recycle Bin used on file shares
+$RECYCLE.BIN/
+
+# Windows Installer files
+*.cab
+*.msi
+*.msix
+*.msm
+*.msp
+
+# Windows shortcuts
+*.lnk

README.md

@@ -0,0 +1 @@
+# pycontw-documentation

docs/index.md

@@ -0,0 +1,3 @@
+# PyCon TW Documentation
+
+This website serves as a repository for the transition documents from PyCon TW throughout the years.

docs/organize/coc.md

@@ -0,0 +1,129 @@
+---
+title: 行為準則 Code of Conduct
+summary: 
+    PyCon Taiwan 致力於為所有人提供無騷擾的會議體驗（包含數位場域），我們不容許以任何形式騷擾任何參與者、不容許任何的騷擾和性別歧視、種族主義或排他性笑話。本公約適用於參與者在 PyCon Taiwan 相關場域中的一切言行，期望大家一起合作。
+
+    PyCon Taiwan aims to provide a joyous, pleasant and vibrant environment. This convention applies to all the words and deeds of participants in the relevant entities and digital fields of PyCon Taiwan. It is hoped that everyone will work together to make PyCon Taiwan full of mutual respect and trust.
+authors:
+    - PyCon TW organizers
+date: 2023-01-01
+---
+
+# 行為準則 Code of Conduct
+
+PyCon Taiwan 致力於為所有人提供無騷擾的會議體驗（包含數位場域），我們不容許以任何形式騷擾任何參與者、不容許任何的騷擾和性別歧視、種族主義或排他性笑話。本公約適用於參與者在 PyCon Taiwan 相關場域中的一切言行，期望大家一起合作。
+
+PyCon Taiwan aims to provide a joyous, pleasant and vibrant environment. This convention applies to all the words and deeds of participants in the relevant entities and digital fields of PyCon Taiwan. It is hoped that everyone will work together to make PyCon Taiwan full of mutual respect and trust.
+
+## 三大準則 Principles
+
+PyCon Taiwan 致力於為所有人提供無騷擾的會議體驗（包含數位場域），我們不容許以任何形式騷擾任何參與者。期望大家一起合作，務必遵守以下三大原則，PyCon Taiwan 籌備團隊有權調整任何違反此準則的行為。
+
+PyCon Taiwan is dedicated to providing a harassment-free conference experience for everyone. We do not tolerate harassment toward conference participants in any form.Remember that harassment and jokes that are sexist, racist, or exclusionary are not tolerated at PyCon Taiwan. PyCon Taiwan take appropriate actions to redirect behavior violating the Code of Conduct.
+
+### 禁止騷擾 Do not Harass Others
+
+大會不容忍任何的騷擾或歧視。無分國籍、種族、語言、性別、性取向、年齡、身心狀況、信仰、職業、資歷、政治傾向、智力等，每一位參與者都應該獲得同樣的尊重。
+
+PyCon Taiwan will not tolerate any form of harassment and discrimination. Each attendee should be equally respected regardless of nationality, race, language, gender, sexual orientation, age, disability, physical appearance, faith, profession, seniority, political view, or intellect.
+
+### 彼此欣賞 Appreciate Each Other
+
+每位參與者都應該抱持專業的態度與行為。Python 的使用者來自不同的專業分工、技術背景與應用領域。我們以非常多樣的方式使用並貢獻 Python 技術。任何貶低社群中其它成員的言行都是不適當的。
+
+Each attendee is expected to act professionally when attending PyCon Taiwan. Users of Python are diverse in their professional roles, technical backgrounds, and application areas. They contribute to the technology in many different ways, some amazingly unimaginable. Opinions or actions that undervalue other members of the community are inappropriate and will not be tolerated.
+
+### 體貼他人 Show Consideration
+
+請勿在大會的任何場合做出任何形式的性暗示。這些場合包含但不限於演講、開放空間、社群媒體。請避免源自刻板印象的言行。會議中請把手機調為靜音，或是其它不會影響他人的模式。
+
+Sexual contents in any form are inappropriate in any conference venue, including but not limited to talks, open spaces, or social media. Words and actions originated from stereotypes are discouraged. Cell phones should be set to silent or a mode that does not annoy others in the conference rooms.
+
+## 違反與通報 Violation and Reporting
+
+籌備團隊有權調整任何違反此準則的行為。僅需根據籌備團隊的裁決，違反本行為準則者可能必須離開會場（包含數位場域）並不得要求退費。本行為準則適用於實體場地與數位場域，並經由籌備團隊認可執行。
+
+Conference organizers will take appropriate actions on behaviors violating the Code of Conduct. Violators may be required to leave the conference without a refund at the sole discretion of the organizers. This Code of Conduct is applicable to both physical and online events approved by the organizers of PyCon Taiwan.
+
+### 通報要件 Requirements
+
+如果您認為某人處於危險之中（包含他們自己造成的危險），確實感到自己的安全受到威脅，請立即撥打 110 以聯繫臺灣執法單位，或詢問 PyCon Taiwan 工作人員。如果不確定該事件是否違規，或所發生場域是否在行為準則範疇內，我們仍然鼓勵您通報。
+
+If you believe someone is in danger, including from themselves, the most important thing is to find help. If you feel your safety is in jeopardy, please immediately contact law enforcement in Taiwan (dialing 110 in Taiwan). Ask an organizing staff if you do not have a cell phone. If you believe the Code of Conduct has been violated, please report the incident to a staff member right away. If you are unsure whether it is a violation, or whether the space where it has happened is covered by this Code of Conduct, we encourage you to still report it.
+
+### 如何通報 How to Report
+
+如果發生衝突，可以直接聯繫任一通報應變者：
+
+1. PyCon Taiwan 事件通報應變委員會 ([email protected])
+2. Winnie (PyCon TW 2023 大會主席, [email protected])
+3. Pochun (PyCon TW 2023 大會主席, [email protected])
+
+How to Report
+In the event where there is conflict of interest, you may directly contact any of the lead incident responders:
+
+1. Committee of Incident Response, PyCon Taiwan ([email protected])
+2. Winnie (Chairperson of PyCon TW 2023, [email protected])
+3. Pochun (Chairperson PyCon TW 2023, [email protected])
+
+### 通報內容 Report Data
+
+如果您透過電子郵件進行通報，請盡量包含以下內容：
+
+1. 您的聯繫方式（以便與您取得聯繫）。
+2. 事件發生的日期和時間。
+3. 事件發生地點。
+4. 事件是否正在發生。
+5. 事件描述。
+6. 被舉報人的識別資訊：姓名、外貌、身高、服裝、口音、識別徽章資訊，如公司名稱、名牌或識別證。
+7. 圍繞事件的其他情況。
+8. 其他參與及其聯繫方式或描述。
+
+If you make a report via email or phone, please include:
+
+1. Your contact information (so we can get in touch with you if we need to follow up).
+2. Date and time of the incident.
+3. Location of the incident.
+4. Whether the incident is ongoing.
+5. Description of the incident.
+6. Identifying information of the reported person: name, physical appearance, height, clothing, voice accent, identifying badge information such as company name, ribbons, or badge number.
+7. Additional circumstances surrounding the incident.
+8. Other people involved in, or witnesses to the incident, and their contact information or description.
+
+### 處理流程 Procedure
+
+當您向通報應變者通報時，他們將蒐集相關的事件資訊。通報應變者收到通報後，他們將立即與大會工作人員協商討論如何處理，除非存在利益衝突（直接與大會工作人員有關），他們將聯繫任何非利益相關方協商討論。
+
+如果事件正在發生且需要立即處理，任何通報應變者都可以採取適當的行動，以確保所有相關人員的安全。如果事件不具急迫性，大會工作人員將開會討論通報之事件以確定應變方式。
+
+When you make a report to an incident responder, they will gather information about the incident according to the Procedure For Incident Response. After an incident responder takes the report, they will immediately consult with the PyCon Taiwan staff, unless there is a conflict of interest (involved directly with one of the PyCon Taiwan staff), in which case any non-interested parties will be contacted.
+
+If the incident is ongoing and needs to be immediately addressed, any lead incident responder may take appropriate action to ensure the safety of everyone involved. If the situation requires it, this may take the form of a referral to an appropriate non-PyCon agency, including the law enforcement in Taiwan.
+
+If the incident is less urgent, the report will be discussed by the event staff, who will meet to determine an appropriate response.
+
+### 保密原則 Confidentiality
+
+所有通報內容都將保密。 當我們與被舉報人討論通報事件時，我們將盡可能匿名化通報之事件細節以保護舉報者之隱私。
+
+然而，有些事件是發生在一對一的互動中，即便我們匿名化通報之事件細節，被檢舉者仍可能猜到是誰舉報他們。如果您擔心遭遇報復或人身安全，請在通報內容中註明。在某些情況下，我們會將多個匿名通報轉譯成一種行為模式，並針對該行為採取行動。
+
+在某些情況下，我們可能會需要發表公開聲明。
+
+All reports are confidential. When we discuss incidents with people who are reported, we will anonymize details as much as we can to protect the reporter’s privacy. However, the reported person may be able to guess who made the report in certain situations, even with details anonymized. If you have concerns about retaliation or your personal safety, please note those in your report. We still encourage you to report, so that we can support you while keeping our conference attendees safe. In some cases, we can compile several anonymized reports into a pattern of behavior, and take action based on these reports.
+
+In certain cases, we may determine that a public statement needs to be made. In such cases, the identities of all victims and reporters will remain confidential unless the individuals involved instruct us otherwise.
+
+### 備註 Notes
+
+以上通報流程改寫自 [PyCon 通報行為準則事件處理流程](https://github.com/python/pycon-code-of-conduct/blob/master/Attendee%20Procedure%20for%20incident%20handling.md)。
+
+This procedure has been adapted from the [PyCon Procedure for Incident Handling](https://github.com/python/pycon-code-of-conduct/blob/master/Attendee%20Procedure%20for%20incident%20handling.md).
+
+---
+
+此文件採用[姓名標示-相同方式分享 3.0 台灣](https://creativecommons.org/licenses/by-sa/3.0/tw/deed.zh_TW)授權條款。
+
+This document is licensed under an Attribution-ShareAlike 3.0 Taiwan license.
+
+![](https://i.imgur.com/cVjN760.jpg =200x)

mkdocs.yml

@@ -0,0 +1,3 @@
+site_name: PyCon TW Documentation
+repo_name: pycontw-documentation
+repo_url: https://github.com/pycontw/pycontw-documentation