|
| 1 | +{% extends "base.html" %} |
| 2 | +{% load static %} |
| 3 | + |
| 4 | +{% block content %} |
| 5 | + |
| 6 | +<div class="row my-4"> |
| 7 | + <div class="col-12 text-center mb-3"> |
| 8 | + <h1>CODE OF CONDUCT</h1> |
| 9 | + <p class="mt-2">Here at Code Institute we want to create a safe and welcoming environment for all hackathon |
| 10 | + participants. |
| 11 | + It's important to keep open communication with your team throughout the hackathon, as suddenly dropping off |
| 12 | + without letting them know can impact their progress and motivation, and may lead to incomplete tasks and |
| 13 | + disorganization. By participating in this event, you agree to follow this code of conduct:</p> |
| 14 | + |
| 15 | + <ol class="text-left"> |
| 16 | + <li>Be respectful and inclusive towards all other participants, facilitators, Hackteam, Staff or anyone else |
| 17 | + involved in the hackathon. Discriminatory language or behavior of any kind is not allowed. |
| 18 | + </li> |
| 19 | + <li>Only register if you can commit a minimum of 3 hours a day.</li> |
| 20 | + <li>Keep in contact with your team. All project discussions should take place within the dedicated team |
| 21 | + Slack Channel. This way, our Hackathon Facilitators and Staff can stay up to date on your progress and |
| 22 | + offer support when needed. We want to make sure that everyone on the team is aware of all goings-on. |
| 23 | + </li> |
| 24 | + <li>We want to ensure that everyone on the team has a chance to participate and add their unique skills and |
| 25 | + perspectives. Let's work together to make sure everyone is included and valued. More experienced team |
| 26 | + members should keep in mind that some members may be less experienced, and may need extra support and |
| 27 | + guidance. By offering more time and assistance to those who may need it, we can ensure that everyone has |
| 28 | + an opportunity to grow their skills and contribute to the project. Remember, this is a team effort and |
| 29 | + we want to work together to achieve our goals rather than rushing ahead. |
| 30 | + </li> |
| 31 | + <li>If you need to drop off from the event before it ends, you must inform your team and the team |
| 32 | + facilitator. If you drop off without informing your team, you will be ineligible to participate in the |
| 33 | + next hackathon. |
| 34 | + </li> |
| 35 | + <li>If you witness or experience any behavior that violates this code of conduct, please report it |
| 36 | + immediately to your facilitator, the HackTeam or the Code Institute Community Team.</li> |
| 37 | + |
| 38 | + </ol> |
| 39 | + <p>By participating in a Code Institute Hackathon, you agree to abide by this code of conduct and any decisions |
| 40 | + made by Code Institute regarding violations of it.</p> |
| 41 | + </div> |
| 42 | +</div> |
| 43 | + |
| 44 | +{% endblock %} |
0 commit comments