Cleanup of initial-combine branch

[cecilianor]

During today's standup, Cecilia would like to discuss what tasks need to be completed before we pull/merge the initial combine branch in to main.

Cecilia would like us to have a meeting (at some point soon) where we agree on the following:

• Documentation standards:
  • Documentation standard. Are we using Doxygen or Qt's standards?
  • Whichever standard we use: How do we follow it correctly? How do we comment functions and variables consistently across the team?
• Code standards:
  • What are the general standards for our code?
  • Can we agree on naming standards for our code? Are shorthand forms okay?
  • Which case or cases will be used in naming of variables? Is m_variable okay, or do we prefer mVariable or myVariable or something else? What about naming of functions? What are best practices for enums?

• Folder structure:

  • The project currently has multiple mains and having library files in multiple different folders. Can we streamline this?
  • Can we remove duplicate files/folders that are not supposed to be there anymore, like duplicate http folders or multiple mains?

  Nils knows C++ the best, so he should probably have the final say on these matters. Cecilia can set up a document where these things are written down, and she suggests porting them to both Overleaf (for the report) and Git (for ease of access and additional backups).

[cecilianor]

Also, I don't think the unit tests need to be a part of the initial-combine-branch. That can be worked on in a separate branch or separate branches.