From 39e797c549e8bab8f6d1033e0b7080ced3fe5011 Mon Sep 17 00:00:00 2001 From: carlotacb Date: Wed, 17 Apr 2024 16:09:54 +0200 Subject: [PATCH 1/8] change link text --- src/components/Notification.vue | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/components/Notification.vue b/src/components/Notification.vue index 9ab19124..3b715b44 100644 --- a/src/components/Notification.vue +++ b/src/components/Notification.vue @@ -132,7 +132,7 @@ const getEvent = function (id: string): ScheduleEvent | undefined { margin-left: 16px; background-color: $primary-color; border-radius: 5px; - color: $contrast-color; + color: #fff; cursor: url('../assets/img/rocket-fire.png'), auto; font-weight: bold; letter-spacing: 1px; From 52bb0c20cc35cc9537be1f27949e5623c0d5ab8d Mon Sep 17 00:00:00 2001 From: carlotacb Date: Wed, 17 Apr 2024 16:11:33 +0200 Subject: [PATCH 2/8] typo a la schedule --- src/views/Schedule.vue | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/views/Schedule.vue b/src/views/Schedule.vue index a3e8654e..e46c8bf6 100644 --- a/src/views/Schedule.vue +++ b/src/views/Schedule.vue @@ -43,8 +43,8 @@ const currentSchedule = computed<'live' | 'detailed'>(() => { >

- ** The schedule is in construction times can change and also activities - will appear as they are confirmed. + ** The schedule is under construction. Times can change and also + activities will appear as soon as they are confirmed.

From a34ce6876e0c82cee08c865e322b57e904a0ec1e Mon Sep 17 00:00:00 2001 From: carlotacb Date: Wed, 17 Apr 2024 16:13:16 +0200 Subject: [PATCH 3/8] mentors order --- src/views/Mentors.vue | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/views/Mentors.vue b/src/views/Mentors.vue index a8d2da37..3f10a808 100644 --- a/src/views/Mentors.vue +++ b/src/views/Mentors.vue @@ -13,9 +13,9 @@ import PanelContainer from '@/components/PanelContainer.vue' Mentors are experts in various technologies and programming languages who can help you with:
    -
  • 💣 Issues with your code
    • -
  • 🚀 Boosting up your project
  • 💻 Getting started with your project
    • +
  • 🚀 Boosting up your project
    • +
  • 💣 Issues with your code
  • 🏆 Submitting it to Devpost
From bf41ce61898f63e75172d659124d005064bd6555 Mon Sep 17 00:00:00 2001 From: carlotacb Date: Wed, 17 Apr 2024 16:37:32 +0200 Subject: [PATCH 4/8] rules and judging with new text --- src/data/judging.ts | 14 ++++++++------ src/data/rules.ts | 32 +++++++++++++++++--------------- 2 files changed, 25 insertions(+), 21 deletions(-) diff --git a/src/data/judging.ts b/src/data/judging.ts index 0f59c6a0..7bd5c95c 100644 --- a/src/data/judging.ts +++ b/src/data/judging.ts @@ -16,13 +16,15 @@ We will have a judging expo on **${formatIntervalInTimezone( '5/5/2024 10:15:00', '5/5/2024 13:15:00' )}**. -We will assign you a time slot to present your project (one for HackUPC + as many challenges as you participate), you need to go to in front of A3 building and an organizer will assign you to a queue and may give you an estimated time when you will present. +We will have a judging expo on Sunday ☀️ **from 10:15 to 13:15**, divided in three timeslots of 1h. To present your project, you should follow these steps:\n\n -The presentation can only be **3 minutes** long and with **no slides**, Prezi's or any visual support except your hack. You can check out other projects at any judging room. - -The top teams will move on to an additional round of panel judging in the Closing Ceremony. - -If you participate in a challenge, you'll have to present at the specific sponsor room, which is independent of the HackUPC judging.`, +1. Make sure you submitted your project to Devpost before the deadline ⏳! +2. Watch out for the message on Slack from the organizers, with the timeslot that corresponds to you 📱 +3. When your turn is up, present yourself to the front of the A3 building, where an organizer will add you to the queue 🏢 +4. Wait for the organizer to call up your project and give you your judging room 🙋 +5. Go to the room the organizer told you 🚶🏻‍♀️ +6. Present your amazing project to the judges 🏆 +`, size: 'big', }, { diff --git a/src/data/rules.ts b/src/data/rules.ts index c37c7c70..ed246f3c 100644 --- a/src/data/rules.ts +++ b/src/data/rules.ts @@ -24,21 +24,23 @@ These are some highlights of the HackUPC competition rules ⚖️ **Please read { title: 'The rules of the competition', description: ` -1. There is no minimum team size, however, the maximum size is 4 people. There will be 1 prize for each member of the team, independently of the team size. -2. Teams should be made up exclusively of students (or recent graduates within one year of having graduated) who are not organizers, judges, sponsors, or in any other privileged position at the event. Volunteers are allowed to participate in their free time, accepting the extra difficulty of hacking and volunteering at the same time, but their role won't give them any judging advantage in front of the rest of participants. -3. All team members should be present at the event. Leaving the venue for some time to hack elsewhere or sleep is fine. -4. Teams can of course gain advice and support from organizers, volunteers, sponsors, and others. -5. All work on a project should be done at the hackathon. -6. Teams can use an idea they had before the event. -7. Teams can work on ideas that have already been done. Hacks do not have to be “innovative”. If somebody wants to work on a common idea they should be allowed to do so and should be judged on the quality of their hack. These days it’s hard to find something that’s fully original and teams might not know an idea has been done before anyway. -8. Teams can work on an idea that they have worked on before (as long as they do not re-use code). -9. Teams can use libraries, frameworks, or open-source code in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed. -10. Adding new features to existing projects is allowed. Judges will only consider new functionality introduced or new features added during the hackathon in determining the winners. -11. Teams must stop hacking once the time is up. However, teams are allowed to debug and make small fixes to their programs after time is up. e.g. If during demoing your hack you find a bug that breaks your application and the fix is only a few lines of code, it's okay to fix that. Making large changes or adding new features is not allowed. -12. Participants who asked for a travel reimbursement need to post a project before the deadline in order to get the reimbursement. -13. Projects that violate the [Code of Conduct](https://legal.hackersatupc.org/hackupc/code_of_conduct) are not allowed. -14. Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the Competition Rules, breaking the [Code of Conduct](https://legal.hackersatupc.org/hackupc/code_of_conduct), or other unsporting behaviour. - `, +1. There is no minimum team size, however, the maximum size is 4 people. There will be **1 prize for each member of the team**, independently of the team size. +2. Every team can only submit up to **one project**, although they can apply to multiple sponsor challenges and win multiple prizes with said project. +3. Teams should be made up **exclusively of students** (or recent graduates within one year of having graduated) who are not organizers, judges, sponsors, or in any other privileged position at the event. Volunteers are allowed to participate in their free time, accepting the extra difficulty of hacking and volunteering at the same time, but their role won't give them any judging advantage in front of the rest of participants. +4. All team members should be **present at the event**. Leaving the venue for some time to hack elsewhere or sleep is fine. +5. All team members should be **accepted** into the hackathon by the organization and registered into the online platforms used before and during the event. +6. All team members should be **reachable** by any member of the organization team during the event. +7. Teams can of course gain **advice and support** from organizers, volunteers, sponsors, and others. +8. All work on a project should be **done at the hackathon**. +9. Teams can use an **idea they had before the event**. +10. Teams can work on **ideas that have already been done**. Hacks do not have to be “innovative”. If somebody wants to work on a common idea they should be allowed to do so and should be judged on the quality of their hack. These days it’s hard to find something that’s fully original and teams might not know an idea has been done before anyway. +11. Teams can work on an **idea that they have worked on before** (as long as they do not re-use code). +12. Teams can **use libraries, frameworks, or open-source code** in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed. +13. Adding **new features to existing projects is allowed**. Judges will only consider new functionality introduced or new features added during the hackathon in determining the winners. +14. Teams must **stop hacking once the time is up**. However, teams are allowed to debug and make small fixes to their programs after time is up. e.g. If during demoing your hack you find a bug that breaks your application and the fix is only a few lines of code, it's okay to fix that. Making large changes or adding new features is not allowed. +15. Participants who asked for a travel reimbursement need to **post a project before the deadline** in order to get the reimbursement, check all the information in the [travel reimbursement section](/travel). +16. Projects that violate the [Code of Conduct](https://legal.hackersatupc.org/hackupc/code_of_conduct) are not allowed. +17. Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the Competition Rules, breaking the [Code of Conduct](https://legal.hackersatupc.org/hackupc/code_of_conduct), or other unsporting behaviour.`, size: 'big', }, ] From ce68f2ce488e00e7490edd416ae425176bc182c9 Mon Sep 17 00:00:00 2001 From: carlotacb Date: Wed, 17 Apr 2024 16:44:09 +0200 Subject: [PATCH 5/8] add google maps button in maps --- src/views/Map.vue | 72 +++++++++++++++++++++++++++++------------------ 1 file changed, 44 insertions(+), 28 deletions(-) diff --git a/src/views/Map.vue b/src/views/Map.vue index d39e5d42..6f240118 100644 --- a/src/views/Map.vue +++ b/src/views/Map.vue @@ -1,6 +1,7 @@