Make GfRC retargetable
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 领域
- content, documentation
调研方向
该 issue 没有指明文件、测试或入口点。首先定位 GfRC 文档并查看包含七条评论的讨论，然后在编辑之前与维护者解决版本控制、许可、重定向语言和规范范围方面的问题；完成的标准是形成一份已达成共识且可复用的指南文本。
由索引模型根据 Issue 内容生成。
描述
CC @hasufell @simonpj @mpilgrem
There are continuous attempts to apply GfRC not only to HF itself, but also to other bodies. Currently most of them are void and null at best, because GfRC as written is not "retargetable". There are a few items which need to be fixed.
- As witnessed recently on more than one occasion, GfRC is not set in stone. An organisation subscribing to GfRC should be able to specify a version (say, v2025.05.09) instead of hotlinking an evolving text.
- Organisations should be able to copy a particular edition of GfRC to their own repository for future reference. This is currently illegal, because GfRC does not grant any license to subscribers. Should be one of Creative Commons licenses, I suppose.
- GfRC should say something like "the participating body" and "the leadership of the participating body" instead of "members of the Haskell Foundation" and "the chair of the Foundation, or the vice-chair or co-chair". I'm not sure what's the standard English legal wording for this, maybe "a group refering to these Guidelines" and "leadership of the group refering to these Guidelines" are most suitable.
- It should be made clear that only the section under "Guidelines For Respectful Communication" is normative and the rest ("Preamble", "Motivation", "Acknowledgements") are not. E. g., an organisation may seek to impose GfRC on its employees, a discussion forum may impose GfRC on all participants, but both cases would contradict Preamble. Similarly, motivations may vary, including "...because my employer told me so" or "...because it's a precondition for affilication with HF" and such.
- 主要语言
- CSS
- 星标
- 42
- 派生
- 53
- 平均合并
- 1 天 20 小时
- 30 天内合并 PR
- 4
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
haskellfoundation/haskellfoundation.github.io 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
haskellfoundation/haskellfoundation.github.io#623 · 1 个 reaction ·
-
难度 4/5 3-5 天 新手友好度 45/100
haskellfoundation/haskellfoundation.github.io#624 · 1 个 reaction ·
-
The Technical Working Group doesn't seem to be mentioned anywhere on the website!可能重新可做 @LaurentRDC 于 259 天前认领，目前没有进行中的 PR。 未关闭Important
haskellfoundation/haskellfoundation.github.io#569 · 已指派 1 人 ·
-
难度 1/5 1 小时以内 新手友好度 50/100
haskellfoundation/haskellfoundation.github.io#436 · 1 条评论 ·
-
难度 1/5 1 小时以内 新手友好度 55/100
haskellfoundation/haskellfoundation.github.io#400 · 1 条评论 · 2 个 reaction ·
查看 haskellfoundation/haskellfoundation.github.io 的全部 Issue
相似的 Issue
-
instance instance add
难度 2/5 1-3 小时 新手友好度 68/100
searxng/searx-instances#941 · 1 条评论 ·
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
难度 1/5 1 小时以内 新手友好度 95/100
lingdojo/kana-dojo#31294 · 1 条评论 · 5 个 reaction ·
维护者通常 1 天内回复
-
dependencies javascript Status: Triage
难度 2/5 1-3 小时 新手友好度 72/100
json-schema-org/website#2521 ·
维护者通常 1 天内回复
-
saggiamente.com未关闭N: AdGuard Browser Extension P4: Low T: Annoyance
难度 2/5 1-3 小时 新手友好度 64/100
AdguardTeam/AdguardFilters#242999 ·
维护者通常 1 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 88/100