Report generation, notofication, storing and reviewing

[bumbu]

Perfect workflow:

• Click a button
• Done

Prerequisites:

• User's GitHub laboratory repository
• User's Name and Surname
• User's group
• Teacher Name, Surname and grade
• Template for laboratory work report
• Report submission deadline and penality points
• Laboratory work's tasks, points for each task and a template to mark completed tasks in laboratory work's readme

Submiting (server-side):

• Ask GitHub for OAuth authorization (in case that repository is private)
• Check if there is a submited laboratory work (otherwise cancel and show a debug message to user)
• Check if we can extract the list of completed tasks (otherwise cancel and show a debug message to user)
• Check if all tasks match tasks from that laboratory work (otherwise cancel and show a debug message to user)
• Init template
• Fill template with:
  • Laboratory work's number
  • Student's name and surname
  • Student's group
  • Teacher's Name, Surname and grade
  • Laboratory work's well formated readme
• Store template
• Notify teacher

Reviewing: TODO

Working drafts:

• RRG
• Report Generator Prototype

Old issues:

• Create a service for report generation
• Check report generating script

[minivan]

We'll have to grab a :beer: or :beers: and discuss this. I don't really understand the whole tasks thing.

[bumbu]

Sure