|
5 | 5 |
|
6 | 6 | <div class="row my-4"> |
7 | 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> |
| 8 | + <h1>Hackathon Code of Conduct</h1> |
| 9 | + <p class="mt-2">At Code Institute, our hackathons are fast-moving, collaborative events that thrive on active |
| 10 | + participation and teamwork. They provide exciting opportunities to learn and innovate, but the pace can be |
| 11 | + intense. We encourage participants to consider whether this environment aligns with their personal |
| 12 | + preferences and availability. Ensuring you're comfortable with the demands of the event will help you and |
| 13 | + your team make the most of the experience, while maintaining a mindful approach to your well-being and that |
| 14 | + of others.</p> |
14 | 15 |
|
15 | 16 | <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 | | - |
| 17 | + <li><strong>Adherence to Code Institute Policies and Procedures:</strong> By participating, you agree to |
| 18 | + follow this Code of Conduct and accept all decisions made by Code Institute regarding violations. All |
| 19 | + decisions are final. All participants must, in addition to this Code of Conduct, abide by and respect |
| 20 | + all additional relevant policies and procedures of Code Institute and the Code Institute Community, |
| 21 | + including the <a href="https://codeinstitute.net/se/code-conduct-slack-community/" target="_blank">Community Guidelines and Code of Conduct</a> and the <a href="https://learn.codeinstitute.net/ci_support/diplomainsoftwaredevelopmentecomm/support" target="_blank">Safeguarding Policy</a>. Please be sure to |
| 22 | + familiarise yourself with these documents.</li> |
| 23 | + <li><strong>Safeguarding:</strong> If you have any safeguarding concerns, report them to a Designated |
| 24 | + Safeguarding Lead (DSL) or via the <a href="https://docs.google.com/forms/d/e/1FAIpQLSf1pM-9tXi1A-jE17LmFbFSEKVtWWjsCuzyr_gt5Ao3Z_ceBw/viewform" target="_blank">Safeguarding Referral Form</a>. All concerns will be handled in line with |
| 25 | + our Safeguarding Policy.</li> |
| 26 | + <li><strong>PREVENT Duty:</strong> Any behaviour promoting extremism or radicalisation is prohibited. If you witness or suspect any attempts to draw |
| 27 | + participants into extremist views, please report this immediately to our Designated Safeguarding Leads |
| 28 | + (DSLs) or via the <a href="https://docs.google.com/forms/d/e/1FAIpQLSf1pM-9tXi1A-jE17LmFbFSEKVtWWjsCuzyr_gt5Ao3Z_ceBw/viewform" target="_blank">Safeguarding Referral Form</a>.</li> |
| 29 | + <li><strong>Appropriate Behaviour:</strong> Participants must respect all participants, facilitators, |
| 30 | + HackTeam, and staff. Discrimination, harassment, or abusive language based on any protected |
| 31 | + characteristic is strictly prohibited.</li> |
| 32 | + <li><strong>Participation and Communication:</strong> Only register if you can commit to a minimum of 3 |
| 33 | + hours per day. Team communication must take place within the team Slack channel to ensure visibility and |
| 34 | + support from facilitators.</li> |
| 35 | + <li><strong>Withdrawal:</strong> If you need to leave the event, inform your team or the Community Team. |
| 36 | + Failure to notify may result in disqualification from future hackathons.</li> |
| 37 | + <li><strong>Teamwork and Well-being:</strong> Teams must ensure that all members can contribute and feel |
| 38 | + valued. Experienced members should offer guidance to less experienced teammates. Your well-being is |
| 39 | + important to us. Take regular breaks and take a step back as needed. Please reach out to the Community |
| 40 | + Team if you feel overwhelmed.</li> |
| 41 | + <li><strong>Reporting Violations:</strong> Report violations of this Code of Conduct, the Community |
| 42 | + Guidelines, or Safeguarding Policy to the Community Team. For safeguarding issues, contact a DSL or |
| 43 | + complete the referral form.</li> |
| 44 | + <li><strong>Judging and Feedback:</strong> Judges’ decisions are final. Due to time constraints, we are |
| 45 | + unable to provide detailed feedback on individual projects or scores.</li> |
| 46 | + <li><strong>Project Ownership and Data Protection:</strong> Participants retain ownership and legal |
| 47 | + responsibility of their projects. By submitting, participants grant Code Institute a non-exclusive, |
| 48 | + royalty-free, perpetual licence to use, display, and showcase the project for educational, marketing, |
| 49 | + and community purposes. Participants must ensure compliance with data protection laws (including GDPR) |
| 50 | + in their submissions. Code Institute will manage all submitted data in accordance with its privacy |
| 51 | + policy.</li> |
| 52 | + <li><strong>Content Standards:</strong> Projects must be free of harmful, graphic, or inappropriate material |
| 53 | + and must adhere to relevant laws. Violating projects will be removed, and teams may be disqualified. |
| 54 | + This is at the complete discretion of Code Institute.</li> |
38 | 55 | </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 | 56 | </div> |
42 | 57 | </div> |
43 | 58 |
|
|
0 commit comments