> 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/organizing-team-and-contributors.md).

# Organizing Team and Contributors

<figure><img src="/files/pd8PUC38K82ojnRFOumA" alt=""><figcaption></figcaption></figure>

PyCon Togo 2025 was made possible by a dedicated team of volunteers, who managed every aspect of the conference to ensure a smooth experience for all participants. Roles were clearly defined to cover all operational, technical, and logistical needs.

#### **Roles and Responsibilities**

* **Conference Chair / Lead Organizer**\
  Oversaw the entire event, coordinated all teams, ensured smooth collaboration among volunteers, and managed strategic decisions.
* **Conference Co-Chair**\
  Supported the Chair in planning and executing the conference, facilitated team coordination, and ensured tasks were completed efficiently.
* **Program Coordinators**\
  Managed the scheduling of talks, workshops, panels, and lightning talks. Coordinated with speakers and ensured sessions ran on time.
* **Volunteer Managers**\
  Supervised the volunteers, assigned tasks, coordinated shifts, and ensured that all areas were adequately staffed during the event.
* **Media Team**\
  Handled video recording, livestreaming, photography, and social media updates. Ensured all media was captured, uploaded, and shared publicly.
* **Technical / IT Team**\
  Ensured stable internet connectivity, set up livestreaming infrastructure, handled any technical issues, and coordinated audiovisual equipment.
* **Logistics & Accommodation Coordinators**\
  Organized local transportation, lodging, and meals for speakers, volunteers, and guests. Managed dietary restrictions and ensured participants’ comfort.
* **Registration & Check-in Team**\
  Managed attendee registration, check-in via the application, and on-site registration for late arrivals. Verified tickets and facilitated smooth entry for all participants.
* **Health & Safety / Medical Support**\
  Provided occupational health support, first aid, and managed any medical emergencies during the event.
* **Catering & Food Team**\
  Managed all meals and beverages, taking into account dietary restrictions and preferences for breakfast, lunch, and other breaks.

#### **Contributors (Volunteers)**

PyCon Togo 2025 benefited from the dedication of numerous volunteers who contributed to various aspects of the event. These volunteers came from **Togo, Nigeria, Ghana, Mozambique, and the United Kingdom**, highlighting the diversity and international collaboration within the Python community. They assisted in areas such as registration, media coverage, logistics, technical support, and attendee services, playing a crucial role in the success of the conference.

#### **Contributor (Volunteer) Engagement**

The volunteers demonstrated exceptional commitment and enthusiasm, dedicating their time and skills to ensure every aspect of the event ran smoothly. Their active engagement included early preparation, real-time problem solving, supporting attendees, and ensuring that speakers and participants had a seamless experience. This level of dedication was vital to creating a welcoming, organized, and professional conference environment.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://report.pytogo.org/organizing-team-and-contributors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.