The Astropy Ecosystem: current state and recent changes

Update talk at the 2018 Astropy Coordination meeting in Tucson, AZ, USA

Transcript

1. The Astropy Ecosystem Current state and recent changes Thomas Robitaille (@astrofrog)
2. Developer and user community Affiliated (and coordinated) packages Infrastructure packages and tools Educational materials
3. Developer and user community Affiliated (and coordinated) packages Infrastructure packages and tools Educational materials
4. Official project roles
5. Communication channels Developers: astropy-dev, GitHub, and recently Slack (with Matrix option!) Users: astropy@python.org, Facebook, Twitter
6. 2018 Paper (decided at the 2017 coordination meeting!)
7. Astropy Proposal for Enhancements
9. Developer and user community Affiliated (and coordinated) packages Infrastructure packages and tools Educational materials
10. These can be: • Functionality under development • More specialized functionality • Packages with incompatible licenses Adhere to Astropy coding, testing, and docs guidelines Use Astropy wherever possible (avoid duplication) Astropy affiliated packages (original definition)
11. Image reprojection Observation planning Publication-quality image plotting Machine learning Photometry Interface to many web services/archives Gamma-ray data analysis CCD image reduction Interfaces to ds9 Spectroscopic analysis ‘Big’ spectral cube analysis (e.g. ALMA, etc.) Spectral cube slicing <your package here!> etc. Currently 41 affiliated packages
12. New in 2018: Formalized review/acceptance criteria https://github.com/astropy/astropy-procedures/blob/master/documents/affiliated_package_review_guidelines.md Astropy affiliated packages
13. New in 2018: Formalized review/acceptance criteria https://github.com/astropy/astropy-procedures/blob/master/documents/affiliated_package_review_process.md Astropy affiliated packages
14. New in 2018: Visible ‘ratings’ at affiliated.astropy.org Astropy affiliated packages
15. New in 2018: Define astropy-coordinated packages (originally discussed at CCA meeting in 2017) Packages that are actually managed by the project and would thus be assigned a ‘role’ - showing long-term committment Proposed list: astropy-healpix, astroplan, astroquery, ccdproc, photutils, regions, reproject, specutils These are packages that would live inside the astropy GitHub organization Astropy affiliated packages
16. Developer and user community Affiliated (and coordinated) packages Infrastructure packages and tools Educational materials
17. Website - astropy.org
18. package-template New in 2017/18: uses cookiecutter for setting up package
19. astropy-helpers Primary goal: provide helpers that are specific to setup.py tasks Provide customizations that make it easier to work with C/Cython extensions, determining developer version numbers, building documentation, etc.
20. New in 2018: Documentation! (README) astropy-helpers
21. New in 2018: split out Sphinx extensions/theme astropy-helpers
22. sphinx-astropy Goals: Provide a home for the ‘default’ Sphinx configuration for astropy and affiliated packages Meta-package for documentation-building dependencies Contain small custom project-specific extensions (sphinx, astropy-sphinx-theme, numpydoc, sphinx-automoadpi, sphinx-gallery, pillow) (e.g linking to issues in changelog)
23. pytest-astropy and plugins
24. Continuous integration Travis (Linux/Mac) AppVeyor (Windows) CircleCI (Linux) Centralized way of setting up conda and dependencies
25. astropy-bot Recently generalized into OpenAstronomy/baldrick
26. astropy-procedures (formerly astropy-tools) Procedure documents (e.g. affiliated package review guidelines), scripts for batch updating astropy-helpers, etc.
27. Developer and user community Affiliated (and coordinated) packages Infrastructure packages and tools Educational materials
28. tutorials.astropy.org