Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Discuss the future of this repo

Aperta
  • Qualcosa non va?
#4,636 7 commenti 3 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
5/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
go
Ambito
api

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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).

Lingua principale
Go
Stelle
11.3k
Fork
2.6k
Merge medio
2g 14h
PR unite (30g)
33

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di google/go-github

Tutte le issue di google/go-github

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.