Tasks for 2025 updated (#46)

Author: ReimarBauer

docs/04_gsoc.md

@@ -34,14 +34,17 @@ We have labled small sized issues as "good first issue" on <https://github.com/O
 
 ## Difficulty level: Hard
  * [wms: Support Of Simple Trajectory Calculations](/develop/GSOC/support_of_simple_trajectory_calculations)
- * [msui: Overlay Measured Data](/develop/GSOC/overlay_measured_data)
 
 ## Difficulty level: Medium
  * [cli: Improve Tutorials](/develop/GSOC/improve_tutorials)
+ * [cli: Use MSS Figure Objects](/develop/GSOC/figure_objects)
  * [wms: Plot Gallery integrated](/develop/GSOC/integrated_plot_gallery)
  * [wms: Implement and support color bars being served](/develop/GSOC/color_bars_served)
  * [msui: View Layout and Restoring](/develop/GSOC/view_restoring)
+ * [msui/mswms/mscolab: Replace pyfilesystem2](/develop/GSOC/replace_pyfilesystem2)
  * [msui/mscolab: Improve User Managment](/develop/GSOC/improve_user_managment)
+ * [tests/mscolab/mswms: Flask native configuration](/develop/GSOC/flask_native)
+ * [tests: Replace Multiprocessing](/develop/GSOC/replace_multiprocessing)
 
 ## Your own idea
 

docs/develop/GSOC/figure_objects.md

@@ -0,0 +1,33 @@
+---
+layout: page
+title: GSOC Idea
+permalink: /develop/GSOC/figure_objects
+exclude: true
+---
+
+# API to use MSS figure objects in other python modules e.g. Jupyter Notebook
+
+- **Project description**:
+    The MSS tool is currently designed for interactive use and having an mssautoplot 
+    cli script for post-campaign analysis, retrieving a standardized set of layers for hundreds 
+    of time-steps an automated plotting feature was developed. 
+    The next step is to create based on the mssautoplot an API to be used in other python modules. 
+
+    This should enable a user to add its own data to our figures used. 
+    This is especially interesting for data of the linearview. 
+    There a user can overlay on its own measured data. In addition scatter plots shall be enabled.
+    The new API may be used in a Jupyter Notebook. 
+    This needs also a different solution to create a mssautoplot.json file by a textual user interface. 
+    
+- **Duration**: 175h - 350h
+  
+- **Skills**: Python, Git, Textual, Jupyter Notebook
+
+- **Difficulty level**: Medium
+
+- **Related Readings/Links**:
+    - https://mss.readthedocs.io/en/stable/mssautoplot.html
+    - https://mss.readthedocs.io/en/stable/tutorial.html
+
+- **Potential mentors**:
+    [email protected], [email protected], [email protected] 

docs/develop/GSOC/flask_native.md

@@ -0,0 +1,22 @@
+---
+layout: page
+title: GSOC Idea
+permalink: /develop/GSOC/flask_native
+exclude: true
+---
+
+# use flask-native global configuration
+
+- **Project description**:
+Every Flask app has a .config attribute to store configuration. Additionally, for MSColab/MSWMS we have mscolab_settings/mswms_settings. This is redundant, we could just use app.config for everything that should be made globally available in the application in a key-value fashion.
+
+- **Duration**: 175-350h
+- **Skills**: Python, flask, pytest Git, AI-Assistant
+- **Difficulty level**: Medium
+- **Related Readings/Links**:
+  - https://github.com/Open-MSS/MSS/issues/2506
+  - https://github.com/Open-MSS/MSS/issues/2442
+  - https://flask.palletsprojects.com/en/3.0.x/patterns/appfactories/
+- **Potential mentors**:
+  [email protected], [email protected]
+

docs/develop/GSOC/overlay_measured_data.md

@@ -0,0 +1,19 @@
+---
+layout: page
+title: GSOC Idea
+permalink: /develop/GSOC/replace_multiprocessing
+exclude: true
+---
+# Replace multiprocessing usage in test fixtures with subprocess
+
+- **Project description**:
+We want to use our tests on all supported platforms. This means we have to remove*/replace the multiprocessing fork method by subprocess.
+A server process during tests should start in its own python process. This separation enables options for testing with e.g. basic_auth or different wsgi servers.
+
+
+- **Duration**: 175-350h
+- **Skills**: Python, (flask), (socketIO), pytest, Git, AI-Assistant
+- **Difficulty level**: Medium
+- **Related Readings/Links**:
+- **Potential mentors**:
+  [email protected], [email protected]

docs/develop/GSOC/replace_multiprocessing.md

@@ -0,0 +1,22 @@
+---
+layout: page
+title: GSOC Idea
+permalink: /develop/GSOC/replace_pyfilesystem2
+exclude: true
+---
+
+# replace pyfilesystem2 by pathlib
+
+- **Project description**:
+The whole project needs to become refactored for replacing our usage of pyfilesystem2 by pathlib.
+
+
+- **Duration**: 175-350h
+- **Skills**: Python, flask, socketIO, pathlib, Git, AI-Assistant
+- **Difficulty level**: Medium
+- **Related Readings/Links**:
+  - https://github.com/Open-MSS/MSS/issues/2103
+  - https://github.com/Open-MSS/MSS/issues/2347
+- **Potential mentors**:
+  [email protected], [email protected]
+

docs/develop/GSOC/replace_pyfilesystem2.md

@@ -12,7 +12,8 @@ exclude: true
   The PyQT Gui of the MSS client can currently handle different views by one flight path. 
   This means once a new flight path is loaded and activated all views change to this flight path. 
   Such a View configuration consists of many windows with a complex set of configuration options that 
-  are tedious to re-create after shutting down the application.
+  are tedious to re-create after shutting down the application. The configuration of individual views
+  can be stored using the autoplot docking widget on a local mssautoplot.json. 
   The mscolab UI should allow for storing and restoring the view configuration of  
   multiple windows for the user for an operation. The autoplot dockingwidget may use this configuration too.
   This includes also to store all qsetting parameters on the server.