Gitlab Community Edition Instance

Skip to content

A general task queue for reviewer and tutors

Description / Overview

The idea is that tutors and reviewer transparently see which task is up next. This is either a specific task or the description of a generic possibly infinite task that outputs a specific task when requested.

Note: this is just an idea and needs further specification.

Use cases

  • A tutor wants to correct only specific tasks e.g. of one type of submission type.
  • A reviewer (re-)assigns a specific task to a tutor that might have a priority (prepend).
  • A reviewer assigns a batch of tasks to themselves e.g. all of a specific student. See #51 (closed).
  • A tutor that quickly needs to focus on another tasks can keep track of the postponed task(s).

Note: I use the general term task since this behaviour might be very generic to implement (in the future more complex tasks might evolve). In the end tutors and reviewers are nothing more than human implementations of the Actor pattern. 🙈 For us a task usually is creating, reviewing or clarifying feedback.

With more than one reviewer these queues need to support some level of concurrency.

Links / references

Feature checklist

  • User can add certain tasks to a queue
  • User can remove tasks from list (what happens with the task?)
  • Tasks are archived when done
Edited by Jan Maximilian Michal