Feature requests summary

manuel commented

2024-10-04 09:17:19 +08:00

Owner

List of features that were supported in 23fa and would be nice to have in JOJ3 and/or teapot.

JOJ3

custom runs:
- ~~based on who pushes a different workflow is run, eg. run the official workflow (TT) or a custom one (students)~~
- students write their own test framework (eg. cpplint, cppcheck, clang-tidy, google-test, etc.)
allow grading cc which takes effect only if committed by a TT member, eg. test(h1/e4): grading
limit submission count by user per problem

Teapot

display score badges in issues:
- ~~out of 100 for OJ (regardless of number of test cases and their weights)~~
- ~~out of 100 for CQ (decrease score as issues are discovered)~~
score and failed boards
- organise per assignment inside a "repo type" folder, eg. homework/h1-oj.csv, homework/h1-failed.md, homework/h2-cq.csv, p1/m1-oj.csv, p1/m2-failed.md
- ~~use markdown for scoreboard and include the link to the related posted issue~~
- sort scores from low to high in scoreboards
- sort failed boards from newest to oldest
- map submitter name to real name
Reuse one issue for one problem

JOJ3 and teapot

multi-submissions:
- allow to submit multiple tasks at once, eg. test(h1/e2 h1/e3): joj
- allow to submit a whole assignment, ie. automatically loop over all tasks, eg. test(h1): joj or test(h1/all): joj
report a summary of encountered problems (eg. in a issue) but still give access to complete logs (compilation and CQ). Could be as an attached log file (teapot) or on gitea actions "console" (joj3).

List of features that were supported in 23fa and would be nice to have in JOJ3 and/or teapot. ## JOJ3 - [x] custom runs: - [ ] ~~based on who pushes a different workflow is run, eg. run the official workflow (TT) or a custom one (students)~~ - [x] students write their own test framework (eg. cpplint, cppcheck, clang-tidy, google-test, etc.) - [x] allow `grading` cc which takes effect only if committed by a TT member, eg. `test(h1/e4): grading` - [x] limit submission count by user per problem ## Teapot - [ ] display score badges in issues: - [ ] ~~out of 100 for OJ (regardless of number of test cases and their weights)~~ - [ ] ~~out of 100 for CQ (decrease score as issues are discovered)~~ - [x] score and failed boards - [x] organise per assignment inside a "repo type" folder, eg. `homework/h1-oj.csv, homework/h1-failed.md, homework/h2-cq.csv, p1/m1-oj.csv, p1/m2-failed.md` - [ ] ~~use markdown for scoreboard and include the link to the related posted issue~~ - [x] sort scores from low to high in scoreboards - [x] sort failed boards from newest to oldest - [x] map submitter name to real name - [x] Reuse one issue for one problem ## JOJ3 and teapot - [x] multi-submissions: - [ ] allow to submit multiple tasks at once, eg. `test(h1/e2 h1/e3): joj` - [ ] allow to submit a whole assignment, ie. automatically loop over all tasks, eg. `test(h1): joj` or `test(h1/all): joj` - [x] report a summary of encountered problems (eg. in a issue) but still give access to complete logs (compilation and CQ). Could be as an attached log file (teapot) or on gitea actions "console" (joj3).