Minor editorial comments on preliminary proposal text

[matthewfeickert]

@jarrodmillman Reading over the preliminary proposal I had two small editorial comments/questions:

1. In

safe-ose-2025/description.md

Line 16 in c1d47a4

Domain-specific projects, such as Astropy (astronomy), Scikit-HEP (particle physics), and Pangeo (geoscience), build upon these core libraries to provide specialized tools for various fields.

"Domain-specific projects", the use of "projects" following the description of NumPy and SciPy might be slightly confusing to reviewers as they might think of these as actual libraries. In the case of Astropy, that actually is true, but the scikit-hep library is meant as a metapackage for the Scikit-HEP ecosystem and realistically most power users are never going to install it. Similarly, there is no Pangeo library, there is the Pangeo software ecosystem.

To me, reframing from "Domain-specific projects" to "Domain-specific ecosystems" makes more sense. Though I can also understand if you're looking for any other word to differentiate scales and scope, given that "ecosystem" is already used a lot (by necessity of the proposal) in this document.

2. In

safe-ose-2025/description.md

Line 28 in c1d47a4

**$\spcore$** (IPython \citep{perez2007ipython}, NumPy, SciPy, Matplotlib \citep{hunter2007matplotlib}, Pandas \citep{mckinney-proc-scipy-2010}, NetworkX \citep{hagberg2008}, scikit-image \citep{vanderwalt2014scikit}, scikit-learn \citep{scikit-learn}, xarray \citep{hoyer2017xarray}, and zarr).

Zarr doesn't have a citation associated with it. While the repo (https://github.com/zarr-developers/zarr-python) doesn't have a CITATION.cff file (perhaps worth a suggestion to them) it does have citation information listed for their Zenodo archive.