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

Discuss the future of this repo

Abierto
  • ¿Algo no está bien?
#4,636 11 comentarios 3 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
5/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
go
Área
api

Línea de trabajo

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.

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

Descripción

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

Lenguaje dominante
Go
Estrellas
11.3k
Forks
2.6k
Merge medio
2 d 8 h
PR fusionados (30 d)
38

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

Todos los issues de google/go-github

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.