I have an ask of everyone here. In the ROSES 2024 program, there's a new component to the B.20: Heliophysics Tools & Methods call:

This call solicits proposals to advance the goal of a robust, vital, and cohesive Python environment for Heliophysics. Two types of HTM programs are solicited: new HTM efforts and HTM maintenance efforts…

2.2 Heliophysics Tools and Methods Maintenance proposals 
This type of proposal is targeted at existing efforts within the Python in Heliophysics Community (PyHC) that have attracted a broad user base. Types of projects to be proposed under this call may include but are not limited to:
•	Converting the software to a newer version of the programming language
•	Addressing bugs and issues 
•	Improving the package's alignment with current PyHc software standards 
•	Improving the package's alignment with the requirements in SPD-41a 
•	Significant documentation improvements, including installation instructions 
•	Merging capability of one or more smaller packages into a larger one 
•	Interoperability and usability improvements

I understand that these calls are smaller in size. However, to my understanding, this is a pilot program. To keep it in future NASA calls—and ideally to show it needs more funding support—it's imperative that it receives as many proposals as possible. We need to show NASA that this is an incredibly important (and needed) call. I'd love it if the PyHC could spam this with proposals to fund maintenance efforts for darn near all of our packages. PyHC has often pioneered the open source software path in Heliophysics, and I don't want this to be an exception.

In reply to @jeandet:one.ems.host
I've just pushed a new release of SciQLop, with DMGs for MacOs 11+ and on Linux you can use the AppImage directly without any setup. https://github.com/SciQLop/SciQLop/releases/tag/v0.7.1