Assignment administration workflow

Assignment administration workflow#

This is the release schedule:

Day	Time	What	Where
Friday afternoon during week -1	12:30	- Book chapter - Programming assignment - See below for content of week -1	- Book - Workbook - Homepage
Monday afternoon	12:30	Lecture slides	Homepage
Wednesday morning	10:30	Programming assignment solutions Workshop	- Workbook - Homepage
Wednesday afternoon	12:30	Workshop solutions	Workbook
Friday morning	8:30	Group assignment	- Workbook - Homepage
Friday afternoon	12:30	- Group assignment report (with and without solutions) - Group assignment solutions - See above for content of week +1	- Workbook - Homepage

Note that the Friday afternoon always contains release of this week and the next one.

Steps to publish assignments:#

Update formatting files if not done yet:
- Citation file
- CC BY footer
- Consistent headers
- Catchy title in readme, descriptive title for files
- Readme contains links with relative paths to the other files.
- Binary files (images, datasets) are stored on FTP server or Git LFS repository.
- No copyright issues
- Split files into separate tasks where possible
- Add markdown version of .py files (to be implemented in workflow) in assignment_book and solution_book branch.
- Placeholders in README.md are replaced with the actual assignment name.
If programming assignment:
- Change default branch of assignment repository to assignment_template (Settings - Branches - Default branch - Change default branch).
- Create new assignment (but this time public) based on this template assignment with the same name but with _template after it (so for example PA1.1_template).
- Make this repo a template too.
- Rename branch of the template assignment from assignment_template to assignment.
- Change default branch of the original assignment repository back to main.
Check correct version in .gitmodules file: assignment.
Adjust toc.yml in workbook with all files of the assignment. The readme is taken as the section header page, the other files are added as subsections. For GAs: the report is not added in the assignment version.
Update changelog in workbook
Check whether automatic commits don’t include undesired changes from other assignment repositories.
Check rendering in book
Update overview on homepage MUDE
Update changelog for homepage
Share link with students

More details below

Workflow for GA printing, scanning and grading#

See table below, where teacher refers to the content leader and MUDE MT refers to content coordinator.

What	Who	When
During the session
Send email to non-group student	MUDE MT	Thursday/Friday (scheduled email)
Print questions and distribute over rooms	TA	Friday morning (before 9:30)
Get scrap paper from cupboard in one of the rooms and distribute	TA	Friday morning (before 9:30)
After the session (ASAP)
Scan all papers and store where?	TA	Before handover meeting
Distribute among graders and to responsible Teacher	TA	At handover meeting
Grade the fist batch (~10) and finalize mark scheme	Teacher	Friday afternoon
Send answers from non-group student to grader	MUDE MT	Friday afternoon
During following week
Draft general feedback to students	Teacher
Grading of other reports, collect grades in excel	TA
Final check on grades general feedback	Teacher
Upload grades to brightspace	TA
Publish grades on brightspace	MUDE MT
Announcement with general feedback	MUDE MT
Add feedback to workbook	MUDE MT
Collect papers for returning to groups at next	TA

Steps to print report questions#

Go the assignment repository
Open the assignment_print branch
Open report.md
Copy the raw content into https://print.markdown.janqi.com/
Print!

Steps to update assignments with typos or solution:#

Update assignment repository.
If solution to be published: change branch name in .gitmodules file to solution in release branch
If assignment is finished for GAs: add report to _toc.yml of the workbook.
Update changelog in workbook
If no changes have been made to the workbook-repository, but you want to update the workbook with the updated assignment repositories: trigger the build workflow manually from the workflow tab
Check whether automatic commits don’t include undesired changes from other assignment repositories.
Check rendering in book

More details below.

Solutions are shared for/on:

Workshop assignments after processing the feedback collected for the workshop, preferably on the same day.
Group assignments after grading
Programming assignments after deadline: preferable on Saturday after Friday deadline.

Prepare repositories as administrator#

Create an organization for your assignments. This repository will include source repositories, but also student repositories.
Go to People to add members. In MUDE, the MUDE MT is added to a team (under Teams) and has been given All-repository admin rights under Settings - Organization roles - Role assignment.
Apply for a GitHub Education GitHub Team for some useful additional options
Create repositories from the template repsitory with the same git history: TUDelft-MUDE/assignment_repo_template. Therefore clone the template repository and push it to a new remote (it’s like a fork, but you cannot create more than one fork). This template contains a README.md containing some basic information, a citation file, template notebook, license file, template report, requirements file and github workflow for stripping out assignment and solution blocks. In MUDE we use:
- WS1.1 for workshops assignments indicated with <Q1/Q2>.<week1-8>
- GA1.1 for group assignments indicated with <Q1/Q2>.<week1-8>
- PA1.1 for programming assignments indicated with <Q1/Q2>.<week1-8>
Go to Settings - General:
- under General: check Template repository
- under Features: uncheck Wikis
- under Pull requests: check Always suggest updating pull request branches Loading and Automatically delete head branches
Go to Rules - Rulesets, click Import a ruleset and import this file. This is imported to protect the assignment and solution branches which should be read-only.
Go to Settings - Collaborators and teams to add the responsible people. In MUDE the responsible teacher of the topic has admin access and can add his topic-colleagues. To bypass this, a repository secret needs to be added to every repository called FG_MUDE_2025_TOKEN, which can be a fine-grained PAT with a least content access.

Combine assignments in workbook#

The workbook has all the assignment repos as submodules so that it can use those files to create previews in the book. To be able to clone those submodules during the build, a personal access token is added as GH_PAT to the repository action secrets with ‘repo’ scope, as explained in the TeachBooks Manual. Furthermore, a step in the workflow is included to update submodules.

Release assignment in workbook#

How to release an assignment to students in the workbook is shown below (note that this video includes a deprecated implementation of github dependabot):

To share the solution, change the branch assignment to solution in the .gitmodules file and retrigger the dependabot as shown in shown in the video above (and merge pull request,update changelog and add version number)

Which should then be followed by the same steps as shown above to add the assignment to the workbook.

Permissions GitHub#

Permissions are managed with GitHub teams and organization roles:

Teacher and TAs are added with an all-repository read role
The MUDE MT team (child team of the ‘Teacher and TAs’-team) has an all-repository admin role
Child teams of the ‘Teacher and TAs’-team are created for every topic. The content leaders are added to these teams. These teams are assigned admin rights for their specific assignment repositories, allowing them full control over their repositories (except for editing the assignment and solution branch).

The base permission of the organisation is set to ‘no permissions’, repository and pages creation is disabled ( Settings - Member privileges). Furthermore, admin repository permissions are all disabled ( Settings - Collaborators and teams - Admin repository permissions).