Trying to navigate the repo to find some information about the Software Requirements specification document for this use case, I realized that it is very difficult. Some pointers are:
Avoid same naming between folders with different cases. For example, there is a folder named Exp and one called exp. That is not portable between systems.
Folder naming should be self explanatory. There is no need for extremes, but the code can be under a folder named src and include subfolders that will show what it is in there in a word. For example, if there are 5 scripts that include utility functions they can all be under a folder named utils.
I understand that the repo was refreshed in June, but I would like to ask if it can be brought to a state close to what our Development Documentation discusses.
Trying to navigate the repo to find some information about the Software Requirements specification document for this use case, I realized that it is very difficult. Some pointers are:
Expand one calledexp. That is not portable between systems.srcand include subfolders that will show what it is in there in a word. For example, if there are 5 scripts that include utility functions they can all be under a folder namedutils.I understand that the repo was refreshed in June, but I would like to ask if it can be brought to a state close to what our Development Documentation discusses.
Thank you