List view

• Define a consistent guide for data validation

  In the ISPyPSA repo in particular, across submodules and functions there are variations in how data validation (and e.g. handling empty inputs, implementing flexibility within inputs) is being applied at the moment. We would like to create a set of guidelines for developers to follow when adding or updating features and functionality to ensure a consistent approach across the codebase.

  No due date

  •0/3 issues closed
  0% complete3 open0 closed

• Define project-wide style guide

  Set up and document a clear style guide to be applied across the Open ISP project. This includes: - deciding on and applying standard names for columns/variables that refer to concepts like REZs, sub-regions, "name(s)", technology vs. resource etc. - documenting a code-specific style guide (simple stuff like var naming conventions) - documenting paradigmatic/architectural style guide etc. Alongside setting up the style guide, we could consider setting up a glossary-style document for transparency and ease of use, and to log reasoning where applicable.

  No due date

  •0/3 issues closed
  0% complete3 open0 closed

• Define project-wide git workflow

  We need to discuss, decide on and then document an agreed upon git workflow that should be adopted project-wide. This should be able to guide new collaborators and ensure cleaner, simpler and easier collaborative ongoing work.

  No due date

  •2/5 issues closed
  40% complete3 open2 closed