CodeYourFuture / CodeYourFuture/Changes
CYF Pathways 2.0 proposal
- Lingua principale
- JavaScript
- Stelle
- 3
- Fork
- 4
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
[Please have a look at [this file](https://docs.google.com/document/d/1HmTcQlxpAC0cEn9Cl3PoaTU5VHwH_c77DsRPeUQu-wE/edit?usp=sharing) for more details]
## I want to do this:
As the newly formed London board, we wanted to change the way the tracks are implemented. We feel that having tracks after the Full Stack course with a duration of 5 weeks would clarify the expectations and objectives of the tracks as well as relieving the pressure put on the program managers.
## Here’s why I want to do it:
Tracks are always a confusing moment for the trainees and volunteers. It produces a lot of stress for everyone in the community, stretches resources and results on trainees dropping out.
## Here’s how it serves our goals:
Getting everyone to do the full stack course will help trainees and CYF identify their strengths and weaknesses more objectively. Having a tests before getting into the tracks and final project is improving our chances of higher employment at the end of the course and limiting frustration during final projects.
## This is how much time I can put towards this change:
We are ready to support CYF staff to implement any changes required.
## This is the help I need from others to get this done (if any):
Feedback on the solution (such as the checkpoint test) and communication.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Inizia leggendo il Google Doc collegato, quindi confronta i suoi track proposti di cinque settimane, il test di checkpoint e le modifiche alla comunicazione con la descrizione dell’issue. Non vengono indicati file del repository, test o entry point; per considerare il lavoro completato servirebbero una proposta concordata e un piano di implementazione definito con il feedback dello staff di CYF.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Ambito
- content
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100