Skip to content

Add grading criteria for KTH DevOps course - #2928

Merged
monperrus merged 3 commits into
2026from
update-grading-criteria
May 12, 2026
Merged

Add grading criteria for KTH DevOps course#2928
monperrus merged 3 commits into
2026from
update-grading-criteria

Conversation

@larissaschmid

Copy link
Copy Markdown
Collaborator

Added detailed grading criteria that are aligned with Bloom's taxonomy, including project requirements, demo expectations, scientific paper presentations, executable tutorials, open-source contributions, and feedback guidelines.

larissaschmid and others added 3 commits March 26, 2026 13:14
Added detailed grading criteria for the KTH DevOps course, including project requirements, demo expectations, scientific paper presentations, executable tutorials, open-source contributions, and feedback guidelines.
Added passing criteria for various sections.
Updated project description and deliverables for clarity. Adjusted terminology for system architecture and integration.
@monperrus
monperrus merged commit 62b44bb into 2026 May 12, 2026
2 checks passed
@larissaschmid
larissaschmid deleted the update-grading-criteria branch May 20, 2026 08:48
algomaster99 added a commit to algomaster99/github-canvas-integration-devops that referenced this pull request Aug 29, 2026
…hema

grading-criteria.md was redesigned for 2026 (KTH/devops-course#2928) to use
Category/Criterion/Description/Requirement table columns instead of the old
Criteria/Yes/No checklist, which broke validate_criteria() (every row failed
validation) and rubric_payload() (assumed 'Criteria' + arbitrary Yes/No rating
columns). Category isn't used downstream, so it's dropped during parsing.

Rubric mapping follows the shape of a prior year's real Canvas rubric:
description is "Criterion: Description", and ratings are Mandatory(1pt)/-(0pt)
for Mandatory rows or Yes(1pt)/No(0pt) otherwise.

Also drops the auto-filed "grading file not formatted" GitHub issue on
validation failure -- it hardcoded an assignee that's no longer a valid
GitHub user, causing a 422 that masked the actual validation errors.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants