Retraining
Developers with weaknesses in either set design or toolkit proficiency may have to go through retraining. When this happens, the Developer Compliance and Code Review teams jointly discuss and have to agree that retraining is in order for it to take place. During that discussion, the teams have to discuss if the developer has to go through the junior program again, or if they can go through retraining as described here.
To be eligible for retraining, the developer must:
- Be proficient in either set design or with the toolkit, but lacking in the other. Retraining is to address issues with one of the two, not both at the same time. If the team deems the developer weak in both, retraining via the junior program is mandatory.
- Acknowledge the issues raised by the teams and be willing to revise their portfolio in good faith.
- Accept to go through retraining. Developers can freely opt to apply to the junior program to have more support from the Code Review Team.
While in retraining, the developer:
- Cannot make any new non-revision claims.
- Must drop non-revision claims. Exceptions can be made for sets where the developer already has significant progress towards publication, and only with explicit approval from the Code Review Team. If an exception like this is approved, it must be reviewed before publication like revisions.
- Must run their revision by the appropriate team for approval before publication.
At the start of the process, the teams will:
- Clearly identify at least 5 sets that require a revision, explicitly identifying issues.
- Set a clear road map for progress towards the end of retraining. This does not need to be an exhaustive list of problematic sets to fix for large portfolios, but needs to be comprehensive so everyone involved can clearly identify what issues are left to address.
- Set clear expectations for progress. The developer is expected to apply recommendations for one revision to the next ones, requiring less oversight as things go on.
For retraining restrictions to be lifted, the developer must:
- Show commitment to revise every set in their portfolio that present the issues identified by the teams.
- Show proficiency in doing the above by revising no less than 3 sets with reviews.
After any review, the Code Review Team can decide that the junior program is necessary. This gives access to junior spaces and more direct support from Code Reviewers for everything, but means that only one revision claim at a time can be made.
The goal of this process is to give the opportunity to developers to bring their standards up to be valuable contributors to the project and the community.