Expose pinning service api spec

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

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
55/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
技术栈
html
领域
documentation

调研方向

首先找到 specs.ipfs.tech 的源文件和现有的 "Content Filtering" 块。将所请求的 Pinning 指针添加到 https://ipfs.github.io/pinning-services-api-spec/;当该指针在 https://specs.ipfs.tech/ 上可见时即完成。

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

描述

need/triage

Done Criteria

Minimum: there is a pointer from https://specs.ipfs.tech/ to https://ipfs.github.io/pinning-services-api-spec/

Why Important

Further solidifies specs.ipfs.tech as the canonical place for IPFS specs.

User/Customer

Someone looking for the surface area of IPFS-related specs. (I assume though that anyone who already knows about the pinning service api will be able to find it easily enough without this.)

Notes

  1. I know the pinning service is not a major area of investment, but I was surprised that I didn't see it at https://specs.ipfs.tech/ and had to remember it was elsewhere. I assume there was discussion about this in the past, but I couldn't quickly find it. If nothing else, this issue can serve as a pointer even if don't do the work.
  2. I'm imagining adding another block after "Content Filtering" at https://specs.ipfs.tech/ for "Pinning", and from there can link out to https://ipfs.github.io/pinning-services-api-spec/ for now.
  3. This seems like an easy issue to assign to an "Agent" to create a PR for. I am happy to do this if it's even wanted - fine if not.
主要语言
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 摘要。