astropy.github.com
astropy.github.com copied to clipboard
The Astropy web pages
From @astrofrog: > Somewhere (doesn't have to be too obvious necessarily) we should keep a list of people who were previously in roles, so that there is an official place...
Motivation: Over the years, the Project has evolved more quickly than `roles.json` (that renders to https://www.astropy.org/team) can be updated. As a result, there are now roles that do not exist...
We are requesting affiliated status for our package PyAutoGalaxy :).
I see "Matrix" listed under https://www.astropy.org/team.html but I don't find it mentioned in https://www.astropy.org/help.html . @Cadair should add the info.
Roles: Add sub-roles for infrastructure and other related updates, remove Madison due to inactivity
Another stab at the infrastructure stuff in #519 . * There is now a proper Infrastructure Team with sub-roles. * The existing ones are pretty comprehensive to begin with, so...
Suggested by @pllim at the 2023 coordination meeting: we should update the astropy web page style to respect the OS-level theme for dark vs light mode. This is probably some...
At the moment the roles are in a bit of a random order, as several infrastructure ones are separated. Things like devops, docs infra and testing infra should probably be...
Dear all, Here is our package Pyxel. Pyxel is a general detector simulation framework. I would like to propose it as an affiliated package.
In the past several releases (and we only do a release every 6 months, so it's been a while), only @astrofrog and @saimn are alternating, so based on that, I...
I think it is overkill to have so many sub-roles for community engagement. Infrastructure staff maintains multiple packages across the board (and manages releases for them too, etc) and yet...