> For the complete documentation index, see [llms.txt](https://hacktoberfest-handbook.mlh.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacktoberfest-handbook.mlh.com/fest-planning-guide/safety-and-code-of-conduct.md). # Safety and Code of Conduct Every Fest must provide a safe, welcoming, and accessible environment. These requirements apply to both Hacktoberfest Hack Day and Hacktoberfest Meetup. ## MLH Code of Conduct Everyone involved in the Fest must follow the [MLH Code of Conduct](https://github.com/MLH/mlh-policies/blob/main/code-of-conduct.md). Before the event: * Link the Code of Conduct from the OrganizerHQ event page and attendee communications. * Identify the host or venue representative attendees can approach with a concern. * Make sure volunteers know how to respond to a report and how to contact venue security or emergency services. * Review the current MLH incident-reporting procedures and contact information in the Code of Conduct. At the event, explain that harassment and abuse are not tolerated and that the policy applies throughout the venue and during every Fest-related activity. Escalate possible violations promptly and protect the privacy of anyone who reports a concern. ## Emergency Plan Create a written emergency plan and make it available to hosts and volunteers. Keep a physical or offline copy at the venue in case internet access is unavailable. Plan for scenarios that are relevant to your venue, including: * Fire, evacuation, or severe weather * A medical emergency * Power or internet failure * Theft, missing equipment, or another security concern * An attendee who is lost, distressed, or needs assistance * A Code of Conduct report or other unsafe behavior The plan should include: * The venue address and evacuation routes * Local emergency and non-emergency contact numbers * Venue security and the on-site venue contact * Lead host and backup host contact information * Instructions for communicating with attendees during an incident * A plan for pausing, relocating, or ending the event if necessary At least one designated event lead must be present, reachable, and alert throughout the Fest. In an emergency, stay calm, isolate the immediate risk when it is safe to do so, and follow the directions of venue staff and emergency responders. For more detailed planning guidance, see the main MLH Organizer Guide's [Prepare Your Emergency Plan](https://guide.mlh.com/general-information/event-logistics/prepare-your-emergency-plan) and [Locking Down a Venue](https://guide.mlh.com/general-information/locking-down-a-venue) pages. ## Accessibility and Venue Safety Before attendees arrive, verify that: * Entrances, program rooms, restrooms, and emergency exits are accessible. * Walkways, power cables, equipment, and furniture do not create avoidable hazards. * The venue’s capacity, fire, food, security, insurance, and visitor rules are understood. * Attendees know how to request an accommodation or report a venue issue. * Emergency exits and evacuation instructions are visible and unobstructed. Contact if you need help applying these requirements to your approved Fest. --- # 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://hacktoberfest-handbook.mlh.com/fest-planning-guide/safety-and-code-of-conduct.md?ask=&goal= ``` `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.