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

Discuss the future of this repo

Offen
  • Stimmt etwas nicht?
#4,636 7 Kommentare 3 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
5/100
Issue-Typ
Dokumentation
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
go
Bereich
api

Rechercherichtung

This is a governance question about the project's future, not a code change, and the payload names no files, tests or entry points. Read the linked PR #4565 comment thread for context. Done means maintainers have reached a decision on archiving or forking, which is not something a first-time contributor can settle alone.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Continued discussion from here: https://github.com/google/go-github/pull/4565#issuecomment-6219708129

I don't want to fully hijack this PR thread, but... Google hasn't been involved in maintaining this library in YEARS. @gmlewis, if you're still interested in continuing maintenance, there's a pretty solid case to be made to just fork this out into a neutral organization and maintain it there. I personally don't have bandwidth or interest to step back into a maintainer role, but I would be supportive of an administrative fork, since no one at Google seems interested anymore, and that abandonment is actively hurting the project (as seen in PRs like this one, and other issues in the past).

That's an interesting idea, @willnorris!

At this moment, there are 206 "Watchers", 2.6K forks, and 11.3K stars.
I can't help but notice that this repo is heavily used by the Terraform project, yet there has been no external sponsorship from any outside entities to help keep this project going.

I have been maintaining this repo for 10 years because of my friendship with Will and because I told him I would, but I'm honestly not interested in maintaining this repo anymore.

Here are the options as I see them:

Option A: We declare this repo as "ARCHIVED" (even though we cannot archive it) and let users maintain their own forks (and see if we can then auto-close PRs with an error message).

Option B: We declare this repo as "ARCHIVED" and we ask for a volunteer to create a neutral organization, create the fork, and maintain this repo there (which could be documented here).

Vorherrschende Sprache
Go
Sterne
11.3k
Forks
2.6k
Ø Merge
2 T. 14 Std.
Gemergte PRs (30 T.)
33

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 google/go-github

Alle Issues in google/go-github

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

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