Skip to content

Milestones

List view

  • This work must be completed by the launch of ITD-1-2025

    Due by January 1, 2025
    β€’3/3 issues closed
  • This milestone collects the tickets that belong to iteration, optimising, and revising tasks.

    Due by October 27, 2024
    β€’14/14 issues closed
  • By the end of this milestone the following criteria will be met:

    Due by August 19, 2024
  • The completion of the ITD signifies that it is now fully prepared for the volunteers to test proceed through the steps.

    Due by July 22, 2024
  • Work we need done before we launch the new ITD # Programme 1, ITD 30 days Leaders: @zacheeniyokwizera A mix of Scrimba and Applied Digital Skills from Google, with one CYF challenge at the end 1. Write a CV in Google docs with [Generative AI](https://www.codecademy.com/learn/streamline-resume-creation-with-generative-ai-case-study) 2. Evaluate data with [Google Sheets: a career in data analytics](https://applieddigitalskills.withgoogle.com/c/college-and-continuing-education/en/try-a-career-in-data-analytics/overview.html) 3. Build and deploy [five websites to Netlify with Scrimba](https://v2.scrimba.com/learn-html-and-css-c0p) including the capstone project step with review 4. Complete [CYF Blocks](https://blocks.codeyourfuture.io/#introduction) ### By the end of ITD, you should have: 1. A CV which you have written and revised 2. A spreadsheet you have made in Google sheets 3. A portfolio website deployed to Netlify 4. A basic understanding of programming: variables, loops, control flow demonstrated by completing CYF Blocks

    Due by August 30, 2024
    β€’8/8 issues closed
  • Work we need done before the launch of new ITP ## At the end of ITP, you should be able to 1. Predict and explain the execution of a computer program 1. Reason about where and when software is executed 1. Refactor and iterate code based on new requirements 1. Extract simple composable functions for common use cases 1. Interpret business requirements and express them as test cases 1. Create a strategy for implementing an application based on a set of user stories 1. Design interactions with a provided data set 1. Verify the accessibility of a web application 1. Describe how processes and file descriptors really work 1. Open a pull request and iterate on it in response to feedback ## We suggest mandating 1. [Codewars](https://www.codewars.com/users/CodeYourFuture/authored_collections) 5kyu 1. [The Bandit](https://overthewire.org/wargames/bandit/) 30 1. [Code In Place](https://codeinplace.stanford.edu/) ## Tech 1. JavaScript 1. Python 1. Git 1. Linux 1. SQL

    Due by September 30, 2024
    β€’28/28 issues closed
  • 1st sift requirements (end of ITP, before start of piscine) - B2 English CEFR - Functional Maths Level 2 - Cover letter (minor manual check) - Codility, get 100% on the kata? - Rainbird check 2nd sift (end of piscine, before start of jobs program) - Logical reasoning exercise - Coding session - 3 weeks, 3 projects, 2 team projects & 1 individual

    Due by September 1, 2024
    β€’3/3 issues closed
  • Once **How our curriculum works** has been released, we'll need to realign Fundamentals to be in sync with the goals and concepts developed in the HOCW module. Some of the work involved: - Create new workshops related to **self educate**, **self coordinate** and **self evaluate** for each week of Fundamentals - Reuse some blocks from How our curriculum works in the Fundamentals module - Add morning orientation blocks to the Fundamentals module - Improve existing workshops

    Due by May 31, 2024
  • Implement the self educate section of the **How our curriculum works** module ## Volunteer stories πŸ“– As a new volunteer, I need to: - Explain what the milestones are - Explain why the milestones are important As a new volunteer, during the first three sessions I've attended, I need to: - Review at least 1 PR - so we can keep building a community of self evaluators

    Due by May 7, 2024
    β€’3/3 issues closed
  • Implement the **self coordinate** section of the **How our curriculum works** module ## Volunteer stories πŸ“– As a TRAINEE OR VOLUNTEER, I know WHAT THE RHYTHM OF THE WEEK is, So that WE BROADLY UNDERSTAND WHAT TO DO AND WHEN during a typical week at CYF As a TRAINEE OR VOLUNTEER, I know how to reinforce THE RHYTHM OF THE WEEK, So that we don't lose momentum when the class is running. As a new volunteer, I need to: - Locate the day plan for a given sprint week in a given module - Identify the morning orientation block in a day plan - Use the module view and the rhythm of the week to identify when certain sections need to start during the week As a new volunteer, during the first three sessions I've attended, I need to: - Take part in Saturday class as a time keeper/facilitator

    Due by April 23, 2024
    β€’7/7 issues closed
  • Implement the self educate section of the **How our curriculum works** module ## Volunteer stories πŸ“– As a new volunteer, I need to: - Navigate the curriculum to locate the prep content - Explain why active learning is critical to the CYF educational philosophy - List some strategies for active learning/participation during Saturday sessions - Explain why prep before an in-person session is important - Describe how we use workshops during Saturday sessions at CYF - Explain why we don't lecture at CYF - List and describe the challenges of using a flipped classroom model As a new volunteer, during the first three sessions I've attended, I need to: - Discuss at least one current problem with at least one small group/individual trainees so we can keep building a community of self educators

    Due by April 9, 2024
    β€’7/7 issues closed
  • No due date
    β€’1/1 issues closed
  • Definition of done The curriculum website with Migracode branding is in production. This means a volunteer or trainee can show up and know what they are doing every week.

    Due by May 1, 2024
    β€’10/10 issues closed
  • Pick up changes and improvements from delivery

    Due by May 1, 2024
    β€’3/3 issues closed
  • Pick up changes and improvements after delivery

    Due by March 1, 2024
    β€’5/5 issues closed
  • Pick up changes from delivery and classes

    Due by April 1, 2024
    β€’2/2 issues closed
  • Due by December 20, 2023
    β€’1/1 issues closed
  • Due by December 6, 2023
    β€’4/4 issues closed
  • Due by December 8, 2023
    β€’5/5 issues closed
  • Due by December 15, 2023
    β€’4/4 issues closed
  • First iteration of JS3 rewrite

    Due by December 1, 2023
    β€’30/30 issues closed
  • Due by September 27, 2023
    β€’17/17 issues closed
  • Due by August 23, 2023
    β€’21/21 issues closed
  • Due by August 9, 2023
    β€’30/30 issues closed