Existing documentation and organization is oriented mostly around exposing individual packages. This is important. Complimentary to this, we should consider a different entry point: “I am a scientist in domain X. What stack should I be using?” This would help people understand that each domain is probably using many different packages for their workflows, and also that these packages are used in other scientific fields. In terms of data modeling, a stack would have a many-to-many relationship with packages.
Another related set of questions involve what parts of already organized domain stacks should be “promoted” to the ecosystem level (i.e., Scientific Python). For example, would it make sense to merge discussion forums (using categories and tags to keep things organized); governance structures; and codes of conduct standards, reporting guidelines, and review committees.
The summits bring together developers and users of specific domain stacks (e.g., Pangeo, Astropy, scikit-hep, scverse, NIPY) to discuss the shortcomings of the current documentation and organization, the needs of various scientific “domain stacks,” and to develop a shared roadmap and vision for better documenting and organizing domain stack documentation and organization.