Revise steward and editor roles

未关闭
#552 4 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
领域
documentation

调研方向

先阅读 issues #291 和 #367 中的背景,然后审查 specs.ipfs.tech 中列出的八个领域。当项目就核心与领域的 stewardship 模型达成一致(包括核心维护者和领域编辑者的角色与职责),或达成一个有明确理由支持的替代方案时,这项工作即告完成。

由索引模型根据 Issue 内容生成。

描述

need/triage

A 2022 a stewards team was created via #291. The list of stewards can be found here https://github.com/orgs/ipfs/teams/specs-stewards/members (although it's not publicly readable, as #367 points out.)

With a single, large set of stewards, it's unlikely that any steward is deeply familiar enough with the full surface area. In practice only 1-3 of these stewards have been actively engaged at any point in time. We should update to a core-and-area model, with a small number of core stewards responsible for keeping the spec family coherent and identifying the boundaries, and area editors (lightly inherited from IETF) responsible for specific areas.

Here are the 8 current areas, as defined in specs.ipfs.tech:

  • Architecture
  • Meta
  • Routing
  • Exchange
  • HTTP Gateways
  • Data Formats
  • IPNS
  • Content Filtering

Alternatively, we could have both "Area Directors" and individual "Spec Editors" (more closely mirroring IETF). But that may be too heavy — director seems like an inflated name for this context.

主要语言
HTML
星标
1.2k
派生
250
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ipfs/specs 的其他 Issue

查看 ipfs/specs 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。