Proposal to relocate repo / org
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
This is a governance proposal to move the StackExchange.Redis repository to the seredis GitHub organization, not a code change, and the payload names no files, tests or entry points. Read the two comments and the linked seredis organization first to see what the maintainers have already agreed. Done means a maintainer decision on the move, carried out through GitHub's repository transfer, so a newcomer has no code to write here.
由索引模型根据 Issue 内容生成。
描述
So: SE.Redis has been under the StackExchange org for... well, forever.
This is historically apt. The primary maintainers have not left the library - we have, however, left Stack Exchange (the company), years ago.
Effectively, the primary team are:
- @mgravell (currently at Redis, ex Stack Exchange, ex Microsoft)
- @NickCraver (currently at Microsoft, ex Stack Exchange)
- @philon-msft (currently at Microsoft)
I'm not suggesting for a moment that Stack Exchange would ever do anything malign, but it does make me a little nervous re supply-chain when the library is at the whim of an org that the core maintainers don't represent.
For the same reasons, and for politics / "ownership claim" reasons, I'm also nervous of moving the library directly under the umbrella of Redis or Microsoft.
My proposal: move it under the seredis org:
- we, the primary team, own that org
- we, the primary team, own seredis.dev, which is where we are serving the docs etc
- (we, the primary team, also own the NuGet keys - but this is unrelated to the GitHub repo)
As I understand it, GitHub should automatically take care of redirects if we move it.
Thoughts?
Pre-empting questions:
- this has zero impact on anything like licensing
- this has zero impact on support
- mostly it just changes the URL and org-level access (the latter of which impacts nobody except the maintainers)
- no, there is no drama or background story underpinning this suggested move - just "an abundance of caution"
- 主要语言
- C#
- 星标
- 6.2k
- 派生
- 1.6k
- 平均合并
- 9 小时 42 分钟
- 30 天内合并 PR
- 51
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
StackExchange/StackExchange.Redis 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 78/100
StackExchange/StackExchange.Redis#3249 · 2 条评论 ·
维护者通常 1 天内回复
-
HotKeysClusterTests.CanUseClusterFilter skips intermittently, hiding the assertions it exists for未关闭
难度 2/5 1-3 小时 新手友好度 76/100
StackExchange/StackExchange.Redis#3239 · 2 条评论 ·
维护者通常 1 天内回复
-
Feature Request: Add Automatic ForceReconnect Recovery for Persistent ConnectionMultiplexer Connection Failures可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 5/5 一周以上 新手友好度 38/100
StackExchange/StackExchange.Redis#3309 · 9 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
StackExchange/StackExchange.Redis#3240 ·
维护者通常 1 天内回复
-
RedisValue equality treats "1,000", "(5)" and " 5 " as numbers, via NumberStyles.Any可能已有人在做 @banlor 于 42 天前认领。 未关闭
难度 5/5 一周以上 新手友好度 35/100
StackExchange/StackExchange.Redis#3233 · 1 条评论 ·
维护者通常 1 天内回复
查看 StackExchange/StackExchange.Redis 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 80/100
Unity-Technologies/unity-agent-plugin#118 ·
维护者通常 1 天内回复
-
The Recommended preset turns on Import Uno DSP, which only works with the Material theme可能已有人在做 @agneszitte 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 92/100
unoplatform/uno.templates#2388 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
eyalgolan/statecraft-israel#2732 ·
维护者通常 1 天内回复
-
要トリアージ
难度 2/5 1-3 小时 新手友好度 64/100
维护者通常 1 天内回复
-
kind/chore status/draft
难度 2/5 1-3 小时 新手友好度 65/100
Altinn/altinn-events#1158 ·
维护者通常 1 天内回复