Discuss the future of this repo
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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).
- 主要语言
- Go
- 星标
- 11.3k
- 派生
- 2.6k
- 平均合并
- 2 天 8 小时
- 30 天内合并 PR
- 38
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
google/go-github 的其他 Issue
-
Rate-limit retry replays a consumed request body for POST/PUT/PATCH可能已有人在做 @AdamMagued 于 1 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 70/100
google/go-github#4656 · 1 条评论 ·
维护者通常 1 天内回复
-
otel: redact sensitive query parameters before recording http.url可能已有人在做 @sai5880 于 1 天前认领。 未关闭
难度 4/5 1-2 天 新手友好度 55/100
维护者通常 1 天内回复
-
Error() methods modify the request URL of the response they wrap可能已有人在做 @AdamMagued 于 2 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 30/100
维护者通常 1 天内回复
-
http.Client.Timeout is ignored by redirect-aware requests可能已有人在做 @sb123sb123 于 31 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 68/100
维护者通常 1 天内回复
-
Add Copilot content exclusion set/get enterprise and org set endpoints可能已有人在做 @Tens1des 于 45 天前认领。 未关闭
google/go-github#4526 · 1 条评论 · 1 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 91/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 84/100
praetorianer777/Dynamo#53 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
kind/engineering pulumi/pulumi-terraform Task Workflow Failure
难度 2/5 1-3 小时 新手友好度 64/100
pulumi/pulumi-terraform#1261 ·
维护者通常 1 天内回复
-
Controllers integration tests fail when port 8080 is in use可能已有人在做 @noahnut 今天认领。 未关闭area/cluster-autoscaler kind/bug needs-triage
难度 2/5 1-3 小时 新手友好度 78/100
kubernetes-sigs/cluster-autoscaler#236 · 1 条评论 ·
维护者通常 1 天内回复