From 2bf295efdad4d820fd2a1c408e5f3ae31f8b81c7 Mon Sep 17 00:00:00 2001 From: Morgan Roderick Date: Wed, 27 Aug 2025 19:57:24 +0200 Subject: [PATCH] chore: remove unused i18n feature The files were added in _ https://github.com/codebar/planner/pull/647 - https://github.com/codebar/planner/pull/813 But has not been put to use. Once we're at Rails 8, we can re-visit if we want to implement localisation. I'm sure things have moved forwards since this was introduced in 2018. --- app/controllers/application_controller.rb | 15 - config/initializers/locale.rb | 2 +- config/locales/admin.de.yml | 46 -- config/locales/admin.en_AU.yml | 46 -- config/locales/admin.en_GB.yml | 46 -- config/locales/admin.en_US.yml | 46 -- config/locales/admin.es.yml | 46 -- config/locales/admin.fi.yml | 46 -- config/locales/admin.fr.yml | 46 -- config/locales/admin.no.yml | 46 -- config/locales/de.yml | 595 ------------------- config/locales/en_AU.yml | 553 ------------------ config/locales/en_GB.yml | 553 ------------------ config/locales/en_US.yml | 551 ------------------ config/locales/es.yml | 636 --------------------- config/locales/fi.yml | 553 ------------------ config/locales/fr.yml | 552 ------------------ config/locales/no.yml | 553 ------------------ config/locales/simple_form.de.yml | 31 - config/locales/simple_form.fr.yml | 25 - crowdin.yml | 3 - spec/features/internationalization_spec.rb | 32 -- 22 files changed, 1 insertion(+), 5021 deletions(-) delete mode 100644 config/locales/admin.de.yml delete mode 100644 config/locales/admin.en_AU.yml delete mode 100644 config/locales/admin.en_GB.yml delete mode 100644 config/locales/admin.en_US.yml delete mode 100644 config/locales/admin.es.yml delete mode 100644 config/locales/admin.fi.yml delete mode 100644 config/locales/admin.fr.yml delete mode 100644 config/locales/admin.no.yml delete mode 100644 config/locales/de.yml delete mode 100644 config/locales/en_AU.yml delete mode 100644 config/locales/en_GB.yml delete mode 100644 config/locales/en_US.yml delete mode 100644 config/locales/es.yml delete mode 100644 config/locales/fi.yml delete mode 100644 config/locales/fr.yml delete mode 100644 config/locales/no.yml delete mode 100644 config/locales/simple_form.de.yml delete mode 100644 config/locales/simple_form.fr.yml delete mode 100644 crowdin.yml delete mode 100644 spec/features/internationalization_spec.rb diff --git a/app/controllers/application_controller.rb b/app/controllers/application_controller.rb index fc90f2386..4cae06cea 100644 --- a/app/controllers/application_controller.rb +++ b/app/controllers/application_controller.rb @@ -26,7 +26,6 @@ class ApplicationController < ActionController::Base helper_method :current_user helper_method :current_service - before_action :set_locale before_action :accept_terms, if: :logged_in? def render_not_found @@ -131,11 +130,6 @@ def has_access? private - def set_locale - store_locale_to_cookie(params[:locale]) if locale - I18n.locale = cookies[:locale] || I18n.default_locale - end - def user_not_authorized redirect_to(user_path, notice: 'You are not authorized to perform this action.') end @@ -155,13 +149,4 @@ def redirect_back(fallback_location:, **args) redirect_to fallback_location, **args end end - - def store_locale_to_cookie(locale) - cookies[:locale] = { value: locale, - expires: Time.zone.now + 36_000 } - end - - def locale - params[:locale] if params[:locale] && I18n.available_locales.include?(params[:locale].to_sym) - end end diff --git a/config/initializers/locale.rb b/config/initializers/locale.rb index 645e57125..39754a263 100644 --- a/config/initializers/locale.rb +++ b/config/initializers/locale.rb @@ -2,5 +2,5 @@ # config.i18n.load_path += Dir[Rails.root.join('my', 'locales', '*.{rb,yml}').to_s] Rails.application.config.i18n.default_locale = :en Rails.application.config.i18n.fallbacks = true -Rails.application.config.i18n.available_locales = [:en, :fr, :de] +Rails.application.config.i18n.available_locales = [:en] #config.i18n.enforce_available_locales = false diff --git a/config/locales/admin.de.yml b/config/locales/admin.de.yml deleted file mode 100644 index 863a3c8da..000000000 --- a/config/locales/admin.de.yml +++ /dev/null @@ -1,46 +0,0 @@ -de: - admin: - shared: - workshops: Workshops - events: Events - meetings: Meetings - sponsors: Sponsors - students: Students - coaches: Coaches - organisers: Organisers - - bans: - create: - success: 'Mitglied wurde gesperrt und per E-mail informiert.' - new: - title: 'Sperrung' - create: 'Mitglied sperren' - members: - update_subscriptions: - unsubscribe: "%{member} wurde erfolgreich aus der Liste der %{chapter}er %{group} ausgetragen." - send_attendance_email: - success: 'Anwesenheits-Warn-E-mail verschickt.' - send_eligibility_email: - success: 'Anfrage zur Teilnahmeberechtigung verschickt' - - sponsors: - show: - edit_button: Edit sponsor - website: Website - address: Address - directions: Directions - description: Description - student_spots: Student spots - coach_spots: Coach spots - level: Level - accessibility_info: Accessibility information - contacts: Contacts - map_preview: Map preview - sponsorships: Sponsorships - activities: Activities - empty_state: - directions: No directions provided. - description: No description provided. - accessibility_info: No accessibility information provided. Please reach out to the sponsor so they can provide you with this information. - map: An address must be specified for the map preview to be generated. - sponsorships: No sponsorships diff --git a/config/locales/admin.en_AU.yml b/config/locales/admin.en_AU.yml deleted file mode 100644 index 2a91b3068..000000000 --- a/config/locales/admin.en_AU.yml +++ /dev/null @@ -1,46 +0,0 @@ -en-AU: - admin: - shared: - workshops: Workshops - events: Events - meetings: Meetings - sponsors: Sponsors - students: Students - coaches: Coaches - organisers: Organisers - - bans: - create: - success: 'Member marked as supended and suspension email sent.' - new: - title: 'Suspension' - create: 'Suspend member' - members: - update_subscriptions: - unsubscribe: "Successfully unsubscribed %{member} from %{chapter}'s %{group} group" - send_attendance_email: - success: 'Attendance warning email sent.' - send_eligibility_email: - success: 'Eligibility inquiry email sent.' - - sponsors: - show: - edit_button: Edit sponsor - website: Website - address: Address - directions: Directions - description: Description - student_spots: Student spots - coach_spots: Coach spots - level: Level - accessibility_info: Accessibility information - contacts: Contacts - map_preview: Map preview - sponsorships: Sponsorships - activities: Activities - empty_state: - directions: No directions provided. - description: No description provided. - accessibility_info: No accessibility information provided. Please reach out to the sponsor so they can provide you with this information. - map: An address must be specified for the map preview to be generated. - sponsorships: No sponsorships diff --git a/config/locales/admin.en_GB.yml b/config/locales/admin.en_GB.yml deleted file mode 100644 index 63ed42b6a..000000000 --- a/config/locales/admin.en_GB.yml +++ /dev/null @@ -1,46 +0,0 @@ -en-GB: - admin: - shared: - workshops: Workshops - events: Events - meetings: Meetings - sponsors: Sponsors - students: Students - coaches: Coaches - organisers: Organisers - - bans: - create: - success: 'Member marked as supended and suspension email sent.' - new: - title: 'Suspension' - create: 'Suspend member' - members: - update_subscriptions: - unsubscribe: "Successfully unsubscribed %{member} from %{chapter}'s %{group} group" - send_attendance_email: - success: 'Attendance warning email sent.' - send_eligibility_email: - success: 'Eligibility inquiry email sent.' - - sponsors: - show: - edit_button: Edit sponsor - website: Website - address: Address - directions: Directions - description: Description - student_spots: Student spots - coach_spots: Coach spots - level: Level - accessibility_info: Accessibility information - contacts: Contacts - map_preview: Map preview - sponsorships: Sponsorships - activities: Activities - empty_state: - directions: No directions provided. - description: No description provided. - accessibility_info: No accessibility information provided. Please reach out to the sponsor so they can provide you with this information. - map: An address must be specified for the map preview to be generated. - sponsorships: No sponsorships diff --git a/config/locales/admin.en_US.yml b/config/locales/admin.en_US.yml deleted file mode 100644 index d69df560c..000000000 --- a/config/locales/admin.en_US.yml +++ /dev/null @@ -1,46 +0,0 @@ -en-US: - admin: - shared: - workshops: Workshops - events: Events - meetings: Meetings - sponsors: Sponsors - students: Students - coaches: Coaches - organisers: Organisers - - bans: - create: - success: 'Member marked as supended and suspension email sent.' - new: - title: 'Suspension' - create: 'Suspend member' - members: - update_subscriptions: - unsubscribe: "Successfully unsubscribed %{member} from %{chapter}'s %{group} group" - send_attendance_email: - success: 'Attendance warning email sent.' - send_eligibility_email: - success: 'Eligibility inquiry email sent.' - - sponsors: - show: - edit_button: Edit sponsor - website: Website - address: Address - directions: Directions - description: Description - student_spots: Student spots - coach_spots: Coach spots - level: Level - accessibility_info: Accessibility information - contacts: Contacts - map_preview: Map preview - sponsorships: Sponsorships - activities: Activities - empty_state: - directions: No directions provided. - description: No description provided. - accessibility_info: No accessibility information provided. Please reach out to the sponsor so they can provide you with this information. - map: An address must be specified for the map preview to be generated. - sponsorships: No sponsorships diff --git a/config/locales/admin.es.yml b/config/locales/admin.es.yml deleted file mode 100644 index 436ae0706..000000000 --- a/config/locales/admin.es.yml +++ /dev/null @@ -1,46 +0,0 @@ -es: - admin: - shared: - workshops: Workshops - events: Events - meetings: Meetings - sponsors: Sponsors - students: Students - coaches: Coaches - organisers: Organisers - - bans: - create: - success: 'Member marked as supended and suspension email sent.' - new: - title: 'Suspension' - create: 'Suspend member' - members: - update_subscriptions: - unsubscribe: "Successfully unsubscribed %{member} from %{chapter}'s %{group} group" - send_attendance_email: - success: 'Attendance warning email sent.' - send_eligibility_email: - success: 'Eligibility inquiry email sent.' - - sponsors: - show: - edit_button: Edit sponsor - website: Website - address: Address - directions: Directions - description: Description - student_spots: Student spots - coach_spots: Coach spots - level: Level - accessibility_info: Accessibility information - contacts: Contacts - map_preview: Map preview - sponsorships: Sponsorships - activities: Activities - empty_state: - directions: No directions provided. - description: No description provided. - accessibility_info: No accessibility information provided. Please reach out to the sponsor so they can provide you with this information. - map: An address must be specified for the map preview to be generated. - sponsorships: No sponsorships diff --git a/config/locales/admin.fi.yml b/config/locales/admin.fi.yml deleted file mode 100644 index 30d473835..000000000 --- a/config/locales/admin.fi.yml +++ /dev/null @@ -1,46 +0,0 @@ -fi: - admin: - shared: - workshops: Workshops - events: Events - meetings: Meetings - sponsors: Sponsors - students: Students - coaches: Coaches - organisers: Organisers - - bans: - create: - success: 'Member marked as supended and suspension email sent.' - new: - title: 'Suspension' - create: 'Suspend member' - members: - update_subscriptions: - unsubscribe: "Successfully unsubscribed %{member} from %{chapter}'s %{group} group" - send_attendance_email: - success: 'Attendance warning email sent.' - send_eligibility_email: - success: 'Eligibility inquiry email sent.' - - sponsors: - show: - edit_button: Edit sponsor - website: Website - address: Address - directions: Directions - description: Description - student_spots: Student spots - coach_spots: Coach spots - level: Level - accessibility_info: Accessibility information - contacts: Contacts - map_preview: Map preview - sponsorships: Sponsorships - activities: Activities - empty_state: - directions: No directions provided. - description: No description provided. - accessibility_info: No accessibility information provided. Please reach out to the sponsor so they can provide you with this information. - map: An address must be specified for the map preview to be generated. - sponsorships: No sponsorships diff --git a/config/locales/admin.fr.yml b/config/locales/admin.fr.yml deleted file mode 100644 index 9ce6eb57f..000000000 --- a/config/locales/admin.fr.yml +++ /dev/null @@ -1,46 +0,0 @@ -fr: - admin: - shared: - workshops: Workshops - events: Events - meetings: Meetings - sponsors: Sponsors - students: Students - coaches: Coaches - organisers: Organisers - - bans: - create: - success: 'Member marked as supended and suspension email sent.' - new: - title: 'Suspension' - create: 'Suspend member' - members: - update_subscriptions: - unsubscribe: "Successfully unsubscribed %{member} from %{chapter}'s %{group} group" - send_attendance_email: - success: 'Attendance warning email sent.' - send_eligibility_email: - success: 'Eligibility inquiry email sent.' - - sponsors: - show: - edit_button: Edit sponsor - website: Website - address: Address - directions: Directions - description: Description - student_spots: Student spots - coach_spots: Coach spots - level: Level - accessibility_info: Accessibility information - contacts: Contacts - map_preview: Map preview - sponsorships: Sponsorships - activities: Activities - empty_state: - directions: No directions provided. - description: No description provided. - accessibility_info: No accessibility information provided. Please reach out to the sponsor so they can provide you with this information. - map: An address must be specified for the map preview to be generated. - sponsorships: No sponsorships diff --git a/config/locales/admin.no.yml b/config/locales/admin.no.yml deleted file mode 100644 index d25f3f19e..000000000 --- a/config/locales/admin.no.yml +++ /dev/null @@ -1,46 +0,0 @@ -"no": - admin: - shared: - workshops: Workshops - events: Events - meetings: Meetings - sponsors: Sponsors - students: Students - coaches: Coaches - organisers: Organisers - - bans: - create: - success: 'Member marked as supended and suspension email sent.' - new: - title: 'Suspension' - create: 'Suspend member' - members: - update_subscriptions: - unsubscribe: "Successfully unsubscribed %{member} from %{chapter}'s %{group} group" - send_attendance_email: - success: 'Attendance warning email sent.' - send_eligibility_email: - success: 'Eligibility inquiry email sent.' - - sponsors: - show: - edit_button: Edit sponsor - website: Website - address: Address - directions: Directions - description: Description - student_spots: Student spots - coach_spots: Coach spots - level: Level - accessibility_info: Accessibility information - contacts: Contacts - map_preview: Map preview - sponsorships: Sponsorships - activities: Activities - empty_state: - directions: No directions provided. - description: No description provided. - accessibility_info: No accessibility information provided. Please reach out to the sponsor so they can provide you with this information. - map: An address must be specified for the map preview to be generated. - sponsorships: No sponsorships diff --git a/config/locales/de.yml b/config/locales/de.yml deleted file mode 100644 index 64ebc3b6f..000000000 --- a/config/locales/de.yml +++ /dev/null @@ -1,595 +0,0 @@ -de: - brand: "codebar.io" - date: - formats: - default: "%d.%m.%Y" - email: "%a, %d %B um %H:%M" - email_title: "%A, %d %b um %H:%M %Z" - short: "%d.%m.%Y %H:%M " - date: "%d %b %Y" - website_format: "%a, %d %B %Y um %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "um %H:%M Uhr am %d.%m.%Y" - workshop: "%A, %e %B %Y um %R" - dashboard: "%a, %d %b %Y, %H:%M" - time: - formats: - default: "%a, %d %b %Y %H:%M" - email: "%a, %d %B um %H:%M" - email_title: "%A, %d %b um %H:%M %Z" - short: "%d.%m.%Y %H:%M " - date: "%d %b %Y" - full_date: "%d %B %Y" - default_date: "%d.%m.%Y" - website_format: "%a, %d %B %Y um %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "um %H:%M Uhr am %d.%m.%Y" - workshop: "%A, %e %B %Y um %R" - dashboard: "%A, %b %d" - number: - currency: - format: - unit: '£' - delimiter: ',' - separator: '.' - precision: 0 - format: '%u%n' - homepage: - intro: "codebar is a charity that facilitates the growth of a diverse tech community by running free regular programming workshops for minority groups in tech." - explanation: "Unser Ziel ist unterrepräsentierten Menschen zu programmieren in einer sicheren und kollaborative Umgebung lernen und erweitern ihre Karrierechancen zu ermöglichen. Um dies zu erreichen betreiben wir kostenlose regelmäßige Workshops, regelmäßige Einzelveranstaltungen und versuchen, die Möglichkeiten für unsere Schüler die Technologie und Programmierung zugänglicher zu schaffen." - participate: - students_title: "Students" - students_explanation_p1: "Our students come from diverse backgrounds—some aspiring to become full-time developers, while others simply want to learn the basics of coding in a supportive environment." - students_explanation_p2: "Join our vibrant community and take part in our workshops!" - students_button: "Join us as a student" - coaches_title: "Coaches" - coaches_explanation_p1: "We encourage new students to start with our tutorials on HTML/CSS, JavaScript, Ruby, Python, or Git, while also helping them grasp key programming concepts." - coaches_explanation_p2: "That’s why we’re always looking for more developers to join our community and coach at our workshops." - coaches_button: "Join us as a coach" - workshop_title: "Workshops" - workshop_explanation_p1: "We’re proud to be hosted by amazing companies that support our mission. Our typical format includes 30 minutes of socialising over food and drinks, a lightning talk, and then hands-on coding." - workshop_explanation_p2: "Help us grow and support our chapters by hosting or sponsoring our workshops, and together, we can expand opportunities for more aspiring developers." - workshop_button: "Let's work together" - workshop_email_subject: "Regarding hosting a workshop" - chapters: - title: "Chapters" - events: - upcoming: "Upcoming Events" - donation_platforms: - title: "How to support us" - mailer: - workshop_invitation: - attending: - subject: "Attendance Confirmation for %{date_time}" - attending_reminder: - subject: "Workshop Reminder %{date_time}" - invite_coach: - subject: "Workshop Coach Invitation %{date_time}" - invite_student: - subject: "Workshop Invitation %{date_time}" - notify_waiting_list: - subject: "A spot just became available" - waiting_list_reminder: - subject: "Reminder: you're on the codebar waiting list (%{date_time})" - virtual: - invite_coach: - subject: "Virtual Workshop Coach Invitation %{date_time}" - invite_student: - subject: "Virtual Workshop Invitation %{date_time}" - attending_reminder: - subject: "Virtual Workshop Reminder %{date_time}" - waiting_list_reminder: - subject: "Reminder: you're on the codebar waiting list (%{date_time})" - messages: - accepted_invitation: "Vielen Dank für die Rückmeldung, %{name}. Wir sehen uns beim Workshop!" - already_invited: 'You have already RSVPd or joined the waitlist for this workshop.' - error_blank_note: 'You must select a note' - rejected_invitation: "Wir bedauern es sehr dass du nicht teilnehmen kannst. Vielen Dank für das Bescheid geben, %{name}." - already_rsvped: "Du hast deine Teilnahme schon bestätigt!" - not_attending_already: "Du hast bereits bestätigt, dass du nicht teilnehmen kannst." - no_available_seats: "Leider sind keine weiteren Kapazitäten verfügbar :(. Falls du auf die Warteliste möchtest sende uns eine Mail an %{email}" - feedback_saved: "Vielen Dank für dein Feedback!" - feedback_not_found: "Sie haben bereits ein Feedback eingereicht." - updated_note: "Aktualisierung erfolgreich." - invalid_session: 'Your session is invalid' - invitations: - meeting: - cancel: "Thanks for letting us know you can't make it." - rsvp: "Your RSVP was successful. We look forward to seeing you at the Monthly!" - rsvped_to_other_workshop: "Du hast dich schon für einen anderen Workshop an diesem Datum angemeldet. Falls du an diesem Workshop teilnehmen möchtest, melde dich bitte zuerst von dem anderen Workshop ab." - spot_confirmed: "Deine Teilnahme an %{event} wurde bestätigt! Wir freuen uns bereits dich dort begrüßen zu dürfen." - spot_not_confirmed: 'Deine Teilnahme wurde noch nicht bestätigt. Wir werden die Teilnahme bestätigen sobald du das Formular ausgefüllt hast.' - notifications: - provider_already_connected: 'Sie sind bereits angemeldet!' - not_logged_in: "Du musst angemeldet sein, um auf diese Seite zugreifen zu können." - navigation: - dashboard: "Übersicht" - code_of_conduct: "Verhaltensregeln" - breach_code_of_conduct: "Breach Code of Conduct" - coach_guide: "Handbuch für Coaches" - student_guide: "Handbuch für Lernende" - tutorials: "Tutorials" - becoming_sponsor: "Sponsor werden" - faq: "Häufig gestellte Fragen" - blog: "Blog" - codebar_stories: "codebar Stories" - stats: "Stats" - dashboard: - join_workshops_in: "Komm zu unseren kostenlosen Workshops in" - workshops_goal: "um sich mit den Programmier- und Webentwicklungsgrundlagen vertraut zu machen." - tweets_by: "Tweets von" - latest_sponsors: "Neusten Sponsoren" - policy: - intro: "Es gibt eine hohe Nachfrage für unsere Workshops und meistens gibt es auch eine Warteliste. Um sicherzustellen, dass so viele Leute wie möglich kommen können, haben wir ein paar einfache Anwesenheitsregeln." - rule1: "Bevor du dich dafür entscheidest, an einem Event mitzumachen. Stell bitte sicher, ob du für eine Teilnahme berechtigt bist. Wenn du dir unsicher bist, melde dich einfach bei uns." - rule2: "Du musst dich anmelden und deine Teilnahme bestätigen, um an unseren Workshops teilzunehmen." - rule3: "Falls du bereits zu einem Workshop zugesagt hast, später aber feststellst, dass du nicht mehr teilnehmen kannst, melde dich bitte wieder beim Workshop ab. Du kannst einfach schnell über deine Bestätigungs-E-Mail absagen." - rule4: "Bitte sag uns mindestens 24 Stunden vorher Bescheid, wenn du nicht mehr teilnehmen kannst." - rule5: "Wir wissen natürlich, dass manchmal kurzfrisitig etwas dazwischen kommen kann, aber selbst du nur eine Stunde vor dem Workshop absagen musst, sag uns bitte Bescheid." - what_happens: "Was passiert, wenn ich die Teilnahmeregeln nicht beachte?" - strikes_system: "Wenn wir feststellen, dass du drei Mal ohne abzusagen nicht zum Workshop gekommen bist, werden wir dich für die nächsten 4 Wochen aus unserem Teilnehmer-Verteiler entfernen. Wir melden uns bei dir nach deinem ersten Fehlen, um sicherzustellen, dass du die Regeln verstehst." - removing: "Falls du noch drei Mal ohne abzusagen fehlst, werden wir dich endgültig von unserer Teilnehmer-Liste entfernen müssen." - rsvping: "Wir bestrafen regelmäßiges an- und vorzeitiges abmelden nicht, aber bitte versuche es zu vermeiden. Falls dir eine Teilnahme an einem bestimmten Tag nicht möglich ist dann melde uns das bitte, damit wir das in zukünftige Planungen einbeziehen können." - eligibility_note: "Noch ein Hinweis zur Teilnahmeberechtigung" - abuse: "Wir sind alle ziemlich entspannt und vertrauen dir, wir prüfen also nicht ob jemand teilnehmen darf. Sollte es allerdings jemals danach aussehen als würde das ausgenutzt werden müssten wir das ändern – was wir wirklich nicht machen wollen." - reminder: "Bitte behalte also im Kopf, dass die Workshops dafür da sind die Technikwelt für unterrepräsentierte Gruppen zu öffnen." - teacher_guide: - laptop: "Für unsere Workshops brauchst du keinen Laptop. Deine Aufgabe ist es, Lernende zu leiten und zu begleiten. Falls du mit dem Tutorial nicht vertraut bist, sieh es dir vorher genauer an, wenn du mithelfen möchtest." - keyboard: "Übernimm nicht die Tastatur! Das kann abschreckend und einschüchternd wirken." - typing: "Ermutige die Lernenden, selbst zu tippen, anstatt zu kopieren." - questions: "Erkläre, dass es keine dummen Fragen gibt." - mistakes: "Sag den Lernenden, dass es OK ist, Fehler zu machen." - introduction: "Stelle dich immer vor. Erzähle, was dich zum ehrenamtlichen Helfen in deiner Freizeit motiviert und warum du das Programmieren magst." - backgrounds: "Gib Deinen Lernenden die Gelegenheit, einander kennen zu lernen. Frage sie nach ihren Namen, warum sie gekommen sind, was sie beruflich machen. Rege zu Beginn eine kurze Diskussion an." - limits: "Setze bei den Lernenden kein Wissen voraus, gehe aber davon aus, dass ihre Intelligenz und Fähigkeiten unbeschränkt sind." - collaboration: "Arbeite mit den Lernenden zusammen. Wenn du zwei Leute betreust, solltest du mit beiden arbeiten. Widme nicht deine ganze Aufmerksamkeit einer Einzelperson." - discussion: "Erlaube den Lernenden zunächst, Fragen eigenständig zu beantworten. Hilf ihnen mit erkenntnisleitenden Fragen. Rege eine Diskussion an." - talk_slow: "Lass dir Zeit. Du bist der/die Lehrer/in, sie sind die Lernenden. Lege kurze Pausen zwischen Fragen ein." - mild_approach: "Sage nicht rabiat \"Nein\", wenn die Lernenden etwas unrichtig machen. Gehe sanft und behutsam an das Problem heran." - paper: "Benutze Stift und Papier oder ein Whiteboard! Viele der Lernenden haben keine Vorgeschichte mit der Informatik. Zeichnungen und visuelle Hilfen können sehr nützlich sein." - stubling: "Lasse zu, dass die Lernenden auch mal stolpern. Wir lernen aus Fehlern, indem wir unseren eigenen Weg von der Frustration zur Lösung des Problems finden. Stehe den Lernenden unterstützend zur Seite, aber lass sie selbständig erkunden." - suggestions: "Hast du noch Vorschläge? Eröffne einen pull request oder erstelle eine issue\"" - workshops: - already_wish_to_attend: 'You have already RSVPd or joined the waitlist for this workshop.' - lead: "Attend our workshops to learn programming in a safe and supportive environment at your own pace, or to share your knowledge and coach our students." - registration_not_open: 'This workshop is not open for registrations' - events: - title: "Veranstaltungen" - past: "Vergangene" - no_upcoming_events: "Es gibt keine bevorstehenden Veranstaltungen." - view_past_events: "Vergangene Veranstaltungen anzeigen" - view_all: "Alle anzeigen" - hosted_by: "Veranstaltet von" - organisers: "Organisatoren" - venue_at: "bei" - attend_as_student: "Als Student teilnehmen" - attend_as_coach: "Als Trainer teilnehmen" - location: "Ort" - sponsors: "Sponsoren" - thx_to_sponsors: "Ein großes Dankeschön an alle unsere Sponsoren, die die Veranstaltung möglich gemacht haben!" - coaches: "Trainer" - students: Students - schedule: "Zeitplan" - send_us_an_email: "Schreibe uns eine E-Mail" - not_open_for_rsvp: Die Anmeldung für diese Veranstaltung ist noch nicht geöffnet. - virtual: This is a virtual event. - faq: - experience: - q: "Wie erfahren sollte ich sein, um am Workshop teilnehmen?" - a: - contribution: - q: "Welche Beiträge kann ich leisten?" - a: "Dein Beitrag kann klein sein, zum Beispiel kannst du einen Rechtschreibfehler korrigieren, aber auch riesig. Du kannst bei der Dokumentation helfen, einen Bug den du gefunden hast beheben, mit dem Design helfen oder sogar größere Aufgaben angehen und dabei helfen neue Funktionen einzubauen. Jedes kleine bisschen hilft!" - laptop: - q: "Soll ich einen Laptop mitbringen?" - a_html: "Ja, Du solltest einen Laptop mitbringen. Wenn du keinen besitzt %{link}, da wir möglicherweise in der Lage sind zu helfen." - keyboard: - q: "Soll ich eine Tastatur mitbringen?" - a_html: "Eine Tastatur könnte nützlich sein, da Du den ganzen Tag mit jemandem zusammen an Deinem Laptop arbeitest. Wenn Du keine Tastatur besitzt, %{link} und wir versuchen, etwas zu organisieren." - travel_costs: - q: "Ich werde pendeln. Können Sie mir bei meinen Reisekosten helfen?" - a: "Wir werden einige Reisestipendien anbieten. Bitte stellen dich sicher, dass du den Fragebogen ausfüllst, nachdem du dich angemeldet hast und wir werden uns mit dir in Verbindung setzen." - coaches: - want_to_coach: "Möchtest Du in unseren Workshops coachen?" - read_before: "Wenn Du unsere Workshops noch nicht besucht hast, lies bitte unseren" - code_of_conduct: "Verhaltenskodex" - policy: "da wir eine Nulltoleranzpolitik haben und von allen ein entsprechendes Verhalten erwarten. Das solltest Du lesen: Unser" - guide: "Coaching Guide" - unable_attend: "Bitte aktualisiere deine Teilnahme auf der Webseite falls du, nachdem du dich angemeldet hast, doch nicht kommen kannst. Wir verlassen uns darauf, dass unsere Trainer kommen, dass die Workshops rundlaufen." - food: "PS: Es gibt Essen am Workshop. Wir versuchen immer vegetarisches, veganes und Gluten-freies Essen anzubieten. Solltest du andere Dieätanforderungen haben, schicke uns bitte eine E-Mail an" - code_of_conduct: - title: "Verhaltenskodex" - summary: - title: "Die kurze Version" - intro: "Wir möchten jedem eine belästigungsfreie Erfahrung bieten, unabhängig von Geschlecht, sexueller Orientierung, Behinderung, Aussehen, Körperbau, Ethnizität oder Religionszugehörigkeit. Wir tolerieren keinerlei Belästigung von Teilnehmer_innen. Sexualisierte Sprache und Darstellungen sind bei all unseren Veranstaltungen, inklusive Vorträgen, Workshops, Feiern, auf Twitter uns allen anderen Onlinemedien unerwünscht. Teilnehmer_innen, die gegen diese Regeln verstoßen, müssen mit Sanktionen durch das Veranstaltungspersonal rechnen, inklusive eines Verweises der Veranstaltung und aller zukünftiger Veranstaltungen." - content: - title: "Die lange Version" - harassment: "Belästigung umfasst unter anderem beleidigende Aussagen über Geschlecht, sexuelle Orientierung, Behinderung, körperliches Aussehen wie Körperbau, Ethnizität oder Religionszugehörigkeit (oder Nichtvorhandensein einer solchen), sexualisierende Darstellungen in öffentlichen Räumen, bewusste Einschüchterung, Stalking, Verfolgung, unerwünschtes Fotografieren oder Aufnehmen, wiederholte Störung von Vorträgen und anderen Veranstaltungen, unerwünschten körperlichen Kontakt und unerwünschte sexuelle Aufmerksamkeit." - comply: "Teilnehmer_innen, die wegen solchen Verhaltens ermahnt werden, haben dieses sofort einzustellen." - sponsors: "Diese Verhaltensregeln gelten auch für Sponsor_innen. Insbesondere sollten Sponsor_innen darauf achten, dass sie keine sexualisierenden Bilder, Aktivitäten oder andere sexualisierende Werbemittel einsetzen. Personal (auch Freiwillige) sollten darauf achten, keine sexualisierende Kleidung, Uniformen oder Kostüme zu tragen, oder sonstwie ein sexualisiertes Umfeld zu gestalten." - sanctions: "Sollten Teilnehmer_innen durch belästigendes Verhalten auffallen, steht es dem Konferenzpersonal frei, entsprechende Maßnahmen zu ergreifen, die es für angemessen hält. Dies schließt Ermahnungen bis hin zum Verweis von der Veranstaltung ein." - concerns: "Solltest du dich belästigt fühlen oder mitbekommen, dass jemand anders belästigt wird oder sonstige Probleme auftreten, wende dich bitte sofort an ein Mitglied des Veranstaltungspersonals." - applies_to: "Wir erwarten, dass Teilnehmer diese Regeln bei allen codebar Veranstaltungen einhalten." - questions: "Wenn du Fragen oder Bedenken bezüglich dieses Kodex hast bitte" - contact: "Kontaktiere uns" - email_subject: "Fragen zum Verhaltenskodex" - sponsors: - sponsoring: "Sponsoren" - members: - sign_up: "Anmelden" - sign_in_with_github: "Anmelden mit GitHub" - sign_up_as_student: "Meldet mich als Student an *" - sign_up_as_student_disclaimer: "* Ich verstehe und erfülle die Teilnahmebedingungen." - sign_up_as_coach: "Melde dich als Trainer an" - code_of_conduct: "Verhaltenskodex" - new: - intro_html: "We provide a welcoming, inclusive, and supportive learning environment, with a strict zero-tolerance policy for any form of harassment or inappropriate behavior. Please take a moment to review our code of conduct before signing up." - students: - intro_html: "Wenn du als Student teilnehmen möchtest, musst du unsere Teilnahmebedingungen erfüllen weil unsere Workshops nur für Frauen, LGBTQ und Menschen aus unterrepräsentierten Gruppen geöffnet sind." - github: "Abschließend, wenn du auf den Anmeldebutton klickst, wirst du auf eine Seite namens GitHub weitergeleitet. Nachdem du dich mit deinem GitHub Zugang angemeldet hast, wirst du wieder auf die codebar Seite zurückgeleitet. Du musst dir einen Zugang erstellen, wenn du noch keinen hast. Das dauert nicht lang und ist etwas was sich als nützlich erweisen wird wenn du anfängst zu programmieren!" - invitations: "Wir verschicken Einladungen regelmäßig, sei also bitte nicht besorgt, wenn du sie nicht direkt nach der Anmeldung erhältst." - footer: - email_us: "Schreibe uns eine E-Mail an:" - contact_info: "Kontaktinfo:" - faq: - payment: - q: "Muss ich bezahlen um an codebar teilzunehmen?" - a_p1: "Auf keinem Fall! Wir haben das Glück, dass uns einige tolle Firmen als Gastgeber und/oder mit Essen unterstützen. Und unsere" - awesome_coaches: "fantastische Trainer" - a_p2: "die uns ihre Zeit kostenlos zur Verfügung stellen um der Gemeinschaft zu helfen." - technologies: - q: "Welche Technologien lehrt ihr?" - a: "Wir haben eine Vielfalt an Tutorien zu HTML, CSS, JavaScript und Ruby. Wenn du etwas Anderes lernen möchtest zögere nicht uns eine E-Mail zu schicken, weil wir möglicherweise noch jemanden finden können der uns dabei hilft." - eligibility: - q: "Ich möchte an einem Workshop teilnehmen. Bin ich berechtigt?" - a: "Unsere Workshops sind für Frauen, LGBTQ und Menschen die in der Tech-Branche unterrepräsentiert sind geöffnet. Wenn du zu einer dieser Gruppen gehörst bist du herzlich eingeladen teilzunehmen. Wenn nicht, gibt es andere tolle Initiativen, wie Open Tech School London, bei denen man in einer kollaborativen Umgebung lernen kann. Bitte lies auch unseren Studentenratgeber für weitere Informationen." - career: - q: "Ist codebar nur für Menschen gedacht die eine Karriere als Entwickler_in anstreben?" - a: "Nein! codebar soll Menschen den Spaß am Programmieren vermitteln. Wir helfen ihnen sowohl grundlegende Programmierfähigkeiten zu lernen als auch Neues zu entdecken und bei eigenen Projekten. Allen die Entwickler_innen werden möchten bieten wir Hilfe und Anleitung ihr Ziel zu erreichen." - format: - q: "Wie ist das Workshopformat?" - a: "Wir versuchen einen Trainer pro für je zwei Teilnehmer_innen zu haben. Wir bilden aus den Studenten die das gleiche Tutorium bearbeiten wollen Zweiergruppen und weisen ihnen eine_n Trainer_in zu. Der Rest geschieht einfach." - laptop: - q: "Muss ich einen Laptop zu den Workshops mitbringen?" - a: "Ja, wir empfehlen, dass du einen Laptop mitbringst, weil es einfacher für dich sein wird nach den Workshops weiterzuarbeiten. Wenn du keinen besitzt, schick uns eine E-Mail, dann versuchen wir dir auszuhelfen." - online_resources: - q: "Es gibt so viele Tutorien online, wieso sollte ich zu codebar gehen?" - a: "Programmieren kann furchteinflößend sein und viele finden es schwer einen Einstieg zu finden. Dadurch dass wir dich in Kontakt mit Menschen bringen die dir helfen und dich anweisen können machen wir deine Erfahrung und deinen Lernprozess einfacher und angenehmer." - preperations: - q: "Ich würde gerne bei codebar coachen. Muss ich noch irgendetwas anderes tun als mich anzumelden?" - a_p1: "Ja. Lies bitte zuerst unsere" - coaching_guide_tutorials: "Coaching Tutorien" - a_p2: ". Arbeite dich anschließend bitte in unsere" - a_p3: "Tutorien ein. Die Tutorien sind Open Source, wenn du also etwas verbessern möchtest kannst du gerne ein Ticket im GitHub Repository eröffnen oder einen Pull Request schicken." - a_p4: "Wir erwarten nicht, dass die Trainer mit allen Technologien und Sprachen vertraut sind zu denen wir Materialien haben." - location: - q: "Wo finden die Workshops statt?" - a: "Da wir leider keinen dauerhaften Veranstaltungsort haben, finden die Veranstaltungen bei verschiedenen Firmen, die sich als Gastgeber anbieten, statt." - disabled_access: - q: "Gibt es einen behindertengerechten Zugang zu den Workshops?" - a: "Das hängt leider komplett davon ab wo der Workshop stattfindet und ob das Gebäude einen entsprechenden Zugang hat. Schick uns bitte eine E-Mail an meetings[at]codebar.io, dass wir uns erkundigen und dir bescheid sagen können." - bring_codebar_to_my_city: - q: "Ich würde codebar gerne in meine Stadt holen. Kann ich das machen?" - a: "Natürlich. Bei codebar geht es darum eine Gemeinschaft aus erfahrenen Entwickler_innen, die in ihrer Freizeit anderen helfen möchten, aufzubauen. Wenn du codebar dort aufbauen möchtest wo du lebst, würden wir uns gerne mit dir darüber unterhalten und sehen, wie wir dir dabei helfen können - schick uns einfach eine E-Mail." - our_coaches: - q: "Unsere Trainer" - a_p1: "Du findest alle Trainer die uns bei unseren Workshops geholfen haben auf der" - a_p2: ". Sie sind nach der Anwesenheitshäufigkeit sortiert. Wir zeigen so unsere Wertschätzung - ohne sie könnten wir nicht existieren." - participant_student_guide: - title: "Student Guide" - attendance_policy: - title: "Attendance Policy" - intro: "codebar is, and always has been, open to all levels of coding experience. While most of the tutorials on our website are aimed at newcomers to web development, we intend to continue our open-door policy for any student who needs coach support on their own projects. Due to the fact that our workshops are frequently oversubscribed, we ask students to respect the following expectations for participation in our workshops" - rule1: "In order to attend a workshop, you must be on the RSVP list. If you have not RSVP’d or were not allocated a spot, you will not be admitted into a workshop." - rule2: "If you can no longer attend a workshop, please cancel your RSVP by 12:00 latest on the day of the workshop. We understand that last-minute emergencies occur -- if this is the case, please get in touch with an organizer directly as soon as possible. Repeated no-shows will result in temporary or permanent suspension of your invitations." - rule3: "No guests are allowed. Our workshops are already overcrowded and we cannot make any exceptions. If your friend meets our eligibility criteria, get them to sign up and RSVP themselves." - rule4: "Please be respectful of our hosts. Do not show up exceedingly early to a workshop (not earlier than 15 minutes before the event begins) and try to leave the workstation clean and as you found it." - rule5: "Please do not work on projects that were assigned as part of any bootcamp or university curriculum. Talk to your course adviser if you feel like you need additional support with your coursework. We welcome your attendance, but we encourage you to use your time at codebar to develop skills that are outside the normal scope of your studies." - rule6: "Do not bring along and ask for help with any commercial work. This involves work you're being paid to do." - rule7: "Projects that involve specific frameworks/libraries (Rails, NodeJS, Meteor, Angular, Ember, React, etc) or languages that are not part of the codebar tutorials (anything other than Ruby or Javascript) are welcome but we cannot guarantee that a coach will be available to help you. In these cases we recommend selecting a codebar tutorial or katas (codewars.com or exercism.io) as a back-up option." - eligibility_criteria: - title: "Eligibility Criteria" - p_1: "Codebar wurde aus der Erkenntnis, dass es ein Mangel an Frauen, LGBTQ und Angehörige von ethnischen Gruppen unterrepräsentiert in Tech begonnen." - p_2: "If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School or Ask a Dev where you can learn in a collaborative environment." - p_3: "Bedenkt, dass man, ist es manchmal schwierig für uns, festzustellen, ob die Teilnehmer die basierend auf ihren vor- und Nachnamen Förderkriterien erfüllen. Wir werden unser Bestes versuchen, um über social Media profile vorher überprüfen, aber wenn wir nicht, wir kontaktieren Sie bitten um eine kurze Bestätigung, dass Sie dieses Dokument gelesen haben und behaupten, dass Sie eine oder mehrere Kriterien erfüllen. Wir werden niemals die Teilnehmer angeben, welche Gruppe Fragen." - p_4: "codebar is first and foremost a resource for students who cannot afford formal training through coding bootcamps or university degrees, for financial reasons or otherwise. Our coaches, organisers and sponsors donate their time and money to help those who have faced unfair barriers to entry into the tech world. We have strived to create an inclusive, welcoming community, and so far, we have not had to implement a formal policy to enforce the eligibility criteria -- we have left this to the honesty and good faith of the students." - p_5: "If you are unsure whether you are eligible, please get in touch. If we determine that you have signed up and do not belong to an eligible group, we will permanently suspend your student invitations without warning." - p_6: "We take this issue very seriously, and we appreciate your cooperation and understanding." - disability: - title: "Students with Disability" - description: "We want to ensure that our workshops are as accessible as possible. If you are disabled and are unsure about whether our venues can cater to your needs, we encourage you to please get in touch with us at hello@codebar.io and we will do what we can to accommodate you." - chapters: - intro_html: "Hallo und willkommen bei codebar!" - info: "Wenn du Fragen hast kannst du unsere FAQ lesen, du kannst uns aber auch gerne an %{email} schreiben, wenn du die Antwort die du suchst nicht findest. Ansonsten kannst du den folgenden Button verwenden um den Anmeldeprozess zu starten." - sign_up: "um zu unseren Workshops eingeladen zu werden." - no_incoming: "Aktuell sind keine Workshops geplant." - contact: "Um das %{city}er Team zu kontaktieren kannst du einfach eine E-Mail an %{email} schicken" - feedback_form: - title: 'Workshop Feedback' - description: Deine Einreichung ist komplett anonym. Wir lesen jedes Feedback und verwenden es um unsere Workshops zu verbessern. - note: Bitte nenne keine Namen, sondern wähle deinen Trainer aus dem entsprechenden Feld aus. Das hilft uns dabei Probleme zu adressieren, aber gleichzeitig anonym Feedback mit den Trainern zu teilen. Die Privatsphäre unserer Mitglieder ist uns sehr wichtig! - rating: Deine Gesamtbewertung des Workshops - coach: 'Wer war dein Trainer?' - select_coach: '- Trainer wählen -' - tutorial: 'Welches Tutorium habt ihr bearbeitet?' - select_tutorial: '- Tutorium wählen -' - request: 'Wie fandest du den Workshop?' - suggestions: "Gab es etwas das dir nicht gefallen hat? Was können wir tun um uns zu verbessern?" - member: - jobs: - title: My jobs - preview: Preview - index: - description: Our aim is to be the one stop shop for junior developer roles. All jobs featured on our job board must fall under the following three categories; paid internships, apprenticeships or junior developer roles. Additionally, jobs must not require previous experience or a degree and must be paid positions. Each job that is submitted will be approved by the codebar team before appearing on the job board. - testimonial: Within 2 days of posting an ad on the codebar job board, we had dozens of high quality applications and we made an offer to a candidate within 2 weeks. There are a lot of talented interns and junior developers; posting on the codebar job board is a great way to reach them. - title: Reach our community of %{students_count} junior developers - offer: - title: "For a flat fee of £50 your post will be:" - job_board: "- shown on the job board for 30 days" - slack: "- promoted to our Slack community of 5500 members" - pending: - title: Deine Jobeinträge in Prüfung - description: Du hast %{count} Jobeinträge die geprüft werden. - none: Du hast keine Jobeinträge in Prüfung. - new: - title: Job eintragen - degree: There is no degree requirement - experience: There is no previous experience requirement - rules_intro: "Bitte prüfe vor dem Abschicken, dass:" - details: dein Eintrag detailliert die zu erledigende Arbeit darstellt - suitability: "der Job passend für Menschen ist, die nach Praktika und Junior-Positionen suchen, die ihnen helfen ihre Karriere aufzubauen" - salary: der Job ein angemessenes Gehalt bietet - short: "der Eintrag kurz und auf den Punkt ist" - approval_info: "*Nach dem Abschicken wird der Job sichtbar sobald er geprüft und bestätigt wurde." - newsletter: "For an additional £200 you can have your job listing featured in our newsletter and made available to an audience of over 10000 students and coaches. To find out more details and when our next newsletter is due send us an email at hello@codebar.io." - pay: - html: You have made the required payment of £50. - button: - pay: Make a payment - edit: - title: Edit job listing - pages: - cookies: - title: Cookie Policy - p1: 'Cookies are small pieces of text used to store information on web browsers. They are used by websites accross a number of different devices to store and receive identifiers and other information. Our Website and Service use cookies and other similar technologies (collectively in this Policy, "cookies"), in order to provide a better service to you and to generally improve our Website and Service. For example, we may use cookies to help direct you to the appropriate part of our Website, by indicating that you are a repeat visitor. We also may use information to present you with services that are matched to your preferences and to manage and track the effectiveness of our marketing efforts.' - p2: Some portions of the codebar website are functional without cookies, and you may generally choose whether to accept cookies. Most web browsers are set to accept cookies by default, however, you may be able to delete cookies yourself through your browser's cookie manager. To do so, please follow the instructions provided by your web browser. Please note that disabling cookies will reset your session, disable auto-login, and may adversely affect the availability and functionality of our Website and the services we can provide to you. - sub: - title: Below are the cookies used by the codebar website. - table: - header: - h1: Name - h2: Purpose - h3: Expires - functional: - title: Functional Cookies - description: Stores information about your session. - planner_name: _planner_session - planner_purpose: Stores session data - planner_expiry: Expires after 24 hours - google_analytics: - title: Google Analytics - description: Google Analytics collects information about how you use the codebar website. This enables us to identify how busy the website is and possible improvements. - info: We don’t allow Google to use or share our analytics data. - opt_out: You can [opt out of Google Analytics](https://tools.google.com/dlpage/gaoptout). - ga_name: _ga - ga_purpose: Tracks if you have visited codebar.io before - ga_expiry: After 2 years - gid_name: _ga - gid_purpose: Tracks if you have visited codebar.io before - gid_expiry: After 24 hours - cloudflare: - title: Cloudflare - cfduid_name: _pfduid - cfduid_purpose: Used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. - cfduid_expiry: 1 year - privacy_policy: - title: Privacy Policy - subtitle: This Privacy Policy was last updated on 13 May 2021. - intro: - p1: 'This Privacy Policy has been created by codebar ("codebar", "we", "us", or "our") whose companies house registered name and address is as follows:' - address_html: " - codebar Ltd,
- International House,
- 101 King's Cross Road,
- London, England,
- WC1X 9LP
- Company No. 10791813
" - p2: codebar Ltd trades on behalf of the charity registered UK and Wales no. 1187776. For the purpose of this Privacy Policy codebar Ltd is the data controller. - p3: Your privacy means a lot to us, and we take it very seriously. We aim to be transparent with you about the data we collect about you and how it is used and shared. This Privacy Policy lets you know what information we collect when you use the codebar website, https://codebar.io/, or interact with any of the services we provide, such as signing up to workshops and events ("Services"). By using our Services you acknowledge and understand our use of your data under this Privacy Policy and how it applies to your use of our Services. - information: - title: 1. Information we collect - what_we_collect: - title: 1.1 Personal data we collect from you - p1: 'We have set out in the table below the personal data we collect about you and how we use it, which will differ based on the capacity in which you interact with codebar:' - table: - headers: - h1: Who - h2: What data we process - h3: What we use it for - h4: Lawful basis - r1: - c1: Students - c2: This includes personal data that is provided by you or collected by us to enable you to subscribe to codebar as a student. This may include your name, email address, phone number, pronouns, self-written bio, your self-recognition as being underrepresented (with your consent), and the location you choose to subscribe to. - c3: For administrative purposes when you sign up to events, to communicate with you, and to provide you with our newsletters and events information. - c4: - l1: Performance of a contract - l2: Consent - l3: Legitimate interests - r2: - c1: Coaches - c2: This includes personal data that is provided by you or collected by us to enable you to volunteer at codebar as a coach. This may include your name, email address, phone number, pronouns, self-written bio/skills, your self-recognition as being underrepresented (with your consent), and the location you choose to volunteer at. - c3: For administrative purposes when you volunteer for workshops, to communicate with you, to manage workshop attendance, and to provide you with our newsletters and events information. - c4: - l1: Consent - l2: Legitimate interests - r3: - c1: Organizers - c2: This includes personal data that is provided by you or collected by us, which may include your name, email address, phone number, pronouns, self-written bio/skills, slack username, signed documentation, and the location you choose to volunteer at. - c3: To organise and communicate workshops. - c4: - l1: Legitimate interests - r4: - c1: Hosts - c2: We may collect personal information of employees working at companies that agree to host our workshops. This information may include the employees' name, email address, contact number, and place of work. - c3: In order to market, promote, host and operate workshops. - c4: - l1: Legitimate interests - r5: - c1: Sponsors - c2: We need to collect personal data in relation to your sponsorship of codebar. This may include information such as your name, and bank details. - c3: To fulfill contractual obligations we have with you, for example, to process invoices related to your sponsorship. - c4: - l1: Performance of a contract - l2: Legitimate interests - r6: - c1: Trustees and directors - c2: We need to collect personal data in relation to your position as trustee and/or director. This may include information such as your name, contact number, address, email address, and date of birth. - c3: In order to establish our status as a charity, to comply with legal obligations, and respond to legal requests. - c4: - l1: Legitimate interests - l2: Compliance with legal obligations - how_we_share: - title: 1.2 How we share your information - p1_html: 'When you subscribe to an event, we share your name with our host companies as we are required to provide a list with all attendee names when you subscribe to any of our events. We **do not share** your email address or any other personal information.' - legal_basis: - title: 1.3 Legal basis for our use of your personal information - p1: As set out in the table above, sometimes the legal basis on which we collect and process your data is because our legitimate interests make the processing necessary, and those legitimate interests are not overridden by your interests or fundamental rights and freedoms. For example, we collect and store your data in order to process event information, and to ensure the efficient running and promotion of workshops. - retention: - title: 2. Retention - p1: We will keep your personal information for as long as reasonably necessary to fulfil the purposes we collected it for. To determine the appropriate retention period, we consider the amount, nature and sensitivity of the personal information, the potential risk of harm from unauthorised use or disclosure of your personal information, the purposes for which we process your personal data and whether we can achieve those purposes through other means, and the applicable legal, regulatory, tax, accounting or other requirements. - p2: We may retain your personal information for a longer period in the event of a complaint or if we reasonably believe there is a prospect of dispute in respect to our relationship with you. - international_transfers: - title: 3. International transfers - p1: Personal information we collect may be transferred to and stored in countries outside of the jurisdiction you are in for the purposes specified in this Privacy Policy. We will only transfer your personal information to countries that have been deemed to provide an adequate level of protection for personal information, and/or any international transfers will be made pursuant to appropriate safeguards in accordance with the applicable laws and regulations, such as standard data protection clauses adopted by the UK and European Commission. - p2: If you wish to enquire further about these safeguards used, please contact us by email at the address below or by mail using the postal address provided below. - your_rights: - title: 4. Your data protection rights - p1: 'Data protection law provides you with rights in respect of personal data that we hold about you, including the:' - l1: 'Right to Access: You have the right to obtain access to your data, and certain other information (similar to that provided in this Privacy Policy).' - l2: 'Right to Rectification: You are entitled to have your data corrected if it is inaccurate or incomplete.' - l3: 'Right to Erasure: This enables you in some circumstances to request and obtain the deletion of your data where there is no legal reason for us to keep using it.' - l4: 'Right to Restriction of Processing: You have rights to suspend further use of your data, whereby we can still store your data but cannot use it further. This may mean we can no longer provide you with Services.' - l5: 'Right to Data Portability: You have rights in some circumstances to request the transfer of your data to yourself or to a third party.' - l6: 'Right to Objection: You have the right to object to certain types of data processing, including for direct marketing purposes.' - l7: 'Right to Withdrawal of Consent: Where we are relying on consent to process your data, you have the right to withdraw your consent at any time by using any opt-out links, or by contacting us at the details provided below (although if you do so, it does not mean that anything we have done with your data with your consent up to that point is unlawful and we may be able to continue to process your personal information to the extent required or otherwise permitted by law, in particular in connection with exercising and defending our legal rights or meeting our legal and regulatory obligations).' - l8: 'Right to Lodge a Complaint: You can lodge a complaint in relation to our use of your personal information with the local supervisory authority, the Information Commissioner (UK).' - p2: If you would like to exercise any of these rights or if you have a complaint about how we handle your data, please contact us at the email address stated below. - security: - title: 5. Security - p1: The security of your personal information is important to us. codebar takes reasonable steps to implement and update administrative, technical, and physical security measures to help protect your information against unauthorised access, loss, destruction, or alteration. However, the Internet is not a 100% secure environment so we can't guarantee the security of the transmission or storage of your information. codebar has no control over or responsibility for the security or practices or privacy policies of third parties, even if you interact with them when using our Services. - changes: - title: 6. Changes to this Privacy Policy - p1: We reserve the right to modify or update this Privacy Policy at any time in accordance with this provision. If we make changes to this Privacy Policy, we will post the revised Privacy Policy on the codebar website. Please regularly review https://codebar.io/privacy-policy to check for any updates or changes to our Privacy Policy. The date this Privacy Policy was last revised is identified at the top of this page. - cookies: - title: 7. Cookies - p1_html: 'We use cookies to recognise you and your location. You can control cookies through your browser settings and other tools. For more information read our [cookie policy](https://codebar.io/cookie-policy).' - contact: - title: 8. Contact - p1: "If you have any questions or complaints about this Privacy Policy or our information handling practices, you may email us at company@codebar.io stating 'Data inquiry' in the subject title, or by postal mail at: codebar Ltd, International House, 101 King's Cross Road, London, WC1X 9LP." - breach: - title: What happens if you violate codebar’s Code of Conduct? - opening_para: All codebar events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment towards any community member or organiser in any form. Harassment includes any type of aggressive behaviour or offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. - second_para: The Code of Conduct is in place to protect every codebar member - students, coaches and organisers. If any member violates these rules the below procedure and sanctions will be implemented. - outcome_title: 3 types of outcomes - correction: Correction - The use of inappropriate language or other behavior deemed unprofessional or unwelcome in the codebar community. This includes the use of terminology that is discouraged, e.g. 'guys'. In this situation you will be sent a private message, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. - warning: Warning - You will receive an email warning. The organiser will explain the incident, including the impact on the person involved and the community. We will give as much information as possible, so you’re aware of what happened and try to learn from the incident. The organiser will add a note to your codebar profile so that all chapter organisers are aware of the incident. We expect you to take our comments on board, further action may be taken depending on your reaction. Examples of behaviour that will get you a warning include - targeted offensive language, or the sharing of sexual images in codebar spaces. 2 email warnings will result in a lifetime ban. - lifetime_ban: Lifetime ban - You will no longer be able to RSVP to any future codebar events. You will also be removed from codebar’s Slack workspace. Examples of behaviour that will get you an automatic lifetime ban include - physical intimidation, stalking, inappropriate physical contact, unwelcome sexual attention or repeated behaviour after you’ve been spoken to by someone from the codebar team (directors or chapter organisers). - closing_para: The above is only a starting point. The details of the incident may change how we view it, e.g. some verbal harassment may be so serious that we would give a lifetime ban. - how_to_support_us: - volunteer: - title: Volunteer with us - become_an_organiser: - title: Become an organiser - description: Champion inclusion and diversity in the tech industry as a workshop organiser with codebar. Your contribution will create an empowering and safe environment, fostering learning and collaboration among individuals exploring coding in our vibrant community. - link: Email us to become an organiser - become_a_coach: - title: Become a coach - description: Affect change as a volunteer coach with codebar - your expertise and guidance will pave the way for aspiring developers, unlocking the world of coding and creating opportunities for folks from groups under represented in the tech industry. - volunteer: - title: Other skills - description: Your unique abilities could be our missing piece in the codebar puzzle. Having a diverse range of skills in our team is necessary to enrich our community. From fundraising to event coordination to marketing, we always welcome new talent to drive our mission forward. - link: Email us to become a volunteer - fundraise: - title: Fundraise - description_html: "Join the codebar team with a physical challenge event. Whether you are a runner, swimmer, or cyclist, sign up with our registration form for your desired event and raise vital funds to help keep our events running. If your event does not appear below, feel free to drop us an email and we would be happy to coordinate with you." - image_alt: A Black British woman crosses the finish line at the Hackney Half Marathon in London in a shower of confetti while spectators cheer her on. - codebar_stories_podcast: - image_alt: codebar stories banner - opening: codebar Stories is a new podcast brought to you by codebar, we'll be smashing down the belief that tech isn't for you by sharing real-life stories from members of our community who have transitioned into a new career in tech. - contact_us_html: "Sponsoring codebar Stories offers you a unique opportunity to connect with a diverse, engaged audience within the tech community. As a podcast dedicated to empowering underrepresented groups through coding education, your brand will align with our values of diversity, inclusivity, and social impact. Through sponsorship, you'll gain visibility, build positive PR, and demonstrate your commitment to fostering the next generation of tech talent, all while supporting a meaningful cause. Sound good? Please drop us an email podcast@codebar.io." - - admin: - dashboard: - title: 'Admin' - workshop: - manage_rsvps: - text: 'Studenten und Trainer zum Workshop einladen. Die Bestätigungs-E-Mail wird ausgelöst und sie werden von der Warteliste entfernt.' - destroy: - success: "Werkstatt erfolgreich gelöscht" - failure: "Workshop kann nicht gelöscht werden. Dies kann passieren weil der Workshop eingeladene Teilnehmer hat und/oder lang genug auf der Webseite aufgeführt war, dass er nicht gelöscht werden kann." - messages: - meeting: - created: 'Meeting wurde erfolgreich erstellt' - updated: 'Meetingdetails erfolgreich aktualisiert' - invitations_already_sent: 'Einladungen wurden bereits verschickt; sie werden nicht erneut versendet' - sending_invitations: 'Einladungen werden verschickt' - invitation: - rsvp_member: "%{name} wurde erfolgreich hinzugefügt und per E-Mail benachrichtigt." - already_on_list: "%{name} ist bereits auf der Liste!" - rsvp_error: "Es ist etwas schief gegangen, %{name} wurde nicht hinzugefügt." - update_rsvp: 'Teilnahme von %{name} aktualisiert' - simple_form: - placeholders: - job: - company: 'e.g. codebar' - company_website: 'e.g. https://codebar.io' - title: 'e.g. Internship' - description: 'Use text or markdown for the job description' - location: 'e.g. London or Berlin' - hints: - job: - remote: Only check if the role is fully remote only - salary: Annual pay before tax, without commas or decimal points - activerecord: - attributes: - job: - title: Title - company: Name - company_address: Address - company_postcode: Postcode - company_website: Website - email: Contact email - link_to_job: Link to job post - expiry_date: Application closing date - donation_platforms: - title: "Donate" - description: "Your support—whether through a one-time gift or ongoing commitment—drives our mission to create a more inclusive tech industry. It enables us to provide continuous learning opportunities and empower individuals from underrepresented groups to grow and thrive in tech." - link: "Find out how else to support us" - donation_form: - title: "Use the donation page" - text: "Make a lasting impact with codebar by giving a one-time donation or committing to a monthly contribution." - image_alt: "codebar logo" - github_sponsors: - title: "Github Sponsors" - text: "Support codebar’s mission directly through GitHub Sponsors and help shape the future of technology with your generous donation." - image_alt: "Github Sponsors logo" - open_collective: - title: "Open Collective" - text: "Setup a recurring contribution or make a one-time donation through Open Collective." - image_alt: "Open Collective logo" - give_as_you_live: - title: "Give as you Live" - text: "Give as you Live is a platform enabling you to raise funds for your favourite charity with your everyday online shopping." - image_alt: "Give as you Live logo" diff --git a/config/locales/en_AU.yml b/config/locales/en_AU.yml deleted file mode 100644 index 5b13e8ae9..000000000 --- a/config/locales/en_AU.yml +++ /dev/null @@ -1,553 +0,0 @@ -en-AU: - brand: "codebar.io" - date: - formats: - default: "%d/%m/%Y" - email: "%a, %d %B at %H:%M" - email_title: "%A, %d %b at %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - website_format: "%a, %d %B %Y at %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y at %R" - dashboard: "%a, %d %b %Y, %H:%M" - time: - formats: - default: "%a, %d %b %Y %H:%M" - email: "%a, %d %B at %H:%M" - email_title: "%A, %d %b at %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - full_date: "%d %B %Y" - default_date: "%d/%m/%Y" - website_format: "%a, %d %B %Y at %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y at %R" - dashboard: "%A, %b %d" - number: - currency: - format: - unit: '£' - delimiter: ',' - separator: '.' - precision: 0 - format: '%u%n' - homepage: - intro: "codebar is a charity that facilitates the growth of a diverse tech community by running free regular programming workshops for minority groups in tech." - explanation: "Our goal is to enable people from underrepresented groups to learn programming in a safe and collaborative environment and expand their career opportunities. To achieve this we run free regular workshops, regular one-off events and try to create opportunities for our students making technology and coding more accessible." - participate: - students_title: "Students" - students_explanation_p1: "Our students come from diverse backgrounds—some aspiring to become full-time developers, while others simply want to learn the basics of coding in a supportive environment." - students_explanation_p2: Join our vibrant community and take part in our workshops!" - students_button: "Join us as a student" - coaches_title: "Coaches" - coaches_explanation_p1: "We encourage new students to start with our tutorials on HTML/CSS, JavaScript, Ruby, Python, or Git, while also helping them grasp key programming concepts." - coaches_explanation_p2: "That’s why we’re always looking for more developers to join our community and coach at our workshops." - coaches_button: "Join us as a coach" - workshop_title: "Workshops" - workshop_explanation_p1: "We’re proud to be hosted by amazing companies that support our mission. Our typical format includes 30 minutes of socialising over food and drinks, a lightning talk, and then hands-on coding." - workshop_explanation_p2: "Help us grow and support our chapters by hosting or sponsoring our workshops, and together, we can expand opportunities for more aspiring developers." - workshop_button: "Let's work together" - workshop_email_subject: "Regarding hosting a workshop" - chapters: - title: "Chapters" - events: - upcoming: "Upcoming Events" - donation_platforms: - title: "How to support us" - mailer: - workshop_invitation: - attending: - subject: "Attendance Confirmation for %{date_time}" - attending_reminder: - subject: "Workshop Reminder %{date_time}" - invite_coach: - subject: "Workshop Coach Invitation %{date_time}" - invite_student: - subject: "Workshop Invitation %{date_time}" - notify_waiting_list: - subject: "A spot just became available" - waiting_list_reminder: - subject: "Reminder: you're on the codebar waiting list (%{date_time})" - messages: - accepted_invitation: "Thanks for getting back to us %{name}. See you at the workshop!" - already_invited: 'You have already RSVPd or joined the waitlist for this workshop.' - error_blank_note: 'You must select a note' - rejected_invitation: "We are so sad you can't make it, but thanks for letting us know %{name}." - already_rsvped: "You have already confirmed your attendance!" - not_attending_already: "You have already confirmed you can't make it!" - no_available_seats: "Unfortunately there are no more spaces left :(. If you would like to join our waiting list send us an email at %{email}" - feedback_saved: "Thank you for taking the time to give us feedback!" - feedback_not_found: "You have already submitted feedback for this event." - updated_note: "Successfully updated note." - invalid_session: 'Your session is invalid' - invitations: - meeting: - cancel: "Thanks for letting us know you can't make it." - rsvp: "Your RSVP was successful. We look forward to seeing you at the Monthly!" - rsvped_to_other_workshop: "You have already RSVP'd to another workshop on this date. If you would prefer to attend this workshop, please cancel your other RSVP first." - spot_confirmed: "Your spot has been confirmed for %{event}! We look forward to seeing you there." - spot_not_confirmed: 'Your spot has not yet been confirmed. We will verify your attendance after you complete the questionnaire.' - notifications: - provider_already_connected: 'You are already signed in!' - not_logged_in: "You must be logged in to access this page." - navigation: - dashboard: "Dashboard" - code_of_conduct: "Code of Conduct" - breach_code_of_conduct: "Breach Code of Conduct" - coach_guide: "Coach Guide" - student_guide: "Student Guide" - tutorials: "Tutorials" - becoming_sponsor: "Becoming a Sponsor" - faq: "FAQ" - blog: "Blog" - codebar_stories: "codebar Stories" - stats: "Stats" - dashboard: - join_workshops_in: "Join our free workshops in" - workshops_goal: "to get to grips with the basics of programming and web development." - tweets_by: "Tweets by" - latest_sponsors: "Latest Sponsors" - policy: - intro: "There’s high demand for our workshops and we have a waiting list on most weeks. To make sure as many people as possible can come, we have a straightforward attendance policy." - rule1: "Before you RSVP make sure you are eligible to attend. If you’re not sure get in touch for a chat." - rule2: "You must sign up and RSVP to attend our workshops." - rule3: "If you RSVP then later realise you can’t make it, you must cancel. It only takes a few seconds to do through your confirmation email." - rule4: "Please try to cancel with at least 24 hours notice." - rule5: "We know that sometimes things come up last minute, but even if you only cancel an hour before the workshop, get in touch and let us know." - what_happens: "What happens if I don’t respect the policy?" - strikes_system: "We operate a three strikes system. That means if you don’t come in without cancelling an RSVP three times, we will take you off our invite list for four weeks. We’ll get in touch after your first absence to make sure you understand this." - removing: "If you fail to attend without cancelling another three times, we might have to remove you permanently from our invitation list." - rsvping: "There is no penalty for RSVP-ing and then cancelling on a regular basis, but please avoid it. If you always struggle to make it in on a certain day then let us know – that kind of feedback is really important to us." - eligibility_note: "Another note on eligibility" - abuse: "We’re a fairly relaxed bunch and we trust you, so we don’t police students as to their eligibility. However if it ever looks like this is being abused we may have to change that – which we really don’t want to do." - reminder: "So please remember what these workshops are for – to open up tech to people that are underrepresented in the industry." - teacher_guide: - laptop: "You don't need a laptop for our workshops. You are there to watch and guide the students. If you don't feel comfortable with the tutorial you should spend time on it before coming if you want to help out." - keyboard: "Do not take over the keyboard! This can be off-putting and scary." - typing: "Encourage the students to type and not copy paste." - questions: "Explain that there are no bad questions." - mistakes: "Explain to students that it's OK to make mistakes." - introduction: "Always introduce yourself. Say why you want to help out and are spending your own time on this, why you like programming." - backgrounds: "Give your students the opportunity to get to know each other. Ask their names, why they are here, what they do in their day jobs. Encourage a brief discussion before starting." - limits: "Assume that anyone you're teaching has no knowledge but infinite intelligence." - collaboration: "Work collaboratively with your student. If you have two students, you should work with both. Don't focus all your attention on one of them." - discussion: "Let students have a go at answering the questions first. Help with open and leading questions. Encourage a discussion." - talk_slow: "Take it slow, you are the teacher, they are the student. Allow for time between questions." - mild_approach: "Don't say no when the students are not doing something right. Be gentle, approach it in a mild way." - paper: "Use pen and paper or go to a whiteboard! Often students are coming from a non-technical background. Drawing and explaining with visual material is really helpful." - stubling: "Let them stumble. We learn by making mistakes, getting frustrated, and working through problem in our own way. Be supportive, but let them explore." - suggestions: "Do you have something to suggest? Make a pull request or create an issue" - workshops: - already_wish_to_attend: 'You have already RSVPd or joined the waitlist for this workshop.' - lead: "Attend our workshops to learn programming in a safe and supportive environment at your own pace, or to share your knowledge and coach our students." - registration_not_open: 'This workshop is not open for registrations' - events: - title: "Events" - past: "Past" - no_upcoming_events: "There are no upcoming events." - view_past_events: "View past events" - view_all: "View all" - hosted_by: "Hosted by" - organisers: "Organisers" - venue_at: "at" - attend_as_student: "Attend as a student" - attend_as_coach: "Attend as a coach" - location: "Location" - sponsors: "Sponsors" - thx_to_sponsors: "A big thanks to all of our sponsors for making the event possible!" - coaches: "Coaches" - students: Students - schedule: "Schedule" - send_us_an_email: "send us an email" - not_open_for_rsvp: This event is not open for RSVP yet. - virtual: This is a virtual event. - faq: - experience: - q: "How experienced should I be to join the workshop?" - a: - contribution: - q: "What kind of contributions can I make?" - a: "Your contributions can be tiny, as simple as fixing a typo, to something incredible. You can help with documentation, fix a bug that you found, improve the copy, help with design or even tackle bigger tasks and help introduce new features. Every little helps!" - laptop: - q: "Do I need to bring a laptop?" - a_html: "Yes, you should bring a laptop. If you don't have one %{link} as we may be able to help." - keyboard: - q: "Do I need to bring a keyboard?" - a_html: "A keyboard would help as you will spend the entire day pairing with someone on your laptop. If you don't have a keyboard, %{link} and we'll try to organise something for you." - travel_costs: - q: "I will be commuting. Can you help with my travel expenses?" - a: "We will be offering some travel grants. Just make sure you fill in the questionnaire after you RSVP and we will get in touch." - coaches: - want_to_coach: "Do you want to coach at our workshops?" - read_before: "If you have not attended our workshops before, make sure you read our" - code_of_conduct: "code of conduct" - policy: "as we have a zero tolerance policy and expect everyone to behave appropriately. You should also go through our" - guide: "coaching guide" - unable_attend: "In case you are unable to attend after you RSVP, please make sure you come back and update your attendance as we rely on coaches showing up in order for our workshops to run smoothly." - food: "PS: There will also be food at the workshop. We always make an effort to have vegetarian, vegan and gluten-free options available. If you have any other dietary requirements, send us email at" - code_of_conduct: - title: "Code of conduct" - summary: - title: "The Quick Version" - intro: "Our events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of our members in any form. Sexual language and imagery is not appropriate for any of our events, including talks, workshops, parties, and online media. Members violating these rules may be sanctioned or expelled from the event and any future events at the discretion of the organisers." - content: - title: "The Long Version" - harassment: "Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention." - comply: "We expect any participants asked to stop any harassing behaviour to comply immediately." - sponsors: "Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment." - sanctions: "If a participant engages in harassing behaviour the organisers may take any action they deem appropriate. This includes warning the offender or expulsion." - concerns: "If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact one of the organisers immediately." - applies_to: "We expect participants to follow these rules at all codebar events. If they fail to do so, the following process will take place." - questions: "If you have any questions or concerns about this code please" - contact: "contact us" - email_subject: "Regarding code of conduct" - sponsors: - sponsoring: "Sponsoring" - members: - sign_up: "Join our community" - sign_in_with_github: "Sign in with GitHub" - sign_up_as_student: "Join us as a student" - sign_up_as_student_disclaimer: "* I understand and meet the eligibility criteria." - sign_up_as_coach: "Join as a coach" - code_of_conduct: "code of conduct" - new: - intro_html: "We provide a welcoming, inclusive, and supportive learning environment, with a strict zero-tolerance policy for any form of harassment or inappropriate behavior. Please take a moment to review our code of conduct before signing up." - students: - intro_html: "If you’re interested in attending as a student, be sure to check our eligibility criteria. Our workshops and events are exclusively for women, non-binary, LGBTQ+ members, and people from underrepresented groups." - github: "When you click the sign-up button, you'll be redirected to GitHub. After logging in with your GitHub account, you'll return to the codebar website. If you don’t have an account yet, creating one is quick and easy—and it will be useful as you begin your coding journey!" - invitations: "Invitations are sent out periodically, so don't worry if you don't receive one as soon as you register." - footer: - email_us: "Send us an email at" - contact_info: "Contact Info:" - faq: - payment: - q: "Do I need to pay to attend codebar?" - a_p1: "Absolutely not! We are lucky enough to have some great companies who are able to host the workshops and/or kindly provide food. And our" - awesome_coaches: "awesome coaches" - a_p2: "give their time freely to help the community." - technologies: - q: "What technologies do you teach?" - a: "We have a variety of available tutorials in HTML, CSS, JavaScript and Ruby. If you want to learn something else don't hesitate to send us an email as we might still be able to find someone to help you out." - eligibility: - q: "I want to attend a workshop. Am I eligible?" - a: "Our workshops are available to women, LGBTQ and people who are underrepresented in the tech industry. If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School London where you can learn in a collaborative environment. Please see our student guide for more information." - career: - q: "Is codebar only aimed at people who want to move into a career as a developer?" - a: "No! codebar is about getting people excited about programming. We'll help them learn some basic coding skills, as well as how to explore and do things on their own. For those who do want to become developers, we will provide help and guidance to help them achieve their goal." - format: - q: "What is the format of the workshops?" - a: "We try to have one coach for every two students. We will pair up students who want to work on the same tutorial, and assign them a coach. The rest just happens." - laptop: - q: "Do I need to bring a laptop with me at the workshops?" - a: "Yes, we suggest that you bring a laptop as it will be easier for you to carry on working on things after the workshops. It you don't have one, send us an email so we can try and help out." - online_resources: - q: "There are so many online resources, why should I come to codebar?" - a: "Coding can be intimidating and a lot of people find it hard to get started. By putting you in touch with people who can help and guide you we make the experience and learning process easier and more enjoyable." - preperations: - q: "I would like to coach at codebar. Is there anything I should do besides signing up?" - a_p1: "Yes. First you should read our" - coaching_guide_tutorials: "coaching guide tutorials" - a_p2: ". Then spend sometime familiarising yourself with the" - a_p3: "tutorials. The tutorials are open source so if there is something that you want to improve open an issue on the GitHub repository or send a pull request." - a_p4: "We don't expect the coaches to be familiar with all the technologies and languages we have material on." - location: - q: "Where do the workshops take place?" - a: "As we don't have a permanent venue, our workshops are hosted by different companies in various locations around London. So far we've run workshops in Shoreditch, London Bridge, Holborn and Kings Cross." - disabled_access: - q: "Is there disabled access at the workshops?" - a: "Unfortunately, that depends entirely on where we are hosting our workshops and if the venue has disabled access. If you would like to attend, send us an email at meetings[at]codebar.io so we can enquire about it and let you know." - bring_codebar_to_my_city: - q: "I would like to bring codebar to my city. Can I do that?" - a: "Of course. codebar is about building a community of experienced developers that are able to give up some of their time to help others. If you are keen on running codebar where you live, we would love to speak to you about it and see how we can help make this happen, so send us an email." - our_coaches: - q: "Our coaches" - a_p1: "You can see all the coaches have helped out in our workshops on the" - a_p2: ". They are ordered by number of attendances. This is our way of showing our appreciation to them, as without them, we wouldn't be able to exist." - participant_student_guide: - title: "Student Guide" - attendance_policy: - title: "Attendance Policy" - intro: "codebar is, and always has been, open to all levels of coding experience. While most of the tutorials on our website are aimed at newcomers to web development, we intend to continue our open-door policy for any student who needs coach support on their own projects. Due to the fact that our workshops are frequently oversubscribed, we ask students to respect the following expectations for participation in our workshops" - rule1: "In order to attend a workshop, you must be on the RSVP list. If you have not RSVP’d or were not allocated a spot, you will not be admitted into a workshop." - rule2: "If you can no longer attend a workshop, please cancel your RSVP by 12:00 latest on the day of the workshop. We understand that last-minute emergencies occur -- if this is the case, please get in touch with an organizer directly as soon as possible. Repeated no-shows will result in temporary or permanent suspension of your invitations." - rule3: "No guests are allowed. Our workshops are already overcrowded and we cannot make any exceptions. If your friend meets our eligibility criteria, get them to sign up and RSVP themselves." - rule4: "Please be respectful of our hosts. Do not show up exceedingly early to a workshop (not earlier than 15 minutes before the event begins) and try to leave the workstation clean and as you found it." - rule5: "Please do not work on projects that were assigned as part of any bootcamp or university curriculum. Talk to your course adviser if you feel like you need additional support with your coursework. We welcome your attendance, but we encourage you to use your time at codebar to develop skills that are outside the normal scope of your studies." - rule6: "Do not bring along and ask for help with any commercial work. This involves work you're being paid to do." - rule7: "Projects that involve specific frameworks/libraries (Rails, NodeJS, Meteor, Angular, Ember, React, etc) or languages that are not part of the codebar tutorials (anything other than Ruby or Javascript) are welcome but we cannot guarantee that a coach will be available to help you. In these cases we recommend selecting a codebar tutorial or katas (codewars.com or exercism.io) as a back-up option." - eligibility_criteria: - title: "Eligibility Criteria" - p_1: "codebar was started out of recognition that there is a shortage of women, LGBTQ, and people belonging to underrepresented ethnic groups in tech." - p_2: "If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School or Ask a Dev where you can learn in a collaborative environment." - p_3: "Bearing that in mind, it is sometimes difficult for us to identify whether attendees meet the eligibility criteria based on their first and last names. If we cannot determine your eligibility, we will contact you asking for a short confirmation that you have read this document and assert that you meet one or more of the criteria. We will never ask participants to specify which group." - p_4: "codebar is first and foremost a resource for students who cannot afford formal training through coding bootcamps or university degrees, for financial reasons or otherwise. Our coaches, organisers and sponsors donate their time and money to help those who have faced unfair barriers to entry into the tech world. We have strived to create an inclusive, welcoming community, and so far, we have not had to implement a formal policy to enforce the eligibility criteria -- we have left this to the honesty and good faith of the students." - p_5: "If you are unsure whether you are eligible, please get in touch. If we determine that you have signed up and do not belong to an eligible group, we will permanently suspend your student invitations without warning." - p_6: "We take this issue very seriously, and we appreciate your cooperation and understanding." - disability: - title: "Students with Disability" - description: "We want to ensure that our workshops are as accessible as possible. If you are disabled and are unsure about whether our venues can cater to your needs, we encourage you to please get in touch with us at hello@codebar.io and we will do what we can to accommodate you." - chapters: - intro_html: "Hi and welcome to codebar!" - info: "Check out our FAQ page for any questions you might have, or email us at %{email} if you can't find the answer you're looking for. Otherwise, click the Join our community button to join us." - sign_up: "to be invited to our workshops." - no_incoming: "There are no workshops coming up." - contact: "To contact the %{city} team, send an email to %{email}" - feedback_form: - title: 'Workshop feedback' - description: Your submission will be completely anonymous. We read every piece of feedback and use it to help us improve our workshops. - note: Please do not mention any names, but instead choose your coach from the dropdown. This enables us to address issues but also to anonymously share feedback with coaches. Member privacy is very important to us! - rating: Your overall rating of the workshop - coach: 'Who was your coach?' - select_coach: '- Select Coach -' - tutorial: 'What tutorial did you go through?' - select_tutorial: '- Select Tutorial -' - request: 'How did you find the workshop?' - suggestions: "Was there something you didn't like? What can we do to improve your experience?" - pages: - cookies: - title: Cookie Policy - p1: 'Cookies are small pieces of text used to store information on web browsers. They are used by websites accross a number of different devices to store and receive identifiers and other information. Our Website and Service use cookies and other similar technologies (collectively in this Policy, "cookies"), in order to provide a better service to you and to generally improve our Website and Service. For example, we may use cookies to help direct you to the appropriate part of our Website, by indicating that you are a repeat visitor. We also may use information to present you with services that are matched to your preferences and to manage and track the effectiveness of our marketing efforts.' - p2: Some portions of the codebar website are functional without cookies, and you may generally choose whether to accept cookies. Most web browsers are set to accept cookies by default, however, you may be able to delete cookies yourself through your browser's cookie manager. To do so, please follow the instructions provided by your web browser. Please note that disabling cookies will reset your session, disable auto-login, and may adversely affect the availability and functionality of our Website and the services we can provide to you. - sub: - title: Below are the cookies used by the codebar website. - table: - header: - h1: Name - h2: Purpose - h3: Expires - functional: - title: Functional Cookies - description: Stores information about your session. - planner_name: _planner_session - planner_purpose: Stores session data - planner_expiry: Expires after 24 hours - google_analytics: - title: Google Analytics - description: Google Analytics collects information about how you use the codebar website. This enables us to identify how busy the website is and possible improvements. - info: We don’t allow Google to use or share our analytics data. - opt_out: You can [opt out of Google Analytics](https://tools.google.com/dlpage/gaoptout). - ga_name: _ga - ga_purpose: Tracks if you have visited codebar.io before - ga_expiry: After 2 years - gid_name: _ga - gid_purpose: Tracks if you have visited codebar.io before - gid_expiry: After 24 hours - cloudflare: - title: Cloudflare - cfduid_name: _pfduid - cfduid_purpose: Used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. - cfduid_expiry: 1 year - privacy_policy: - title: Privacy Policy - subtitle: This Privacy Policy was last updated on 13 May 2021. - intro: - p1: 'This Privacy Policy has been created by codebar ("codebar", "we", "us", or "our") whose companies house registered name and address is as follows:' - address_html: " - codebar Ltd,
- International House,
- 101 King's Cross Road,
- London, England,
- WC1X 9LP
- Company No. 10791813
" - p2: codebar Ltd trades on behalf of the charity registered UK and Wales no. 1187776. For the purpose of this Privacy Policy codebar Ltd is the data controller. - p3: Your privacy means a lot to us, and we take it very seriously. We aim to be transparent with you about the data we collect about you and how it is used and shared. This Privacy Policy lets you know what information we collect when you use the codebar website, https://codebar.io/, or interact with any of the services we provide, such as signing up to workshops and events ("Services"). By using our Services you acknowledge and understand our use of your data under this Privacy Policy and how it applies to your use of our Services. - information: - title: 1. Information we collect - what_we_collect: - title: 1.1 Personal data we collect from you - p1: 'We have set out in the table below the personal data we collect about you and how we use it, which will differ based on the capacity in which you interact with codebar:' - table: - headers: - h1: Who - h2: What data we process - h3: What we use it for - h4: Lawful basis - r1: - c1: Students - c2: This includes personal data that is provided by you or collected by us to enable you to subscribe to codebar as a student. This may include your name, email address, phone number, pronouns, self-written bio, , your self-recognition as being underrepresented (with your consent), and the location you choose to subscribe to. - c3: For administrative purposes when you sign up to events, to communicate with you, and to provide you with our newsletters and events information. - c4: - l1: Performance of a contract - l2: Consent - l3: Legitimate interests - r2: - c1: Coaches - c2: This includes personal data that is provided by you or collected by us to enable you to volunteer at codebar as a coach. This may include your name, email address, phone number, pronouns, self-written bio/skills, , your self-recognition as being underrepresented (with your consent), and the location you choose to volunteer at. - c3: For administrative purposes when you volunteer for workshops, to communicate with you, to manage workshop attendance, and to provide you with our newsletters and events information. - c4: - l1: Consent - l2: Legitimate interests - r3: - c1: Organizers - c2: This includes personal data that is provided by you or collected by us, which may include your name, email address, phone number, pronouns, self-written bio/skills, , slack username, signed documentation, and the location you choose to volunteer at. - c3: To organise and communicate workshops. - c4: - l1: Legitimate interests - r4: - c1: Hosts - c2: We may collect personal information of employees working at companies that agree to host our workshops. This information may include the employees' name, email address, contact number, , and place of work. - c3: In order to market, promote, host and operate workshops. - c4: - l1: Legitimate interests - r5: - c1: Sponsors - c2: We need to collect personal data in relation to your sponsorship of codebar. This may include information such as your name, and bank details. - c3: To fulfill contractual obligations we have with you, for example, to process invoices related to your sponsorship. - c4: - l1: Performance of a contract - l2: Legitimate interests - r6: - c1: Trustees and directors - c2: We need to collect personal data in relation to your position as trustee and/or director. This may include information such as your name, contact number, address, email address, and date of birth. - c3: In order to establish our status as a charity, to comply with legal obligations, and respond to legal requests. - c4: - l1: Legitimate interests - l2: Compliance with legal obligations - how_we_share: - title: 1.2 How we share your information - p1_html: 'When you subscribe to an event, we share your name with our host companies as we are required to provide a list with all attendee names when you subscribe to any of our events. We **do not share** your email address or any other personal information.' - legal_basis: - title: 1.3 Legal basis for our use of your personal information - p1: As set out in the table above, sometimes the legal basis on which we collect and process your data is because our legitimate interests make the processing necessary, and those legitimate interests are not overridden by your interests or fundamental rights and freedoms. For example, we collect and store your data in order to process event information, and to ensure the efficient running and promotion of workshops. - retention: - title: 2. Retention - p1: We will keep your personal information for as long as reasonably necessary to fulfil the purposes we collected it for. To determine the appropriate retention period, we consider the amount, nature and sensitivity of the personal information, the potential risk of harm from unauthorised use or disclosure of your personal information, the purposes for which we process your personal data and whether we can achieve those purposes through other means, and the applicable legal, regulatory, tax, accounting or other requirements. - p2: We may retain your personal information for a longer period in the event of a complaint or if we reasonably believe there is a prospect of dispute in respect to our relationship with you. - international_transfers: - title: 3. International transfers - p1: Personal information we collect may be transferred to and stored in countries outside of the jurisdiction you are in for the purposes specified in this Privacy Policy. We will only transfer your personal information to countries that have been deemed to provide an adequate level of protection for personal information, and/or any international transfers will be made pursuant to appropriate safeguards in accordance with the applicable laws and regulations, such as standard data protection clauses adopted by the UK and European Commission. - p2: If you wish to enquire further about these safeguards used, please contact us by email at the address below or by mail using the postal address provided below. - your_rights: - title: 4. Your data protection rights - p1: 'Data protection law provides you with rights in respect of personal data that we hold about you, including the:' - l1: 'Right to Access: You have the right to obtain access to your data, and certain other information (similar to that provided in this Privacy Policy).' - l2: 'Right to Rectification: You are entitled to have your data corrected if it is inaccurate or incomplete.' - l3: 'Right to Erasure: This enables you in some circumstances to request and obtain the deletion of your data where there is no legal reason for us to keep using it.' - l4: 'Right to Restriction of Processing: You have rights to suspend further use of your data, whereby we can still store your data but cannot use it further. This may mean we can no longer provide you with Services.' - l5: 'Right to Data Portability: You have rights in some circumstances to request the transfer of your data to yourself or to a third party.' - l6: 'Right to Objection: You have the right to object to certain types of data processing, including for direct marketing purposes.' - l7: 'Right to Withdrawal of Consent: Where we are relying on consent to process your data, you have the right to withdraw your consent at any time by using any opt-out links, or by contacting us at the details provided below (although if you do so, it does not mean that anything we have done with your data with your consent up to that point is unlawful and we may be able to continue to process your personal information to the extent required or otherwise permitted by law, in particular in connection with exercising and defending our legal rights or meeting our legal and regulatory obligations).' - l8: 'Right to Lodge a Complaint: You can lodge a complaint in relation to our use of your personal information with the local supervisory authority, the Information Commissioner (UK).' - p2: If you would like to exercise any of these rights or if you have a complaint about how we handle your data, please contact us at the email address stated below. - security: - title: 5. Security - p1: The security of your personal information is important to us. codebar takes reasonable steps to implement and update administrative, technical, and physical security measures to help protect your information against unauthorised access, loss, destruction, or alteration. However, the Internet is not a 100% secure environment so we can't guarantee the security of the transmission or storage of your information. codebar has no control over or responsibility for the security or practices or privacy policies of third parties, even if you interact with them when using our Services. - changes: - title: 6. Changes to this Privacy Policy - p1: We reserve the right to modify or update this Privacy Policy at any time in accordance with this provision. If we make changes to this Privacy Policy, we will post the revised Privacy Policy on the codebar website. Please regularly review https://codebar.io/privacy-policy to check for any updates or changes to our Privacy Policy. The date this Privacy Policy was last revised is identified at the top of this page. - cookies: - title: 7. Cookies - p1_html: 'We use cookies to recognise you and your location. You can control cookies through your browser settings and other tools. For more information read our [cookie policy](https://codebar.io/cookie-policy).' - contact: - title: 8. Contact - p1: "If you have any questions or complaints about this Privacy Policy or our information handling practices, you may email us at company@codebar.io stating 'Data inquiry' in the subject title, or by postal mail at: codebar Ltd, International House, 101 King's Cross Road, London, WC1X 9LP." - breach: - title: What happens if you violate codebar’s Code of Conduct? - opening_para: All codebar events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment towards any community member or organiser in any form. Harassment includes any type of aggressive behaviour or offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. - second_para: The Code of Conduct is in place to protect every codebar member - students, coaches and organisers. If any member violates these rules the below procedure and sanctions will be implemented. - outcome_title: 3 types of outcomes - correction: Correction - The use of inappropriate language or other behavior deemed unprofessional or unwelcome in the codebar community. This includes the use of terminology that is discouraged, e.g. 'guys'. In this situation you will be sent a private message, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. - warning: Warning - You will receive an email warning. The organiser will explain the incident, including the impact on the person involved and the community. We will give as much information as possible, so you’re aware of what happened and try to learn from the incident. The organiser will add a note to your codebar profile so that all chapter organisers are aware of the incident. We expect you to take our comments on board, further action may be taken depending on your reaction. Examples of behaviour that will get you a warning include - targeted offensive language, or the sharing of sexual images in codebar spaces. 2 email warnings will result in a lifetime ban. - lifetime_ban: Lifetime ban - You will no longer be able to RSVP to any future codebar events. You will also be removed from codebar’s Slack workspace. Examples of behaviour that will get you an automatic lifetime ban include - physical intimidation, stalking, inappropriate physical contact, unwelcome sexual attention or repeated behaviour after you’ve been spoken to by someone from the codebar team (directors or chapter organisers). - closing_para: The above is only a starting point. The details of the incident may change how we view it, e.g. some verbal harassment may be so serious that we would give a lifetime ban. - how_to_support_us: - volunteer: - title: Volunteer with us - become_an_organiser: - title: Become an organiser - description: Champion inclusion and diversity in the tech industry as a workshop organiser with codebar. Your contribution will create an empowering and safe environment, fostering learning and collaboration among individuals exploring coding in our vibrant community. - link: Email us to become an organiser - become_a_coach: - title: Become a coach - description: Affect change as a volunteer coach with codebar - your expertise and guidance will pave the way for aspiring developers, unlocking the world of coding and creating opportunities for folks from groups under represented in the tech industry. - volunteer: - title: Other skills - description: Your unique abilities could be our missing piece in the codebar puzzle. Having a diverse range of skills in our team is necessary to enrich our community. From fundraising to event coordination to marketing, we always welcome new talent to drive our mission forward. - link: Email us to become a volunteer - fundraise: - title: Fundraise - description_html: "Join the codebar team with a physical challenge event. Whether you are a runner, swimmer, or cyclist, sign up with our registration form for your desired event and raise vital funds to help keep our events running. If your event does not appear below, feel free to drop us an email and we would be happy to coordinate with you." - image_alt: A Black British woman crosses the finish line at the Hackney Half Marathon in London in a shower of confetti while spectators cheer her on. - codebar_stories_podcast: - image_alt: codebar stories banner - opening: codebar Stories is a new podcast brought to you by codebar, we'll be smashing down the belief that tech isn't for you by sharing real-life stories from members of our community who have transitioned into a new career in tech. - contact_us_html: "Sponsoring codebar Stories offers you a unique opportunity to connect with a diverse, engaged audience within the tech community. As a podcast dedicated to empowering underrepresented groups through coding education, your brand will align with our values of diversity, inclusivity, and social impact. Through sponsorship, you'll gain visibility, build positive PR, and demonstrate your commitment to fostering the next generation of tech talent, all while supporting a meaningful cause. Sound good? Please drop us an email podcast@codebar.io." - - admin: - dashboard: - title: 'Admin' - workshop: - manage_rsvps: - text: 'RSVP Students and Coaches to the workshop. The attendance confirmation email will be triggered and they will be removed from the waiting list.' - destroy: - success: "Workshop deleted successfully" - failure: "Workshop cannot be deleted. This is because it has invitees and/or workshop information is on the website for a while long enough that it cannot be deleted." - messages: - meeting: - created: 'Meeting successfully created' - updated: 'You have successfully updated the details of this meeting' - invitations_already_sent: 'Invitations were previously sent; they will not be sent again' - sending_invitations: 'Invitations are being sent out' - invitation: - rsvp_member: "%{name} has been successfully added and notified via email." - already_on_list: "%{name} is already on the list!" - rsvp_error: "Something went wrong, %{name} has not been added." - update_rsvp: 'Updated attendance of %{name}' - simple_form: - placeholders: - job: - company: 'e.g. codebar' - company_website: 'e.g. https://codebar.io' - title: 'e.g. Internship' - description: 'Use text or markdown for the job description' - location: 'e.g. London or Berlin' - hints: - job: - remote: Only check if the role is fully remote only - salary: Annual pay before tax, without commas or decimal points - activerecord: - attributes: - job: - title: Title - company: Name - company_address: Address - company_postcode: Postcode - company_website: Website - email: Contact email - link_to_job: Link to job post - expiry_date: Application closing date - donation_platforms: - title: "Donate" - description: "Your support—whether through a one-time gift or ongoing commitment—drives our mission to create a more inclusive tech industry. It enables us to provide continuous learning opportunities and empower individuals from underrepresented groups to grow and thrive in tech." - link: "Find out how else to support us" - donation_form: - title: "Use the donation page" - text: "Make a lasting impact with codebar by giving a one-time donation or committing to a monthly contribution." - image_alt: "codebar logo" - github_sponsors: - title: "Github Sponsors" - text: "Support codebar’s mission directly through GitHub Sponsors and help shape the future of technology with your generous donation." - image_alt: "Github Sponsors logo" - open_collective: - title: "Open Collective" - text: "Setup a recurring contribution or make a one-time donation through Open Collective." - image_alt: "Open Collective logo" - give_as_you_live: - title: "Give as you Live" - text: "Give as you Live is a platform enabling you to raise funds for your favourite charity with your everyday online shopping." - image_alt: "Give as you Live logo" diff --git a/config/locales/en_GB.yml b/config/locales/en_GB.yml deleted file mode 100644 index 9dd982b55..000000000 --- a/config/locales/en_GB.yml +++ /dev/null @@ -1,553 +0,0 @@ -en-GB: - brand: "codebar.io" - date: - formats: - default: "%d/%m/%Y" - email: "%a, %d %B at %H:%M" - email_title: "%A, %d %b at %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - website_format: "%a, %d %B %Y at %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y at %R" - dashboard: "%a, %d %b %Y, %H:%M" - time: - formats: - default: "%a, %d %b %Y %H:%M" - email: "%a, %d %B at %H:%M" - email_title: "%A, %d %b at %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - full_date: "%d %B %Y" - default_date: "%d/%m/%Y" - website_format: "%a, %d %B %Y at %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y at %R" - dashboard: "%A, %b %d" - number: - currency: - format: - unit: '£' - delimiter: ',' - separator: '.' - precision: 0 - format: '%u%n' - homepage: - intro: "codebar is a charity that facilitates the growth of a diverse tech community by running free regular programming workshops for underrepresented groups in tech." - explanation: "Our goal is to enable people from underrepresented groups to learn programming in a safe and collaborative environment and expand their career opportunities. To achieve this we run free regular workshops, regular one-off events and try to create opportunities for our students making technology and coding more accessible." - participate: - students_title: "Students" - students_explanation_p1: "Our students come from diverse backgrounds—some aspiring to become full-time developers, while others simply want to learn the basics of coding in a supportive environment." - students_explanation_p2: "Join our vibrant community and take part in our workshops!" - students_button: "Join us as a student" - coaches_title: "Coaches" - coaches_explanation_p1: "We encourage new students to start with our tutorials on HTML/CSS, JavaScript, Ruby, Python, or Git, while also helping them grasp key programming concepts." - coaches_explanation_p2: "That’s why we’re always looking for more developers to join our community and coach at our workshops." - coaches_button: "Join us as a coach" - workshop_title: "Workshops" - workshop_explanation_p1: "We’re proud to be hosted by amazing companies that support our mission. Our typical format includes 30 minutes of socialising over food and drinks, a lightning talk, and then hands-on coding." - workshop_explanation_p2: "Help us grow and support our chapters by hosting or sponsoring our workshops, and together, we can expand opportunities for more aspiring developers." - workshop_button: "Let's work together" - workshop_email_subject: "Regarding hosting a workshop" - chapters: - title: "Chapters" - events: - upcoming: "Upcoming Events" - donation_platforms: - title: "How to support us" - mailer: - workshop_invitation: - attending: - subject: "Attendance Confirmation for %{date_time}" - attending_reminder: - subject: "Workshop Reminder %{date_time}" - invite_coach: - subject: "Workshop Coach Invitation %{date_time}" - invite_student: - subject: "Workshop Invitation %{date_time}" - notify_waiting_list: - subject: "A spot just became available" - waiting_list_reminder: - subject: "Reminder: you're on the codebar waiting list (%{date_time})" - messages: - accepted_invitation: "Thanks for getting back to us %{name}. See you at the workshop!" - already_invited: 'You have already RSVPd or joined the waitlist for this workshop.' - error_blank_note: 'You must select a note' - rejected_invitation: "We are so sad you can't make it, but thanks for letting us know %{name}." - already_rsvped: "You have already confirmed your attendance!" - not_attending_already: "You have already confirmed you can't make it!" - no_available_seats: "Unfortunately there are no more spaces left :(. If you would like to join our waiting list send us an email at %{email}" - feedback_saved: "Thank you for taking the time to give us feedback!" - feedback_not_found: "You have already submitted feedback for this event." - updated_note: "Successfully updated note." - invalid_session: 'Your session is invalid' - invitations: - meeting: - cancel: "Thanks for letting us know you can't make it." - rsvp: "Your RSVP was successful. We look forward to seeing you at the Monthly!" - rsvped_to_other_workshop: "You have already RSVP'd to another workshop on this date. If you would prefer to attend this workshop, please cancel your other RSVP first." - spot_confirmed: "Your spot has been confirmed for %{event}! We look forward to seeing you there." - spot_not_confirmed: 'Your spot has not yet been confirmed. We will verify your attendance after you complete the questionnaire.' - notifications: - provider_already_connected: 'You are already signed in!' - not_logged_in: "You must be logged in to access this page." - navigation: - dashboard: "Dashboard" - code_of_conduct: "Code of Conduct" - breach_code_of_conduct: "Breach Code of Conduct" - coach_guide: "Coach Guide" - student_guide: "Student Guide" - tutorials: "Tutorials" - becoming_sponsor: "Becoming a Sponsor" - faq: "FAQ" - blog: "Blog" - codebar_stories: "codebar Stories" - stats: "Stats" - dashboard: - join_workshops_in: "Join our free workshops in" - workshops_goal: "to get to grips with the basics of programming and web development." - tweets_by: "Tweets by" - latest_sponsors: "Latest Sponsors" - policy: - intro: "There’s high demand for our workshops and we have a waiting list on most weeks. To make sure as many people as possible can come, we have a straightforward attendance policy." - rule1: "Before you RSVP make sure you are eligible to attend. If you’re not sure get in touch for a chat." - rule2: "You must sign up and RSVP to attend our workshops." - rule3: "If you RSVP then later realise you can’t make it, you must cancel. It only takes a few seconds to do through your confirmation email." - rule4: "Please try to cancel with at least 24 hours notice." - rule5: "We know that sometimes things come up last minute, but even if you only cancel an hour before the workshop, get in touch and let us know." - what_happens: "What happens if I don’t respect the policy?" - strikes_system: "We operate a three strikes system. That means if you don’t come in without cancelling an RSVP three times, we will take you off our invite list for four weeks. We’ll get in touch after your first absence to make sure you understand this." - removing: "If you fail to attend without cancelling another three times, we might have to remove you permanently from our invitation list." - rsvping: "There is no penalty for RSVP-ing and then cancelling on a regular basis, but please avoid it. If you always struggle to make it in on a certain day then let us know – this kind of feedback is really important to us." - eligibility_note: "Another note on eligibility" - abuse: "We’re a fairly relaxed bunch and we trust you, so we don’t police students as to their eligibility. However if it ever looks like this is being abused we may have to change that – which we really don’t want to do." - reminder: "So please remember what these workshops are for – to open up tech to people that are underrepresented in the industry." - teacher_guide: - laptop: "You don't need a laptop for our workshops. You are there to watch and guide the students. You shouldn't teach any tutorials that you don't feel comfortable with." - keyboard: "Do not take over the keyboard! This can be off-putting and scary." - typing: "Encourage the students to type and not copy and paste." - questions: "Explain that there are no bad questions." - mistakes: "Explain to students that it's OK to make mistakes." - introduction: "Always introduce yourself. Say why you want to help out and are spending your own time on this, and why you like programming." - backgrounds: "Give your students the opportunity to get to know each other. Ask their names, why they are here, what they do in their day jobs. Encourage a brief discussion before starting." - limits: "Assume that anyone you're teaching has no knowledge but infinite intelligence." - collaboration: "Work collaboratively with your student. If you have two students, you should work with both. Don't focus all of your attention on one." - discussion: "Let students have a go at answering the questions first. Help with open and leading questions. Encourage a discussion." - talk_slow: "Take it slow, you are the teacher, they are the student. Allow for time between questions." - mild_approach: "Don't say no when the students are not doing something right. Be gentle, take a mild approach." - paper: "Use pen and paper or go to a whiteboard! Often students are coming from a non-technical background. Drawing and explaining with visual material is really helpful." - stubling: "Let them stumble. We learn by making mistakes, getting frustrated, and working through problems in our own ways. Be supportive, but let them explore." - suggestions: "Do you have something to suggest? Make a pull request or create an issue" - workshops: - already_wish_to_attend: 'You have already RSVPd or joined the waitlist for this workshop.' - lead: "Attend our workshops to learn programming in a safe and supportive environment at your own pace, or to share your knowledge and coach our students." - registration_not_open: 'This workshop is not open for registrations' - events: - title: "Events" - past: "Past" - no_upcoming_events: "There are no upcoming events." - view_past_events: "View past events" - view_all: "View all" - hosted_by: "Hosted by" - organisers: "Organisers" - venue_at: "at" - attend_as_student: "Attend as a student" - attend_as_coach: "Attend as a coach" - location: "Location" - sponsors: "Sponsors" - thx_to_sponsors: "A big thanks to all of our sponsors for making the event possible!" - coaches: "Coaches" - students: Students - schedule: "Schedule" - send_us_an_email: "send us an email" - not_open_for_rsvp: This event is not open for RSVP yet. - virtual: This is a virtual event. - faq: - experience: - q: "How experienced should I be to join the workshop?" - a: - contribution: - q: "What kind of contributions can I make?" - a: "Your contributions can be tiny, as simple as fixing a typo, to something incredible. You can help with documentation, fix a bug that you found, improve the copy, help with design or even tackle bigger tasks and help introduce new features. Every little helps!" - laptop: - q: "Do I need to bring a laptop?" - a_html: "Yes, you should bring a laptop. If you don't have one %{link} as we may be able to help." - keyboard: - q: "Do I need to bring a keyboard?" - a_html: "A keyboard would help as you will spend the entire day pairing with someone on your laptop. If you don't have a keyboard, %{link} and we'll try to organise something for you." - travel_costs: - q: "I will be commuting. Can you help with my travel expenses?" - a: "We will be offering some travel grants. Just make sure you fill in the questionnaire after you RSVP and we will get in touch." - coaches: - want_to_coach: "Do you want to coach at our workshops?" - read_before: "If you have not attended our workshops before, make sure you read our" - code_of_conduct: "code of conduct" - policy: "as we have a zero tolerance policy and expect everyone to behave appropriately. You should also go through our" - guide: "coaching guide" - unable_attend: "In case you are unable to attend after you RSVP, please make sure you come back and update your attendance as we rely on coaches showing up in order for our workshops to run smoothly." - food: "PS: There will also be food at the workshop. We always make an effort to have vegetarian, vegan and gluten-free options available. If you have any other dietary requirements, send us email at" - code_of_conduct: - title: "Code of conduct" - summary: - title: "The Quick Version" - intro: "Our events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of our members in any form. Sexual language and imagery is not appropriate for any of our events, including talks, workshops, parties, and online media. Members violating these rules may be sanctioned or expelled from the event and any future events at the discretion of the organisers." - content: - title: "The Long Version" - harassment: "Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention." - comply: "We expect any participants asked to stop any harassing behaviour to comply immediately." - sponsors: "Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment." - sanctions: "If a participant engages in harassing behaviour the organisers may take any action they deem appropriate. This includes warning the offender or expulsion." - concerns: "If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact one of the organisers immediately." - applies_to: "We expect participants to follow these rules at all codebar events. If they fail to do so, the following process will take place." - questions: "If you have any questions or concerns about this code please" - contact: "contact us" - email_subject: "Regarding code of conduct" - sponsors: - sponsoring: "Sponsoring" - members: - sign_up: "Join our community" - sign_in_with_github: "Sign in with GitHub" - sign_up_as_student: "Join us as a student" - sign_up_as_student_disclaimer: "* I understand and meet the eligibility criteria." - sign_up_as_coach: "Join us as a coach" - code_of_conduct: "code of conduct" - new: - intro_html: "We provide a welcoming, inclusive, and supportive learning environment, with a strict zero-tolerance policy for any form of harassment or inappropriate behavior. Please take a moment to review our code of conduct before signing up." - students: - intro_html: "If you’re interested in attending as a student, be sure to check our eligibility criteria. Our workshops and events are exclusively for women, non-binary, LGBTQ+ members, and people from underrepresented groups." - github: "When you click the sign-up button, you'll be redirected to GitHub. After logging in with your GitHub account, you'll return to the codebar website. If you don’t have an account yet, creating one is quick and easy—and it will be useful as you begin your coding journey!" - invitations: "Invitations are sent out periodically, so don't worry if you don't receive one as soon as you register." - footer: - email_us: "Send us an email at" - contact_info: "Contact Info:" - faq: - payment: - q: "Do I need to pay to attend codebar?" - a_p1: "Absolutely not! We are lucky enough to have some great companies who are able to host the workshops and/or kindly provide food. And our" - awesome_coaches: "awesome coaches" - a_p2: "give their time freely to help the community." - technologies: - q: "What technologies do you teach?" - a: "We have a variety of available tutorials in HTML, CSS, JavaScript and Ruby. If you want to learn something else don't hesitate to send us an email as we might still be able to find someone to help you out." - eligibility: - q: "I want to attend a workshop. Am I eligible?" - a: "Our workshops are available to women, LGBTQ and people who are underrepresented in the tech industry. If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School London where you can learn in a collaborative environment. Please see our student guide for more information." - career: - q: "Is codebar only aimed at people who want to move into a career as a developer?" - a: "No! codebar is about getting people excited about programming. We'll help them learn some basic coding skills, as well as how to explore and do things on their own. For those who do want to become developers, we will provide help and guidance to help them achieve their goal." - format: - q: "What is the format of the workshops?" - a: "We try to have one coach for every two students. We will pair up students who want to work on the same tutorial, and assign them a coach. The rest just happens." - laptop: - q: "Do I need to bring a laptop with me at the workshops?" - a: "Yes, we suggest that you bring a laptop as it will be easier for you to carry on working on things after the workshops. It you don't have one, send us an email so we can try and help out." - online_resources: - q: "There are so many online resources, why should I come to codebar?" - a: "Coding can be intimidating and a lot of people find it hard to get started. By putting you in touch with people who can help and guide you we make the experience and learning process easier and more enjoyable." - preperations: - q: "I would like to coach at codebar. Is there anything I should do besides signing up?" - a_p1: "Yes. First you should read our" - coaching_guide_tutorials: "coaching guide tutorials" - a_p2: ". Then spend sometime familiarising yourself with the" - a_p3: "tutorials. The tutorials are open source so if there is something that you want to improve open an issue on the GitHub repository or send a pull request." - a_p4: "We don't expect the coaches to be familiar with all the technologies and languages we have material on." - location: - q: "Where do the workshops take place?" - a: "As we don't have a permanent venue, our workshops are hosted by different companies in various locations around London. So far we've run workshops in Shoreditch, London Bridge, Holborn and Kings Cross." - disabled_access: - q: "Is there disabled access at the workshops?" - a: "Unfortunately, that depends entirely on where we are hosting our workshops and if the venue has disabled access. If you would like to attend, send us an email at meetings[at]codebar.io so we can enquire about it and let you know." - bring_codebar_to_my_city: - q: "I would like to bring codebar to my city. Can I do that?" - a: "Of course. codebar is about building a community of experienced developers that are able to give up some of their time to help others. If you are keen on running codebar where you live, we would love to speak to you about it and see how we can help make this happen, so send us an email." - our_coaches: - q: "Our coaches" - a_p1: "You can see all the coaches have helped out in our workshops on the" - a_p2: ". They are ordered by number of attendances. This is our way of showing our appreciation to them, as without them, we wouldn't be able to exist." - participant_student_guide: - title: "Student Guide" - attendance_policy: - title: "Attendance Policy" - intro: "codebar is, and always has been, open to all levels of coding experience. While most of the tutorials on our website are aimed at newcomers to web development, we intend to continue our open-door policy for any student who needs coach support on their own projects. Due to the fact that our workshops are frequently oversubscribed, we ask students to respect the following expectations for participation in our workshops:" - rule1: "In order to attend a event, you must be on the RSVP list. If you have not RSVP’d or were not allocated a spot, you will not be admitted into an event." - rule2: "If you can no longer attend an event, please cancel your RSVP by 12:00 latest on the day of the event. We understand that last-minute emergencies occur -- if this is the case, please get in touch with an organiser directly as soon as possible. Repeated no-shows will result in temporary or permanent suspension of your invitations." - rule3: "No guests are allowed. Our events are already overcrowded and we cannot make any exceptions. If your friend meets our eligibility criteria and wants to attend, ask them to sign up and RSVP themselves." - rule4: "Please be respectful to our hosts. Do not show up exceedingly early to an event (not earlier than 15 minutes before the event start time) and try to leave the workstation clean and as you found it." - rule5: "Please do not work on projects that were assigned as part of any bootcamp or university curriculum. Talk to your course adviser if you feel like you need additional support with your coursework. We welcome your attendance, but we encourage you to use your time at codebar to develop skills that are outside the normal scope of your studies." - rule6: "Do not bring along and ask for help with any commercial work. This involves work you're being paid to do." - rule7: "Projects that involve specific frameworks/libraries (Rails, NodeJS, Meteor, Angular, Ember, React, etc) or languages that are not part of the codebar tutorials (anything other than Ruby or Javascript) are welcome, but we cannot guarantee that a coach will be available to help you. In these cases we recommend selecting a codebar tutorial or katas (codewars.com or exercism.io) as a back-up option." - eligibility_criteria: - title: "Eligibility Criteria" - p_1: "codebar was started out of recognition that there is a shortage of women, non-binary, LGBTQ, and people belonging to underrepresented ethnic groups in tech." - p_2: "If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School or Ask a Dev where you can learn in a collaborative environment." - p_3: "Bearing that in mind, it is sometimes difficult for us to identify whether attendees meet the eligibility criteria based on their first and last names. If we cannot determine your eligibility, we will contact you asking for a short confirmation that you have read this page and assert that you meet one or more of the criteria. We will never ask participants to specify which group." - p_4: "codebar is first and foremost a resource for students who cannot afford formal training through coding bootcamps or university degrees, for financial reasons or otherwise. Our coaches, organisers and sponsors donate their time and money to help those who have faced unfair barriers to entry into the tech world. We have strived to create an inclusive, welcoming community, and so far, we have not had to implement a formal policy to enforce the eligibility criteria -- we have left this to the honesty and good faith of the students." - p_5: "If you are unsure of your eligibility, please get in touch. If we determine that you have signed up and are not eligible, we will permanently suspend your student invitations without warning." - p_6: "We take this issue very seriously, and we appreciate your cooperation and understanding." - disability: - title: "Students with Disability" - description: "We want to ensure that our events are as accessible as possible. For each venue we try to get accessibility information, however if you don't see any information on the relevant event page please get in touch with us at hello@codebar.io and we will do what we can to accommodate you." - chapters: - intro_html: "Hi and welcome to codebar!" - info: "Check out our FAQ page for any questions you might have, or email us at %{email} if you can't find the answer you're looking for. Otherwise, click the Join our community button to get started." - sign_up: "to be invited to our workshops." - no_incoming: "There are no workshops coming up." - contact: "To contact the %{city} team, send an email to %{email}" - feedback_form: - title: 'Workshop feedback' - description: Your submission will be completely anonymous. We read every piece of feedback and use it to help us improve our workshops. - note: Please do not mention any names, but instead choose your coach from the dropdown. This enables us to address issues but also to anonymously share feedback with coaches. Member privacy is very important to us! - rating: Your overall rating of the workshop - coach: 'Who was your coach?' - select_coach: '- Select Coach -' - tutorial: 'What tutorial did you go through?' - select_tutorial: '- Select Tutorial -' - request: 'How did you find the workshop?' - suggestions: "Was there something you didn't like? What can we do to improve your experience?" - pages: - cookies: - title: Cookie Policy - p1: 'Cookies are small pieces of text used to store information on web browsers. They are used by websites accross a number of different devices to store and receive identifiers and other information. Our Website and Service use cookies and other similar technologies (collectively in this Policy, "cookies"), in order to provide a better service to you and to generally improve our Website and Service. For example, we may use cookies to help direct you to the appropriate part of our Website, by indicating that you are a repeat visitor. We also may use information to present you with services that are matched to your preferences and to manage and track the effectiveness of our marketing efforts.' - p2: Some portions of the codebar website are functional without cookies, and you may generally choose whether to accept cookies. Most web browsers are set to accept cookies by default, however, you may be able to delete cookies yourself through your browser's cookie manager. To do so, please follow the instructions provided by your web browser. Please note that disabling cookies will reset your session, disable auto-login, and may adversely affect the availability and functionality of our Website and the services we can provide to you. - sub: - title: Below are the cookies used by the codebar website. - table: - header: - h1: Name - h2: Purpose - h3: Expires - functional: - title: Functional Cookies - description: Stores information about your session. - planner_name: _planner_session - planner_purpose: Stores session data - planner_expiry: Expires after 24 hours - google_analytics: - title: Google Analytics - description: Google Analytics collects information about how you use the codebar website. This enables us to identify how busy the website is and possible improvements. - info: We don’t allow Google to use or share our analytics data. - opt_out: You can [opt out of Google Analytics](https://tools.google.com/dlpage/gaoptout). - ga_name: _ga - ga_purpose: Tracks if you have visited codebar.io before - ga_expiry: After 2 years - gid_name: _ga - gid_purpose: Tracks if you have visited codebar.io before - gid_expiry: After 24 hours - cloudflare: - title: Cloudflare - cfduid_name: _pfduid - cfduid_purpose: Used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. - cfduid_expiry: 1 year - privacy_policy: - title: Privacy Policy - subtitle: This Privacy Policy was last updated on 13 May 2021. - intro: - p1: 'This Privacy Policy has been created by codebar ("codebar", "we", "us", or "our") whose companies house registered name and address is as follows:' - address_html: " - codebar Ltd,
- International House,
- 101 King's Cross Road,
- London, England,
- WC1X 9LP
- Company No. 10791813
" - p2: codebar Ltd trades on behalf of the charity registered UK and Wales no. 1187776. For the purpose of this Privacy Policy codebar Ltd is the data controller. - p3: Your privacy means a lot to us, and we take it very seriously. We aim to be transparent with you about the data we collect about you and how it is used and shared. This Privacy Policy lets you know what information we collect when you use the codebar website, https://codebar.io/, or interact with any of the services we provide, such as signing up to workshops and events ("Services"). By using our Services you acknowledge and understand our use of your data under this Privacy Policy and how it applies to your use of our Services. - information: - title: 1. Information we collect - what_we_collect: - title: 1.1 Personal data we collect from you - p1: 'We have set out in the table below the personal data we collect about you and how we use it, which will differ based on the capacity in which you interact with codebar:' - table: - headers: - h1: Who - h2: What data we process - h3: What we use it for - h4: Lawful basis - r1: - c1: Students - c2: This includes personal data that is provided by you or collected by us to enable you to subscribe to codebar as a student. This may include your name, email address, phone number, pronouns, self-written bio, , your self-recognition as being underrepresented (with your consent), and the location you choose to subscribe to. - c3: For administrative purposes when you sign up to events, to communicate with you, and to provide you with our newsletters and events information. - c4: - l1: Performance of a contract - l2: Consent - l3: Legitimate interests - r2: - c1: Coaches - c2: This includes personal data that is provided by you or collected by us to enable you to volunteer at codebar as a coach. This may include your name, email address, phone number, pronouns, self-written bio/skills, , your self-recognition as being underrepresented (with your consent), and the location you choose to volunteer at. - c3: For administrative purposes when you volunteer for workshops, to communicate with you, to manage workshop attendance, and to provide you with our newsletters and events information. - c4: - l1: Consent - l2: Legitimate interests - r3: - c1: Organizers - c2: This includes personal data that is provided by you or collected by us, which may include your name, email address, phone number, pronouns, self-written bio/skills, , slack username, signed documentation, and the location you choose to volunteer at. - c3: To organise and communicate workshops. - c4: - l1: Legitimate interests - r4: - c1: Hosts - c2: We may collect personal information of employees working at companies that agree to host our workshops. This information may include the employees' name, email address, contact number, , and place of work. - c3: In order to market, promote, host and operate workshops. - c4: - l1: Legitimate interests - r5: - c1: Sponsors - c2: We need to collect personal data in relation to your sponsorship of codebar. This may include information such as your name, and bank details. - c3: To fulfill contractual obligations we have with you, for example, to process invoices related to your sponsorship. - c4: - l1: Performance of a contract - l2: Legitimate interests - r6: - c1: Trustees and directors - c2: We need to collect personal data in relation to your position as trustee and/or director. This may include information such as your name, contact number, address, email address, and date of birth. - c3: In order to establish our status as a charity, to comply with legal obligations, and respond to legal requests. - c4: - l1: Legitimate interests - l2: Compliance with legal obligations - how_we_share: - title: 1.2 How we share your information - p1_html: 'When you subscribe to an event, we share your name with our host companies as we are required to provide a list with all attendee names when you subscribe to any of our events. We **do not share** your email address or any other personal information.' - legal_basis: - title: 1.3 Legal basis for our use of your personal information - p1: As set out in the table above, sometimes the legal basis on which we collect and process your data is because our legitimate interests make the processing necessary, and those legitimate interests are not overridden by your interests or fundamental rights and freedoms. For example, we collect and store your data in order to process event information, and to ensure the efficient running and promotion of workshops. - retention: - title: 2. Retention - p1: We will keep your personal information for as long as reasonably necessary to fulfil the purposes we collected it for. To determine the appropriate retention period, we consider the amount, nature and sensitivity of the personal information, the potential risk of harm from unauthorised use or disclosure of your personal information, the purposes for which we process your personal data and whether we can achieve those purposes through other means, and the applicable legal, regulatory, tax, accounting or other requirements. - p2: We may retain your personal information for a longer period in the event of a complaint or if we reasonably believe there is a prospect of dispute in respect to our relationship with you. - international_transfers: - title: 3. International transfers - p1: Personal information we collect may be transferred to and stored in countries outside of the jurisdiction you are in for the purposes specified in this Privacy Policy. We will only transfer your personal information to countries that have been deemed to provide an adequate level of protection for personal information, and/or any international transfers will be made pursuant to appropriate safeguards in accordance with the applicable laws and regulations, such as standard data protection clauses adopted by the UK and European Commission. - p2: If you wish to enquire further about these safeguards used, please contact us by email at the address below or by mail using the postal address provided below. - your_rights: - title: 4. Your data protection rights - p1: 'Data protection law provides you with rights in respect of personal data that we hold about you, including the:' - l1: 'Right to Access: You have the right to obtain access to your data, and certain other information (similar to that provided in this Privacy Policy).' - l2: 'Right to Rectification: You are entitled to have your data corrected if it is inaccurate or incomplete.' - l3: 'Right to Erasure: This enables you in some circumstances to request and obtain the deletion of your data where there is no legal reason for us to keep using it.' - l4: 'Right to Restriction of Processing: You have rights to suspend further use of your data, whereby we can still store your data but cannot use it further. This may mean we can no longer provide you with Services.' - l5: 'Right to Data Portability: You have rights in some circumstances to request the transfer of your data to yourself or to a third party.' - l6: 'Right to Objection: You have the right to object to certain types of data processing, including for direct marketing purposes.' - l7: 'Right to Withdrawal of Consent: Where we are relying on consent to process your data, you have the right to withdraw your consent at any time by using any opt-out links, or by contacting us at the details provided below (although if you do so, it does not mean that anything we have done with your data with your consent up to that point is unlawful and we may be able to continue to process your personal information to the extent required or otherwise permitted by law, in particular in connection with exercising and defending our legal rights or meeting our legal and regulatory obligations).' - l8: 'Right to Lodge a Complaint: You can lodge a complaint in relation to our use of your personal information with the local supervisory authority, the Information Commissioner (UK).' - p2: If you would like to exercise any of these rights or if you have a complaint about how we handle your data, please contact us at the email address stated below. - security: - title: 5. Security - p1: The security of your personal information is important to us. codebar takes reasonable steps to implement and update administrative, technical, and physical security measures to help protect your information against unauthorised access, loss, destruction, or alteration. However, the Internet is not a 100% secure environment so we can't guarantee the security of the transmission or storage of your information. codebar has no control over or responsibility for the security or practices or privacy policies of third parties, even if you interact with them when using our Services. - changes: - title: 6. Changes to this Privacy Policy - p1: We reserve the right to modify or update this Privacy Policy at any time in accordance with this provision. If we make changes to this Privacy Policy, we will post the revised Privacy Policy on the codebar website. Please regularly review https://codebar.io/privacy-policy to check for any updates or changes to our Privacy Policy. The date this Privacy Policy was last revised is identified at the top of this page. - cookies: - title: 7. Cookies - p1_html: 'We use cookies to recognise you and your location. You can control cookies through your browser settings and other tools. For more information read our [cookie policy](https://codebar.io/cookie-policy).' - contact: - title: 8. Contact - p1: "If you have any questions or complaints about this Privacy Policy or our information handling practices, you may email us at company@codebar.io stating 'Data inquiry' in the subject title, or by postal mail at: codebar Ltd, International House, 101 King's Cross Road, London, WC1X 9LP." - breach: - title: What happens if you violate codebar’s Code of Conduct? - opening_para: All codebar events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment towards any community member or organiser in any form. Harassment includes any type of aggressive behaviour or offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. - second_para: The Code of Conduct is in place to protect every codebar member - students, coaches and organisers. If any member violates these rules the below procedure and sanctions will be implemented. - outcome_title: 3 types of outcomes - correction: Correction - The use of inappropriate language or other behavior deemed unprofessional or unwelcome in the codebar community. This includes the use of terminology that is discouraged, e.g. 'guys'. In this situation you will be sent a private message, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. - warning: Warning - You will receive an email warning. The organiser will explain the incident, including the impact on the person involved and the community. We will give as much information as possible, so you’re aware of what happened and try to learn from the incident. The organiser will add a note to your codebar profile so that all chapter organisers are aware of the incident. We expect you to take our comments on board, further action may be taken depending on your reaction. Examples of behaviour that will get you a warning include - targeted offensive language, or the sharing of sexual images in codebar spaces. 2 email warnings will result in a lifetime ban. - lifetime_ban: Lifetime ban - You will no longer be able to RSVP to any future codebar events. You will also be removed from codebar’s Slack workspace. Examples of behaviour that will get you an automatic lifetime ban include - physical intimidation, stalking, inappropriate physical contact, unwelcome sexual attention or repeated behaviour after you’ve been spoken to by someone from the codebar team (directors or chapter organisers). - closing_para: The above is only a starting point. The details of the incident may change how we view it, e.g. some verbal harassment may be so serious that we would give a lifetime ban. - how_to_support_us: - volunteer: - title: Volunteer with us - become_an_organiser: - title: Become an organiser - description: Champion inclusion and diversity in the tech industry as a workshop organiser with codebar. Your contribution will create an empowering and safe environment, fostering learning and collaboration among individuals exploring coding in our vibrant community. - link: Email us to become an organiser - become_a_coach: - title: Become a coach - description: Affect change as a volunteer coach with codebar - your expertise and guidance will pave the way for aspiring developers, unlocking the world of coding and creating opportunities for folks from groups under represented in the tech industry. - volunteer: - title: Other skills - description: Your unique abilities could be our missing piece in the codebar puzzle. Having a diverse range of skills in our team is necessary to enrich our community. From fundraising to event coordination to marketing, we always welcome new talent to drive our mission forward. - link: Email us to become a volunteer - fundraise: - title: Fundraise - description_html: "Join the codebar team with a physical challenge event. Whether you are a runner, swimmer, or cyclist, sign up with our registration form for your desired event and raise vital funds to help keep our events running. If your event does not appear below, feel free to drop us an email and we would be happy to coordinate with you." - image_alt: A Black British woman crosses the finish line at the Hackney Half Marathon in London in a shower of confetti while spectators cheer her on. - codebar_stories_podcast: - image_alt: codebar stories banner - opening: codebar Stories is a new podcast brought to you by codebar, we'll be smashing down the belief that tech isn't for you by sharing real-life stories from members of our community who have transitioned into a new career in tech. - contact_us_html: "Sponsoring codebar Stories offers you a unique opportunity to connect with a diverse, engaged audience within the tech community. As a podcast dedicated to empowering underrepresented groups through coding education, your brand will align with our values of diversity, inclusivity, and social impact. Through sponsorship, you'll gain visibility, build positive PR, and demonstrate your commitment to fostering the next generation of tech talent, all while supporting a meaningful cause. Sound good? Please drop us an email podcast@codebar.io." - - admin: - dashboard: - title: 'Admin' - workshop: - manage_rsvps: - text: 'RSVP Students and Coaches to the workshop. The attendance confirmation email will be triggered and they will be removed from the waiting list.' - destroy: - success: "Workshop deleted successfully" - failure: "Workshop cannot be deleted. This is because it has invitees and/or workshop information is on the website for a while long enough that it cannot be deleted." - messages: - meeting: - created: 'Meeting successfully created' - updated: 'You have successfully updated the details of this meeting' - invitations_already_sent: 'Invitations were previously sent; they will not be sent again' - sending_invitations: 'Invitations are being sent out' - invitation: - rsvp_member: "%{name} has been successfully added and notified via email." - already_on_list: "%{name} is already on the list!" - rsvp_error: "Something went wrong, %{name} has not been added." - update_rsvp: 'Updated attendance of %{name}' - simple_form: - placeholders: - job: - company: 'e.g. codebar' - company_website: 'e.g. https://codebar.io' - title: 'e.g. Internship' - description: 'Use text or markdown for the job description' - location: 'e.g. London or Berlin' - hints: - job: - remote: Only check if the role is fully remote only - salary: Annual pay before tax, without commas or decimal points - activerecord: - attributes: - job: - title: Title - company: Name - company_address: Address - company_postcode: Postcode - company_website: Website - email: Contact email - link_to_job: Link to job post - expiry_date: Application closing date - donation_platforms: - title: "Donate" - description: "Your support—whether through a one-time gift or ongoing commitment—drives our mission to create a more inclusive tech industry. It enables us to provide continuous learning opportunities and empower individuals from underrepresented groups to grow and thrive in tech." - link: "Find out how else to support us" - donation_form: - title: "Use the donation page" - text: "Make a lasting impact with codebar by giving a one-time donation or committing to a monthly contribution." - image_alt: "codebar logo" - github_sponsors: - title: "Github Sponsors" - text: "Support codebar’s mission directly through GitHub Sponsors and help shape the future of technology with your generous donation." - image_alt: "Github Sponsors logo" - open_collective: - title: "Open Collective" - text: "Setup a recurring contribution or make a one-time donation through Open Collective." - image_alt: "Open Collective logo" - give_as_you_live: - title: "Give as you Live" - text: "Give as you Live is a platform enabling you to raise funds for your favourite charity with your everyday online shopping." - image_alt: "Give as you Live logo" diff --git a/config/locales/en_US.yml b/config/locales/en_US.yml deleted file mode 100644 index 5063d0dbf..000000000 --- a/config/locales/en_US.yml +++ /dev/null @@ -1,551 +0,0 @@ -en-US: - brand: "codebar.io" - date: - formats: - default: "%d/%m/%Y" - email: "%a, %d %B at %H:%M" - email_title: "%A, %d %b at %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - website_format: "%a, %d %B %Y at %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y at %R" - dashboard: "%a, %d %b %Y, %H:%M" - time: - formats: - default: "%a, %d %b %Y %H:%M" - email: "%a, %d %B at %H:%M" - email_title: "%A, %d %b at %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - full_date: "%d %B %Y" - default_date: "%d/%m/%Y" - website_format: "%a, %d %B %Y at %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y at %R" - dashboard: "%A, %b %d" - number: - currency: - format: - unit: '£' - delimiter: ',' - separator: '.' - precision: 0 - format: '%u%n' - homepage: - intro: "codebar is a charity that facilitates the growth of a diverse tech community by running free regular programming workshops for minority groups in tech." - explanation: "Our goal is to enable people from underrepresented groups to learn programming in a safe and collaborative environment and expand their career opportunities. To achieve this we run free regular workshops, regular one-off events and try to create opportunities for our students making technology and coding more accessible." - participate: - students_title: "Students" - students_explanation_p1: "Our students come from diverse backgrounds—some aspiring to become full-time developers, while others simply want to learn the basics of coding in a supportive environment." - students_explanation_p2: "Join our vibrant community and take part in our workshops!" - students_button: "Join us as a student" - coaches_title: "Coaches" - coaches_explanation_p1: "We encourage new students to start with our tutorials on HTML/CSS, JavaScript, Ruby, Python, or Git, while also helping them grasp key programming concepts." - coaches_explanation_p2: "That’s why we’re always looking for more developers to join our community and coach at our workshops." - coaches_button: "Join us as a coach" - workshop_title: "Workshops" - workshop_explanation_p1: "We’re proud to be hosted by amazing companies that support our mission. Our typical format includes 30 minutes of socialising over food and drinks, a lightning talk, and then hands-on coding." - workshop_explanation_p2: "Help us grow and support our chapters by hosting or sponsoring our workshops, and together, we can expand opportunities for more aspiring developers." - workshop_button: "Let's work together" - workshop_email_subject: "Regarding hosting a workshop" - chapters: - title: "Chapters" - events: - upcoming: "Upcoming Events" - donation_platforms: - title: "How to support us" - mailer: - workshop_invitation: - attending: - subject: "Attendance Confirmation for %{date_time}" - attending_reminder: - subject: "Workshop Reminder %{date_time}" - invite_coach: - subject: "Workshop Coach Invitation %{date_time}" - invite_student: - subject: "Workshop Invitation %{date_time}" - notify_waiting_list: - subject: "A spot just became available" - waiting_list_reminder: - subject: "Reminder: you're on the codebar waiting list (%{date_time})" - messages: - accepted_invitation: "Thanks for getting back to us %{name}. See you at the workshop!" - already_invited: 'You have already RSVPd or joined the waitlist for this workshop.' - error_blank_note: 'You must select a note' - rejected_invitation: "We are so sad you can't make it, but thanks for letting us know %{name}." - already_rsvped: "You have already confirmed your attendance!" - not_attending_already: "You have already confirmed you can't make it!" - no_available_seats: "Unfortunately there are no more spaces left :(. If you would like to join our waiting list send us an email at %{email}" - feedback_saved: "Thank you for taking the time to give us feedback!" - feedback_not_found: "You have already submitted feedback for this event." - updated_note: "Successfully updated note." - invalid_session: 'Your session is invalid' - invitations: - meeting: - cancel: "Thanks for letting us know you can't make it." - rsvp: "Your RSVP was successful. We look forward to seeing you at the Monthly!" - rsvped_to_other_workshop: "You have already RSVP'd to another workshop on this date. If you would prefer to attend this workshop, please cancel your other RSVP first." - spot_confirmed: "Your spot has been confirmed for %{event}! We look forward to seeing you there." - spot_not_confirmed: 'Your spot has not yet been confirmed. We will verify your attendance after you complete the questionnaire.' - notifications: - provider_already_connected: 'You are already signed in!' - not_logged_in: "You must be logged in to access this page." - navigation: - dashboard: "Dashboard" - code_of_conduct: "Code of Conduct" - breach_code_of_conduct: "Breach Code of Conduct" - coach_guide: "Coach Guide" - student_guide: "Student Guide" - tutorials: "Tutorials" - becoming_sponsor: "Becoming a Sponsor" - faq: "FAQ" - blog: "Blog" - codebar_stories: "codebar Stories" - stats: "Stats" - dashboard: - join_workshops_in: "Join our free workshops in" - workshops_goal: "to get to grips with the basics of programming and web development." - tweets_by: "Tweets by" - latest_sponsors: "Latest Sponsors" - policy: - intro: "There’s high demand for our workshops and we have a waiting list on most weeks. To make sure as many people as possible can come, we have a straightforward attendance policy." - rule1: "Before you RSVP make sure you are eligible to attend. If you’re not sure get in touch for a chat." - rule2: "You must sign up and RSVP to attend our workshops." - rule3: "If you RSVP then later realise you can’t make it, you must cancel. It only takes a few seconds to do through your confirmation email." - rule4: "Please try to cancel with at least 24 hours notice." - rule5: "We know that sometimes things come up last minute, but even if you only cancel an hour before the workshop, get in touch and let us know." - what_happens: "What happens if I don’t respect the policy?" - strikes_system: "We operate a three strikes system. That means if you don’t come in without cancelling an RSVP three times, we will take you off our invite list for four weeks. We’ll get in touch after your first absence to make sure you understand this." - removing: "If you fail to attend without cancelling another three times, we might have to remove you permanently from our invitation list." - rsvping: "There is no penalty for RSVP-ing and then cancelling on a regular basis, but please avoid it. If you always struggle to make it in on a certain day then let us know – that kind of feedback is really important to us." - eligibility_note: "Another note on eligibility" - abuse: "We’re a fairly relaxed bunch and we trust you, so we don’t police students as to their eligibility. However if it ever looks like this is being abused we may have to change that – which we really don’t want to do." - reminder: "So please remember what these workshops are for – to open up tech to people that are underrepresented in the industry." - teacher_guide: - laptop: "You don't need a laptop for our workshops. You are there to watch and guide the students. If you don't feel comfortable with the tutorial you should spend time on it before coming if you want to help out." - keyboard: "Do not take over the keyboard! This can be off-putting and scary." - typing: "Encourage the students to type and not copy paste." - questions: "Explain that there are no bad questions." - mistakes: "Explain to students that it's OK to make mistakes." - introduction: "Always introduce yourself. Say why you want to help out and are spending your own time on this, why you like programming." - backgrounds: "Give your students the opportunity to get to know each other. Ask their names, why they are here, what they do in their day jobs. Encourage a brief discussion before starting." - limits: "Assume that anyone you're teaching has no knowledge but infinite intelligence." - collaboration: "Work collaboratively with your student. If you have two students, you should work with both. Don't focus all your attention on one of them." - discussion: "Let students have a go at answering the questions first. Help with open and leading questions. Encourage a discussion." - talk_slow: "Take it slow, you are the teacher, they are the student. Allow for time between questions." - mild_approach: "Don't say no when the students are not doing something right. Be gentle, approach it in a mild way." - paper: "Use pen and paper or go to a whiteboard! Often students are coming from a non-technical background. Drawing and explaining with visual material is really helpful." - stubling: "Let them stumble. We learn by making mistakes, getting frustrated, and working through problem in our own way. Be supportive, but let them explore." - suggestions: "Do you have something to suggest? Make a pull request or create an issue" - workshops: - lead: "Attend our workshops to learn programming in a safe and supportive environment at your own pace, or to share your knowledge and coach our students." - events: - title: "Events" - past: "Past" - no_upcoming_events: "There are no upcoming events." - view_past_events: "View past events" - view_all: "View all" - hosted_by: "Hosted by" - organisers: "Organisers" - venue_at: "at" - attend_as_student: "Attend as a student" - attend_as_coach: "Attend as a coach" - location: "Location" - sponsors: "Sponsors" - thx_to_sponsors: "A big thanks to all of our sponsors for making the event possible!" - coaches: "Coaches" - students: Students - schedule: "Schedule" - send_us_an_email: "send us an email" - not_open_for_rsvp: This event is not open for RSVP yet. - virtual: This is a virtual event. - faq: - experience: - q: "How experienced should I be to join the workshop?" - a: - contribution: - q: "What kind of contributions can I make?" - a: "Your contributions can be tiny, as simple as fixing a typo, to something incredible. You can help with documentation, fix a bug that you found, improve the copy, help with design or even tackle bigger tasks and help introduce new features. Every little helps!" - laptop: - q: "Do I need to bring a laptop?" - a_html: "Yes, you should bring a laptop. If you don't have one %{link} as we may be able to help." - keyboard: - q: "Do I need to bring a keyboard?" - a_html: "A keyboard would help as you will spend the entire day pairing with someone on your laptop. If you don't have a keyboard, %{link} and we'll try to organise something for you." - travel_costs: - q: "I will be commuting. Can you help with my travel expenses?" - a: "We will be offering some travel grants. Just make sure you fill in the questionnaire after you RSVP and we will get in touch." - coaches: - want_to_coach: "Do you want to coach at our workshops?" - read_before: "If you have not attended our workshops before, make sure you read our" - code_of_conduct: "code of conduct" - policy: "as we have a zero tolerance policy and expect everyone to behave appropriately. You should also go through our" - guide: "coaching guide" - unable_attend: "In case you are unable to attend after you RSVP, please make sure you come back and update your attendance as we rely on coaches showing up in order for our workshops to run smoothly." - food: "PS: There will also be food at the workshop. We always make an effort to have vegetarian, vegan and gluten-free options available. If you have any other dietary requirements, send us email at" - code_of_conduct: - title: "Code of conduct" - summary: - title: "The Quick Version" - intro: "Our events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of our members in any form. Sexual language and imagery is not appropriate for any of our events, including talks, workshops, parties, and online media. Members violating these rules may be sanctioned or expelled from the event and any future events at the discretion of the organisers." - content: - title: "The Long Version" - harassment: "Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention." - comply: "We expect any participants asked to stop any harassing behaviour to comply immediately." - sponsors: "Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment." - sanctions: "If a participant engages in harassing behaviour the organisers may take any action they deem appropriate. This includes warning the offender or expulsion." - concerns: "If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact one of the organisers immediately." - applies_to: "We expect participants to follow these rules at all codebar events. If they fail to do so, the following process will take place." - questions: "If you have any questions or concerns about this code please" - contact: "contact us" - email_subject: "Regarding code of conduct" - sponsors: - sponsoring: "Sponsoring" - members: - sign_up: "Join our community" - sign_in_with_github: "Sign in with GitHub" - sign_up_as_student: "Join us as a student" - sign_up_as_student_disclaimer: "* I understand and meet the eligibility criteria." - sign_up_as_coach: "Join us as a coach" - code_of_conduct: "code of conduct" - new: - intro_html: "We provide a welcoming, inclusive, and supportive learning environment, with a strict zero-tolerance policy for any form of harassment or inappropriate behavior. Please take a moment to review our code of conduct before signing up." - students: - intro_html: "If you’re interested in attending as a student, be sure to check our eligibility criteria. Our workshops and events are exclusively for women, non-binary, LGBTQ+ members, and people from underrepresented groups." - github: "When you click the sign-up button, you'll be redirected to GitHub. After logging in with your GitHub account, you'll return to the codebar website. If you don’t have an account yet, creating one is quick and easy—and it will be useful as you begin your coding journey!" - invitations: "Invitations are sent out periodically, so don't worry if you don't receive one as soon as you register." - footer: - email_us: "Send us an email at" - contact_info: "Contact Info:" - faq: - payment: - q: "Do I need to pay to attend codebar?" - a_p1: "Absolutely not! We are lucky enough to have some great companies who are able to host the workshops and/or kindly provide food. And our" - awesome_coaches: "awesome coaches" - a_p2: "give their time freely to help the community." - technologies: - q: "What technologies do you teach?" - a: "We have a variety of available tutorials in HTML, CSS, JavaScript and Ruby. If you want to learn something else don't hesitate to send us an email as we might still be able to find someone to help you out." - eligibility: - q: "I want to attend a workshop. Am I eligible?" - a: "Our workshops are available to women, LGBTQ and people who are underrepresented in the tech industry. If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School London where you can learn in a collaborative environment. Please see our student guide for more information." - career: - q: "Is codebar only aimed at people who want to move into a career as a developer?" - a: "No! codebar is about getting people excited about programming. We'll help them learn some basic coding skills, as well as how to explore and do things on their own. For those who do want to become developers, we will provide help and guidance to help them achieve their goal." - format: - q: "What is the format of the workshops?" - a: "We try to have one coach for every two students. We will pair up students who want to work on the same tutorial, and assign them a coach. The rest just happens." - laptop: - q: "Do I need to bring a laptop with me at the workshops?" - a: "Yes, we suggest that you bring a laptop as it will be easier for you to carry on working on things after the workshops. It you don't have one, send us an email so we can try and help out." - online_resources: - q: "There are so many online resources, why should I come to codebar?" - a: "Coding can be intimidating and a lot of people find it hard to get started. By putting you in touch with people who can help and guide you we make the experience and learning process easier and more enjoyable." - preperations: - q: "I would like to coach at codebar. Is there anything I should do besides signing up?" - a_p1: "Yes. First you should read our" - coaching_guide_tutorials: "coaching guide tutorials" - a_p2: ". Then spend sometime familiarising yourself with the" - a_p3: "tutorials. The tutorials are open source so if there is something that you want to improve open an issue on the GitHub repository or send a pull request." - a_p4: "We don't expect the coaches to be familiar with all the technologies and languages we have material on." - location: - q: "Where do the workshops take place?" - a: "As we don't have a permanent venue, our workshops are hosted by different companies in various locations around London. So far we've run workshops in Shoreditch, London Bridge, Holborn and Kings Cross." - disabled_access: - q: "Is there disabled access at the workshops?" - a: "Unfortunately, that depends entirely on where we are hosting our workshops and if the venue has disabled access. If you would like to attend, send us an email at meetings[at]codebar.io so we can enquire about it and let you know." - bring_codebar_to_my_city: - q: "I would like to bring codebar to my city. Can I do that?" - a: "Of course. codebar is about building a community of experienced developers that are able to give up some of their time to help others. If you are keen on running codebar where you live, we would love to speak to you about it and see how we can help make this happen, so send us an email." - our_coaches: - q: "Our coaches" - a_p1: "You can see all the coaches have helped out in our workshops on the" - a_p2: ". They are ordered by number of attendances. This is our way of showing our appreciation to them, as without them, we wouldn't be able to exist." - participant_student_guide: - title: "Student Guide" - attendance_policy: - title: "Attendance Policy" - intro: "codebar is, and always has been, open to all levels of coding experience. While most of the tutorials on our website are aimed at newcomers to web development, we intend to continue our open-door policy for any student who needs coach support on their own projects. Due to the fact that our workshops are frequently oversubscribed, we ask students to respect the following expectations for participation in our workshops" - rule1: "In order to attend a workshop, you must be on the RSVP list. If you have not RSVP’d or were not allocated a spot, you will not be admitted into a workshop." - rule2: "If you can no longer attend a workshop, please cancel your RSVP by 12:00 latest on the day of the workshop. We understand that last-minute emergencies occur -- if this is the case, please get in touch with an organizer directly as soon as possible. Repeated no-shows will result in temporary or permanent suspension of your invitations." - rule3: "No guests are allowed. Our workshops are already overcrowded and we cannot make any exceptions. If your friend meets our eligibility criteria, get them to sign up and RSVP themselves." - rule4: "Please be respectful of our hosts. Do not show up exceedingly early to a workshop (not earlier than 15 minutes before the event begins) and try to leave the workstation clean and as you found it." - rule5: "Please do not work on projects that were assigned as part of any bootcamp or university curriculum. Talk to your course adviser if you feel like you need additional support with your coursework. We welcome your attendance, but we encourage you to use your time at codebar to develop skills that are outside the normal scope of your studies." - rule6: "Do not bring along and ask for help with any commercial work. This involves work you're being paid to do." - rule7: "Projects that involve specific frameworks/libraries (Rails, NodeJS, Meteor, Angular, Ember, React, etc) or languages that are not part of the codebar tutorials (anything other than Ruby or Javascript) are welcome but we cannot guarantee that a coach will be available to help you. In these cases we recommend selecting a codebar tutorial or katas (codewars.com or exercism.io) as a back-up option." - eligibility_criteria: - title: "Eligibility Criteria" - p_1: "codebar was started out of recognition that there is a shortage of women, LGBTQ, and people belonging to underrepresented ethnic groups in tech." - p_2: "If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School or Ask a Dev where you can learn in a collaborative environment." - p_3: "Bearing that in mind, it is sometimes difficult for us to identify whether attendees meet the eligibility criteria based on their first and last names. If we cannot determine your eligibility, we will contact you asking for a short confirmation that you have read this document and assert that you meet one or more of the criteria. We will never ask participants to specify which group." - p_4: "codebar is first and foremost a resource for students who cannot afford formal training through coding bootcamps or university degrees, for financial reasons or otherwise. Our coaches, organisers and sponsors donate their time and money to help those who have faced unfair barriers to entry into the tech world. We have strived to create an inclusive, welcoming community, and so far, we have not had to implement a formal policy to enforce the eligibility criteria -- we have left this to the honesty and good faith of the students." - p_5: "If you are unsure whether you are eligible, please get in touch. If we determine that you have signed up and do not belong to an eligible group, we will permanently suspend your student invitations without warning." - p_6: "We take this issue very seriously, and we appreciate your cooperation and understanding." - disability: - title: "Students with Disability" - description: "We want to ensure that our workshops are as accessible as possible. If you are disabled and are unsure about whether our venues can cater to your needs, we encourage you to please get in touch with us at hello@codebar.io and we will do what we can to accommodate you." - chapters: - intro_html: "Hi and welcome to codebar!" - info: "Check out our FAQ page for any questions you might have, or email us at %{email} if you can't find the answer you're looking for. Otherwise, click the Join our community button to join us." - sign_up: "to be invited to our workshops." - no_incoming: "There are no workshops coming up." - contact: "To contact the %{city} team, send an email to %{email}" - feedback_form: - title: 'Workshop feedback' - description: Your submission will be completely anonymous. We read every piece of feedback and use it to help us improve our workshops. - note: Please do not mention any names, but instead choose your coach from the dropdown. This enables us to address issues but also to anonymously share feedback with coaches. Member privacy is very important to us! - rating: Your overall rating of the workshop - coach: 'Who was your coach?' - select_coach: '- Select Coach -' - tutorial: 'What tutorial did you go through?' - select_tutorial: '- Select Tutorial -' - request: 'How did you find the workshop?' - suggestions: "Was there something you didn't like? What can we do to improve your experience?" - pages: - cookies: - title: Cookie Policy - p1: 'Cookies are small pieces of text used to store information on web browsers. They are used by websites accross a number of different devices to store and receive identifiers and other information. Our Website and Service use cookies and other similar technologies (collectively in this Policy, "cookies"), in order to provide a better service to you and to generally improve our Website and Service. For example, we may use cookies to help direct you to the appropriate part of our Website, by indicating that you are a repeat visitor. We also may use information to present you with services that are matched to your preferences and to manage and track the effectiveness of our marketing efforts.' - p2: Some portions of the codebar website are functional without cookies, and you may generally choose whether to accept cookies. Most web browsers are set to accept cookies by default, however, you may be able to delete cookies yourself through your browser's cookie manager. To do so, please follow the instructions provided by your web browser. Please note that disabling cookies will reset your session, disable auto-login, and may adversely affect the availability and functionality of our Website and the services we can provide to you. - sub: - title: Below are the cookies used by the codebar website. - table: - header: - h1: Name - h2: Purpose - h3: Expires - functional: - title: Functional Cookies - description: Stores information about your session. - planner_name: _planner_session - planner_purpose: Stores session data - planner_expiry: Expires after 24 hours - google_analytics: - title: Google Analytics - description: Google Analytics collects information about how you use the codebar website. This enables us to identify how busy the website is and possible improvements. - info: We don’t allow Google to use or share our analytics data. - opt_out: You can [opt out of Google Analytics](https://tools.google.com/dlpage/gaoptout). - ga_name: _ga - ga_purpose: Tracks if you have visited codebar.io before - ga_expiry: After 2 years - gid_name: _ga - gid_purpose: Tracks if you have visited codebar.io before - gid_expiry: After 24 hours - cloudflare: - title: Cloudflare - cfduid_name: _pfduid - cfduid_purpose: Used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. - cfduid_expiry: 1 year - privacy_policy: - title: Privacy Policy - subtitle: This Privacy Policy was last updated on 13 May 2021. - intro: - p1: 'This Privacy Policy has been created by codebar ("codebar", "we", "us", or "our") whose companies house registered name and address is as follows:' - address_html: " - codebar Ltd,
- International House,
- 101 King's Cross Road,
- London, England,
- WC1X 9LP
- Company No. 10791813
" - p2: codebar Ltd trades on behalf of the charity registered UK and Wales no. 1187776. For the purpose of this Privacy Policy codebar Ltd is the data controller. - p3: Your privacy means a lot to us, and we take it very seriously. We aim to be transparent with you about the data we collect about you and how it is used and shared. This Privacy Policy lets you know what information we collect when you use the codebar website, https://codebar.io/, or interact with any of the services we provide, such as signing up to workshops and events ("Services"). By using our Services you acknowledge and understand our use of your data under this Privacy Policy and how it applies to your use of our Services. - information: - title: 1. Information we collect - what_we_collect: - title: 1.1 Personal data we collect from you - p1: 'We have set out in the table below the personal data we collect about you and how we use it, which will differ based on the capacity in which you interact with codebar:' - table: - headers: - h1: Who - h2: What data we process - h3: What we use it for - h4: Lawful basis - r1: - c1: Students - c2: This includes personal data that is provided by you or collected by us to enable you to subscribe to codebar as a student. This may include your name, email address, phone number, pronouns, self-written bio, , your self-recognition as being underrepresented (with your consent), and the location you choose to subscribe to. - c3: For administrative purposes when you sign up to events, to communicate with you, and to provide you with our newsletters and events information. - c4: - l1: Performance of a contract - l2: Consent - l3: Legitimate interests - r2: - c1: Coaches - c2: This includes personal data that is provided by you or collected by us to enable you to volunteer at codebar as a coach. This may include your name, email address, phone number, pronouns, self-written bio/skills, , your self-recognition as being underrepresented (with your consent), and the location you choose to volunteer at. - c3: For administrative purposes when you volunteer for workshops, to communicate with you, to manage workshop attendance, and to provide you with our newsletters and events information. - c4: - l1: Consent - l2: Legitimate interests - r3: - c1: Organizers - c2: This includes personal data that is provided by you or collected by us, which may include your name, email address, phone number, pronouns, self-written bio/skills, , slack username, signed documentation, and the location you choose to volunteer at. - c3: To organise and communicate workshops. - c4: - l1: Legitimate interests - r4: - c1: Hosts - c2: We may collect personal information of employees working at companies that agree to host our workshops. This information may include the employees' name, email address, contact number, , and place of work. - c3: In order to market, promote, host and operate workshops. - c4: - l1: Legitimate interests - r5: - c1: Sponsors - c2: We need to collect personal data in relation to your sponsorship of codebar. This may include information such as your name, and bank details. - c3: To fulfill contractual obligations we have with you, for example, to process invoices related to your sponsorship. - c4: - l1: Performance of a contract - l2: Legitimate interests - r6: - c1: Trustees and directors - c2: We need to collect personal data in relation to your position as trustee and/or director. This may include information such as your name, contact number, address, email address, and date of birth. - c3: In order to establish our status as a charity, to comply with legal obligations, and respond to legal requests. - c4: - l1: Legitimate interests - l2: Compliance with legal obligations - how_we_share: - title: 1.2 How we share your information - p1_html: 'When you subscribe to an event, we share your name with our host companies as we are required to provide a list with all attendee names when you subscribe to any of our events. We **do not share** your email address or any other personal information.' - legal_basis: - title: 1.3 Legal basis for our use of your personal information - p1: As set out in the table above, sometimes the legal basis on which we collect and process your data is because our legitimate interests make the processing necessary, and those legitimate interests are not overridden by your interests or fundamental rights and freedoms. For example, we collect and store your data in order to process event information, and to ensure the efficient running and promotion of workshops. - retention: - title: 2. Retention - p1: We will keep your personal information for as long as reasonably necessary to fulfil the purposes we collected it for. To determine the appropriate retention period, we consider the amount, nature and sensitivity of the personal information, the potential risk of harm from unauthorised use or disclosure of your personal information, the purposes for which we process your personal data and whether we can achieve those purposes through other means, and the applicable legal, regulatory, tax, accounting or other requirements. - p2: We may retain your personal information for a longer period in the event of a complaint or if we reasonably believe there is a prospect of dispute in respect to our relationship with you. - international_transfers: - title: 3. International transfers - p1: Personal information we collect may be transferred to and stored in countries outside of the jurisdiction you are in for the purposes specified in this Privacy Policy. We will only transfer your personal information to countries that have been deemed to provide an adequate level of protection for personal information, and/or any international transfers will be made pursuant to appropriate safeguards in accordance with the applicable laws and regulations, such as standard data protection clauses adopted by the UK and European Commission. - p2: If you wish to enquire further about these safeguards used, please contact us by email at the address below or by mail using the postal address provided below. - your_rights: - title: 4. Your data protection rights - p1: 'Data protection law provides you with rights in respect of personal data that we hold about you, including the:' - l1: 'Right to Access: You have the right to obtain access to your data, and certain other information (similar to that provided in this Privacy Policy).' - l2: 'Right to Rectification: You are entitled to have your data corrected if it is inaccurate or incomplete.' - l3: 'Right to Erasure: This enables you in some circumstances to request and obtain the deletion of your data where there is no legal reason for us to keep using it.' - l4: 'Right to Restriction of Processing: You have rights to suspend further use of your data, whereby we can still store your data but cannot use it further. This may mean we can no longer provide you with Services.' - l5: 'Right to Data Portability: You have rights in some circumstances to request the transfer of your data to yourself or to a third party.' - l6: 'Right to Objection: You have the right to object to certain types of data processing, including for direct marketing purposes.' - l7: 'Right to Withdrawal of Consent: Where we are relying on consent to process your data, you have the right to withdraw your consent at any time by using any opt-out links, or by contacting us at the details provided below (although if you do so, it does not mean that anything we have done with your data with your consent up to that point is unlawful and we may be able to continue to process your personal information to the extent required or otherwise permitted by law, in particular in connection with exercising and defending our legal rights or meeting our legal and regulatory obligations).' - l8: 'Right to Lodge a Complaint: You can lodge a complaint in relation to our use of your personal information with the local supervisory authority, the Information Commissioner (UK).' - p2: If you would like to exercise any of these rights or if you have a complaint about how we handle your data, please contact us at the email address stated below. - security: - title: 5. Security - p1: The security of your personal information is important to us. codebar takes reasonable steps to implement and update administrative, technical, and physical security measures to help protect your information against unauthorised access, loss, destruction, or alteration. However, the Internet is not a 100% secure environment so we can't guarantee the security of the transmission or storage of your information. codebar has no control over or responsibility for the security or practices or privacy policies of third parties, even if you interact with them when using our Services. - changes: - title: 6. Changes to this Privacy Policy - p1: We reserve the right to modify or update this Privacy Policy at any time in accordance with this provision. If we make changes to this Privacy Policy, we will post the revised Privacy Policy on the codebar website. Please regularly review https://codebar.io/privacy-policy to check for any updates or changes to our Privacy Policy. The date this Privacy Policy was last revised is identified at the top of this page. - cookies: - title: 7. Cookies - p1_html: 'We use cookies to recognise you and your location. You can control cookies through your browser settings and other tools. For more information read our [cookie policy](https://codebar.io/cookie-policy).' - contact: - title: 8. Contact - p1: "If you have any questions or complaints about this Privacy Policy or our information handling practices, you may email us at company@codebar.io stating 'Data inquiry' in the subject title, or by postal mail at: codebar Ltd, International House, 101 King's Cross Road, London, WC1X 9LP." - breach: - title: What happens if you violate codebar’s Code of Conduct? - opening_para: All codebar events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment towards any community member or organiser in any form. Harassment includes any type of aggressive behaviour or offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. - second_para: The Code of Conduct is in place to protect every codebar member - students, coaches and organisers. If any member violates these rules the below procedure and sanctions will be implemented. - outcome_title: 3 types of outcomes - correction: Correction - The use of inappropriate language or other behavior deemed unprofessional or unwelcome in the codebar community. This includes the use of terminology that is discouraged, e.g. 'guys'. In this situation you will be sent a private message, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. - warning: Warning - You will receive an email warning. The organiser will explain the incident, including the impact on the person involved and the community. We will give as much information as possible, so you’re aware of what happened and try to learn from the incident. The organiser will add a note to your codebar profile so that all chapter organisers are aware of the incident. We expect you to take our comments on board, further action may be taken depending on your reaction. Examples of behaviour that will get you a warning include - targeted offensive language, or the sharing of sexual images in codebar spaces. 2 email warnings will result in a lifetime ban. - lifetime_ban: Lifetime ban - You will no longer be able to RSVP to any future codebar events. You will also be removed from codebar’s Slack workspace. Examples of behaviour that will get you an automatic lifetime ban include - physical intimidation, stalking, inappropriate physical contact, unwelcome sexual attention or repeated behaviour after you’ve been spoken to by someone from the codebar team (directors or chapter organisers). - closing_para: The above is only a starting point. The details of the incident may change how we view it, e.g. some verbal harassment may be so serious that we would give a lifetime ban. - how_to_support_us: - volunteer: - title: Volunteer with us - become_an_organiser: - title: Become an organiser - description: Champion inclusion and diversity in the tech industry as a workshop organiser with codebar. Your contribution will create an empowering and safe environment, fostering learning and collaboration among individuals exploring coding in our vibrant community. - link: Email us to become an organiser - become_a_coach: - title: Become a coach - description: Affect change as a volunteer coach with codebar - your expertise and guidance will pave the way for aspiring developers, unlocking the world of coding and creating opportunities for folks from groups under represented in the tech industry. - volunteer: - title: Other skills - description: Your unique abilities could be our missing piece in the codebar puzzle. Having a diverse range of skills in our team is necessary to enrich our community. From fundraising to event coordination to marketing, we always welcome new talent to drive our mission forward. - link: Email us to become a volunteer - fundraise: - title: Fundraise - description_html: "Join the codebar team with a physical challenge event. Whether you are a runner, swimmer, or cyclist, sign up with our registration form for your desired event and raise vital funds to help keep our events running. If your event does not appear below, feel free to drop us an email and we would be happy to coordinate with you." - image_alt: A Black British woman crosses the finish line at the Hackney Half Marathon in London in a shower of confetti while spectators cheer her on. - codebar_stories_podcast: - image_alt: codebar stories banner - opening: codebar Stories is a new podcast brought to you by codebar, we'll be smashing down the belief that tech isn't for you by sharing real-life stories from members of our community who have transitioned into a new career in tech. - contact_us_html: "Sponsoring codebar Stories offers you a unique opportunity to connect with a diverse, engaged audience within the tech community. As a podcast dedicated to empowering underrepresented groups through coding education, your brand will align with our values of diversity, inclusivity, and social impact. Through sponsorship, you'll gain visibility, build positive PR, and demonstrate your commitment to fostering the next generation of tech talent, all while supporting a meaningful cause. Sound good? Please drop us an email podcast@codebar.io." - - admin: - dashboard: - title: 'Admin' - workshop: - manage_rsvps: - text: 'RSVP Students and Coaches to the workshop. The attendance confirmation email will be triggered and they will be removed from the waiting list.' - destroy: - success: "Workshop deleted successfully" - failure: "Workshop cannot be deleted. This is because it has invitees and/or workshop information is on the website for a while long enough that it cannot be deleted." - messages: - meeting: - created: 'Meeting successfully created' - updated: 'You have successfully updated the details of this meeting' - invitations_already_sent: 'Invitations were previously sent; they will not be sent again' - sending_invitations: 'Invitations are being sent out' - invitation: - rsvp_member: "%{name} has been successfully added and notified via email." - already_on_list: "%{name} is already on the list!" - rsvp_error: "Something went wrong, %{name} has not been added." - update_rsvp: 'Updated attendance of %{name}' - simple_form: - placeholders: - job: - company: 'e.g. codebar' - company_website: 'e.g. https://codebar.io' - title: 'e.g. Internship' - description: 'Use text or markdown for the job description' - location: 'e.g. London or Berlin' - hints: - job: - remote: Only check if the role is fully remote only - salary: Annual pay before tax, without commas or decimal points - activerecord: - attributes: - job: - title: Title - company: Name - company_address: Address - company_postcode: Postcode - company_website: Website - email: Contact email - link_to_job: Link to job post - expiry_date: Application closing date - donation_platforms: - title: "Donate" - description: "Your support—whether through a one-time gift or ongoing commitment—drives our mission to create a more inclusive tech industry. It enables us to provide continuous learning opportunities and empower individuals from underrepresented groups to grow and thrive in tech." - link: "Find out how else to support us" - donation_form: - title: "Use the donation page" - text: "Make a lasting impact with codebar by giving a one-time donation or committing to a monthly contribution." - image_alt: "codebar logo" - github_sponsors: - title: "Github Sponsors" - text: "Support codebar’s mission directly through GitHub Sponsors and help shape the future of technology with your generous donation." - image_alt: "Github Sponsors logo" - open_collective: - title: "Open Collective" - text: "Setup a recurring contribution or make a one-time donation through Open Collective." - image_alt: "Open Collective logo" - give_as_you_live: - title: "Give as you Live" - text: "Give as you Live is a platform enabling you to raise funds for your favourite charity with your everyday online shopping." - image_alt: "Give as you Live logo" diff --git a/config/locales/es.yml b/config/locales/es.yml deleted file mode 100644 index 995bc5378..000000000 --- a/config/locales/es.yml +++ /dev/null @@ -1,636 +0,0 @@ -es: - brand: "codebar.io" - date: - formats: - default: "%d/%m/%Y" - email: "%a, %d %B at %H:%M" - email_title: "%A, %d %b at %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - website_format: "%a, %d %B %Y at %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y at %R" - dashboard: "%a, %d %b %Y, %H:%M" - time: - formats: - default: "%a, %d %b %Y %H:%M" - email: "%a, %d %B at %H:%M" - email_title: "%A, %d %b at %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - full_date: "%d %B %Y" - default_date: "%d/%m/%Y" - website_format: "%a, %d %B %Y at %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y at %R" - dashboard: "%A, %b %d" - number: - currency: - format: - unit: '£' - delimiter: ',' - separator: '.' - precision: 0 - format: '%u%n' - homepage: - intro: "codebar es una organización benéfica que facilita el crecimiento de una comunidad tecnológica diversa mediante la realización de talleres de programación regulares y gratuitos para grupos minoritarios en tecnología." - explanation: "Nuestro objetivo es permitir que los miembros de grupos minoritarios aprendan programación en un entorno seguro y colaborativo y amplíen sus oportunidades profesionales. Para lograr esto, organizamos talleres regulares gratuitos, eventos únicos regulares y tratamos de crear oportunidades para nuestros estudiantes haciendo que la tecnología y la codificación sean más accesibles." - participate: - students_title: "Estudiantes" - students_explanation_p1: "Nuestros estudiantes provienen de una variedad de orígenes. Algunos quieren convertirse en desarrolladores a tiempo completo, mientras que a otros les gustaría aprender los conceptos básicos de la codificación en un entorno de apoyo." - students_explanation_p2: "Regístrese para unirse a nuestra vibrante comunidad y asistir a nuestros talleres." - students_button: "Regístrate como Estudiante" - coaches_title: "Entrenadores" - coaches_explanation_p1: "Alentamos a los nuevos estudiantes a trabajar en nuestro HTML/CSS, JavaScript, Ruby, Python o Git tutoriales. También les ayudamos a comprender los conceptos de programación." - coaches_explanation_p2: "Entonces, siempre estamos buscando más desarrolladores para que se unan a nuestra comunidad y ayuden a entrenar en nuestros talleres." - coaches_button: "Regístrate como Entrenador" - workshop_title: "Talleres" - workshop_explanation_p1: "Estamos alojados por algunas empresas increíbles que apoyan nuestra causa. Nuestro formato normal es de 30 minutos de socialización con comida y bebida, seguidos de una charla relámpago y luego codificación." - workshop_explanation_p2: "Ayude a nuestra expansión y permítanos brindar ayuda y apoyo a nuestros capítulos organizando y patrocinando nuestros talleres." - workshop_button: "Organiza un taller" - workshop_email_subject: "Respecto a la realización de un taller" - chapters: - title: "Capítulos" - donation_platforms: - title: "How to support us" - mailer: - workshop_invitation: - attending: - subject: "Confirmación de Asistencia para %{date_time}" - attending_reminder: - subject: "Recordatorio de Taller %{date_time}" - invite_coach: - subject: "Invitación al Entrenador del Taller %{date_time}" - invite_student: - subject: "Invitación al Taller %{date_time}" - notify_waiting_list: - subject: "Un lugar acaba de estar disponible" - waiting_list_reminder: - subject: "Recordatorio: estás en la lista de espera de codebar (%{date_time})" - messages: - accepted_invitation: "Gracias por responder a nosotros, %{name}. ¡Nos vemos en el taller!" - already_invited: 'Ya ha confirmado su asistencia o se ha unido a la lista de espera para este taller.' - error_blank_note: 'Debes seleccionar una nota' - rejected_invitation: "Estamos muy tristes de que no pueda asistir, pero gracias por hacérnoslo saber, %{name}." - already_rsvped: "¡Ya has confirmado tu asistencia!" - not_attending_already: "¡Ya has confirmado que no puedes asistir!" - no_available_seats: "Desafortunadamente no hay más espacios :(. Si desea unirse a nuestra lista de espera, envíenos un correo electrónico a %{email}" - feedback_saved: "¡Gracias por tomarse el tiempo para enviarnos sus comentarios!" - feedback_not_found: "Ya ha enviado comentarios para este evento." - updated_note: "Nota actualizada correctamente" - invalid_session: 'Tu sesión no es válida' - invitations: - meeting: - cancel: "Gracias por informarnos que no puede asistir." - rsvp: "Su RSVP fue exitoso. ¡Esperamos verte en el Monthly!" - rsvped_to_other_workshop: "Ya ha confirmado su asistencia a otro taller en esta fecha. Si prefiere asistir a este taller, primero cancele su otro RSVP." - spot_confirmed: "Tu lugar ha sido confirmado para %{event}! Esperamos verlos allí." - spot_not_confirmed: 'Tu lugar aún no ha sido confirmado. Verificaremos su asistencia después de completar el cuestionario.' - notifications: - provider_already_connected: '¡Ya has iniciado sesión!' - not_logged_in: "Debes iniciar sesión para acceder a esta página." - navigation: - dashboard: "Tablero" - code_of_conduct: "Código de Conducta" - breach_code_of_conduct: "Breach Code of Conduct" - coach_guide: "Guía para entrenadores" - student_guide: "Guía para estudiantes" - tutorials: "Tutoriales" - becoming_sponsor: "Convertirse en patrocinador" - faq: "Preguntas más frecuentes" - blog: "Blog" - codebar_stories: "codebar Cuentos" - stats: "Stats" - dashboard: - join_workshops_in: "Únase a nuestros talleres gratuitos en" - workshops_goal: "para familiarizarse con los conceptos básicos de programación y desarrollo web." - tweets_by: "Tweets de" - latest_sponsors: "Últimos patrocinadores" - policy: - intro: "Hay una gran demanda de nuestros talleres y tenemos una lista de espera durante la mayoría de las semanas. Para asegurarse de que puedan llegar la mayor cantidad posible, tenemos una política de asistencia directa." - rule1: "Antes de que RSVP se asegure de que usted es elegible para asistir. Si no está seguro de ponerse en contacto con un chat." - rule2: "Debe registrarse y confirmar su asistencia para asistir a nuestros talleres." - rule3: "Si luego descubre que no puede hacerlo, debe cancelarlo. Solo le tomará unos segundos hacerlo a través de su correo electrónico de confirmación." - rule4: "Intente cancelar con al menos 24 horas de anticipación." - rule5: "Sabemos que a veces las cosas surgen de última hora, pero incluso si solo cancelas una hora antes del taller, ponte en contacto y háganoslo saber." - what_happens: "¿Qué pasa si no respeto la política?" - strikes_system: "Operamos un sistema de 'tres huelgas'. Eso significa que si no entiende sin cancelar un RSVP tres veces, lo llevaremos a nuestra lista de invitación durante cuatro semanas. Nos pondremos en contacto después de su primera ausencia para asegurarse de que usted Entienda esto." - removing: "Si no asiste sin cancelar otras tres veces, es posible que tengamos que eliminarlo permanentemente de nuestra lista de invitación." - rsvping: "No hay penalización por RSVP-ING y luego cancelando regularmente, pero evítelo. Si siempre lucha para hacerlo en un día determinado, háganoslo saber, ese tipo de retroalimentación es realmente importante para nosotros." - eligibility_note: "Otra nota sobre elegibilidad" - abuse: "Somos un grupo bastante relajado y confiamos en usted, por lo que no contamos con los estudiantes de policía en cuanto a su elegibilidad. Sin embargo, si alguna vez parece que esto está siendo abusado, es posible que tengamos que cambiar eso, lo que realmente no queremos hacer." - reminder: "Así que, por favor, recuerde que son estos talleres, para abrir tecnología a las personas que están subrepresentadas en la industria." - teacher_guide: - laptop: "No necesita una computadora portátil para nuestros talleres. Usted está ahí para ver y guiar a los estudiantes. Si no se siente cómodo con el tutorial, debe pasar tiempo antes de venir si quiere ayudarlo." - keyboard: "¡No tomes el teclado! Esto puede estar fuera de lugar y aterrador." - typing: "Anime a los estudiantes a escribir y no a copiar y pegar." - questions: "Explique que no hay malas preguntas." - mistakes: "Explique a los estudiantes que está bien cometer errores." - introduction: "Siempre preséntate. Diga por qué quiere ayudar y está gastando su propio tiempo en esto, por qué le gusta la programación." - backgrounds: "Dale a tus alumnos la oportunidad de conocerse. Pregunte sus nombres, por qué están aquí, lo que hacen en sus trabajos del día. Fomente una breve discusión antes de comenzar." - limits: "Supongamos que cualquier persona que estás enseñando no tiene conocimiento, sino inteligencia infinita." - collaboration: "Trabaja en colaboración con su estudiante. Si tiene dos estudiantes, debe trabajar con ambos. No enfoque toda su atención en uno de ellos." - discussion: "Deje que los estudiantes tengan una oportunidad primero respondiendo las preguntas. Ayuda con preguntas abiertas y líderes. Fomenta una discusión." - talk_slow: "Tómalo lento, tú eres el maestro, son el estudiante. Permitir tiempo entre preguntas." - mild_approach: "No digas que no cuando los estudiantes no están haciendo algo bien. Sé amable, acercarse de una manera suave." - paper: "¡Usa la pluma y el papel o vaya a una pizarra! A menudo, los estudiantes provengan de un fondo no técnico. El dibujo y la explicación con material visual es realmente útil." - stubling: "Déjalos tropezar. Aprendemos cometer errores, frustrándonos y trabajando a través del problema a nuestra manera. Esperamos, pero déjalos explorar." - suggestions: "¿Tienes algo que sugerir? Haz una 'pull request' o crear un problema" - workshops: - already_wish_to_attend: "Ya tienes RSVPD o se unió a la lista de espera para este taller." - lead: "Asista a nuestros talleres para aprender la programación en un entorno seguro y de apoyo a su propio ritmo, o para compartir sus conocimientos y entrenar a nuestros estudiantes." - registration_not_open: "Este taller no está abierto para inscripciones." - events: - title: "Eventos" - past: "Pasados" - no_upcoming_events: "No hay eventos próximos." - view_past_events: "Ver eventos pasados" - view_all: "Ver todos" - hosted_by: "Alojado por" - organisers: "Organizadores" - venue_at: "en" - attend_as_student: "Asiste como estudiante" - attend_as_coach: "Asiste como entrenador" - location: "Localización" - sponsors: "Patrocinadores" - thx_to_sponsors: "¡Muchas gracias a todos nuestros patrocinadores por hacer posible el evento!" - coaches: "Entrenadores" - students: Estudiantes - schedule: "Calendario" - send_us_an_email: "envianos un email" - not_open_for_rsvp: "Este evento aún no está abierto para confirmar su asistencia." - virtual: This is a virtual event. - faq: - experience: - q: "¿Qué experiencia necesito tener para unirme al taller?" - a: - contribution: - q: "¿Qué tipo de contribuciones puedo hacer?" - a: "Sus contribuciones pueden ser pequeñas, tan simples como arreglar un error tipográfico, a algo increíble. Puede ayudar con la documentación, solucionar un error que ha encontrado, mejorar la copia, ayudar a diseñar o incluso abordar tareas más grandes y ayudar a introducir nuevas características. Cada Poco ayuda!" - laptop: - q: "¿Necesito traer una computadora portátil?" - a_html: "Sí, debe traer una computadora portátil. Si no tiene un %{link}, es posible que podamos ayudarlo." - keyboard: - q: "¿Necesito traer un teclado?" - a_html: "Un teclado ayudaría, ya que pasará todo el día emparejando con alguien en su computadora portátil. Si no tiene un teclado,% {link} e intentaremos organizar algo para usted." - travel_costs: - q: "Estaré viajando. ¿Me pueden ayudar con mis gastos de viaje?" - a: "Vamos a ofrecer algunas becas de viaje. Solo asegúrate de completar el cuestionario después de que RSVP y nos pondremos en contacto." - coaches: - want_to_coach: "¿Quieres formarte en nuestros talleres?" - read_before: "Si no ha asistido a nuestros talleres antes, asegúrate de leer nuestro" - code_of_conduct: "código de conducta" - policy: "Como tenemos una política de tolerancia cero y esperamos que todos se comporten de manera adecuada. También deberías pasar por nuestro" - guide: "guía para entrenadores" - unable_attend: "En caso de que no pueda asistir después de su RSVP, asegúrese de regresar y actualizar su asistencia a medida que confíe en los entrenadores que aparecen para que nuestros talleres se ejecuten sin problemas." - food: "También habrá comida en el taller. Siempre nos esforzamos en tener disponibles opciones vegetarianas, veganas y sin gluten. Si tiene otros requisitos dietéticos, envíenos un correo electrónico a" - code_of_conduct: - title: "Código de Conducta" - summary: - title: "La Versión Rápida" - intro: "Nuestros eventos están dedicados a proporcionar una experiencia libre de acoso para todos, independientemente del género, la orientación sexual, la discapacidad, la apariencia física, el tamaño del cuerpo, la raza o la religión. No toleramos el acoso de nuestros miembros en ninguna forma. Lenguaje sexual y Las imágenes no son apropiadas para ninguno de nuestros eventos, incluidas las conversaciones, talleres, fiestas, twitter y cualquier otro medio en línea. Los miembros que violan estas reglas pueden ser sancionados o expulsados del evento y cualquier evento futuro a discreción de los organizadores." - content: - title: "La Versión Larga" - harassment: "El hostigamiento incluye comentarios verbales ofensivos relacionados con el género, la orientación sexual, la discapacidad, la apariencia física, el tamaño del cuerpo, la raza, la religión, las imágenes sexuales en los espacios públicos, la intimidación deliberada, el acecho, lo siguiente, hostigando la fotografía o la grabación, la interrupción sostenida de las conversaciones u otros eventos. , contacto físico inapropiado, y atención sexual no deseada." - comply: "Esperamos que cualquier participante le pida que detengamos cualquier comportamiento de acoso para cumplirlo de inmediato." - sponsors: "Los patrocinadores también están sujetos a la política contra el acoso. En particular, los patrocinadores no deben usar imágenes, actividades u otros materiales sexualizados. El personal (incluidos los voluntarios) no debe usar ropa / uniformes / disfraces sexualizados, o crear un entorno sexualizado." - sanctions: "Si un participante se involucra en el comportamiento de acoso, los organizadores pueden tomar cualquier acción que considere apropiados. Esto incluye advertir al delincuente o expulsión." - concerns: "Si está siendo acosado, observe que alguien más está siendo acosado, o tiene alguna otra inquietud, comuníquese con uno de los organizadores de inmediato." - applies_to: "We expect participants to follow these rules at all codebar events. If they fail to do so, the following process will take place." - questions: "Si tiene alguna pregunta o inquietud sobre este código, por favor" - contact: "Contacta con nosotros" - email_subject: "Con respecto al Código de conducta" - sponsors: - sponsoring: "Patrocinio" - members: - sign_up: "Inscribirse" - sign_in_with_github: "Iniciar sesión con Github" - sign_up_as_student: "Inscribirme como estudiante *" - sign_up_as_student_disclaimer: "* Entiendo y cumplo con los criterios de elegibilidad." - sign_up_as_coach: "Regístrate como Entrenador" - code_of_conduct: "código de conducta" - new: - intro_html: "We provide a welcoming, inclusive, and supportive learning environment, with a strict zero-tolerance policy for any form of harassment or inappropriate behavior. Please take a moment to review our code of conduct before signing up." - students: - intro_html: "Si desea asistir a un estudiante, asegúrese de conocer a nuestro criterio de elegibilidad como nuestros talleres solo están disponibles para las mujeres, LGBTQ, personas de grupos minoritarios subrepresentados." - github: "Por último, cuando hace clic en el botón Registrarse, se lo llevará a algo llamado GitHub. Después de iniciar sesión con una cuenta GitHub, volverá al sitio web de codebar. Si aún no tiene una cuenta, Tendrás que crear uno. ¡No tarda mucho tiempo y es algo que vendrá de manera útil cuando comience con la codificación!" - invitations: "Las invitaciones se envían periódicamente, así que no se preocupe si no recibe uno tan pronto como se registre." - footer: - email_us: "Envíenos un correo electrónico a" - contact_info: "Datos de contacto:" - faq: - payment: - q: "¿Tengo que pagar para asistir a codebar?" - a_p1: "¡Absolutamente no! Tenemos la suerte de contar con grandes empresas que pueden organizar los talleres y / o proporcionar amablemente la comida. Y nuestros" - awesome_coaches: "Entrenadores Increíbles" - a_p2: "dar su tiempo libremente para ayudar a la comunidad" - technologies: - q: "¿Qué tecnologías enseñas?" - a: "Tenemos una variedad de tutoriales disponibles en HTML, CSS, JavaScript and Ruby. Si quieres aprender algo más, no dudes en enviarnos un correo electrónico ya que aún podríamos encontrar a alguien que te ayude." - eligibility: - q: "Quiero asistir a un taller. ¿Soy elegible?" - a: "ya que aún podríamos encontrar a alguien que te ayude. If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School London where you can learn in a collaborative environment. Please see our student guide for more information." - career: - q: "¿codebar solo está dirigido a personas que desean avanzar en una carrera como desarrollador?" - a: "¡No! codebar se trata de conseguir que las personas se entusiasman con la programación. Los ayudaremos a aprender algunas habilidades básicas de codificación, así como cómo explorar y hacer las cosas por su cuenta. Para aquellos que quieren convertirse en desarrolladores, proporcionaremos ayuda y Orientación para ayudarles a lograr su objetivo." - format: - q: "¿Cuál es el formato de los talleres?" - a: "Tratamos de tener un entrenador para cada dos estudiantes. Vamos a emparejar a los estudiantes que quieran trabajar en el mismo tutorial y asignarles un entrenador. El resto solo sucede." - laptop: - q: "¿Necesito traer una computadora portátil a los talleres?" - a: "Sí, le sugerimos que traiga una computadora portátil, ya que será más fácil para usted seguir trabajando en cosas después de los talleres. No tiene uno, envíenos un correo electrónico tutorials. Los tutoriales son de código abierto, por lo que si hay algo que desea mejorar, abre un problema en el repositorio de GitHUB o envíe una 'pull request'." - a_p4: "No esperamos que los entrenadores estén familiarizados con todas las tecnologías e idiomas en los que tenemos material." - location: - q: "¿Dónde se llevan a cabo los talleres?" - a: "Como no tenemos un lugar permanente, nuestros talleres son organizados por diferentes compañías en varios lugares de Londres. Hasta ahora, hemos realizado talleres en Shoreditch, London Bridge, Holborn y Kings Cross." - disabled_access: - q: "¿Hay acceso para discapacitados en los talleres?" - a: "Desafortunadamente, eso depende completamente de dónde estamos alojando nuestros talleres y si el lugar tiene un acceso para discapacitados. Si desea asistir, envíenos un correo electrónico a meetings[at]codebar.io así que podemos preguntarle al respecto y le avisamos." - bring_codebar_to_my_city: - q: "Me gustaría traer la barra de código a mi ciudad. ¿Puedo hacer eso?" - a: "Por supuesto. codebar se trata de construir una comunidad de desarrolladores experimentados que puedan renunciar a uno de sus tiempo para ayudar a otros. Si está interesado en correr la barra de código donde vive, nos encantaría hablarle al respecto y ver cómo podemos ayudarlo a suceder esto, así que envíenos un correo electrónico." - our_coaches: - q: "Nuestros Entrenadores" - a_p1: "Puedes ver que todos los entrenadores han ayudado en nuestros talleres sobre el" - a_p2: ". Están ordenados por el número de asistencias. Esta es nuestra forma de mostrarles nuestra apreciación, ya que sin ellos, no podríamos existir." - participant_student_guide: - title: "Guía de estudiante" - attendance_policy: - title: "Politica de asistencia" - intro: "codebar es, y siempre ha sido, abierta a todos los niveles de experiencia de codificación. Si bien la mayoría de los tutoriales en nuestro sitio web están dirigidos a recién llegados al desarrollo web, tenemos la intención de continuar con nuestra política de puertas abiertas para cualquier estudiante que necesite apoyo de entrenadores en sus propios proyectos. Debido al hecho de que nuestros talleres con frecuencia se suscriben sobre suscripción, le pedimos a los estudiantes que respeten las siguientes expectativas de participación en nuestros talleres:" - rule1: "Para asistir a un taller, debe estar en la lista RSVP. Si no tiene RSVP'd o no se le asignó un lugar, no se le admitirá en un taller." - rule2: "Si ya no puede asistir a un taller, cancele su RSVP antes de las 12:00 más reciente en el día del taller. Entendemos que ocurren emergencias de última hora, si este es el caso, por favor póngase en contacto con un organizador directamente lo antes posible. Las repetidas no programas resultarán en suspensión temporal o permanente de sus invitaciones." - rule3: "No se permiten invitados. Nuestros talleres ya están superpoblados y no podemos hacer excepciones. Si su amigo cumple con nuestros criterios de elegibilidad, haga que se inscienden a ellos mismos y RSVP." - rule4: "Por favor, sea respetuoso con nuestros anfitriones. No aparezca extremadamente temprano a un taller (no antes de 15 minutos antes de que comience el evento) e intente dejar la estación de trabajo limpia y, como lo encontró." - rule5: "No trabaje en proyectos que fueron asignados como parte de cualquier currículo de bootcamp o universidad. Hable con su asesor de cursos si siente que necesita un soporte adicional con sus cursos. Damos la bienvenida a su asistencia, pero nosotros Anímelo a usar su tiempo en Codebar para desarrollar habilidades que están fuera del alcance normal de sus estudios." - rule6: "No lo traigan y pida ayuda con cualquier trabajo comercial. Esto implica que el trabajo está pagado para hacer." - rule7: "Los proyectos que involucran marcos / bibliotecas específicas (rieles, nodejs, meteoros, angulares, embriagos, reaccionar, etc.) o idiomas que no forman parte de los tutoriales de Codebar (nada más que Ruby o JavaScript) son bienvenidos, pero no podemos garantizar que un entrenador estará disponible para ayudarlo. En estos casos, le recomendamos seleccionar un tutorial de codebar o katas (Codewars.com o Ejercismo) como opción de respaldo." - eligibility_criteria: - title: "Criterio de elegibilidad" - p_1: "codebar se inició sin reconocimiento de que hay una escasez de mujeres, LGBTQ y personas que pertenecen a grupos étnicos subrepresentados en tecnología." - p_2: "Si perteneces a uno de estos grupos, es más que bienvenido a asistir. Si no, hay otras iniciativas excelentes como Open Tech School o Ask a Dev donde puede aprender en un entorno de colaboración." - p_3: "Teniendo eso en mente, a veces es difícil para nosotros identificar si los asistentes cumplen con los criterios de elegibilidad según sus nombres y apellidos. Si no podemos determinar su elegibilidad, nos pondremos en contacto con usted para solicitar una breve confirmación de que ha leído este documento. y afirmar que cumple uno o más de los criterios. Nunca pediremos a los participantes que especifiquen a qué grupo." - p_4: "codebar es, ante todo, un recurso para los estudiantes que no pueden pagar capacitación formal a través de codificación de bootcamps o títulos universitarios, por razones financieras o de otro tipo. Nuestros entrenadores, organizadores y patrocinadores donan su tiempo y dinero para ayudar a aquellos que han enfrentado barreras injustas para ingresar a El mundo de la tecnología. Nos hemos esforzado por crear una comunidad inclusiva y acogida, y hasta ahora, no hemos tenido que implementar una política formal para hacer cumplir los criterios de elegibilidad, lo hemos dejado esto a la honestidad y la buena fe de los estudiantes." - p_5: "Si no está seguro de si es elegible, póngase en contacto. Si determinamos que se ha registrado y no pertenezca a un grupo elegible, suspenderemos permanentemente a sus invitaciones de estudiantes sin previo aviso." - p_6: "Tomamos este tema muy en serio, y apreciamos su cooperación y comprensión." - disability: - title: "Alumnos con discapacidad" - description: "Queremos asegurarnos de que nuestros talleres sean lo más accesibles posible. Si está deshabilitado y no está seguro de si nuestros lugares pueden satisfacer sus necesidades, lo alentamos a ponerse en contacto con nosotros en hello@codebar.io y haremos lo que podamos para acomodarlo." - chapters: - intro_html: "¡Hola y bienvenido a coderbar!" - info: "Echa un vistazo a nuestro FAQ para cualquier pregunta que pueda tener, o envíenos un correo electrónico a %{email} si no puede encontrar la respuesta que está buscando. De lo contrario, haga clic en el botón Registrarse para comenzar." - sign_up: "ser invitado a nuestros talleres." - no_incoming: "No hay talleres que se presentan." - contact: "Para ponerse en contacto con el equipo %{city}, envíe un correo electrónico a %{email}" - job: - status: - draft: Borrador - pending: Aprobación pendiente - published: Publicado - expired: Caducado - admin: - status: - pending: Aprobación pendiente - published: Aprobado - expired: Aprobado - expired: 'Este puesto de trabajo ha caducado.' - check_out_jobs_html: 'Echa un vistazo al resto de nuestros %{link}.' - published_on: 'Publicado en' - expires_on: 'Closing date' - apply: 'Aplica para este trabajo' - company: 'Empresa' - salary: 'Salario' - closing_date: 'Fecha de cierre' - contact_email: Email de contacto - posted_by: Publicado por - - location: - title: Localización - remote: 'Remote' - messages: - -draft_html: 'Esta es una vista previa de su trabajo. Edite para modificar o Envíe para aprobación.' - -pending_html: 'Este trabajo está pendiente de aprobación. Editepara modificar su publicación.' - -published_html: 'Este trabajo ha sido publicado.' - -expired_html: 'Este trabajo ha caducado.' - -updated: 'Su trabajo ha sido actualizado.' - -submitted: "Trabajo enviado para aprobación. Recibirás un correo electrónico cuando haya sido aprobado." - -cannot_edit: No puede editar un trabajo que ya ha sido aprobado. - -public_page_html: Ver el %{link} para este trabajo. - jobs: - title: Trabajos - index: - description: Hay %{count} trabajos listados - none: No hay trabajos listados en este momento. Vuelva a consultar pronto ya que las posiciones se agregan regularmente. - feedback_form: - title: 'Comentarios del taller' - description: Su envío será completamente anónimo. Leemos todos los comentarios y los usamos para ayudarnos a mejorar nuestros talleres. - note: Por favor, no mencione ningún nombre, sino que elija su entrenador del menú desplegable. Esto nos permite abordar problemas, pero también compartir comentarios de forma anónima con los entrenadores. ¡La privacidad de los miembros es muy importante para nosotros! - rating: Tu calificación general del taller - coach: '¿Quién fue tu entrenador?' - select_coach: '- Seleccionar entrenador -' - tutorial: '¿Qué tutorial hiciste?' - select_tutorial: '- Select Tutorial -' - request: '¿Cómo encontraste el taller?' - suggestions: "¿Hubo algo que no te gustó? ¿Qué podemos hacer para mejorar tu experiencia?" - member: - jobs: - title: Mi trabajos - preview: Avance - index: - description: Nuestro objetivo es ser la ventanilla única para los roles de desarrollador junior. Todos los trabajos que aparecen en nuestra bolsa de trabajo deben pertenecer a las siguientes tres categorías; pasantías pagadas, aprendizaje o roles de desarrollador junior. Además, los trabajos no deben requerir experiencia previa o un título y deben ser puestos remunerados. Cada trabajo que se envíe será aprobado por el equipo de Codebar antes de aparecer en la bolsa de trabajo. - testimonial: A los 2 días de publicar un anuncio en la bolsa de trabajo Codebar, teníamos docenas de solicitudes de alta calidad y le hicimos una oferta a un candidato en 2 semanas. Hay muchos pasantes talentosos y desarrolladores junior; Publicar en la bolsa de trabajo Codebar es una excelente manera de llegar a ellos. - title: Llega a nuestra comunidad de %{students_count} desarrolladores junior - offer: - title: "Por una tarifa plana de £50 tu publicación:" - job_board: "- se mostrará en la bolsa de trabajo durante 30 días" - slack: "- se promocionará a nuestra comunidad Slack de 5500 miembros" - twitter: "- Será promocionado a nuestros 8600 seguidores en Twitter." - pending: - title: Tus ofertas de trabajo pendientes - description: Tienes %{count} ofertas de trabajo pendientes de enviar. - none: No tienes ofertas de trabajo pendientes. - new: - title: Listar un trabajo - degree: No hay requisito de grado - details: La descripción del puesto detalla el trabajo que se tendrá que realizar - experience: No hay requisito de experiencia previa - rules_intro: "Antes de publicar asegúrate de que:" - suitability: El puesto es adecuado para personas que buscan pasantías, aprendizaje o roles de nivel junior que les permitan desarrollar su carrera. - salary: El trabajo paga un salario adecuado. - short: La descripción del trabajo es corta y al punto. - approval_info: "*Cuando se envía, un trabajo será visible una vez que haya sido revisado y aprobado." - optional_details_message: La información a continuación solo es necesaria si desea que esta publicación de trabajo se comparta con la Búsqueda de Google en el Reino Unido. - newsletter: "Por un adicional £200 puede hacer que su lista de trabajos aparezca en nuestro boletín y esté disponible para una audiencia de más de 10000 estudiantes y entrenadores. Para conocer más detalles y cuándo vence nuestro próximo boletín, envíenos un correo electrónico a hello@codebar.io." - pay: - html: Ha realizado el pago requerido de £50. - button: - pay: realizar un pago - edit: - title: Editar listado de trabajos - pages: - cookies: - title: Cookies - p1: Las cookies son pequeños fragmentos de texto que se utilizan para almacenar información en los navegadores web. Los sitios web los utilizan en varios dispositivos diferentes para almacenar y recibir identificadores y otra información. Nuestro sitio web y servicio utilizan cookies y otras tecnologías similares (colectivamente en esta Política, "cookies"), para brindarle un mejor servicio y, en general, mejorar nuestro sitio web y nuestro servicio. Por ejemplo, podemos utilizar cookies para ayudarlo a dirigirlo a la parte apropiada de nuestro sitio web, lo que indica que es un visitante habitual. También podemos utilizar información para presentarle servicios que se adapten a sus preferencias y para administrar y rastrear la efectividad de nuestros esfuerzos de marketing. - p2: Some portions of the codebar website are functional without cookies, and you may generally choose whether to accept cookies. Most web browsers are set to accept cookies by default, however, you may be able to delete cookies yourself through your browser's cookie manager. To do so, please follow the instructions provided by your web browser. Please note that disabling cookies will reset your session, disable auto-login, and may adversely affect the availability and functionality of our Website and the services we can provide to you. - sub: - title: Below are the cookies used by the codebar website. - table: - header: - h1: Name - h2: Purpose - h3: Expires - functional: - title: Functional Cookies - description: Stores information about your session. - planner_name: _planner_session - planner_purpose: Stores session data - planner_expiry: Expires after 24 hours - google_analytics: - title: Google Analytics - description: Google Analytics collects information about how you use the codebar website. This enables us to identify how busy the website is and possible improvements. - info: We don’t allow Google to use or share our analytics data. - opt_out: You can [opt out of Google Analytics](https://tools.google.com/dlpage/gaoptout). - ga_name: _ga - ga_purpose: Tracks if you have visited codebar.io before - ga_expiry: Después de 2 años - gid_name: _ga - gid_purpose: Tracks if you have visited codebar.io before - gid_expiry: Después de 24 horas - cloudflare: - title: Cloudflare - cfduid_name: _pfduid - cfduid_purpose: Used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. - cfduid_expiry: 1 year - privacy_policy: - title: Privacy Policy - subtitle: This Privacy Policy was last updated on 13 May 2021. - intro: - p1: 'This Privacy Policy has been created by codebar ("codebar", "we", "us", or "our") whose companies house registered name and address is as follows:' - address_html: " - codebar Ltd,
- International House,
- 101 King's Cross Road,
- London, England,
- WC1X 9LP
- Company No. 10791813
" - p2: codebar Ltd trades on behalf of the charity registered UK and Wales no. 1187776. For the purpose of this Privacy Policy codebar Ltd is the data controller. - p3: Your privacy means a lot to us, and we take it very seriously. We aim to be transparent with you about the data we collect about you and how it is used and shared. This Privacy Policy lets you know what information we collect when you use the codebar website, https://codebar.io/, or interact with any of the services we provide, such as signing up to workshops and events ("Services"). By using our Services you acknowledge and understand our use of your data under this Privacy Policy and how it applies to your use of our Services. - information: - title: 1. Information we collect - what_we_collect: - title: 1.1 Personal data we collect from you - p1: 'We have set out in the table below the personal data we collect about you and how we use it, which will differ based on the capacity in which you interact with codebar:' - table: - headers: - h1: Who - h2: What data we process - h3: What we use it for - h4: Lawful basis - r1: - c1: Students - c2: This includes personal data that is provided by you or collected by us to enable you to subscribe to codebar as a student. This may include your name, email address, phone number, pronouns, self-written bio, , your self-recognition as being underrepresented (with your consent), and the location you choose to subscribe to. - c3: For administrative purposes when you sign up to events, to communicate with you, and to provide you with our newsletters and events information. - c4: - l1: Performance of a contract - l2: Consent - l3: Legitimate interests - r2: - c1: Coaches - c2: This includes personal data that is provided by you or collected by us to enable you to volunteer at codebar as a coach. This may include your name, email address, phone number, pronouns, self-written bio/skills, , your self-recognition as being underrepresented (with your consent), and the location you choose to volunteer at. - c3: For administrative purposes when you volunteer for workshops, to communicate with you, to manage workshop attendance, and to provide you with our newsletters and events information. - c4: - l1: Consent - l2: Legitimate interests - r3: - c1: Organizers - c2: This includes personal data that is provided by you or collected by us, which may include your name, email address, phone number, pronouns, self-written bio/skills, , slack username, signed documentation, and the location you choose to volunteer at. - c3: To organise and communicate workshops. - c4: - l1: Legitimate interests - r4: - c1: Hosts - c2: We may collect personal information of employees working at companies that agree to host our workshops. This information may include the employees' name, email address, contact number, , and place of work. - c3: In order to market, promote, host and operate workshops. - c4: - l1: Legitimate interests - r5: - c1: Sponsors - c2: We need to collect personal data in relation to your sponsorship of codebar. This may include information such as your name, and bank details. - c3: To fulfill contractual obligations we have with you, for example, to process invoices related to your sponsorship. - c4: - l1: Performance of a contract - l2: Legitimate interests - r6: - c1: Trustees and directors - c2: We need to collect personal data in relation to your position as trustee and/or director. This may include information such as your name, contact number, address, email address, and date of birth. - c3: In order to establish our status as a charity, to comply with legal obligations, and respond to legal requests. - c4: - l1: Legitimate interests - l2: Compliance with legal obligations - how_we_share: - title: 1.2 How we share your information - p1_html: 'When you subscribe to an event, we share your name with our host companies as we are required to provide a list with all attendee names when you subscribe to any of our events. We **do not share** your email address or any other personal information.' - legal_basis: - title: 1.3 Legal basis for our use of your personal information - p1: As set out in the table above, sometimes the legal basis on which we collect and process your data is because our legitimate interests make the processing necessary, and those legitimate interests are not overridden by your interests or fundamental rights and freedoms. For example, we collect and store your data in order to process event information, and to ensure the efficient running and promotion of workshops. - retention: - title: 2. Retention - p1: We will keep your personal information for as long as reasonably necessary to fulfil the purposes we collected it for. To determine the appropriate retention period, we consider the amount, nature and sensitivity of the personal information, the potential risk of harm from unauthorised use or disclosure of your personal information, the purposes for which we process your personal data and whether we can achieve those purposes through other means, and the applicable legal, regulatory, tax, accounting or other requirements. - p2: We may retain your personal information for a longer period in the event of a complaint or if we reasonably believe there is a prospect of dispute in respect to our relationship with you. - international_transfers: - title: 3. International transfers - p1: Personal information we collect may be transferred to and stored in countries outside of the jurisdiction you are in for the purposes specified in this Privacy Policy. We will only transfer your personal information to countries that have been deemed to provide an adequate level of protection for personal information, and/or any international transfers will be made pursuant to appropriate safeguards in accordance with the applicable laws and regulations, such as standard data protection clauses adopted by the UK and European Commission. - p2: If you wish to enquire further about these safeguards used, please contact us by email at the address below or by mail using the postal address provided below. - your_rights: - title: 4. Your data protection rights - p1: 'Data protection law provides you with rights in respect of personal data that we hold about you, including the:' - l1: 'Right to Access: You have the right to obtain access to your data, and certain other information (similar to that provided in this Privacy Policy).' - l2: 'Right to Rectification: You are entitled to have your data corrected if it is inaccurate or incomplete.' - l3: 'Right to Erasure: This enables you in some circumstances to request and obtain the deletion of your data where there is no legal reason for us to keep using it.' - l4: 'Right to Restriction of Processing: You have rights to suspend further use of your data, whereby we can still store your data but cannot use it further. This may mean we can no longer provide you with Services.' - l5: 'Right to Data Portability: You have rights in some circumstances to request the transfer of your data to yourself or to a third party.' - l6: 'Right to Objection: You have the right to object to certain types of data processing, including for direct marketing purposes.' - l7: 'Right to Withdrawal of Consent: Where we are relying on consent to process your data, you have the right to withdraw your consent at any time by using any opt-out links, or by contacting us at the details provided below (although if you do so, it does not mean that anything we have done with your data with your consent up to that point is unlawful and we may be able to continue to process your personal information to the extent required or otherwise permitted by law, in particular in connection with exercising and defending our legal rights or meeting our legal and regulatory obligations).' - l8: 'Right to Lodge a Complaint: You can lodge a complaint in relation to our use of your personal information with the local supervisory authority, the Information Commissioner (UK).' - p2: If you would like to exercise any of these rights or if you have a complaint about how we handle your data, please contact us at the email address stated below. - security: - title: 5. Security - p1: The security of your personal information is important to us. codebar takes reasonable steps to implement and update administrative, technical, and physical security measures to help protect your information against unauthorised access, loss, destruction, or alteration. However, the Internet is not a 100% secure environment so we can't guarantee the security of the transmission or storage of your information. codebar has no control over or responsibility for the security or practices or privacy policies of third parties, even if you interact with them when using our Services. - changes: - title: 6. Changes to this Privacy Policy - p1: We reserve the right to modify or update this Privacy Policy at any time in accordance with this provision. If we make changes to this Privacy Policy, we will post the revised Privacy Policy on the codebar website. Please regularly review https://codebar.io/privacy-policy to check for any updates or changes to our Privacy Policy. The date this Privacy Policy was last revised is identified at the top of this page. - cookies: - title: 7. Cookies - p1_html: 'We use cookies to recognise you and your location. You can control cookies through your browser settings and other tools. For more information read our [cookie policy](https://codebar.io/cookie-policy).' - contact: - title: 8. Contact - p1: "If you have any questions or complaints about this Privacy Policy or our information handling practices, you may email us at company@codebar.io stating 'Data inquiry' in the subject title, or by postal mail at: codebar Ltd, International House, 101 King's Cross Road, London, WC1X 9LP." - breach: - title: What happens if you violate codebar’s Code of Conduct? - opening_para: All codebar events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment towards any community member or organiser in any form. Harassment includes any type of aggressive behaviour or offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. - second_para: The Code of Conduct is in place to protect every codebar member - students, coaches and organisers. If any member violates these rules the below procedure and sanctions will be implemented. - outcome_title: 3 types of outcomes - correction: Correction - The use of inappropriate language or other behavior deemed unprofessional or unwelcome in the codebar community. This includes the use of terminology that is discouraged, e.g. 'guys'. In this situation you will be sent a private message, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. - warning: Warning - You will receive an email warning. The organiser will explain the incident, including the impact on the person involved and the community. We will give as much information as possible, so you’re aware of what happened and try to learn from the incident. The organiser will add a note to your codebar profile so that all chapter organisers are aware of the incident. We expect you to take our comments on board, further action may be taken depending on your reaction. Examples of behaviour that will get you a warning include - targeted offensive language, or the sharing of sexual images in codebar spaces. 2 email warnings will result in a lifetime ban. - lifetime_ban: Lifetime ban - You will no longer be able to RSVP to any future codebar events. You will also be removed from codebar’s Slack workspace. Examples of behaviour that will get you an automatic lifetime ban include - physical intimidation, stalking, inappropriate physical contact, unwelcome sexual attention or repeated behaviour after you’ve been spoken to by someone from the codebar team (directors or chapter organisers). - closing_para: The above is only a starting point. The details of the incident may change how we view it, e.g. some verbal harassment may be so serious that we would give a lifetime ban. - how_to_support_us: - volunteer: - title: Volunteer with us - become_an_organiser: - title: Become an organiser - description: Champion inclusion and diversity in the tech industry as a workshop organiser with codebar. Your contribution will create an empowering and safe environment, fostering learning and collaboration among individuals exploring coding in our vibrant community. - link: Email us to become an organiser - become_a_coach: - title: Become a coach - description: Affect change as a volunteer coach with codebar - your expertise and guidance will pave the way for aspiring developers, unlocking the world of coding and creating opportunities for folks from groups under represented in the tech industry. - volunteer: - title: Other skills - description: Your unique abilities could be our missing piece in the codebar puzzle. Having a diverse range of skills in our team is necessary to enrich our community. From fundraising to event coordination to marketing, we always welcome new talent to drive our mission forward. - link: Email us to become a volunteer - fundraise: - title: Fundraise - description_html: "Join the codebar team with a physical challenge event. Whether you are a runner, swimmer, or cyclist, sign up with our registration form for your desired event and raise vital funds to help keep our events running. If your event does not appear below, feel free to drop us an email and we would be happy to coordinate with you." - image_alt: A Black British woman crosses the finish line at the Hackney Half Marathon in London in a shower of confetti while spectators cheer her on. - codebar_stories_podcast: - image_alt: codebar stories banner - opening: codebar Stories is a new podcast brought to you by codebar, we'll be smashing down the belief that tech isn't for you by sharing real-life stories from members of our community who have transitioned into a new career in tech. - contact_us_html: "Sponsoring codebar Stories offers you a unique opportunity to connect with a diverse, engaged audience within the tech community. As a podcast dedicated to empowering underrepresented groups through coding education, your brand will align with our values of diversity, inclusivity, and social impact. Through sponsorship, you'll gain visibility, build positive PR, and demonstrate your commitment to fostering the next generation of tech talent, all while supporting a meaningful cause. Sound good? Please drop us an email podcast@codebar.io." - - admin: - dashboard: - title: 'Admin' - jobs: - title: Administrar trabajos - info: - request_changes_html: Para solicitar cambios, envíe un correo electrónico a %{name} a %{email} - approved_by: Aprobado por %{name} el %{date}. - approved_by_no_date: Aprobado por %{name} - messages: - approved: "El trabajo ha sido aprobado y se ha enviado un correo electrónico a %{name} a %{email}" - cannot_approve: No puede aprobar ofertas de trabajo caducadas - confirm_approval: ¿Está seguro de que esta oferta de trabajo cumple con todos los requisitos y desea aprobarla? - unpublished: El trabajo se ha despublicado con éxito. - workshop: - manage_rsvps: - text: 'RSVP Estudiantes y Entrenadores al taller. Se activará el correo electrónico de confirmación de asistencia y se eliminarán de la lista de espera.' - destroy: - success: "Taller eliminado correctamente" - failure: "El taller no se puede eliminar. Esto se debe a que tiene invitados y/o la información del taller está en el sitio web durante un tiempo suficiente para que no se pueda eliminar." - messages: - meeting: - created: 'Reunión creada con éxito' - updated: 'Ha actualizado con éxito los detalles de esta reunión' - invitations_already_sent: 'Las invitaciones fueron enviadas previamente; no se volverán a enviar' - sending_invitations: 'Las invitaciones están siendo enviadas.' - invitation: - rsvp_member: "%{name} se ha agregado con éxito y se le notificó por correo electrónico." - already_on_list: "¡%{name} ya está en la lista!" - rsvp_error: "Algo salió mal, %{name} no se agregó." - update_rsvp: 'Asistencia actualizada de %{name}' - simple_form: - placeholders: - job: - company: 'p.ej. codebar' - company_website: 'p.ej. https://codebar.io' - title: 'p.ej. Internado' - description: 'Use texto o descuento para la descripción del trabajo' - location: 'e.g. London or Berlin' - hints: - job: - remote: Solo verifique si el rol es completamente remoto solo - salary: Pago anual antes de impuestos, sin comas ni puntos decimales - activerecord: - attributes: - job: - title: Título - company: Nombre - company_address: Dirección - company_postcode: Código postal - company_website: Sitio web - email: Email de contacto - link_to_job: Enlace a la publicación de empleo - expiry_date: Fecha de cierre de la solicitud - donation_platforms: - title: "Donate" - description: "Your support—whether through a one-time gift or ongoing commitment—drives our mission to create a more inclusive tech industry. It enables us to provide continuous learning opportunities and empower individuals from underrepresented groups to grow and thrive in tech." - link: "Find out how else to support us" - donation_form: - title: "Usa la página de donaciones" - text: "Make a lasting impact with codebar by giving a one-time donation or committing to a monthly contribution." - image_alt: "codebar logo" - github_sponsors: - title: "Github Sponsors" - text: "Support codebar’s mission directly through GitHub Sponsors and help shape the future of technology with your generous donation." - image_alt: "Github Sponsors logo" - open_collective: - title: "Open Collective" - text: "Configure una contribución recurrente o haga una donación única con Open Collective." - image_alt: "Open Collective logo" - give_as_you_live: - title: "Give as you Live" - text: "Give as you Live is a platform enabling you to raise funds for your favourite charity with your everyday online shopping." - image_alt: "Give as you Live logo" diff --git a/config/locales/fi.yml b/config/locales/fi.yml deleted file mode 100644 index 691ebb230..000000000 --- a/config/locales/fi.yml +++ /dev/null @@ -1,553 +0,0 @@ -fi: - brand: "codebar.io" - date: - formats: - default: "%d/%m/%Y" - email: "%a, %d %B at %H:%M" - email_title: "%A, %d %b at %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - website_format: "%a, %d %B %Y at %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y at %R" - dashboard: "%a, %d %b %Y, %H:%M" - time: - formats: - default: "%a, %d %b %Y %H:%M" - email: "%a, %d %B at %H:%M" - email_title: "%A, %d %b at %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - full_date: "%d %B %Y" - default_date: "%d/%m/%Y" - website_format: "%a, %d %B %Y at %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y at %R" - dashboard: "%A, %b %d" - number: - currency: - format: - unit: '£' - delimiter: ',' - separator: '.' - precision: 0 - format: '%u%n' - homepage: - intro: "codebar is a charity that facilitates the growth of a diverse tech community by running free regular programming workshops for minority groups in tech." - explanation: "Our goal is to enable people from underrepresented groups to learn programming in a safe and collaborative environment and expand their career opportunities. To achieve this we run free regular workshops, regular one-off events and try to create opportunities for our students making technology and coding more accessible." - participate: - students_title: "Students" - students_explanation_p1: "Our students come from diverse backgrounds—some aspiring to become full-time developers, while others simply want to learn the basics of coding in a supportive environment." - students_explanation_p2: "Join our vibrant community and take part in our workshops!" - students_button: "Join us as a student" - coaches_title: "Coaches" - coaches_explanation_p1: "We encourage new students to start with our tutorials on HTML/CSS, JavaScript, Ruby, Python, or Git, while also helping them grasp key programming concepts." - coaches_explanation_p2: "That’s why we’re always looking for more developers to join our community and coach at our workshops." - coaches_button: "Join us as a coach" - workshop_title: "Workshops" - workshop_explanation_p1: "We’re proud to be hosted by amazing companies that support our mission. Our typical format includes 30 minutes of socialising over food and drinks, a lightning talk, and then hands-on coding." - workshop_explanation_p2: "Help us grow and support our chapters by hosting or sponsoring our workshops, and together, we can expand opportunities for more aspiring developers." - workshop_button: "Let's work together" - workshop_email_subject: "Regarding hosting a workshop" - chapters: - title: "Chapters" - events: - upcoming: "Upcoming Events" - donation_platforms: - title: "How to support us" - mailer: - workshop_invitation: - attending: - subject: "Attendance Confirmation for %{date_time}" - attending_reminder: - subject: "Workshop Reminder %{date_time}" - invite_coach: - subject: "Workshop Coach Invitation %{date_time}" - invite_student: - subject: "Workshop Invitation %{date_time}" - notify_waiting_list: - subject: "A spot just became available" - waiting_list_reminder: - subject: "Reminder: you're on the codebar waiting list (%{date_time})" - messages: - accepted_invitation: "Thanks for getting back to us %{name}. See you at the workshop!" - already_invited: 'You have already RSVPd or joined the waitlist for this workshop.' - error_blank_note: 'You must select a note' - rejected_invitation: "We are so sad you can't make it, but thanks for letting us know %{name}." - already_rsvped: "You have already confirmed your attendance!" - not_attending_already: "You have already confirmed you can't make it!" - no_available_seats: "Unfortunately there are no more spaces left :(. If you would like to join our waiting list send us an email at %{email}" - feedback_saved: "Thank you for taking the time to give us feedback!" - feedback_not_found: "You have already submitted feedback for this event." - updated_note: "Successfully updated note." - invalid_session: 'Your session is invalid' - invitations: - meeting: - cancel: "Thanks for letting us know you can't make it." - rsvp: "Your RSVP was successful. We look forward to seeing you at the Monthly!" - rsvped_to_other_workshop: "You have already RSVP'd to another workshop on this date. If you would prefer to attend this workshop, please cancel your other RSVP first." - spot_confirmed: "Your spot has been confirmed for %{event}! We look forward to seeing you there." - spot_not_confirmed: 'Your spot has not yet been confirmed. We will verify your attendance after you complete the questionnaire.' - notifications: - provider_already_connected: 'You are already signed in!' - not_logged_in: "You must be logged in to access this page." - navigation: - dashboard: "Dashboard" - code_of_conduct: "Code of Conduct" - breach_code_of_conduct: "Breach Code of Conduct" - coach_guide: "Coach Guide" - student_guide: "Student Guide" - tutorials: "Tutorials" - becoming_sponsor: "Becoming a Sponsor" - faq: "FAQ" - blog: "Blog" - codebar_stories: "codebar Stories" - stats: "Stats" - dashboard: - join_workshops_in: "Join our free workshops in" - workshops_goal: "to get to grips with the basics of programming and web development." - tweets_by: "Tweets by" - latest_sponsors: "Latest Sponsors" - policy: - intro: "There’s high demand for our workshops and we have a waiting list on most weeks. To make sure as many people as possible can come, we have a straightforward attendance policy." - rule1: "Before you RSVP make sure you are eligible to attend. If you’re not sure get in touch for a chat." - rule2: "You must sign up and RSVP to attend our workshops." - rule3: "If you RSVP then later realise you can’t make it, you must cancel. It only takes a few seconds to do through your confirmation email." - rule4: "Please try to cancel with at least 24 hours notice." - rule5: "We know that sometimes things come up last minute, but even if you only cancel an hour before the workshop, get in touch and let us know." - what_happens: "What happens if I don’t respect the policy?" - strikes_system: "We operate a three strikes system. That means if you don’t come in without cancelling an RSVP three times, we will take you off our invite list for four weeks. We’ll get in touch after your first absence to make sure you understand this." - removing: "If you fail to attend without cancelling another three times, we might have to remove you permanently from our invitation list." - rsvping: "There is no penalty for RSVP-ing and then cancelling on a regular basis, but please avoid it. If you always struggle to make it in on a certain day then let us know – that kind of feedback is really important to us." - eligibility_note: "Another note on eligibility" - abuse: "We’re a fairly relaxed bunch and we trust you, so we don’t police students as to their eligibility. However if it ever looks like this is being abused we may have to change that – which we really don’t want to do." - reminder: "So please remember what these workshops are for – to open up tech to people that are underrepresented in the industry." - teacher_guide: - laptop: "You don't need a laptop for our workshops. You are there to watch and guide the students. If you don't feel comfortable with the tutorial you should spend time on it before coming if you want to help out." - keyboard: "Do not take over the keyboard! This can be off-putting and scary." - typing: "Encourage the students to type and not copy paste." - questions: "Explain that there are no bad questions." - mistakes: "Explain to students that it's OK to make mistakes." - introduction: "Always introduce yourself. Say why you want to help out and are spending your own time on this, why you like programming." - backgrounds: "Give your students the opportunity to get to know each other. Ask their names, why they are here, what they do in their day jobs. Encourage a brief discussion before starting." - limits: "Assume that anyone you're teaching has no knowledge but infinite intelligence." - collaboration: "Work collaboratively with your student. If you have two students, you should work with both. Don't focus all your attention on one of them." - discussion: "Let students have a go at answering the questions first. Help with open and leading questions. Encourage a discussion." - talk_slow: "Take it slow, you are the teacher, they are the student. Allow for time between questions." - mild_approach: "Don't say no when the students are not doing something right. Be gentle, approach it in a mild way." - paper: "Use pen and paper or go to a whiteboard! Often students are coming from a non-technical background. Drawing and explaining with visual material is really helpful." - stubling: "Let them stumble. We learn by making mistakes, getting frustrated, and working through problem in our own way. Be supportive, but let them explore." - suggestions: "Do you have something to suggest? Make a pull request or create an issue" - workshops: - already_wish_to_attend: 'You have already RSVPd or joined the waitlist for this workshop.' - lead: "Attend our workshops to learn programming in a safe and supportive environment at your own pace, or to share your knowledge and coach our students." - registration_not_open: 'This workshop is not open for registrations' - events: - title: "Events" - past: "Past" - no_upcoming_events: "There are no upcoming events." - view_past_events: "View past events" - view_all: "View all" - hosted_by: "Hosted by" - organisers: "Organisers" - venue_at: "at" - attend_as_student: "Attend as a student" - attend_as_coach: "Attend as a coach" - location: "Location" - sponsors: "Sponsors" - thx_to_sponsors: "A big thanks to all of our sponsors for making the event possible!" - coaches: "Coaches" - students: Students - schedule: "Schedule" - send_us_an_email: "send us an email" - not_open_for_rsvp: This event is not open for RSVP yet. - virtual: This is a virtual event. - faq: - experience: - q: "How experienced should I be to join the workshop?" - a: - contribution: - q: "What kind of contributions can I make?" - a: "Your contributions can be tiny, as simple as fixing a typo, to something incredible. You can help with documentation, fix a bug that you found, improve the copy, help with design or even tackle bigger tasks and help introduce new features. Every little helps!" - laptop: - q: "Do I need to bring a laptop?" - a_html: "Yes, you should bring a laptop. If you don't have one %{link} as we may be able to help." - keyboard: - q: "Do I need to bring a keyboard?" - a_html: "A keyboard would help as you will spend the entire day pairing with someone on your laptop. If you don't have a keyboard, %{link} and we'll try to organise something for you." - travel_costs: - q: "I will be commuting. Can you help with my travel expenses?" - a: "We will be offering some travel grants. Just make sure you fill in the questionnaire after you RSVP and we will get in touch." - coaches: - want_to_coach: "Do you want to coach at our workshops?" - read_before: "If you have not attended our workshops before, make sure you read our" - code_of_conduct: "code of conduct" - policy: "as we have a zero tolerance policy and expect everyone to behave appropriately. You should also go through our" - guide: "coaching guide" - unable_attend: "In case you are unable to attend after you RSVP, please make sure you come back and update your attendance as we rely on coaches showing up in order for our workshops to run smoothly." - food: "PS: There will also be food at the workshop. We always make an effort to have vegetarian, vegan and gluten-free options available. If you have any other dietary requirements, send us email at" - code_of_conduct: - title: "Code of conduct" - summary: - title: "The Quick Version" - intro: "Our events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of our members in any form. Sexual language and imagery is not appropriate for any of our events, including talks, workshops, parties, and online media. Members violating these rules may be sanctioned or expelled from the event and any future events at the discretion of the organisers." - content: - title: "The Long Version" - harassment: "Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention." - comply: "We expect any participants asked to stop any harassing behaviour to comply immediately." - sponsors: "Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment." - sanctions: "If a participant engages in harassing behaviour the organisers may take any action they deem appropriate. This includes warning the offender or expulsion." - concerns: "If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact one of the organisers immediately." - applies_to: "We expect participants to follow these rules at all codebar events. If they fail to do so, the following process will take place." - questions: "If you have any questions or concerns about this code please" - contact: "contact us" - email_subject: "Regarding code of conduct" - sponsors: - sponsoring: "Sponsoring" - members: - sign_up: "Join our community" - sign_in_with_github: "Sign in with GitHub" - sign_up_as_student: "Join us as a student" - sign_up_as_student_disclaimer: "* I understand and meet the eligibility criteria." - sign_up_as_coach: "Join us as a coach" - code_of_conduct: "code of conduct" - new: - intro_html: "We provide a welcoming, inclusive, and supportive learning environment, with a strict zero-tolerance policy for any form of harassment or inappropriate behavior. Please take a moment to review our code of conduct before signing up." - students: - intro_html: "If you’re interested in attending as a student, be sure to check our eligibility criteria. Our workshops and events are exclusively for women, non-binary, LGBTQ+ members, and people from underrepresented groups." - github: "When you click the sign-up button, you'll be redirected to GitHub. After logging in with your GitHub account, you'll return to the codebar website. If you don’t have an account yet, creating one is quick and easy—and it will be useful as you begin your coding journey!" - invitations: "Invitations are sent out periodically, so don't worry if you don't receive one as soon as you register." - footer: - email_us: "Send us an email at" - contact_info: "Contact Info:" - faq: - payment: - q: "Do I need to pay to attend codebar?" - a_p1: "Absolutely not! We are lucky enough to have some great companies who are able to host the workshops and/or kindly provide food. And our" - awesome_coaches: "awesome coaches" - a_p2: "give their time freely to help the community." - technologies: - q: "What technologies do you teach?" - a: "We have a variety of available tutorials in HTML, CSS, JavaScript and Ruby. If you want to learn something else don't hesitate to send us an email as we might still be able to find someone to help you out." - eligibility: - q: "I want to attend a workshop. Am I eligible?" - a: "Our workshops are available to women, LGBTQ and people who are underrepresented in the tech industry. If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School London where you can learn in a collaborative environment. Please see our student guide for more information." - career: - q: "Is codebar only aimed at people who want to move into a career as a developer?" - a: "No! codebar is about getting people excited about programming. We'll help them learn some basic coding skills, as well as how to explore and do things on their own. For those who do want to become developers, we will provide help and guidance to help them achieve their goal." - format: - q: "What is the format of the workshops?" - a: "We try to have one coach for every two students. We will pair up students who want to work on the same tutorial, and assign them a coach. The rest just happens." - laptop: - q: "Do I need to bring a laptop with me at the workshops?" - a: "Yes, we suggest that you bring a laptop as it will be easier for you to carry on working on things after the workshops. It you don't have one, send us an email so we can try and help out." - online_resources: - q: "There are so many online resources, why should I come to codebar?" - a: "Coding can be intimidating and a lot of people find it hard to get started. By putting you in touch with people who can help and guide you we make the experience and learning process easier and more enjoyable." - preperations: - q: "I would like to coach at codebar. Is there anything I should do besides signing up?" - a_p1: "Yes. First you should read our" - coaching_guide_tutorials: "coaching guide tutorials" - a_p2: ". Then spend sometime familiarising yourself with the" - a_p3: "tutorials. The tutorials are open source so if there is something that you want to improve open an issue on the GitHub repository or send a pull request." - a_p4: "We don't expect the coaches to be familiar with all the technologies and languages we have material on." - location: - q: "Where do the workshops take place?" - a: "As we don't have a permanent venue, our workshops are hosted by different companies in various locations around London. So far we've run workshops in Shoreditch, London Bridge, Holborn and Kings Cross." - disabled_access: - q: "Is there disabled access at the workshops?" - a: "Unfortunately, that depends entirely on where we are hosting our workshops and if the venue has disabled access. If you would like to attend, send us an email at meetings[at]codebar.io so we can enquire about it and let you know." - bring_codebar_to_my_city: - q: "I would like to bring codebar to my city. Can I do that?" - a: "Of course. codebar is about building a community of experienced developers that are able to give up some of their time to help others. If you are keen on running codebar where you live, we would love to speak to you about it and see how we can help make this happen, so send us an email." - our_coaches: - q: "Our coaches" - a_p1: "You can see all the coaches have helped out in our workshops on the" - a_p2: ". They are ordered by number of attendances. This is our way of showing our appreciation to them, as without them, we wouldn't be able to exist." - participant_student_guide: - title: "Student Guide" - attendance_policy: - title: "Attendance Policy" - intro: "codebar is, and always has been, open to all levels of coding experience. While most of the tutorials on our website are aimed at newcomers to web development, we intend to continue our open-door policy for any student who needs coach support on their own projects. Due to the fact that our workshops are frequently oversubscribed, we ask students to respect the following expectations for participation in our workshops" - rule1: "In order to attend a workshop, you must be on the RSVP list. If you have not RSVP’d or were not allocated a spot, you will not be admitted into a workshop." - rule2: "If you can no longer attend a workshop, please cancel your RSVP by 12:00 latest on the day of the workshop. We understand that last-minute emergencies occur -- if this is the case, please get in touch with an organizer directly as soon as possible. Repeated no-shows will result in temporary or permanent suspension of your invitations." - rule3: "No guests are allowed. Our workshops are already overcrowded and we cannot make any exceptions. If your friend meets our eligibility criteria, get them to sign up and RSVP themselves." - rule4: "Please be respectful of our hosts. Do not show up exceedingly early to a workshop (not earlier than 15 minutes before the event begins) and try to leave the workstation clean and as you found it." - rule5: "Please do not work on projects that were assigned as part of any bootcamp or university curriculum. Talk to your course adviser if you feel like you need additional support with your coursework. We welcome your attendance, but we encourage you to use your time at codebar to develop skills that are outside the normal scope of your studies." - rule6: "Do not bring along and ask for help with any commercial work. This involves work you're being paid to do." - rule7: "Projects that involve specific frameworks/libraries (Rails, NodeJS, Meteor, Angular, Ember, React, etc) or languages that are not part of the codebar tutorials (anything other than Ruby or Javascript) are welcome but we cannot guarantee that a coach will be available to help you. In these cases we recommend selecting a codebar tutorial or katas (codewars.com or exercism.io) as a back-up option." - eligibility_criteria: - title: "Eligibility Criteria" - p_1: "codebar was started out of recognition that there is a shortage of women, LGBTQ, and people belonging to underrepresented ethnic groups in tech." - p_2: "If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School or Ask a Dev where you can learn in a collaborative environment." - p_3: "Bearing that in mind, it is sometimes difficult for us to identify whether attendees meet the eligibility criteria based on their first and last names. If we cannot determine your eligibility, we will contact you asking for a short confirmation that you have read this document and assert that you meet one or more of the criteria. We will never ask participants to specify which group." - p_4: "codebar is first and foremost a resource for students who cannot afford formal training through coding bootcamps or university degrees, for financial reasons or otherwise. Our coaches, organisers and sponsors donate their time and money to help those who have faced unfair barriers to entry into the tech world. We have strived to create an inclusive, welcoming community, and so far, we have not had to implement a formal policy to enforce the eligibility criteria -- we have left this to the honesty and good faith of the students." - p_5: "If you are unsure whether you are eligible, please get in touch. If we determine that you have signed up and do not belong to an eligible group, we will permanently suspend your student invitations without warning." - p_6: "We take this issue very seriously, and we appreciate your cooperation and understanding." - disability: - title: "Students with Disability" - description: "We want to ensure that our workshops are as accessible as possible. If you are disabled and are unsure about whether our venues can cater to your needs, we encourage you to please get in touch with us at hello@codebar.io and we will do what we can to accommodate you." - chapters: - intro_html: "Hi and welcome to codebar!" - info: "Check out our FAQ page for any questions you might have, or email us at %{email} if you can't find the answer you're looking for. Otherwise, click the Join our community button to join us." - sign_up: "to be invited to our workshops." - no_incoming: "There are no workshops coming up." - contact: "To contact the %{city} team, send an email to %{email}" - feedback_form: - title: 'Workshop feedback' - description: Your submission will be completely anonymous. We read every piece of feedback and use it to help us improve our workshops. - note: Please do not mention any names, but instead choose your coach from the dropdown. This enables us to address issues but also to anonymously share feedback with coaches. Member privacy is very important to us! - rating: Your overall rating of the workshop - coach: 'Who was your coach?' - select_coach: '- Select Coach -' - tutorial: 'What tutorial did you go through?' - select_tutorial: '- Select Tutorial -' - request: 'How did you find the workshop?' - suggestions: "Was there something you didn't like? What can we do to improve your experience?" - pages: - cookies: - title: Cookie Policy - p1: 'Cookies are small pieces of text used to store information on web browsers. They are used by websites accross a number of different devices to store and receive identifiers and other information. Our Website and Service use cookies and other similar technologies (collectively in this Policy, "cookies"), in order to provide a better service to you and to generally improve our Website and Service. For example, we may use cookies to help direct you to the appropriate part of our Website, by indicating that you are a repeat visitor. We also may use information to present you with services that are matched to your preferences and to manage and track the effectiveness of our marketing efforts.' - p2: Some portions of the codebar website are functional without cookies, and you may generally choose whether to accept cookies. Most web browsers are set to accept cookies by default, however, you may be able to delete cookies yourself through your browser's cookie manager. To do so, please follow the instructions provided by your web browser. Please note that disabling cookies will reset your session, disable auto-login, and may adversely affect the availability and functionality of our Website and the services we can provide to you. - sub: - title: Below are the cookies used by the codebar website. - table: - header: - h1: Name - h2: Purpose - h3: Expires - functional: - title: Functional Cookies - description: Stores information about your session. - planner_name: _planner_session - planner_purpose: Stores session data - planner_expiry: Expires after 24 hours - google_analytics: - title: Google Analytics - description: Google Analytics collects information about how you use the codebar website. This enables us to identify how busy the website is and possible improvements. - info: We don’t allow Google to use or share our analytics data. - opt_out: You can [opt out of Google Analytics](https://tools.google.com/dlpage/gaoptout). - ga_name: _ga - ga_purpose: Tracks if you have visited codebar.io before - ga_expiry: After 2 years - gid_name: _ga - gid_purpose: Tracks if you have visited codebar.io before - gid_expiry: After 24 hours - cloudflare: - title: Cloudflare - cfduid_name: _pfduid - cfduid_purpose: Used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. - cfduid_expiry: 1 year - privacy_policy: - title: Privacy Policy - subtitle: This Privacy Policy was last updated on 13 May 2021. - intro: - p1: 'This Privacy Policy has been created by codebar ("codebar", "we", "us", or "our") whose companies house registered name and address is as follows:' - address_html: " - codebar Ltd,
- International House,
- 101 King's Cross Road,
- London, England,
- WC1X 9LP
- Company No. 10791813
" - p2: codebar Ltd trades on behalf of the charity registered UK and Wales no. 1187776. For the purpose of this Privacy Policy codebar Ltd is the data controller. - p3: Your privacy means a lot to us, and we take it very seriously. We aim to be transparent with you about the data we collect about you and how it is used and shared. This Privacy Policy lets you know what information we collect when you use the codebar website, https://codebar.io/, or interact with any of the services we provide, such as signing up to workshops and events ("Services"). By using our Services you acknowledge and understand our use of your data under this Privacy Policy and how it applies to your use of our Services. - information: - title: 1. Information we collect - what_we_collect: - title: 1.1 Personal data we collect from you - p1: 'We have set out in the table below the personal data we collect about you and how we use it, which will differ based on the capacity in which you interact with codebar:' - table: - headers: - h1: Who - h2: What data we process - h3: What we use it for - h4: Lawful basis - r1: - c1: Students - c2: This includes personal data that is provided by you or collected by us to enable you to subscribe to codebar as a student. This may include your name, email address, phone number, pronouns, self-written bio, , your self-recognition as being underrepresented (with your consent), and the location you choose to subscribe to. - c3: For administrative purposes when you sign up to events, to communicate with you, and to provide you with our newsletters and events information. - c4: - l1: Performance of a contract - l2: Consent - l3: Legitimate interests - r2: - c1: Coaches - c2: This includes personal data that is provided by you or collected by us to enable you to volunteer at codebar as a coach. This may include your name, email address, phone number, pronouns, self-written bio/skills, , your self-recognition as being underrepresented (with your consent), and the location you choose to volunteer at. - c3: For administrative purposes when you volunteer for workshops, to communicate with you, to manage workshop attendance, and to provide you with our newsletters and events information. - c4: - l1: Consent - l2: Legitimate interests - r3: - c1: Organizers - c2: This includes personal data that is provided by you or collected by us, which may include your name, email address, phone number, pronouns, self-written bio/skills, , slack username, signed documentation, and the location you choose to volunteer at. - c3: To organise and communicate workshops. - c4: - l1: Legitimate interests - r4: - c1: Hosts - c2: We may collect personal information of employees working at companies that agree to host our workshops. This information may include the employees' name, email address, contact number, , and place of work. - c3: In order to market, promote, host and operate workshops. - c4: - l1: Legitimate interests - r5: - c1: Sponsors - c2: We need to collect personal data in relation to your sponsorship of codebar. This may include information such as your name, and bank details. - c3: To fulfill contractual obligations we have with you, for example, to process invoices related to your sponsorship. - c4: - l1: Performance of a contract - l2: Legitimate interests - r6: - c1: Trustees and directors - c2: We need to collect personal data in relation to your position as trustee and/or director. This may include information such as your name, contact number, address, email address, and date of birth. - c3: In order to establish our status as a charity, to comply with legal obligations, and respond to legal requests. - c4: - l1: Legitimate interests - l2: Compliance with legal obligations - how_we_share: - title: 1.2 How we share your information - p1_html: 'When you subscribe to an event, we share your name with our host companies as we are required to provide a list with all attendee names when you subscribe to any of our events. We **do not share** your email address or any other personal information.' - legal_basis: - title: 1.3 Legal basis for our use of your personal information - p1: As set out in the table above, sometimes the legal basis on which we collect and process your data is because our legitimate interests make the processing necessary, and those legitimate interests are not overridden by your interests or fundamental rights and freedoms. For example, we collect and store your data in order to process event information, and to ensure the efficient running and promotion of workshops. - retention: - title: 2. Retention - p1: We will keep your personal information for as long as reasonably necessary to fulfil the purposes we collected it for. To determine the appropriate retention period, we consider the amount, nature and sensitivity of the personal information, the potential risk of harm from unauthorised use or disclosure of your personal information, the purposes for which we process your personal data and whether we can achieve those purposes through other means, and the applicable legal, regulatory, tax, accounting or other requirements. - p2: We may retain your personal information for a longer period in the event of a complaint or if we reasonably believe there is a prospect of dispute in respect to our relationship with you. - international_transfers: - title: 3. International transfers - p1: Personal information we collect may be transferred to and stored in countries outside of the jurisdiction you are in for the purposes specified in this Privacy Policy. We will only transfer your personal information to countries that have been deemed to provide an adequate level of protection for personal information, and/or any international transfers will be made pursuant to appropriate safeguards in accordance with the applicable laws and regulations, such as standard data protection clauses adopted by the UK and European Commission. - p2: If you wish to enquire further about these safeguards used, please contact us by email at the address below or by mail using the postal address provided below. - your_rights: - title: 4. Your data protection rights - p1: 'Data protection law provides you with rights in respect of personal data that we hold about you, including the:' - l1: 'Right to Access: You have the right to obtain access to your data, and certain other information (similar to that provided in this Privacy Policy).' - l2: 'Right to Rectification: You are entitled to have your data corrected if it is inaccurate or incomplete.' - l3: 'Right to Erasure: This enables you in some circumstances to request and obtain the deletion of your data where there is no legal reason for us to keep using it.' - l4: 'Right to Restriction of Processing: You have rights to suspend further use of your data, whereby we can still store your data but cannot use it further. This may mean we can no longer provide you with Services.' - l5: 'Right to Data Portability: You have rights in some circumstances to request the transfer of your data to yourself or to a third party.' - l6: 'Right to Objection: You have the right to object to certain types of data processing, including for direct marketing purposes.' - l7: 'Right to Withdrawal of Consent: Where we are relying on consent to process your data, you have the right to withdraw your consent at any time by using any opt-out links, or by contacting us at the details provided below (although if you do so, it does not mean that anything we have done with your data with your consent up to that point is unlawful and we may be able to continue to process your personal information to the extent required or otherwise permitted by law, in particular in connection with exercising and defending our legal rights or meeting our legal and regulatory obligations).' - l8: 'Right to Lodge a Complaint: You can lodge a complaint in relation to our use of your personal information with the local supervisory authority, the Information Commissioner (UK).' - p2: If you would like to exercise any of these rights or if you have a complaint about how we handle your data, please contact us at the email address stated below. - security: - title: 5. Security - p1: The security of your personal information is important to us. codebar takes reasonable steps to implement and update administrative, technical, and physical security measures to help protect your information against unauthorised access, loss, destruction, or alteration. However, the Internet is not a 100% secure environment so we can't guarantee the security of the transmission or storage of your information. codebar has no control over or responsibility for the security or practices or privacy policies of third parties, even if you interact with them when using our Services. - changes: - title: 6. Changes to this Privacy Policy - p1: We reserve the right to modify or update this Privacy Policy at any time in accordance with this provision. If we make changes to this Privacy Policy, we will post the revised Privacy Policy on the codebar website. Please regularly review https://codebar.io/privacy-policy to check for any updates or changes to our Privacy Policy. The date this Privacy Policy was last revised is identified at the top of this page. - cookies: - title: 7. Cookies - p1_html: 'We use cookies to recognise you and your location. You can control cookies through your browser settings and other tools. For more information read our [cookie policy](https://codebar.io/cookie-policy).' - contact: - title: 8. Contact - p1: "If you have any questions or complaints about this Privacy Policy or our information handling practices, you may email us at company@codebar.io stating 'Data inquiry' in the subject title, or by postal mail at: codebar Ltd, International House, 101 King's Cross Road, London, WC1X 9LP." - breach: - title: What happens if you violate codebar’s Code of Conduct? - opening_para: All codebar events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment towards any community member or organiser in any form. Harassment includes any type of aggressive behaviour or offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. - second_para: The Code of Conduct is in place to protect every codebar member - students, coaches and organisers. If any member violates these rules the below procedure and sanctions will be implemented. - outcome_title: 3 types of outcomes - correction: Correction - The use of inappropriate language or other behavior deemed unprofessional or unwelcome in the codebar community. This includes the use of terminology that is discouraged, e.g. 'guys'. In this situation you will be sent a private message, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. - warning: Warning - You will receive an email warning. The organiser will explain the incident, including the impact on the person involved and the community. We will give as much information as possible, so you’re aware of what happened and try to learn from the incident. The organiser will add a note to your codebar profile so that all chapter organisers are aware of the incident. We expect you to take our comments on board, further action may be taken depending on your reaction. Examples of behaviour that will get you a warning include - targeted offensive language, or the sharing of sexual images in codebar spaces. 2 email warnings will result in a lifetime ban. - lifetime_ban: Lifetime ban - You will no longer be able to RSVP to any future codebar events. You will also be removed from codebar’s Slack workspace. Examples of behaviour that will get you an automatic lifetime ban include - physical intimidation, stalking, inappropriate physical contact, unwelcome sexual attention or repeated behaviour after you’ve been spoken to by someone from the codebar team (directors or chapter organisers). - closing_para: The above is only a starting point. The details of the incident may change how we view it, e.g. some verbal harassment may be so serious that we would give a lifetime ban. - how_to_support_us: - volunteer: - title: Volunteer with us - become_an_organiser: - title: Become an organiser - description: Champion inclusion and diversity in the tech industry as a workshop organiser with codebar. Your contribution will create an empowering and safe environment, fostering learning and collaboration among individuals exploring coding in our vibrant community. - link: Email us to become an organiser - become_a_coach: - title: Become a coach - description: Affect change as a volunteer coach with codebar - your expertise and guidance will pave the way for aspiring developers, unlocking the world of coding and creating opportunities for folks from groups under represented in the tech industry. - volunteer: - title: Other skills - description: Your unique abilities could be our missing piece in the codebar puzzle. Having a diverse range of skills in our team is necessary to enrich our community. From fundraising to event coordination to marketing, we always welcome new talent to drive our mission forward. - link: Email us to become a volunteer - fundraise: - title: Fundraise - description_html: "Join the codebar team with a physical challenge event. Whether you are a runner, swimmer, or cyclist, sign up with our registration form for your desired event and raise vital funds to help keep our events running. If your event does not appear below, feel free to drop us an email and we would be happy to coordinate with you." - image_alt: A Black British woman crosses the finish line at the Hackney Half Marathon in London in a shower of confetti while spectators cheer her on. - codebar_stories_podcast: - image_alt: codebar stories banner - opening: codebar Stories is a new podcast brought to you by codebar, we'll be smashing down the belief that tech isn't for you by sharing real-life stories from members of our community who have transitioned into a new career in tech. - contact_us_html: "Sponsoring codebar Stories offers you a unique opportunity to connect with a diverse, engaged audience within the tech community. As a podcast dedicated to empowering underrepresented groups through coding education, your brand will align with our values of diversity, inclusivity, and social impact. Through sponsorship, you'll gain visibility, build positive PR, and demonstrate your commitment to fostering the next generation of tech talent, all while supporting a meaningful cause. Sound good? Please drop us an email podcast@codebar.io." - - admin: - dashboard: - title: 'Admin' - workshop: - manage_rsvps: - text: 'RSVP Students and Coaches to the workshop. The attendance confirmation email will be triggered and they will be removed from the waiting list.' - destroy: - success: "Workshop deleted successfully" - failure: "Workshop cannot be deleted. This is because it has invitees and/or workshop information is on the website for a while long enough that it cannot be deleted." - messages: - meeting: - created: 'Meeting successfully created' - updated: 'You have successfully updated the details of this meeting' - invitations_already_sent: 'Invitations were previously sent; they will not be sent again' - sending_invitations: 'Invitations are being sent out' - invitation: - rsvp_member: "%{name} has been successfully added and notified via email." - already_on_list: "%{name} is already on the list!" - rsvp_error: "Something went wrong, %{name} has not been added." - update_rsvp: 'Updated attendance of %{name}' - simple_form: - placeholders: - job: - company: 'e.g. codebar' - company_website: 'e.g. https://codebar.io' - title: 'e.g. Internship' - description: 'Use text or markdown for the job description' - location: 'e.g. London or Berlin' - hints: - job: - remote: Only check if the role is fully remote only - salary: Annual pay before tax, without commas or decimal points - activerecord: - attributes: - job: - title: Title - company: Name - company_address: Address - company_postcode: Postcode - company_website: Website - email: Contact email - link_to_job: Link to job post - expiry_date: Application closing date - donation_platforms: - title: "Donate" - description: "Your support—whether through a one-time gift or ongoing commitment—drives our mission to create a more inclusive tech industry. It enables us to provide continuous learning opportunities and empower individuals from underrepresented groups to grow and thrive in tech." - link: "Find out how else to support us" - donation_form: - title: "Use the donation page" - text: "Make a lasting impact with codebar by giving a one-time donation or committing to a monthly contribution." - image_alt: "codebar logo" - github_sponsors: - title: "Github Sponsors" - text: "Support codebar’s mission directly through GitHub Sponsors and help shape the future of technology with your generous donation." - image_alt: "Github Sponsors logo" - open_collective: - title: "Open Collective" - text: "Setup a recurring contribution or make a one-time donation through Open Collective." - image_alt: "Open Collective logo" - give_as_you_live: - title: "Give as you Live" - text: "Give as you Live is a platform enabling you to raise funds for your favourite charity with your everyday online shopping." - image_alt: "Give as you Live logo" diff --git a/config/locales/fr.yml b/config/locales/fr.yml deleted file mode 100644 index 9cf9c1723..000000000 --- a/config/locales/fr.yml +++ /dev/null @@ -1,552 +0,0 @@ -fr: - brand: "codebar.io" - date: - formats: - default: "%d/%m/%Y" - email: "%a, %d %B à %H:%M" - email_title: "%A, %d %b à %H:%M" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - website_format: "%a, %d %B %Y à %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "à %H:%M le %d/%m/%Y" - workshop: "%A, %e %B %Y à %R" - dashboard: "%a, %d %b %Y, %H:%M" - time: - formats: - default: "%a, %d %b %Y %H:%M" - email: "%a, %d %B à %H:%M" - email_title: "%A, %d %b à %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - default_date: "%d/%m/%Y" - website_format: "%a, %d %B %Y à %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y à %R" - dashboard: "%A, %b %d" - number: - currency: - format: - unit: '£' - delimiter: ',' - separator: '.' - precision: 0 - format: '%u%n' - homepage: - intro: "codebar is a charity that facilitates the growth of a diverse tech community by running free regular programming workshops for minority groups in tech." - explanation: "Our goal is to enable people from underrepresented groups to learn programming in a safe and collaborative environment and expand their career opportunities. To achieve this we run free regular workshops, regular one-off events and try to create opportunities for our students making technology and coding more accessible." - participate: - students_title: "Students" - students_explanation_p1: "Our students come from diverse backgrounds—some aspiring to become full-time developers, while others simply want to learn the basics of coding in a supportive environment." - students_explanation_p2: "Join our vibrant community and take part in our workshops!" - students_button: "Join us as a student" - coaches_title: "Coaches" - coaches_explanation_p1: "We encourage new students to start with our tutorials on HTML/CSS, JavaScript, Ruby, Python, or Git, while also helping them grasp key programming concepts." - coaches_explanation_p2: "That’s why we’re always looking for more developers to join our community and coach at our workshops." - coaches_button: "Join us as a coach" - workshop_title: "Workshops" - workshop_explanation_p1: "We’re proud to be hosted by amazing companies that support our mission. Our typical format includes 30 minutes of socialising over food and drinks, a lightning talk, and then hands-on coding." - workshop_explanation_p2: "Help us grow and support our chapters by hosting or sponsoring our workshops, and together, we can expand opportunities for more aspiring developers." - workshop_button: "Let's work together" - workshop_email_subject: "Regarding hosting a workshop" - chapters: - title: "Chapters" - events: - upcoming: "Upcoming Events" - donation_platforms: - title: "How to support us" - mailer: - workshop_invitation: - attending: - subject: "Attendance Confirmation for %{date_time}" - attending_reminder: - subject: "Workshop Reminder %{date_time}" - invite_coach: - subject: "Workshop Coach Invitation %{date_time}" - invite_student: - subject: "Workshop Invitation %{date_time}" - notify_waiting_list: - subject: "A spot just became available" - waiting_list_reminder: - subject: "Reminder: you're on the codebar waiting list (%{date_time})" - messages: - accepted_invitation: "Merci d'avoir confimer %{name}. À bientot à l'atelier!" - already_invited: 'You have already RSVPd or joined the waitlist for this workshop.' - error_blank_note: 'You must select a note' - rejected_invitation: "Désolé que vous ne puissiez pas venir, mais merci %{name} de nous avoir tenu au courant." - already_rsvped: "Vous avez déjà réserver votre place!" - not_attending_already: "Vous avez déjà confimer que vous ne pouvez pas venir!" - no_available_seats: "Il n'y a malheuresement plus de places disponible :(. Si vous souhaitez joindre la liste d'attente merci de nous envoyer un email à %{email}" - feedback_saved: "Merci d'avoir pris le temps de nous laisser un commentaire!" - feedback_not_found: "Vous avez déjà laisser un commentaire à propos de cet évènement." - updated_note: "Votre commentaire à bien été mis à jour." - invalid_session: 'Your session is invalid' - invitations: - meeting: - cancel: "Thanks for letting us know you can't make it." - rsvp: "Your RSVP was successful. We look forward to seeing you at the Monthly!" - rsvped_to_other_workshop: "You have already RSVP'd to another workshop on this date. If you would prefer to attend this workshop, please cancel your other RSVP first." - spot_confirmed: "Your spot has been confirmed for %{event}! We look forward to seeing you there." - spot_not_confirmed: 'Your spot has not yet been confirmed. We will verify your attendance after you complete the questionnaire.' - notifications: - provider_already_connected: 'Vous êtes déjà connecter!' - not_logged_in: "Vous devez être connecter pour accéder à cette page." - navigation: - dashboard: "Dashboard" - code_of_conduct: "Code de Conduite" - breach_code_of_conduct: "Breach Code of Conduct" - coach_guide: "Guide enseignant" - student_guide: "Guide étudiant" - tutorials: "Tutoriels" - becoming_sponsor: "Devenir un sponsor" - faq: "FAQ" - blog: "Blog" - codebar_stories: "codebar Stories" - stats: "Statistiques" - dashboard: - join_workshops_in: "Rejoignez nos ateliers gratuit" - workshops_goal: "pour apprendre les bases de la programmation et du développement web." - tweets_by: "Tweets par" - latest_sponsors: "Les derniers Sponsors" - policy: - intro: "Il y a une forte demande pour nos ateliers et il y a une liste d'attente pratiquement toutes les semaines. Pour être certain qu'un maximum de personnes puissent venir, nous avons une politique d'assiduité stricte." - rule1: "Avant de vous enregistrer merci de vous assurer que vous êtes éligible. Si vous n'êtes pas sure n'hésitez pas à nous contacter." - rule2: "Vous devez vous enregistrer pour venir à nos ateliers." - rule3: "Si vous vous êtes enregister et que vous réaliser que vous ne pouvez plus venir, vous devez laisser votre place à quelqu'un d'autre. Cela ne prend que quelques secondes à faire depuis l'email de confirmation." - rule4: "Essayez d'annuler si possible avec un délai de 24 heures." - rule5: "Il est possible que certaines choses arrivent à la dernière minute, si cela arrive même une heure avant l'atelier, envoyez nous un petit message." - what_happens: "Que se passe t-il si je ne respecte pas les conditions?" - strikes_system: "Nous avons un système avec trois avertissements. Cela veux dire que si vous n'êtes pas présent trois fois, nous vous retirerons de notre listes de participants pour un mois. Nous vous enverrons un message après votre première absence pour s'assurer que vous ayez connaissance de cette règle." - removing: "Si vous êtes absent trois fois de plus, nous devrons vous retirer de facon permanente de nos invitations." - rsvping: "Il n'y a pas de sanctions pour s'enregisrer et annuler par la suite, mais essayer d'éviter dans la mesure du possible. Si il vous est difficile de vous rendre disponible un certain jour, dites le nous, ce genre de retour nous est important pour nous." - eligibility_note: "Un autre commentaire sur nos critères d'èligibilité" - abuse: "Nous sommes plutot souple et nous vous faisons confiance, nous ne vous demanderons rien à propos de votre éligibilité. Mais si nous semble que vous abusez le système nous devrons peut-être changer les régles (ce que nous ne voulons vraiment pas faire)." - reminder: "Donc, merci de vous rappeler pourquoi nous faisons ces ateliers – pour ouvrir la tech à ceux qui sont sous représentés dans le secteur." - teacher_guide: - laptop: "You don't need a laptop for our workshops. You are there to watch and guide the students. If you don't feel comfortable with the tutorial you should spend time on it before coming if you want to help out." - keyboard: "Do not take over the keyboard! This can be off-putting and scary." - typing: "Encourage the students to type and not copy paste." - questions: "Explain that there are no bad questions." - mistakes: "Explain to students that it's OK to make mistakes." - introduction: "Always introduce yourself. Say why you want to help out and are spending your own time on this, why you like programming." - backgrounds: "Give your students the opportunity to get to know each other. Ask their names, why they are here, what they do in their day jobs. Encourage a brief discussion before starting." - limits: "Assume that anyone you're teaching has no knowledge but infinite intelligence." - collaboration: "Work collaboratively with your student. If you have two students, you should work with both. Don't focus all your attention on one of them." - discussion: "Let students have a go at answering the questions first. Help with open and leading questions. Encourage a discussion." - talk_slow: "Take it slow, you are the teacher, they are the student. Allow for time between questions." - mild_approach: "Don't say no when the students are not doing something right. Be gentle, approach it in a mild way." - paper: "Use pen and paper or go to a whiteboard! Often students are coming from a non-technical background. Drawing and explaining with visual material is really helpful." - stubling: "Let them stumble. We learn by making mistakes, getting frustrated, and working through problem in our own way. Be supportive, but let them explore." - suggestions: "Do you have something to suggest? Make a pull request or create an issue" - workshops: - already_wish_to_attend: 'You have already RSVPd or joined the waitlist for this workshop.' - lead: "Attend our workshops to learn programming in a safe and supportive environment at your own pace, or to share your knowledge and coach our students." - registration_not_open: 'This workshop is not open for registrations' - events: - title: "Évènements" - past: "Passé" - no_upcoming_events: "Il n'y a pas d'èvènements futur." - view_past_events: "Voir les èvèment passé" - view_all: "Voir tout" - hosted_by: "Hébergé par" - organisers: "Organisateurs" - venue_at: "à" - attend_as_student: "S'inscrire étudiant" - attend_as_coach: "Inscription enseignant" - location: "Emplacemnet" - sponsors: "Sponsors" - thx_to_sponsors: "Un grand merci à tous nos sponsors qui ont fait de cet évènement une réalité!" - coaches: "Enseignants" - students: Students - schedule: "Programme" - send_us_an_email: "envoyez nous un email" - not_open_for_rsvp: Il n'est pas encore possible de s'inscrire pour cet évènement. - virtual: This is a virtual event. - faq: - experience: - q: "Me faut-il beaucoup d'expérience pour m'inscrire à un atelier?" - a: - contribution: - q: "Quel type de contributions puis-je faire?" - a: "Vos contributions peuvent-être, aussi simple que de corriger un faute, ou quelque chose d'incroyable. Vous pouvez aider à rédiger la documentation, corriger un bug que vous avez trouver, améliorer notre design ou même commencer des tâches encore plus grandes et ajouter de nouvelles fonctionallités. Toutes contributions compte!" - laptop: - q: "Dois-je amener un ordinateur portable?" - a_html: "Oui, vous devriez amener un ordinateur. Si vous n'en avez pas %{link} pourra peut-être aider." - keyboard: - q: "Dois-je apporter un clavier?" - a_html: "Un clavier pourrais vous aider vu que vous allez passer toute la journée avec quelqu'un sur votre ordinateur. Si vous n'avez pas de clavier, %{link} et nous essaierons de vous trouver quelque chose." - travel_costs: - q: "Je voyage de loin. Pouvez-vous m'aider avec mes frais de déplacements?" - a: "Nous offrons des bourses de voyage. Vous devez vous assurer de remplir le questionnaire après vous être enregistrer et nous vous contacterons." - coaches: - want_to_coach: "Voulez vous enseigner à nos ateliers?" - read_before: "Si vous n'êtes jamais venu a nos ateliers, merci de lire notre" - code_of_conduct: "code de conduite" - policy: "vu que nous attendons que chacun se comporte correctement. Vous devriez aussi lire notre" - guide: "guide pour les enseignants" - unable_attend: "Si vous n'êtes plus disponibles après vous être inscris, merci de revenir et mettre à jour vos informations vu que nous avons besoin des enseignants pour que nos ateliers fonctionnent." - food: "PS: Il y aura de la nourriture à nos ateliers. Nous faisons toujours un effort pour avoir des choix végétariens, vegan and sans gluten. Si vous avez des allergies alimentaires envoyez nous un email à" - code_of_conduct: - title: "Code de conduite" - summary: - title: "Version courte" - intro: "Nous nous engageons à fournir une expérience bienveillante et dépourvue de harcèlement pour tout le monde, indépendamment du genre, de l'orientation sexuelle, du handicap, de l'apparence physique, de la taille, de la race ou de la religion. Nous ne tolérons pas le harcèlement de nos membres sous quelque forme que ce soit. L'imagerie et le langage sexuels ne sont appropriés pour aucun de nos événements, y compris les conférences, les ateliers, les soirées, Twitter et tout autre média en ligne. Les membres qui enfreignent ces règles peuvent être sanctionnés ou expulsés de l'événement et de tout événement futur à la discrétion des organisateurs." - content: - title: "Version longue" - harassment: "Sont considérés comme harcèlement : les commentaires offensants liés au genre, à l'orientation sexuelle, au handicap, à l'apparence physique, à la taille, à la race ou à la religion, les images à caractère sexuel dans les espaces publics, les intimidations délibérées, le fait de suivre une personne de manière insistante et sans son accord, la prise de photos ou enregistrements sans consentement préalable des personnes concernées, les interruptions répétées lors de présentations ou autres événements, les contacts physiques inappropriés, ainsi que toute attention sexuelle non désirée." - comply: "Nous nous attendons à ce que tous les participants cessent immédiatement tout comportement de harcèlement en cas de signalement." - sponsors: "Les sponsors sont également soumis à la politique anti-harcèlement. En particulier, les sponsors ne doivent pas utiliser d'images, d'activités ou d'autres contenus à caractère sexuel. Le personnel (y compris les bénévoles) ne doivent pas porter de vêtements / uniformes / costumes sexualisés, ni créer un environnement sexualisé." - sanctions: "Si un participant se livre à un comportement de harcèlement, les organisateurs peuvent prendre toutes les mesures qu'ils jugent appropriées. Cela comprend l'avertissement du contrevenant, ou son expulsion." - concerns: "Si vous êtes harcelé·e, remarquez que quelqu'un d'autre est harcelé, ou avez d'autres préoccupations, veuillez contacter immédiatement l'un des organisateurs." - applies_to: "Nous attendons des participants qu'ils suivent ces règles lors de tous les événements codebar." - questions: "Si vous avez des questions ou des préoccupations concernant ce code de conduite," - contact: "contactez-nous" - email_subject: "Regarding code of conduct" - sponsors: - sponsoring: "Sponsoriser" - members: - sign_up: "S'inscrire" - sign_in_with_github: "Se connecter via GitHub" - sign_up_as_student: "Je souhaite m'inscrire en tant qu'étudiant *" - sign_up_as_student_disclaimer: "* Je comprends et j'accept les critères d'éligibilité." - sign_up_as_coach: "S'inscrire en tant qu'enseignant" - code_of_conduct: "code de conduite" - new: - intro_html: "We provide a welcoming, inclusive, and supportive learning environment, with a strict zero-tolerance policy for any form of harassment or inappropriate behavior. Please take a moment to review our code of conduct before signing up." - students: - intro_html: "Si vous souhaiter vous inscrire en tant qu'étudiant, assurez vous que vous soyez éligible puisque nos ateliers ne sont ouvert qu'aux femmes, LGBTQ, et personnes issus de minorités." - github: "Enfin, quand vous cliquez sur le boutton pour s'inscrire, vous allez être rediriger vers GitHub. Après vous être connecter avec votre compte GitHub, vous serez redirigé vers le site de codebar. Si vous n'avez pas de compte, vous devrez en créer un. Cela ne prend que quelques minutes et cela vous sera utile quand vous commencerez à coder!" - invitations: "Les invitations sont envoyer régulierement, ne vous inquiétez pas si vous n'en recevez pas une quand vous venez de vous inscrire." - footer: - email_us: "Envoyez nous un email à" - contact_info: "Contact:" - faq: - payment: - q: "Dois-je payer pour venir à codebar?" - a_p1: "Pas du tout! Nous avons la chance que de formidables entreprises accueillent nos ateliers et proposent un repas. Et nos" - awesome_coaches: "superbe enseignants" - a_p2: "donne de leur temps pour aider la communauté." - technologies: - q: "Quelles technologies enseignez vous?" - a: "Nous avons plusieurs tutoriels couvrant HTML, CSS, JavaScript et Ruby. Si vous souhaiter apprendre autre chose, envoyez nous un email, nous pourrons peut-être trouver quelqu'un pour vous aider." - eligibility: - q: "Je veux venir à un atelier. Suis-je éligible?" - a: "Nos ateliers sont ouvert aux femmes, LGBTQ et aux communautés sous représentés dans la tech. Si vous faites d'un de ces groupes, vous êtes les bienvenus. Il existe autrement beaucoup d'autres alternatives pour apprendre dans un environnement collaboratif. Référez vous a notre guide pour les étudiants pour plus d'informations." - career: - q: "Est-ce que codebar s'addresse uniquement aux personnes qui souhaitent se diriger vers une carrière de développeur?" - a: "Non! codebar veux faire aimer/découvrir la programmation. Nous les aiderons à apprendre les bases du code, mais aussi à les aider pour se débrouiller seul. Nous pouvons aider et guider ceux qui ont pour but de devenir développeurs." - format: - q: "Quel est le format des ateliers?" - a: "Nous essayons d'avoir un enseignant pour deux étudiants. Nous allons mettre deux étudiants travaillant sur la même chose ensemble si possible, et leur assigner un mentor." - laptop: - q: "Dois-je venir avec un ordinateur aux ateliers?" - a: "Oui, il est plus simple si vous voulez continuer à travailler sur le projet après l'atelier. Si vous n'en avez pas un, envoyez nous un email et nous ferons notre possible pour vous aider." - online_resources: - q: "Il y a beaucoup de resources en ligne, pourquoi je devrais venir à codebar?" - a: "Il peut-être intimidant de coder par soi même et beaucoup de gens ont des problèmes pour se lancer. En vous mettant en relation avec des gens qui peuvent vous aider et vous aider, nous rendons votre apprentissage un peu plus simple et sympathique." - preperations: - q: "Si je veux enseigner à codebar. Dois-je faire autre chose outre le fait de m'inscrire?" - a_p1: "Oui. Tout d'abord vous devriez lire notre" - coaching_guide_tutorials: "tutoriel pour les enseignants" - a_p2: ". Et ensuite essayer de vous familiariser avec les" - a_p3: "tutoriels. Les tutoriels sont open source donc n'hésitez pas a ouvrir une issue ou une pull request sur GitHub." - a_p4: "Nous n'attendons pas que les enseignants connaissent toutes les technologies ou les languages de tous les tutoriels." - location: - q: "Ou se passent les ateliers?" - a: "Nous n'avons pas de locaux fixe, nos ateliers sont hébergés par différentes entreprises." - disabled_access: - q: "Y-a-t-il un accès handicapé aux ateliers?" - a: "Malheuresement, cela dépend de l'entreprise qui héberge l'atelier. Si vous souhaitez vous inscrire à un atelier, envoyez nous un email à meetings[at]codebar.io pour que nous faissions la demande pour vous." - bring_codebar_to_my_city: - q: "Je voudrais commencer codebar dans ma ville. Est ce que cela est possible?" - a: "Bien sur. codebar a pour but de créer une communauté de développeurs qui veulent aider les autres. Si vous êtes exciter a l'idée de lancer codebar ou vous habitez, nous adererions parler avec vous afin de voir comment nous pourrions nous organiser, alors envoyez nous un email." - our_coaches: - q: "Nos enseignants" - a_p1: "Vous pouvez voir tous les enseignants qui ont aider dans nos ateliers sur" - a_p2: ". Ils ont commandé suivant le nombre de participants. C'est notre manière de leur montrer notre gratitude, vu que sans eux, nous ne pourrions exister." - participant_student_guide: - title: "Student Guide" - attendance_policy: - title: "Attendance Policy" - intro: "codebar is, and always has been, open to all levels of coding experience. While most of the tutorials on our website are aimed at newcomers to web development, we intend to continue our open-door policy for any student who needs coach support on their own projects. Due to the fact that our workshops are frequently oversubscribed, we ask students to respect the following expectations for participation in our workshops" - rule1: "In order to attend a workshop, you must be on the RSVP list. If you have not RSVP’d or were not allocated a spot, you will not be admitted into a workshop." - rule2: "If you can no longer attend a workshop, please cancel your RSVP by 12:00 latest on the day of the workshop. We understand that last-minute emergencies occur -- if this is the case, please get in touch with an organizer directly as soon as possible. Repeated no-shows will result in temporary or permanent suspension of your invitations." - rule3: "No guests are allowed. Our workshops are already overcrowded and we cannot make any exceptions. If your friend meets our eligibility criteria, get them to sign up and RSVP themselves." - rule4: "Please be respectful of our hosts. Do not show up exceedingly early to a workshop (not earlier than 15 minutes before the event begins) and try to leave the workstation clean and as you found it." - rule5: "Please do not work on projects that were assigned as part of any bootcamp or university curriculum. Talk to your course adviser if you feel like you need additional support with your coursework. We welcome your attendance, but we encourage you to use your time at codebar to develop skills that are outside the normal scope of your studies." - rule6: "Do not bring along and ask for help with any commercial work. This involves work you're being paid to do." - rule7: "Projects that involve specific frameworks/libraries (Rails, NodeJS, Meteor, Angular, Ember, React, etc) or languages that are not part of the codebar tutorials (anything other than Ruby or Javascript) are welcome but we cannot guarantee that a coach will be available to help you. In these cases we recommend selecting a codebar tutorial or katas (codewars.com or exercism.io) as a back-up option." - eligibility_criteria: - title: "Eligibility Criteria" - p_1: "codebar was started out of recognition that there is a shortage of women, LGBTQ, and people belonging to underrepresented ethnic groups in tech." - p_2: "If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School or Ask a Dev where you can learn in a collaborative environment." - p_3: "Bearing that in mind, it is sometimes difficult for us to identify whether attendees meet the eligibility criteria based on their first and last names. If we cannot determine your eligibility, we will contact you asking for a short confirmation that you have read this document and assert that you meet one or more of the criteria. We will never ask participants to specify which group." - p_4: "codebar is first and foremost a resource for students who cannot afford formal training through coding bootcamps or university degrees, for financial reasons or otherwise. Our coaches, organisers and sponsors donate their time and money to help those who have faced unfair barriers to entry into the tech world. We have strived to create an inclusive, welcoming community, and so far, we have not had to implement a formal policy to enforce the eligibility criteria -- we have left this to the honesty and good faith of the students." - p_5: "If you are unsure whether you are eligible, please get in touch. If we determine that you have signed up and do not belong to an eligible group, we will permanently suspend your student invitations without warning." - p_6: "We take this issue very seriously, and we appreciate your cooperation and understanding." - disability: - title: "Students with Disability" - description: "We want to ensure that our workshops are as accessible as possible. If you are disabled and are unsure about whether our venues can cater to your needs, we encourage you to please get in touch with us at hello@codebar.io and we will do what we can to accommodate you." - chapters: - intro: "Bonjour et bienvenue à codebar! Si vous avez des questions, allez lire notre FAQ, et n'hésitez pas à nous envoyer un email à %{email} si vous ne trouvez pas réponse à votre question. Sinon, vous pouvez utiliser le boutton ci-dessous pour vous inscrire." - sign_up: "pour être inviter à nos ateliers." - no_incoming: "Il n'y a pas d'ateliers prévu." - contact: "Pour contacter l'équipe de %{city}, envoyez un email à %{email}" - feedback_form: - title: 'Workshop feedback' - description: Your submission will be completely anonymous. We read every piece of feedback and use it to help us improve our workshops. - note: Please do not mention any names, but instead choose your coach from the dropdown. This enables us to address issues but also to anonymously share feedback with coaches. Member privacy is very important to us! - rating: Your overall rating of the workshop - coach: 'Who was your coach?' - select_coach: '- Select Coach -' - tutorial: 'What tutorial did you go through?' - select_tutorial: '- Select Tutorial -' - request: 'How did you find the workshop?' - suggestions: "Was there something you didn't like? What can we do to improve your experience?" - newsletter: "For an additional £250 you can have your job listing featured in our newsletter and made available to an audience of over 10000 students and coaches. To find out more details and when our next newsletter is due send us an email at hello@codebar.io." - pages: - cookies: - title: Cookie Policy - p1: 'Cookies are small pieces of text used to store information on web browsers. They are used by websites accross a number of different devices to store and receive identifiers and other information. Our Website and Service use cookies and other similar technologies (collectively in this Policy, "cookies"), in order to provide a better service to you and to generally improve our Website and Service. For example, we may use cookies to help direct you to the appropriate part of our Website, by indicating that you are a repeat visitor. We also may use information to present you with services that are matched to your preferences and to manage and track the effectiveness of our marketing efforts.' - p2: Some portions of the codebar website are functional without cookies, and you may generally choose whether to accept cookies. Most web browsers are set to accept cookies by default, however, you may be able to delete cookies yourself through your browser's cookie manager. To do so, please follow the instructions provided by your web browser. Please note that disabling cookies will reset your session, disable auto-login, and may adversely affect the availability and functionality of our Website and the services we can provide to you. - sub: - title: Below are the cookies used by the codebar website. - table: - header: - h1: Name - h2: Purpose - h3: Expires - functional: - title: Functional Cookies - description: Stores information about your session. - planner_name: _planner_session - planner_purpose: Stores session data - planner_expiry: Expires after 24 hours - google_analytics: - title: Google Analytics - description: Google Analytics collects information about how you use the codebar website. This enables us to identify how busy the website is and possible improvements. - info: We don’t allow Google to use or share our analytics data. - opt_out: You can [opt out of Google Analytics](https://tools.google.com/dlpage/gaoptout). - ga_name: _ga - ga_purpose: Tracks if you have visited codebar.io before - ga_expiry: After 2 years - gid_name: _ga - gid_purpose: Tracks if you have visited codebar.io before - gid_expiry: After 24 hours - cloudflare: - title: Cloudflare - cfduid_name: _pfduid - cfduid_purpose: Used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. - cfduid_expiry: 1 year - privacy_policy: - title: Privacy Policy - subtitle: This Privacy Policy was last updated on 13 May 2021. - intro: - p1: 'This Privacy Policy has been created by codebar ("codebar", "we", "us", or "our") whose companies house registered name and address is as follows:' - address_html: " - codebar Ltd,
- International House,
- 101 King's Cross Road,
- London, England,
- WC1X 9LP
- Company No. 10791813
" - p2: codebar Ltd trades on behalf of the charity registered UK and Wales no. 1187776. For the purpose of this Privacy Policy codebar Ltd is the data controller. - p3: Your privacy means a lot to us, and we take it very seriously. We aim to be transparent with you about the data we collect about you and how it is used and shared. This Privacy Policy lets you know what information we collect when you use the codebar website, https://codebar.io/, or interact with any of the services we provide, such as signing up to workshops and events ("Services"). By using our Services you acknowledge and understand our use of your data under this Privacy Policy and how it applies to your use of our Services. - information: - title: 1. Information we collect - what_we_collect: - title: 1.1 Personal data we collect from you - p1: 'We have set out in the table below the personal data we collect about you and how we use it, which will differ based on the capacity in which you interact with codebar:' - table: - headers: - h1: Who - h2: What data we process - h3: What we use it for - h4: Lawful basis - r1: - c1: Students - c2: This includes personal data that is provided by you or collected by us to enable you to subscribe to codebar as a student. This may include your name, email address, phone number, pronouns, self-written bio, , your self-recognition as being underrepresented (with your consent), and the location you choose to subscribe to. - c3: For administrative purposes when you sign up to events, to communicate with you, and to provide you with our newsletters and events information. - c4: - l1: Performance of a contract - l2: Consent - l3: Legitimate interests - r2: - c1: Coaches - c2: This includes personal data that is provided by you or collected by us to enable you to volunteer at codebar as a coach. This may include your name, email address, phone number, pronouns, self-written bio/skills, , your self-recognition as being underrepresented (with your consent), and the location you choose to volunteer at. - c3: For administrative purposes when you volunteer for workshops, to communicate with you, to manage workshop attendance, and to provide you with our newsletters and events information. - c4: - l1: Consent - l2: Legitimate interests - r3: - c1: Organizers - c2: This includes personal data that is provided by you or collected by us, which may include your name, email address, phone number, pronouns, self-written bio/skills, , slack username, signed documentation, and the location you choose to volunteer at. - c3: To organise and communicate workshops. - c4: - l1: Legitimate interests - r4: - c1: Hosts - c2: We may collect personal information of employees working at companies that agree to host our workshops. This information may include the employees' name, email address, contact number, , and place of work. - c3: In order to market, promote, host and operate workshops. - c4: - l1: Legitimate interests - r5: - c1: Sponsors - c2: We need to collect personal data in relation to your sponsorship of codebar. This may include information such as your name, and bank details. - c3: To fulfill contractual obligations we have with you, for example, to process invoices related to your sponsorship. - c4: - l1: Performance of a contract - l2: Legitimate interests - r6: - c1: Trustees and directors - c2: We need to collect personal data in relation to your position as trustee and/or director. This may include information such as your name, contact number, address, email address, and date of birth. - c3: In order to establish our status as a charity, to comply with legal obligations, and respond to legal requests. - c4: - l1: Legitimate interests - l2: Compliance with legal obligations - how_we_share: - title: 1.2 How we share your information - p1_html: 'When you subscribe to an event, we share your name with our host companies as we are required to provide a list with all attendee names when you subscribe to any of our events. We **do not share** your email address or any other personal information.' - legal_basis: - title: 1.3 Legal basis for our use of your personal information - p1: As set out in the table above, sometimes the legal basis on which we collect and process your data is because our legitimate interests make the processing necessary, and those legitimate interests are not overridden by your interests or fundamental rights and freedoms. For example, we collect and store your data in order to process event information, and to ensure the efficient running and promotion of workshops. - retention: - title: 2. Retention - p1: We will keep your personal information for as long as reasonably necessary to fulfil the purposes we collected it for. To determine the appropriate retention period, we consider the amount, nature and sensitivity of the personal information, the potential risk of harm from unauthorised use or disclosure of your personal information, the purposes for which we process your personal data and whether we can achieve those purposes through other means, and the applicable legal, regulatory, tax, accounting or other requirements. - p2: We may retain your personal information for a longer period in the event of a complaint or if we reasonably believe there is a prospect of dispute in respect to our relationship with you. - international_transfers: - title: 3. International transfers - p1: Personal information we collect may be transferred to and stored in countries outside of the jurisdiction you are in for the purposes specified in this Privacy Policy. We will only transfer your personal information to countries that have been deemed to provide an adequate level of protection for personal information, and/or any international transfers will be made pursuant to appropriate safeguards in accordance with the applicable laws and regulations, such as standard data protection clauses adopted by the UK and European Commission. - p2: If you wish to enquire further about these safeguards used, please contact us by email at the address below or by mail using the postal address provided below. - your_rights: - title: 4. Your data protection rights - p1: 'Data protection law provides you with rights in respect of personal data that we hold about you, including the:' - l1: 'Right to Access: You have the right to obtain access to your data, and certain other information (similar to that provided in this Privacy Policy).' - l2: 'Right to Rectification: You are entitled to have your data corrected if it is inaccurate or incomplete.' - l3: 'Right to Erasure: This enables you in some circumstances to request and obtain the deletion of your data where there is no legal reason for us to keep using it.' - l4: 'Right to Restriction of Processing: You have rights to suspend further use of your data, whereby we can still store your data but cannot use it further. This may mean we can no longer provide you with Services.' - l5: 'Right to Data Portability: You have rights in some circumstances to request the transfer of your data to yourself or to a third party.' - l6: 'Right to Objection: You have the right to object to certain types of data processing, including for direct marketing purposes.' - l7: 'Right to Withdrawal of Consent: Where we are relying on consent to process your data, you have the right to withdraw your consent at any time by using any opt-out links, or by contacting us at the details provided below (although if you do so, it does not mean that anything we have done with your data with your consent up to that point is unlawful and we may be able to continue to process your personal information to the extent required or otherwise permitted by law, in particular in connection with exercising and defending our legal rights or meeting our legal and regulatory obligations).' - l8: 'Right to Lodge a Complaint: You can lodge a complaint in relation to our use of your personal information with the local supervisory authority, the Information Commissioner (UK).' - p2: If you would like to exercise any of these rights or if you have a complaint about how we handle your data, please contact us at the email address stated below. - security: - title: 5. Security - p1: The security of your personal information is important to us. codebar takes reasonable steps to implement and update administrative, technical, and physical security measures to help protect your information against unauthorised access, loss, destruction, or alteration. However, the Internet is not a 100% secure environment so we can't guarantee the security of the transmission or storage of your information. codebar has no control over or responsibility for the security or practices or privacy policies of third parties, even if you interact with them when using our Services. - changes: - title: 6. Changes to this Privacy Policy - p1: We reserve the right to modify or update this Privacy Policy at any time in accordance with this provision. If we make changes to this Privacy Policy, we will post the revised Privacy Policy on the codebar website. Please regularly review https://codebar.io/privacy-policy to check for any updates or changes to our Privacy Policy. The date this Privacy Policy was last revised is identified at the top of this page. - cookies: - title: 7. Cookies - p1_html: 'We use cookies to recognise you and your location. You can control cookies through your browser settings and other tools. For more information read our [cookie policy](https://codebar.io/cookie-policy).' - contact: - title: 8. Contact - p1: "If you have any questions or complaints about this Privacy Policy or our information handling practices, you may email us at company@codebar.io stating 'Data inquiry' in the subject title, or by postal mail at: codebar Ltd, International House, 101 King's Cross Road, London, WC1X 9LP." - breach: - title: What happens if you violate codebar’s Code of Conduct? - opening_para: All codebar events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment towards any community member or organiser in any form. Harassment includes any type of aggressive behaviour or offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. - second_para: The Code of Conduct is in place to protect every codebar member - students, coaches and organisers. If any member violates these rules the below procedure and sanctions will be implemented. - outcome_title: 3 types of outcomes - correction: Correction - The use of inappropriate language or other behavior deemed unprofessional or unwelcome in the codebar community. This includes the use of terminology that is discouraged, e.g. 'guys'. In this situation you will be sent a private message, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. - warning: Warning - You will receive an email warning. The organiser will explain the incident, including the impact on the person involved and the community. We will give as much information as possible, so you’re aware of what happened and try to learn from the incident. The organiser will add a note to your codebar profile so that all chapter organisers are aware of the incident. We expect you to take our comments on board, further action may be taken depending on your reaction. Examples of behaviour that will get you a warning include - targeted offensive language, or the sharing of sexual images in codebar spaces. 2 email warnings will result in a lifetime ban. - lifetime_ban: Lifetime ban - You will no longer be able to RSVP to any future codebar events. You will also be removed from codebar’s Slack workspace. Examples of behaviour that will get you an automatic lifetime ban include - physical intimidation, stalking, inappropriate physical contact, unwelcome sexual attention or repeated behaviour after you’ve been spoken to by someone from the codebar team (directors or chapter organisers). - closing_para: The above is only a starting point. The details of the incident may change how we view it, e.g. some verbal harassment may be so serious that we would give a lifetime ban. - how_to_support_us: - volunteer: - title: Volunteer with us - become_an_organiser: - title: Become an organiser - description: Champion inclusion and diversity in the tech industry as a workshop organiser with codebar. Your contribution will create an empowering and safe environment, fostering learning and collaboration among individuals exploring coding in our vibrant community. - link: Email us to become an organiser - become_a_coach: - title: Become a coach - description: Affect change as a volunteer coach with codebar - your expertise and guidance will pave the way for aspiring developers, unlocking the world of coding and creating opportunities for folks from groups under represented in the tech industry. - volunteer: - title: Other skills - description: Your unique abilities could be our missing piece in the codebar puzzle. Having a diverse range of skills in our team is necessary to enrich our community. From fundraising to event coordination to marketing, we always welcome new talent to drive our mission forward. - link: Email us to become a volunteer - fundraise: - title: Fundraise - description_html: "Join the codebar team with a physical challenge event. Whether you are a runner, swimmer, or cyclist, sign up with our registration form for your desired event and raise vital funds to help keep our events running. If your event does not appear below, feel free to drop us an email and we would be happy to coordinate with you." - image_alt: A Black British woman crosses the finish line at the Hackney Half Marathon in London in a shower of confetti while spectators cheer her on. - codebar_stories_podcast: - image_alt: codebar stories banner - opening: codebar Stories is a new podcast brought to you by codebar, we'll be smashing down the belief that tech isn't for you by sharing real-life stories from members of our community who have transitioned into a new career in tech. - contact_us_html: "Sponsoring codebar Stories offers you a unique opportunity to connect with a diverse, engaged audience within the tech community. As a podcast dedicated to empowering underrepresented groups through coding education, your brand will align with our values of diversity, inclusivity, and social impact. Through sponsorship, you'll gain visibility, build positive PR, and demonstrate your commitment to fostering the next generation of tech talent, all while supporting a meaningful cause. Sound good? Please drop us an email podcast@codebar.io." - - admin: - dashboard: - title: 'Admin' - workshop: - manage_rsvps: - text: "Inscrire les étudiants et les enseignants à l'atelier. Leur email de confirmation va être envoyer et ils seront retirer de la liste d'attente." - destroy: - success: "Atelier supprimé" - failure: "L'atelier ne peut être supprimé. Parce qu'il y a déjà des inscrits ou parce que l'atelier a été en ligne pour trop longtemps." - messages: - meeting: - created: 'Meeting successfully created' - updated: 'You have successfully updated the details of this meeting' - invitations_already_sent: 'Invitations were previously sent; they will not be sent again' - sending_invitations: 'Invitations are being sent out' - invitation: - rsvp_member: "%{name} has been successfully added and notified via email." - already_on_list: "%{name} is already on the list!" - rsvp_error: "Something went wrong, %{name} has not been added." - update_rsvp: 'Updated attendance of %{name}' - simple_form: - placeholders: - job: - company: 'e.g. codebar' - company_website: 'e.g. https://codebar.io' - title: 'e.g. Internship' - description: 'Use text or markdown for the job description' - location: 'e.g. London or Berlin' - hints: - job: - remote: Only check if the role is fully remote only - salary: Annual pay before tax, without commas or decimal points - activerecord: - attributes: - job: - title: Title - company: Name - company_address: Address - company_postcode: Postcode - company_website: Website - email: Contact email - link_to_job: Link to job post - expiry_date: Application closing date - donation_platforms: - title: "Donate" - description: "Your support—whether through a one-time gift or ongoing commitment—drives our mission to create a more inclusive tech industry. It enables us to provide continuous learning opportunities and empower individuals from underrepresented groups to grow and thrive in tech." - link: "Find out how else to support us" - donation_form: - title: "Use the donation page" - text: "Make a lasting impact with codebar by giving a one-time donation or committing to a monthly contribution." - image_alt: "codebar logo" - github_sponsors: - title: "Github Sponsors" - text: "Support codebar’s mission directly through GitHub Sponsors and help shape the future of technology with your generous donation." - image_alt: "Github Sponsors logo" - open_collective: - title: "Open Collective" - text: "Setup a recurring contribution or make a one-time donation through Open Collective." - image_alt: "Open Collective logo" - give_as_you_live: - title: "Give as you Live" - text: "Give as you Live is a platform enabling you to raise funds for your favourite charity with your everyday online shopping." - image_alt: "Give as you Live logo" diff --git a/config/locales/no.yml b/config/locales/no.yml deleted file mode 100644 index 5bb9d6827..000000000 --- a/config/locales/no.yml +++ /dev/null @@ -1,553 +0,0 @@ -"no": - brand: "codebar.io" - date: - formats: - default: "%d/%m/%Y" - email: "%a, %d %B at %H:%M" - email_title: "%A, %d %b at %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - website_format: "%a, %d %B %Y at %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y at %R" - dashboard: "%a, %d %b %Y, %H:%M" - time: - formats: - default: "%a, %d %b %Y %H:%M" - email: "%a, %d %B at %H:%M" - email_title: "%A, %d %b at %H:%M %Z" - short: "%d/%m/%Y %H:%M " - date: "%d %b %Y" - full_date: "%d %B %Y" - default_date: "%d/%m/%Y" - website_format: "%a, %d %B %Y at %H:%M" - day_in_words: "%a" - day: "%d" - month: "%B" - year: "%Y" - meeting_format: "%a %d %B %H:%M" - time: "%H:%M" - year_month: "%Y-%B" - log: "at %H:%M on the %d/%m/%Y" - workshop: "%A, %e %B %Y at %R" - dashboard: "%A, %b %d" - number: - currency: - format: - unit: '£' - delimiter: ',' - separator: '.' - precision: 0 - format: '%u%n' - homepage: - intro: "codebar is a charity that facilitates the growth of a diverse tech community by running free regular programming workshops for minority groups in tech." - explanation: "Our goal is to enable people from underrepresented groups to learn programming in a safe and collaborative environment and expand their career opportunities. To achieve this we run free regular workshops, regular one-off events and try to create opportunities for our students making technology and coding more accessible." - participate: - students_title: "Students" - students_explanation_p1: "Our students come from diverse backgrounds—some aspiring to become full-time developers, while others simply want to learn the basics of coding in a supportive environment." - students_explanation_p2: "Join our vibrant community and take part in our workshops!" - students_button: "Join us as a student" - coaches_title: "Coaches" - coaches_explanation_p1: "We encourage new students to start with our tutorials on HTML/CSS, JavaScript, Ruby, Python, or Git, while also helping them grasp key programming concepts." - coaches_explanation_p2: "That’s why we’re always looking for more developers to join our community and coach at our workshops." - coaches_button: "Join us as a coach" - workshop_title: "Workshops" - workshop_explanation_p1: "We’re proud to be hosted by amazing companies that support our mission. Our typical format includes 30 minutes of socialising over food and drinks, a lightning talk, and then hands-on coding." - workshop_explanation_p2: "Help us grow and support our chapters by hosting or sponsoring our workshops, and together, we can expand opportunities for more aspiring developers." - workshop_button: "Let's work together" - workshop_email_subject: "Regarding hosting a workshop" - chapters: - title: "Chapters" - events: - upcoming: "Upcoming Events" - donation_platforms: - title: "How to support us" - mailer: - workshop_invitation: - attending: - subject: "Attendance Confirmation for %{date_time}" - attending_reminder: - subject: "Workshop Reminder %{date_time}" - invite_coach: - subject: "Workshop Coach Invitation %{date_time}" - invite_student: - subject: "Workshop Invitation %{date_time}" - notify_waiting_list: - subject: "A spot just became available" - waiting_list_reminder: - subject: "Reminder: you're on the codebar waiting list (%{date_time})" - messages: - accepted_invitation: "Thanks for getting back to us %{name}. See you at the workshop!" - already_invited: 'You have already RSVPd or joined the waitlist for this workshop.' - error_blank_note: 'You must select a note' - rejected_invitation: "We are so sad you can't make it, but thanks for letting us know %{name}." - already_rsvped: "You have already confirmed your attendance!" - not_attending_already: "You have already confirmed you can't make it!" - no_available_seats: "Unfortunately there are no more spaces left :(. If you would like to join our waiting list send us an email at %{email}" - feedback_saved: "Thank you for taking the time to give us feedback!" - feedback_not_found: "You have already submitted feedback for this event." - updated_note: "Successfully updated note." - invalid_session: 'Your session is invalid' - invitations: - meeting: - cancel: "Thanks for letting us know you can't make it." - rsvp: "Your RSVP was successful. We look forward to seeing you at the Monthly!" - rsvped_to_other_workshop: "You have already RSVP'd to another workshop on this date. If you would prefer to attend this workshop, please cancel your other RSVP first." - spot_confirmed: "Your spot has been confirmed for %{event}! We look forward to seeing you there." - spot_not_confirmed: 'Your spot has not yet been confirmed. We will verify your attendance after you complete the questionnaire.' - notifications: - provider_already_connected: 'You are already signed in!' - not_logged_in: "You must be logged in to access this page." - navigation: - dashboard: "Dashboard" - code_of_conduct: "Code of Conduct" - breach_code_of_conduct: "Breach Code of Conduct" - coach_guide: "Coach Guide" - student_guide: "Student Guide" - tutorials: "Tutorials" - becoming_sponsor: "Becoming a Sponsor" - faq: "FAQ" - blog: "Blog" - codebar_stories: "codebar Stories" - stats: "Stats" - dashboard: - join_workshops_in: "Join our free workshops in" - workshops_goal: "to get to grips with the basics of programming and web development." - tweets_by: "Tweets by" - latest_sponsors: "Latest Sponsors" - policy: - intro: "There’s high demand for our workshops and we have a waiting list on most weeks. To make sure as many people as possible can come, we have a straightforward attendance policy." - rule1: "Before you RSVP make sure you are eligible to attend. If you’re not sure get in touch for a chat." - rule2: "You must sign up and RSVP to attend our workshops." - rule3: "If you RSVP then later realise you can’t make it, you must cancel. It only takes a few seconds to do through your confirmation email." - rule4: "Please try to cancel with at least 24 hours notice." - rule5: "We know that sometimes things come up last minute, but even if you only cancel an hour before the workshop, get in touch and let us know." - what_happens: "What happens if I don’t respect the policy?" - strikes_system: "We operate a three strikes system. That means if you don’t come in without cancelling an RSVP three times, we will take you off our invite list for four weeks. We’ll get in touch after your first absence to make sure you understand this." - removing: "If you fail to attend without cancelling another three times, we might have to remove you permanently from our invitation list." - rsvping: "There is no penalty for RSVP-ing and then cancelling on a regular basis, but please avoid it. If you always struggle to make it in on a certain day then let us know – that kind of feedback is really important to us." - eligibility_note: "Another note on eligibility" - abuse: "We’re a fairly relaxed bunch and we trust you, so we don’t police students as to their eligibility. However if it ever looks like this is being abused we may have to change that – which we really don’t want to do." - reminder: "So please remember what these workshops are for – to open up tech to people that are underrepresented in the industry." - teacher_guide: - laptop: "You don't need a laptop for our workshops. You are there to watch and guide the students. If you don't feel comfortable with the tutorial you should spend time on it before coming if you want to help out." - keyboard: "Do not take over the keyboard! This can be off-putting and scary." - typing: "Encourage the students to type and not copy paste." - questions: "Explain that there are no bad questions." - mistakes: "Explain to students that it's OK to make mistakes." - introduction: "Always introduce yourself. Say why you want to help out and are spending your own time on this, why you like programming." - backgrounds: "Give your students the opportunity to get to know each other. Ask their names, why they are here, what they do in their day jobs. Encourage a brief discussion before starting." - limits: "Assume that anyone you're teaching has no knowledge but infinite intelligence." - collaboration: "Work collaboratively with your student. If you have two students, you should work with both. Don't focus all your attention on one of them." - discussion: "Let students have a go at answering the questions first. Help with open and leading questions. Encourage a discussion." - talk_slow: "Take it slow, you are the teacher, they are the student. Allow for time between questions." - mild_approach: "Don't say no when the students are not doing something right. Be gentle, approach it in a mild way." - paper: "Use pen and paper or go to a whiteboard! Often students are coming from a non-technical background. Drawing and explaining with visual material is really helpful." - stubling: "Let them stumble. We learn by making mistakes, getting frustrated, and working through problem in our own way. Be supportive, but let them explore." - suggestions: "Do you have something to suggest? Make a pull request or create an issue" - workshops: - already_wish_to_attend: 'You have already RSVPd or joined the waitlist for this workshop.' - lead: "Attend our workshops to learn programming in a safe and supportive environment at your own pace, or to share your knowledge and coach our students." - registration_not_open: 'This workshop is not open for registrations' - events: - title: "Events" - past: "Past" - no_upcoming_events: "There are no upcoming events." - view_past_events: "View past events" - view_all: "View all" - hosted_by: "Hosted by" - organisers: "Organisers" - venue_at: "at" - attend_as_student: "Attend as a student" - attend_as_coach: "Attend as a coach" - location: "Location" - sponsors: "Sponsors" - thx_to_sponsors: "A big thanks to all of our sponsors for making the event possible!" - coaches: "Coaches" - students: Students - schedule: "Schedule" - send_us_an_email: "send us an email" - not_open_for_rsvp: This event is not open for RSVP yet. - virtual: This is a virtual event. - faq: - experience: - q: "How experienced should I be to join the workshop?" - a: - contribution: - q: "What kind of contributions can I make?" - a: "Your contributions can be tiny, as simple as fixing a typo, to something incredible. You can help with documentation, fix a bug that you found, improve the copy, help with design or even tackle bigger tasks and help introduce new features. Every little helps!" - laptop: - q: "Do I need to bring a laptop?" - a_html: "Yes, you should bring a laptop. If you don't have one %{link} as we may be able to help." - keyboard: - q: "Do I need to bring a keyboard?" - a_html: "A keyboard would help as you will spend the entire day pairing with someone on your laptop. If you don't have a keyboard, %{link} and we'll try to organise something for you." - travel_costs: - q: "I will be commuting. Can you help with my travel expenses?" - a: "We will be offering some travel grants. Just make sure you fill in the questionnaire after you RSVP and we will get in touch." - coaches: - want_to_coach: "Do you want to coach at our workshops?" - read_before: "If you have not attended our workshops before, make sure you read our" - code_of_conduct: "code of conduct" - policy: "as we have a zero tolerance policy and expect everyone to behave appropriately. You should also go through our" - guide: "coaching guide" - unable_attend: "In case you are unable to attend after you RSVP, please make sure you come back and update your attendance as we rely on coaches showing up in order for our workshops to run smoothly." - food: "PS: There will also be food at the workshop. We always make an effort to have vegetarian, vegan and gluten-free options available. If you have any other dietary requirements, send us email at" - code_of_conduct: - title: "Code of conduct" - summary: - title: "The Quick Version" - intro: "Our events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of our members in any form. Sexual language and imagery is not appropriate for any of our events, including talks, workshops, parties, and online media. Members violating these rules may be sanctioned or expelled from the event and any future events at the discretion of the organisers." - content: - title: "The Long Version" - harassment: "Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention." - comply: "We expect any participants asked to stop any harassing behaviour to comply immediately." - sponsors: "Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment." - sanctions: "If a participant engages in harassing behaviour the organisers may take any action they deem appropriate. This includes warning the offender or expulsion." - concerns: "If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact one of the organisers immediately." - applies_to: "We expect participants to follow these rules at all codebar events. If they fail to do so, the following process will take place." - questions: "If you have any questions or concerns about this code please" - contact: "contact us" - email_subject: "Regarding code of conduct" - sponsors: - sponsoring: "Sponsoring" - members: - sign_up: "Join our community" - sign_in_with_github: "Sign in with GitHub" - sign_up_as_student: "Join us as a student" - sign_up_as_student_disclaimer: "* I understand and meet the eligibility criteria." - sign_up_as_coach: "Join us as a coach" - code_of_conduct: "code of conduct" - new: - intro_html: "We provide a welcoming, inclusive, and supportive learning environment, with a strict zero-tolerance policy for any form of harassment or inappropriate behavior. Please take a moment to review our code of conduct before signing up." - students: - intro_html: "If you’re interested in attending as a student, be sure to check our eligibility criteria. Our workshops and events are exclusively for women, non-binary, LGBTQ+ members, and people from underrepresented groups." - github: "When you click the sign-up button, you'll be redirected to GitHub. After logging in with your GitHub account, you'll return to the codebar website. If you don’t have an account yet, creating one is quick and easy—and it will be useful as you begin your coding journey!" - invitations: "Invitations are sent out periodically, so don't worry if you don't receive one as soon as you register." - footer: - email_us: "Send us an email at" - contact_info: "Contact Info:" - faq: - payment: - q: "Do I need to pay to attend codebar?" - a_p1: "Absolutely not! We are lucky enough to have some great companies who are able to host the workshops and/or kindly provide food. And our" - awesome_coaches: "awesome coaches" - a_p2: "give their time freely to help the community." - technologies: - q: "What technologies do you teach?" - a: "We have a variety of available tutorials in HTML, CSS, JavaScript and Ruby. If you want to learn something else don't hesitate to send us an email as we might still be able to find someone to help you out." - eligibility: - q: "I want to attend a workshop. Am I eligible?" - a: "Our workshops are available to women, LGBTQ and people who are underrepresented in the tech industry. If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School London where you can learn in a collaborative environment. Please see our student guide for more information." - career: - q: "Is codebar only aimed at people who want to move into a career as a developer?" - a: "No! codebar is about getting people excited about programming. We'll help them learn some basic coding skills, as well as how to explore and do things on their own. For those who do want to become developers, we will provide help and guidance to help them achieve their goal." - format: - q: "What is the format of the workshops?" - a: "We try to have one coach for every two students. We will pair up students who want to work on the same tutorial, and assign them a coach. The rest just happens." - laptop: - q: "Do I need to bring a laptop with me at the workshops?" - a: "Yes, we suggest that you bring a laptop as it will be easier for you to carry on working on things after the workshops. It you don't have one, send us an email so we can try and help out." - online_resources: - q: "There are so many online resources, why should I come to codebar?" - a: "Coding can be intimidating and a lot of people find it hard to get started. By putting you in touch with people who can help and guide you we make the experience and learning process easier and more enjoyable." - preperations: - q: "I would like to coach at codebar. Is there anything I should do besides signing up?" - a_p1: "Yes. First you should read our" - coaching_guide_tutorials: "coaching guide tutorials" - a_p2: ". Then spend sometime familiarising yourself with the" - a_p3: "tutorials. The tutorials are open source so if there is something that you want to improve open an issue on the GitHub repository or send a pull request." - a_p4: "We don't expect the coaches to be familiar with all the technologies and languages we have material on." - location: - q: "Where do the workshops take place?" - a: "As we don't have a permanent venue, our workshops are hosted by different companies in various locations around London. So far we've run workshops in Shoreditch, London Bridge, Holborn and Kings Cross." - disabled_access: - q: "Is there disabled access at the workshops?" - a: "Unfortunately, that depends entirely on where we are hosting our workshops and if the venue has disabled access. If you would like to attend, send us an email at meetings[at]codebar.io so we can enquire about it and let you know." - bring_codebar_to_my_city: - q: "I would like to bring codebar to my city. Can I do that?" - a: "Of course. codebar is about building a community of experienced developers that are able to give up some of their time to help others. If you are keen on running codebar where you live, we would love to speak to you about it and see how we can help make this happen, so send us an email." - our_coaches: - q: "Our coaches" - a_p1: "You can see all the coaches have helped out in our workshops on the" - a_p2: ". They are ordered by number of attendances. This is our way of showing our appreciation to them, as without them, we wouldn't be able to exist." - participant_student_guide: - title: "Student Guide" - attendance_policy: - title: "Attendance Policy" - intro: "codebar is, and always has been, open to all levels of coding experience. While most of the tutorials on our website are aimed at newcomers to web development, we intend to continue our open-door policy for any student who needs coach support on their own projects. Due to the fact that our workshops are frequently oversubscribed, we ask students to respect the following expectations for participation in our workshops" - rule1: "In order to attend a workshop, you must be on the RSVP list. If you have not RSVP’d or were not allocated a spot, you will not be admitted into a workshop." - rule2: "If you can no longer attend a workshop, please cancel your RSVP by 12:00 latest on the day of the workshop. We understand that last-minute emergencies occur -- if this is the case, please get in touch with an organizer directly as soon as possible. Repeated no-shows will result in temporary or permanent suspension of your invitations." - rule3: "No guests are allowed. Our workshops are already overcrowded and we cannot make any exceptions. If your friend meets our eligibility criteria, get them to sign up and RSVP themselves." - rule4: "Please be respectful of our hosts. Do not show up exceedingly early to a workshop (not earlier than 15 minutes before the event begins) and try to leave the workstation clean and as you found it." - rule5: "Please do not work on projects that were assigned as part of any bootcamp or university curriculum. Talk to your course adviser if you feel like you need additional support with your coursework. We welcome your attendance, but we encourage you to use your time at codebar to develop skills that are outside the normal scope of your studies." - rule6: "Do not bring along and ask for help with any commercial work. This involves work you're being paid to do." - rule7: "Projects that involve specific frameworks/libraries (Rails, NodeJS, Meteor, Angular, Ember, React, etc) or languages that are not part of the codebar tutorials (anything other than Ruby or Javascript) are welcome but we cannot guarantee that a coach will be available to help you. In these cases we recommend selecting a codebar tutorial or katas (codewars.com or exercism.io) as a back-up option." - eligibility_criteria: - title: "Eligibility Criteria" - p_1: "codebar was started out of recognition that there is a shortage of women, LGBTQ, and people belonging to underrepresented ethnic groups in tech." - p_2: "If you belong to one of these groups, you are more than welcome to attend. If not, there are some other great initiatives like Open Tech School or Ask a Dev where you can learn in a collaborative environment." - p_3: "Bearing that in mind, it is sometimes difficult for us to identify whether attendees meet the eligibility criteria based on their first and last names. If we cannot determine your eligibility, we will contact you asking for a short confirmation that you have read this document and assert that you meet one or more of the criteria. We will never ask participants to specify which group." - p_4: "codebar is first and foremost a resource for students who cannot afford formal training through coding bootcamps or university degrees, for financial reasons or otherwise. Our coaches, organisers and sponsors donate their time and money to help those who have faced unfair barriers to entry into the tech world. We have strived to create an inclusive, welcoming community, and so far, we have not had to implement a formal policy to enforce the eligibility criteria -- we have left this to the honesty and good faith of the students." - p_5: "If you are unsure whether you are eligible, please get in touch. If we determine that you have signed up and do not belong to an eligible group, we will permanently suspend your student invitations without warning." - p_6: "We take this issue very seriously, and we appreciate your cooperation and understanding." - disability: - title: "Students with Disability" - description: "We want to ensure that our workshops are as accessible as possible. If you are disabled and are unsure about whether our venues can cater to your needs, we encourage you to please get in touch with us at hello@codebar.io and we will do what we can to accommodate you." - chapters: - intro_html: "Hi and welcome to codebar!" - info: "Check out our FAQ page for any questions you might have, or email us at %{email} if you can't find the answer you're looking for. Otherwise, click the Join our community button to join us." - sign_up: "to be invited to our workshops." - no_incoming: "There are no workshops coming up." - contact: "To contact the %{city} team, send an email to %{email}" - feedback_form: - title: 'Workshop feedback' - description: Your submission will be completely anonymous. We read every piece of feedback and use it to help us improve our workshops. - note: Please do not mention any names, but instead choose your coach from the dropdown. This enables us to address issues but also to anonymously share feedback with coaches. Member privacy is very important to us! - rating: Your overall rating of the workshop - coach: 'Who was your coach?' - select_coach: '- Select Coach -' - tutorial: 'What tutorial did you go through?' - select_tutorial: '- Select Tutorial -' - request: 'How did you find the workshop?' - suggestions: "Was there something you didn't like? What can we do to improve your experience?" - pages: - cookies: - title: Cookie Policy - p1: 'Cookies are small pieces of text used to store information on web browsers. They are used by websites accross a number of different devices to store and receive identifiers and other information. Our Website and Service use cookies and other similar technologies (collectively in this Policy, "cookies"), in order to provide a better service to you and to generally improve our Website and Service. For example, we may use cookies to help direct you to the appropriate part of our Website, by indicating that you are a repeat visitor. We also may use information to present you with services that are matched to your preferences and to manage and track the effectiveness of our marketing efforts.' - p2: Some portions of the codebar website are functional without cookies, and you may generally choose whether to accept cookies. Most web browsers are set to accept cookies by default, however, you may be able to delete cookies yourself through your browser's cookie manager. To do so, please follow the instructions provided by your web browser. Please note that disabling cookies will reset your session, disable auto-login, and may adversely affect the availability and functionality of our Website and the services we can provide to you. - sub: - title: Below are the cookies used by the codebar website. - table: - header: - h1: Name - h2: Purpose - h3: Expires - functional: - title: Functional Cookies - description: Stores information about your session. - planner_name: _planner_session - planner_purpose: Stores session data - planner_expiry: Expires after 24 hours - google_analytics: - title: Google Analytics - description: Google Analytics collects information about how you use the codebar website. This enables us to identify how busy the website is and possible improvements. - info: We don’t allow Google to use or share our analytics data. - opt_out: You can [opt out of Google Analytics](https://tools.google.com/dlpage/gaoptout). - ga_name: _ga - ga_purpose: Tracks if you have visited codebar.io before - ga_expiry: After 2 years - gid_name: _ga - gid_purpose: Tracks if you have visited codebar.io before - gid_expiry: After 24 hours - cloudflare: - title: Cloudflare - cfduid_name: _pfduid - cfduid_purpose: Used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. - cfduid_expiry: 1 year - privacy_policy: - title: Privacy Policy - subtitle: This Privacy Policy was last updated on 13 May 2021. - intro: - p1: 'This Privacy Policy has been created by codebar ("codebar", "we", "us", or "our") whose companies house registered name and address is as follows:' - address_html: " - codebar Ltd,
- International House,
- 101 King's Cross Road,
- London, England,
- WC1X 9LP
- Company No. 10791813
" - p2: codebar Ltd trades on behalf of the charity registered UK and Wales no. 1187776. For the purpose of this Privacy Policy codebar Ltd is the data controller. - p3: Your privacy means a lot to us, and we take it very seriously. We aim to be transparent with you about the data we collect about you and how it is used and shared. This Privacy Policy lets you know what information we collect when you use the codebar website, https://codebar.io/, or interact with any of the services we provide, such as signing up to workshops and events ("Services"). By using our Services you acknowledge and understand our use of your data under this Privacy Policy and how it applies to your use of our Services. - information: - title: 1. Information we collect - what_we_collect: - title: 1.1 Personal data we collect from you - p1: 'We have set out in the table below the personal data we collect about you and how we use it, which will differ based on the capacity in which you interact with codebar:' - table: - headers: - h1: Who - h2: What data we process - h3: What we use it for - h4: Lawful basis - r1: - c1: Students - c2: This includes personal data that is provided by you or collected by us to enable you to subscribe to codebar as a student. This may include your name, email address, phone number, pronouns, self-written bio, , your self-recognition as being underrepresented (with your consent), and the location you choose to subscribe to. - c3: For administrative purposes when you sign up to events, to communicate with you, and to provide you with our newsletters and events information. - c4: - l1: Performance of a contract - l2: Consent - l3: Legitimate interests - r2: - c1: Coaches - c2: This includes personal data that is provided by you or collected by us to enable you to volunteer at codebar as a coach. This may include your name, email address, phone number, pronouns, self-written bio/skills, , your self-recognition as being underrepresented (with your consent), and the location you choose to volunteer at. - c3: For administrative purposes when you volunteer for workshops, to communicate with you, to manage workshop attendance, and to provide you with our newsletters and events information. - c4: - l1: Consent - l2: Legitimate interests - r3: - c1: Organizers - c2: This includes personal data that is provided by you or collected by us, which may include your name, email address, phone number, pronouns, self-written bio/skills, , slack username, signed documentation, and the location you choose to volunteer at. - c3: To organise and communicate workshops. - c4: - l1: Legitimate interests - r4: - c1: Hosts - c2: We may collect personal information of employees working at companies that agree to host our workshops. This information may include the employees' name, email address, contact number, , and place of work. - c3: In order to market, promote, host and operate workshops. - c4: - l1: Legitimate interests - r5: - c1: Sponsors - c2: We need to collect personal data in relation to your sponsorship of codebar. This may include information such as your name, and bank details. - c3: To fulfill contractual obligations we have with you, for example, to process invoices related to your sponsorship. - c4: - l1: Performance of a contract - l2: Legitimate interests - r6: - c1: Trustees and directors - c2: We need to collect personal data in relation to your position as trustee and/or director. This may include information such as your name, contact number, address, email address, and date of birth. - c3: In order to establish our status as a charity, to comply with legal obligations, and respond to legal requests. - c4: - l1: Legitimate interests - l2: Compliance with legal obligations - how_we_share: - title: 1.2 How we share your information - p1_html: 'When you subscribe to an event, we share your name with our host companies as we are required to provide a list with all attendee names when you subscribe to any of our events. We **do not share** your email address or any other personal information.' - legal_basis: - title: 1.3 Legal basis for our use of your personal information - p1: As set out in the table above, sometimes the legal basis on which we collect and process your data is because our legitimate interests make the processing necessary, and those legitimate interests are not overridden by your interests or fundamental rights and freedoms. For example, we collect and store your data in order to process event information, and to ensure the efficient running and promotion of workshops. - retention: - title: 2. Retention - p1: We will keep your personal information for as long as reasonably necessary to fulfil the purposes we collected it for. To determine the appropriate retention period, we consider the amount, nature and sensitivity of the personal information, the potential risk of harm from unauthorised use or disclosure of your personal information, the purposes for which we process your personal data and whether we can achieve those purposes through other means, and the applicable legal, regulatory, tax, accounting or other requirements. - p2: We may retain your personal information for a longer period in the event of a complaint or if we reasonably believe there is a prospect of dispute in respect to our relationship with you. - international_transfers: - title: 3. International transfers - p1: Personal information we collect may be transferred to and stored in countries outside of the jurisdiction you are in for the purposes specified in this Privacy Policy. We will only transfer your personal information to countries that have been deemed to provide an adequate level of protection for personal information, and/or any international transfers will be made pursuant to appropriate safeguards in accordance with the applicable laws and regulations, such as standard data protection clauses adopted by the UK and European Commission. - p2: If you wish to enquire further about these safeguards used, please contact us by email at the address below or by mail using the postal address provided below. - your_rights: - title: 4. Your data protection rights - p1: 'Data protection law provides you with rights in respect of personal data that we hold about you, including the:' - l1: 'Right to Access: You have the right to obtain access to your data, and certain other information (similar to that provided in this Privacy Policy).' - l2: 'Right to Rectification: You are entitled to have your data corrected if it is inaccurate or incomplete.' - l3: 'Right to Erasure: This enables you in some circumstances to request and obtain the deletion of your data where there is no legal reason for us to keep using it.' - l4: 'Right to Restriction of Processing: You have rights to suspend further use of your data, whereby we can still store your data but cannot use it further. This may mean we can no longer provide you with Services.' - l5: 'Right to Data Portability: You have rights in some circumstances to request the transfer of your data to yourself or to a third party.' - l6: 'Right to Objection: You have the right to object to certain types of data processing, including for direct marketing purposes.' - l7: 'Right to Withdrawal of Consent: Where we are relying on consent to process your data, you have the right to withdraw your consent at any time by using any opt-out links, or by contacting us at the details provided below (although if you do so, it does not mean that anything we have done with your data with your consent up to that point is unlawful and we may be able to continue to process your personal information to the extent required or otherwise permitted by law, in particular in connection with exercising and defending our legal rights or meeting our legal and regulatory obligations).' - l8: 'Right to Lodge a Complaint: You can lodge a complaint in relation to our use of your personal information with the local supervisory authority, the Information Commissioner (UK).' - p2: If you would like to exercise any of these rights or if you have a complaint about how we handle your data, please contact us at the email address stated below. - security: - title: 5. Security - p1: The security of your personal information is important to us. codebar takes reasonable steps to implement and update administrative, technical, and physical security measures to help protect your information against unauthorised access, loss, destruction, or alteration. However, the Internet is not a 100% secure environment so we can't guarantee the security of the transmission or storage of your information. codebar has no control over or responsibility for the security or practices or privacy policies of third parties, even if you interact with them when using our Services. - changes: - title: 6. Changes to this Privacy Policy - p1: We reserve the right to modify or update this Privacy Policy at any time in accordance with this provision. If we make changes to this Privacy Policy, we will post the revised Privacy Policy on the codebar website. Please regularly review https://codebar.io/privacy-policy to check for any updates or changes to our Privacy Policy. The date this Privacy Policy was last revised is identified at the top of this page. - cookies: - title: 7. Cookies - p1_html: 'We use cookies to recognise you and your location. You can control cookies through your browser settings and other tools. For more information read our [cookie policy](https://codebar.io/cookie-policy).' - contact: - title: 8. Contact - p1: "If you have any questions or complaints about this Privacy Policy or our information handling practices, you may email us at company@codebar.io stating 'Data inquiry' in the subject title, or by postal mail at: codebar Ltd, International House, 101 King's Cross Road, London, WC1X 9LP." - breach: - title: What happens if you violate codebar’s Code of Conduct? - opening_para: All codebar events are dedicated to providing a harassment-free experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment towards any community member or organiser in any form. Harassment includes any type of aggressive behaviour or offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. - second_para: The Code of Conduct is in place to protect every codebar member - students, coaches and organisers. If any member violates these rules the below procedure and sanctions will be implemented. - outcome_title: 3 types of outcomes - correction: Correction - The use of inappropriate language or other behavior deemed unprofessional or unwelcome in the codebar community. This includes the use of terminology that is discouraged, e.g. 'guys'. In this situation you will be sent a private message, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. - warning: Warning - You will receive an email warning. The organiser will explain the incident, including the impact on the person involved and the community. We will give as much information as possible, so you’re aware of what happened and try to learn from the incident. The organiser will add a note to your codebar profile so that all chapter organisers are aware of the incident. We expect you to take our comments on board, further action may be taken depending on your reaction. Examples of behaviour that will get you a warning include - targeted offensive language, or the sharing of sexual images in codebar spaces. 2 email warnings will result in a lifetime ban. - lifetime_ban: Lifetime ban - You will no longer be able to RSVP to any future codebar events. You will also be removed from codebar’s Slack workspace. Examples of behaviour that will get you an automatic lifetime ban include - physical intimidation, stalking, inappropriate physical contact, unwelcome sexual attention or repeated behaviour after you’ve been spoken to by someone from the codebar team (directors or chapter organisers). - closing_para: The above is only a starting point. The details of the incident may change how we view it, e.g. some verbal harassment may be so serious that we would give a lifetime ban. - how_to_support_us: - volunteer: - title: Volunteer with us - become_an_organiser: - title: Become an organiser - description: Champion inclusion and diversity in the tech industry as a workshop organiser with codebar. Your contribution will create an empowering and safe environment, fostering learning and collaboration among individuals exploring coding in our vibrant community. - link: Email us to become an organiser - become_a_coach: - title: Become a coach - description: Affect change as a volunteer coach with codebar - your expertise and guidance will pave the way for aspiring developers, unlocking the world of coding and creating opportunities for folks from groups under represented in the tech industry. - volunteer: - title: Other skills - description: Your unique abilities could be our missing piece in the codebar puzzle. Having a diverse range of skills in our team is necessary to enrich our community. From fundraising to event coordination to marketing, we always welcome new talent to drive our mission forward. - link: Email us to become a volunteer - fundraise: - title: Fundraise - description_html: "Join the codebar team with a physical challenge event. Whether you are a runner, swimmer, or cyclist, sign up with our registration form for your desired event and raise vital funds to help keep our events running. If your event does not appear below, feel free to drop us an email and we would be happy to coordinate with you." - image_alt: A Black British woman crosses the finish line at the Hackney Half Marathon in London in a shower of confetti while spectators cheer her on. - codebar_stories_podcast: - image_alt: codebar stories banner - opening: codebar Stories is a new podcast brought to you by codebar, we'll be smashing down the belief that tech isn't for you by sharing real-life stories from members of our community who have transitioned into a new career in tech. - contact_us_html: "Sponsoring codebar Stories offers you a unique opportunity to connect with a diverse, engaged audience within the tech community. As a podcast dedicated to empowering underrepresented groups through coding education, your brand will align with our values of diversity, inclusivity, and social impact. Through sponsorship, you'll gain visibility, build positive PR, and demonstrate your commitment to fostering the next generation of tech talent, all while supporting a meaningful cause. Sound good? Please drop us an email podcast@codebar.io." - - admin: - dashboard: - title: 'Admin' - workshop: - manage_rsvps: - text: 'RSVP Students and Coaches to the workshop. The attendance confirmation email will be triggered and they will be removed from the waiting list.' - destroy: - success: "Workshop deleted successfully" - failure: "Workshop cannot be deleted. This is because it has invitees and/or workshop information is on the website for a while long enough that it cannot be deleted." - messages: - meeting: - created: 'Meeting successfully created' - updated: 'You have successfully updated the details of this meeting' - invitations_already_sent: 'Invitations were previously sent; they will not be sent again' - sending_invitations: 'Invitations are being sent out' - invitation: - rsvp_member: "%{name} has been successfully added and notified via email." - already_on_list: "%{name} is already on the list!" - rsvp_error: "Something went wrong, %{name} has not been added." - update_rsvp: 'Updated attendance of %{name}' - simple_form: - placeholders: - job: - company: 'e.g. codebar' - company_website: 'e.g. https://codebar.io' - title: 'e.g. Internship' - description: 'Use text or markdown for the job description' - location: 'e.g. London or Berlin' - hints: - job: - remote: Only check if the role is fully remote only - salary: Annual pay before tax, without commas or decimal points - activerecord: - attributes: - job: - title: Title - company: Name - company_address: Address - company_postcode: Postcode - company_website: Website - email: Contact email - link_to_job: Link to job post - expiry_date: Application closing date - donation_platforms: - title: "Donate" - description: "Your support—whether through a one-time gift or ongoing commitment—drives our mission to create a more inclusive tech industry. It enables us to provide continuous learning opportunities and empower individuals from underrepresented groups to grow and thrive in tech." - link: "Find out how else to support us" - donation_form: - title: "Use the donation page" - text: "Make a lasting impact with codebar by giving a one-time donation or committing to a monthly contribution." - image_alt: "codebar logo" - github_sponsors: - title: "Github Sponsors" - text: "Support codebar’s mission directly through GitHub Sponsors and help shape the future of technology with your generous donation." - image_alt: "Github Sponsors logo" - open_collective: - title: "Open Collective" - text: "Setup a recurring contribution or make a one-time donation through Open Collective." - image_alt: "Open Collective logo" - give_as_you_live: - title: "Give as you Live" - text: "Give as you Live is a platform enabling you to raise funds for your favourite charity with your everyday online shopping." - image_alt: "Give as you Live logo" diff --git a/config/locales/simple_form.de.yml b/config/locales/simple_form.de.yml deleted file mode 100644 index 552846bfa..000000000 --- a/config/locales/simple_form.de.yml +++ /dev/null @@ -1,31 +0,0 @@ -de: - simple_form: - "yes": 'Ja' - "no": 'Nein' - required: - text: 'erforderlich' - mark: '*' - # You can uncomment the line below if you need to overwrite the whole required html. - # When using html, text and mark won't be used. - # html: '*' - error_notification: - default_message: "Bitte korrigieren Sie die folgenden Fehler:" - # Examples - # labels: - # defaults: - # password: 'Passwort' - # user: - # new: - # email: 'Bitte geben Sie Ihre E-Mail-Adresse ein.' - # edit: - # email: 'E-Mail-Adresse' - # hints: - # defaults: - # username: 'Bitte geben Sie Ihren Benutzernamen.' - # password: 'Bitte keine Sonderzeichen verwenden.' - # include_blanks: - # defaults: - # age: 'Möchte ich nicht sagen' - # prompts: - # defaults: - # age: 'Bitte wählen Sie Ihr Alter aus' diff --git a/config/locales/simple_form.fr.yml b/config/locales/simple_form.fr.yml deleted file mode 100644 index 248ac4625..000000000 --- a/config/locales/simple_form.fr.yml +++ /dev/null @@ -1,25 +0,0 @@ -fr: - simple_form: - "yes": 'Oui' - "no": 'Non' - required: - text: 'requis' - mark: '*' - # You can uncomment the line below if you need to overwrite the whole required html. - # When using html, text and mark won't be used. - # html: '*' - error_notification: - default_message: "Veuillez corriger les problèmes ci-dessous:" - # Labels and hints examples - # labels: - # defaults: - # password: 'Password' - # user: - # new: - # email: 'E-mail to sign in.' - # edit: - # email: 'E-mail.' - # hints: - # defaults: - # username: 'User name to sign in.' - # password: 'No special characters, please.' diff --git a/crowdin.yml b/crowdin.yml deleted file mode 100644 index ee6e213c0..000000000 --- a/crowdin.yml +++ /dev/null @@ -1,3 +0,0 @@ -files: - - source: /config/locales/en.yml - translation: /config/locales/%osx_locale%.yml diff --git a/spec/features/internationalization_spec.rb b/spec/features/internationalization_spec.rb deleted file mode 100644 index cd522fe70..000000000 --- a/spec/features/internationalization_spec.rb +++ /dev/null @@ -1,32 +0,0 @@ -RSpec.feature 'Internationalization', type: :feature do - after(:each) do - I18n.locale = :en - end - - context 'a visitor to the website' do - context 'views the website in English' do - scenario 'by default' do - visit code_of_conduct_path - - expect(page).to have_content('Our events are dedicated to providing a harassment-free experience for everyone') - end - end - - context 'can configure another language by setting `locale=en|gr|de`' do - scenario 'can view the code of conduct in French' do - visit root_path(locale: 'fr') - visit code_of_conduct_path - - expect(page).to have_content('Nous nous engageons à fournir une expérience bienveillante et dépourvue de harcèlement pour tout le monde') - end - end - - context 'can not configure a non existing language' do - scenario 'by setting `locale=it`' do - visit code_of_conduct_path(locale: 'it') - - expect(page).to have_content('Our events are dedicated to providing a harassment-free experience for everyone') - end - end - end -end