> For the complete documentation index, see [llms.txt](https://report.pytogo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://report.pytogo.org/pycon-togo-2025-post-conference-report/code-of-conduct-report.md).

# Code of Conduct Report

PyCon Togo 2025 was committed to providing a welcoming and inclusive environment for all participants. The conference adhered to a formal Code of Conduct, which outlined expected behaviors and procedures for addressing any incidents.

**Implementation and Awareness**

• **Pre-Event Communication:** All speakers and attendees were informed about the Code of Conduct during the registration process and through pre-conference communications. Speakers were specifically reminded to ensure that their slide contents and spoken material were appropriate for a professional audience, avoiding any language or imagery that could be considered offensive or inappropriate.

• **On-Site Visibility**: The Code of Conduct was prominently displayed on the conference website and referenced in official materials, ensuring that all participants were aware of the expected standards of behavior.

**Incident Reporting and Response**

• **Reporting Mechanisms**: Attendees were provided with clear instructions on how to report any breaches of the Code of Conduct, with designated staff members available to handle such reports confidentially and promptly.

• **Incident Management**: During the event, there were no reported breaches of the Code of Conduct, indicating a respectful and professional atmosphere throughout the conference.

**Post-Event Reflection**

The organizing committee remains dedicated to upholding the principles outlined in the Code of Conduct and will continue to prioritize the safety and inclusivity of all participants in future events. Feedback from attendees regarding the Code of Conduct and its implementation is welcomed, as it helps in refining and strengthening these guidelines for subsequent conferences.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://report.pytogo.org/pycon-togo-2025-post-conference-report/code-of-conduct-report.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.