Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Reworking of credits/team/etc information locations

Offen
  • Stimmt etwas nicht?
#746 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Bereich
content, documentation, web-dev

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
Python
Sterne
47
Forks
107
Ø Merge
3 T. 22 Std.
Gemergte PRs (30 T.)
10

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus astropy/astropy.github.com

Alle Issues in astropy/astropy.github.com

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.