Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Reworking of credits/team/etc information locations

Abierto
  • ¿Algo no está bien?
#746 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Área
content, documentation, web-dev

Línea de trabajo

Start by reviewing the current combined credits and team page and the context in follow-ups #742 and #709. Done means current team roles remain prominent, past contributors link to the latest documentation, and credits have a separate About page while remaining linked from the main website.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

This is a follow-up to #742 #709.

I merged #742 because I thought getting those credits back in place ASAP was a good idea. But I think it's not ideal that the things that were initially (intentionally) separated have been re-combined in a not ideal way. As I see it there's really 3 different things:

  1. The roles/team that is primarily about the current state of the project and who does what as of today
  2. The list of everyone who has ever contributed (i.e. "past and present" team)
  3. The credits, in the sense of "people who may or may not necessarily be part o the team, but who without which astropy wouldn't be possible or at least not as good"

After #742 these are essentially all squished together on one page. That's definitely better than nothing, but is not ideal. Here's what I think is the ideal state

1 should be where it is - it makes sense that's part of the header because its an imporant quick reference
2 may actually make sense to remove from the main web page but instead link to the relevant part of the latest docs. I think that's more fair in some sense since it doesn't privledge the core package over other coordinated package like it currently does.
3 then belongs as a separate page on its own somewhere. My preference is that it gets added to the "about" dropdown that currently exists. (also probably link to at the bottom of the "team" page since these is all a bit fuzzy). Regardless it must be on the main web page somewhere because some of our funders require this as a condition of funding.

It's a bit debatable whether lifetime contributors end up in 1 or 3 but either way there's still significant content for both.

cc @Cadair

Lenguaje dominante
Python
Estrellas
47
Forks
107
Merge medio
15 h 52 min
PR fusionados (30 d)
8

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de astropy/astropy.github.com

Todos los issues de astropy/astropy.github.com

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.