Assumes we will have a top-level directory per language, each with an associated README.md file describing or linking to the conventions we recommend. As discussed in https://github.com/UCL-ARC/coding-standards/issues/2#issuecomment-1770910877 we can also put other language specific content such as recommended linter configuration files in the relevant directories and link to from the README files.
Currently this has empty README.md files for an arbitrary set of languages that I first thought of, other than Python which copies over the existing material from internal documentation. We might want to just remove the empty files and add directories as we add each language, but I'll hold off making changes here till @milanmlft's R recommendations from #8 are merged.
Resolves #2
Assumes we will have a top-level directory per language, each with an associated
README.mdfile describing or linking to the conventions we recommend. As discussed in https://github.com/UCL-ARC/coding-standards/issues/2#issuecomment-1770910877 we can also put other language specific content such as recommended linter configuration files in the relevant directories and link to from the README files.Currently this has empty
README.mdfiles for an arbitrary set of languages that I first thought of, other than Python which copies over the existing material from internal documentation. We might want to just remove the empty files and add directories as we add each language, but I'll hold off making changes here till @milanmlft's R recommendations from #8 are merged.