From a8b5508a61e49a9676e3f441c9d8b627fc862c05 Mon Sep 17 00:00:00 2001 From: Kenan Wright Date: Tue, 8 Oct 2024 13:19:05 +0000 Subject: [PATCH 1/2] Updated to the new code of conduct --- docker-compose.yml | 2 - scripts/docker_seed.sh | 18 ++++---- templates/code-of-conduct.html | 75 ++++++++++++++++++++-------------- 3 files changed, 54 insertions(+), 41 deletions(-) diff --git a/docker-compose.yml b/docker-compose.yml index e8b5d687..1f83bf32 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -1,5 +1,3 @@ -version: "3.4" - services: hackathon-app: image: hackathon-app diff --git a/scripts/docker_seed.sh b/scripts/docker_seed.sh index ed5a96f1..0eff5ea1 100755 --- a/scripts/docker_seed.sh +++ b/scripts/docker_seed.sh @@ -1,12 +1,12 @@ echo "============================" echo "Seeding fixtures" echo "============================" -docker-compose exec hackathon-app python3 manage.py loaddata organisation -docker-compose exec hackathon-app python3 manage.py loaddata accounts -docker-compose exec hackathon-app python3 manage.py loaddata resources -docker-compose exec hackathon-app python3 manage.py loaddata profiles -docker-compose exec hackathon-app python3 manage.py loaddata emailaddresses -docker-compose exec hackathon-app python3 manage.py loaddata hackathons -docker-compose exec hackathon-app python3 manage.py loaddata showcase -docker-compose exec hackathon-app python3 manage.py loaddata showcase_site_settings -docker-compose exec hackathon-app python3 manage.py loaddata reviews +docker compose exec hackathon-app python3 manage.py loaddata organisation +docker compose exec hackathon-app python3 manage.py loaddata accounts +docker compose exec hackathon-app python3 manage.py loaddata resources +docker compose exec hackathon-app python3 manage.py loaddata profiles +docker compose exec hackathon-app python3 manage.py loaddata emailaddresses +docker compose exec hackathon-app python3 manage.py loaddata hackathons +docker compose exec hackathon-app python3 manage.py loaddata showcase +docker compose exec hackathon-app python3 manage.py loaddata showcase_site_settings +docker compose exec hackathon-app python3 manage.py loaddata reviews diff --git a/templates/code-of-conduct.html b/templates/code-of-conduct.html index bbb24e9d..df02076c 100644 --- a/templates/code-of-conduct.html +++ b/templates/code-of-conduct.html @@ -5,39 +5,54 @@
-

CODE OF CONDUCT

-

Here at Code Institute we want to create a safe and welcoming environment for all hackathon - participants. - It's important to keep open communication with your team throughout the hackathon, as suddenly dropping off - without letting them know can impact their progress and motivation, and may lead to incomplete tasks and - disorganization. By participating in this event, you agree to follow this code of conduct:

+

Hackathon Code of Conduct

+

At Code Institute, our hackathons are fast-moving, collaborative events that thrive on active + participation and teamwork. They provide exciting opportunities to learn and innovate, but the pace can be + intense. We encourage participants to consider whether this environment aligns with their personal + preferences and availability. Ensuring you're comfortable with the demands of the event will help you and + your team make the most of the experience, while maintaining a mindful approach to your well-being and that + of others.

    -
  1. Be respectful and inclusive towards all other participants, facilitators, Hackteam, Staff or anyone else - involved in the hackathon. Discriminatory language or behavior of any kind is not allowed. -
    2. -
  2. Only register if you can commit a minimum of 3 hours a day.
    3. -
  3. Keep in contact with your team. All project discussions should take place within the dedicated team - Slack Channel. This way, our Hackathon Facilitators and Staff can stay up to date on your progress and - offer support when needed. We want to make sure that everyone on the team is aware of all goings-on. -
    4. -
  4. We want to ensure that everyone on the team has a chance to participate and add their unique skills and - perspectives. Let's work together to make sure everyone is included and valued. More experienced team - members should keep in mind that some members may be less experienced, and may need extra support and - guidance. By offering more time and assistance to those who may need it, we can ensure that everyone has - an opportunity to grow their skills and contribute to the project. Remember, this is a team effort and - we want to work together to achieve our goals rather than rushing ahead. -
    5. -
  5. If you need to drop off from the event before it ends, you must inform your team and the team - facilitator. If you drop off without informing your team, you will be ineligible to participate in the - next hackathon. -
    6. -
  6. If you witness or experience any behavior that violates this code of conduct, please report it - immediately to your facilitator, the HackTeam or the Code Institute Community Team.
    7. - +
  7. Adherence to Code Institute Policies and Procedures: By participating, you agree to + follow this Code of Conduct and accept all decisions made by Code Institute regarding violations. All + decisions are final. All participants must, in addition to this Code of Conduct, abide by and respect + all additional relevant policies and procedures of Code Institute and the Code Institute Community, + including the Community Guidelines and Code of Conduct and the Safeguarding Policy. Please be sure to + familiarise yourself with these documents.
    8. +
  8. Safeguarding: If you have any safeguarding concerns, report them to a Designated + Safeguarding Lead (DSL) or via the Safeguarding Referral Form. All concerns will be handled in line with + our Safeguarding Policy.
    9. +
  9. PREVENT Duty: Any behaviour promoting extremism or radicalisation is prohibited. If you witness or suspect any attempts to draw + participants into extremist views, please report this immediately to our Designated Safeguarding Leads + (DSLs) or via the Safeguarding Referral Form.
    10. +
  10. Appropriate Behaviour: Participants must respect all participants, facilitators, + HackTeam, and staff. Discrimination, harassment, or abusive language based on any protected + characteristic is strictly prohibited.
    11. +
  11. Participation and Communication: Only register if you can commit to a minimum of 3 + hours per day. Team communication must take place within the team Slack channel to ensure visibility and + support from facilitators.
    12. +
  12. Withdrawal: If you need to leave the event, inform your team or the Community Team. + Failure to notify may result in disqualification from future hackathons.
    13. +
  13. Teamwork and Well-being: Teams must ensure that all members can contribute and feel + valued. Experienced members should offer guidance to less experienced teammates. Your well-being is + important to us. Take regular breaks and take a step back as needed. Please reach out to the Community + Team if you feel overwhelmed.
    14. +
  14. Reporting Violations: Report violations of this Code of Conduct, the Community + Guidelines, or Safeguarding Policy to the Community Team. For safeguarding issues, contact a DSL or + complete the referral form.
    15. +
  15. Judging and Feedback: Judges’ decisions are final. Due to time constraints, we are + unable to provide detailed feedback on individual projects or scores.
    16. +
  16. Project Ownership and Data Protection: Participants retain ownership and legal + responsibility of their projects. By submitting, participants grant Code Institute a non-exclusive, + royalty-free, perpetual licence to use, display, and showcase the project for educational, marketing, + and community purposes. Participants must ensure compliance with data protection laws (including GDPR) + in their submissions. Code Institute will manage all submitted data in accordance with its privacy + policy.
    17. +
  17. Content Standards: Projects must be free of harmful, graphic, or inappropriate material + and must adhere to relevant laws. Violating projects will be removed, and teams may be disqualified. + This is at the complete discretion of Code Institute.
-

By participating in a Code Institute Hackathon, you agree to abide by this code of conduct and any decisions - made by Code Institute regarding violations of it.

From c824d35a5f152105779b025f1637a1dc7b5a52b6 Mon Sep 17 00:00:00 2001 From: Kenan Wright Date: Tue, 8 Oct 2024 13:24:06 +0000 Subject: [PATCH 2/2] Fixed link to safeguarding form --- templates/code-of-conduct.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/code-of-conduct.html b/templates/code-of-conduct.html index df02076c..9bb66b5d 100644 --- a/templates/code-of-conduct.html +++ b/templates/code-of-conduct.html @@ -18,7 +18,7 @@

Hackathon Code of Conduct

follow this Code of Conduct and accept all decisions made by Code Institute regarding violations. All decisions are final. All participants must, in addition to this Code of Conduct, abide by and respect all additional relevant policies and procedures of Code Institute and the Code Institute Community, - including the Community Guidelines and Code of Conduct and the Safeguarding Policy. Please be sure to + including the Community Guidelines and Code of Conduct and the Safeguarding Policy. Please be sure to familiarise yourself with these documents.
  • Safeguarding: If you have any safeguarding concerns, report them to a Designated Safeguarding Lead (DSL) or via the Safeguarding Referral Form. All concerns will be handled in line with