Who: every student, individually. Working target: M1, September 25. You can start before you have a partner.
What you do
- Open New issue → Individual task, set Primary parent issue to
#5, and select Onboarding / administration — no separate grade. Reuse an existing onboarding task if you have one.
- Follow the roster and fork instructions. Add your preferred public name and GitHub profile link to
CONTRIBUTORS.md; no personal profile or report is due now.
- Open the roster PR with
Closes #YOUR_TASK_NUMBER and Relates to #5, using your actual task number. Link the PR in your task and your task here; a comment is enough.
Your task is done when your roster PR is reviewed and merged with your authorship preserved. If access or setup fails, post the exact blocker and ask for help in your task. Fork PRs need no collaborator invitation. Late joiners agree a suitable target.
Next: share a business interest/support need and agree a small next task; use #3 when ready to form a pair. Starter practice under #1 is optional and is not part of completing onboarding. A browser-based roster PR needs no Git or Python installation.
Cohort tracking
A maintainer tracks each student's task/PR and support need. One student's completion closes only their own task.
Assessment and course guidance
Onboarding/access; no separate grade. A roster row or installation alone is not substantive Foundation evidence. Optional starter critique belongs under #1.
These weights apply across the semester, not per issue. Issue closure does not award marks. Tentative grading: 75% individual / 25% pair; grades and private feedback stay outside GitHub.
Student guide · Where tasks belong · Working schedule · Management view. Dates and formats are working targets; announced course direction can adjust them.
Who: every student, individually. Working target: M1, September 25. You can start before you have a partner.
What you do
#5, and select Onboarding / administration — no separate grade. Reuse an existing onboarding task if you have one.CONTRIBUTORS.md; no personal profile or report is due now.Closes #YOUR_TASK_NUMBERandRelates to #5, using your actual task number. Link the PR in your task and your task here; a comment is enough.Your task is done when your roster PR is reviewed and merged with your authorship preserved. If access or setup fails, post the exact blocker and ask for help in your task. Fork PRs need no collaborator invitation. Late joiners agree a suitable target.
Next: share a business interest/support need and agree a small next task; use #3 when ready to form a pair. Starter practice under #1 is optional and is not part of completing onboarding. A browser-based roster PR needs no Git or Python installation.
Cohort tracking
A maintainer tracks each student's task/PR and support need. One student's completion closes only their own task.
Assessment and course guidance
Onboarding/access; no separate grade. A roster row or installation alone is not substantive Foundation evidence. Optional starter critique belongs under #1.
These weights apply across the semester, not per issue. Issue closure does not award marks. Tentative grading: 75% individual / 25% pair; grades and private feedback stay outside GitHub.
Student guide · Where tasks belong · Working schedule · Management view. Dates and formats are working targets; announced course direction can adjust them.