link to todo file from development.rst

development.rst

@@ -18,4 +18,10 @@ We use `CalendarVersioning <https://calver.org/>`__ with the YYYY.MM.DD format,
 
 There is a global version of the Python package (in `src/mpsd_hpc_tools/__init__.py <src/mpsd_hpc_tools/__init__.py>`__) and a local version for each tool (i.e. for ``mpsd-quota`` in `src/mpsd_hpc_tools/quota.py <src/mpsd_hpc_tools/quota.py>`__ When a tool (such as ``mpsd-quota``) is asked for its version (``mpsd-quota --version``), it displays the local version.
 
-Version numbers need to be updated manual: update the local version when committing changes. Commit the global version to the same new date. (Could be automated.)
+Version numbers need to be updated manual: update the local version when committing changes. Commit the global version to the same new date. (Could be automated.)es
+
+
+Brainstorming / TODOs
+---------------------
+
+Are gathered in `todo.org <todo.org>`__.

todo.org

@@ -8,10 +8,16 @@
 
   Alternatively, we could test the tool in-place ONCE we have a test framework
   such as 'reframe' deployed.
+
+  Hans: probably a few simple tests that can execute anywhere are useful just to
+  get the idea of CI going. I'll add this later.
   
 ** (future) features
 - sanity check if program is attempted to run on machines that do not have ~getfattr~ ?
   - perhaps use some environment variable to check if we are on the HPC system, and abort if that is not found?
-- coloured output?
-- reduce available storage if storage is getting tight?
+  - coloured output?
+- reduce available storage if storage is getting tight? Situation: perhaps there
+  are only 10TB of storage left on scratch, but the user has not used any. So
+  that user's quota would (probably) display 25TB available. Should we reduce
+  the number in that situation to 10TB?