Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Discuss the future of this repo

Ouverte
  • Quelque chose ne va pas ?
#4,636 11 commentaires 3 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
5/100
Type d'issue
Documentation
Clarté
À clarifier
Activité
Active
Stack technique
go
Domaine
api

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
Go
Étoiles
11.3k
Forks
2.6k
Merge moyen
2 j 8 h
PR mergées (30 j)
38

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de google/go-github

Toutes les issues de google/go-github

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.