Hein Meling

Should this be linked with #1049 and taken out of draft mode?

We probably want to replace zap logger with the [log/slog package](https://go.googlesource.com/proposal/+/master/design/56345-structured-logging.md) coming in Go 1.21. We should decide whether or not we still want to use a new `internal/logger` package,...

If we start logging via the context as this issue suggests, we should at the same time switch to structured logging and use a log viewer instead of less and...

We should investigate whether or not we still want to add support for slip days for groups now that we have individual grading for groups, it might be easier to...

I've been thinking more about this one. I'm leaning towards allowing single-member groups to push to non-group repositories (i.e., `-labs` repos), and have the tests executed, results recorded, and viewable...

It seems like the best approach would be to keep this as is and run benchmarks (and even tests) externally and then collect results by parsing the benchmark as was...

I'm a bit out of context for this issue, but just noticed that there is API for [`testing.BenchmarkResult`](https://pkg.go.dev/testing#BenchmarkResult) that possibly could be used for this. But there is probably a...

I’m still undecided about this issue. There are benefits to keep it here, such as keeping stuff together. Maybe we should just rename the folder to score. That would require...

Another benefit of moving the kit (as score) module to a separate repository is that cutting a new release becomes easier to collect the changes since last release (it can...

And we could remove the following sentence from `lab-submission.md`: - *These commit messages are not used by QuickFeed, they are only used to identify your lab submission commit when we...