Internal checklist for testnet partner outreach
維護者通常 1 天內回覆
@Santiagocetran 已經在處理了。
開始於 2026年10月16日。
評估
這個 Issue 還沒有評估資料。
描述
Related: OPS-1, issue No. 158, PR No. 189, issue No. 155, issue No. 75
Why this would help
Issue No. 158 produced the partner-facing introduction, Documentation/public/partner-introduction.md, merged in PR No. 189. It explicitly left "any internal outreach checklist" as a separate follow-up. Without that checklist, each person who starts a partner conversation decides on their own what to share, what to ask, and what not to promise. The partner page helps with consistency, but only if everyone uses it the same way.
Suggested next step
Agree on an owner, then draft a short internal checklist, for example under Developer/, covering:
- Before the first conversation: the current partner-introduction link, the network/version to point people at, and the open policy rows to avoid committing on (rewards and slashing values in issue No. 155, distribution eligibility in issue No. 75, testnet resets).
- What to ask the partner: role of interest, model and data type, number of participants, hardware, privacy constraints. These match the "Start a conversation" section of the partner page and the "How do I try it?" section of
what-can-be-trained.md. - Who owns follow-up: the named contact, who runs the onboarding call, and who supports setup (wallet, test ETH, staking, IPFS).
- Where to record it: one place to track partner conversations and their status, so OPS-1's 2–3 validator-partner goal can be tracked.
- When to re-check the page: for example, after issue No. 155 or issue No. 75 settles a row in the partner page's settled-vs-undecided table.
Expected outcome
A short internal checklist that anyone starting partner outreach can follow, kept in sync with the partner-introduction page.
This documents the outreach process only. It doesn't decide partnership terms or reward policy.
- 主要語言
- Python
- 星號
- 4
- 分支
- 7
- 平均合併
- 3 天 4 小時
- 30 天內合併 PR
- 34
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
InfiniteZeroFoundation/DevNet 的其他 Issue
-
ROADMAP.md: refresh "What is still open for P3" (several items were fixed in October)可能已有人在做 @umermjd11 於 3 天前認領。 未關閉documentation good first issue
難度 2/5 1-3 小時 新手友好度 74/100
InfiniteZeroFoundation/DevNet#285 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Update the 25 translated organisation READMEs to match the English version可能已有人在做 @mrCabez 於 1 天前認領。 未關閉good first issue help wanted
難度 2/5 1-3 小時 新手友好度 76/100
InfiniteZeroFoundation/DevNet#277 · 2 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Update the client-service guide to explain training and uploading separately可能已有人在做 @Santiagocetran 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 76/100
InfiniteZeroFoundation/DevNet#266 ·
維護者通常 1 天內回覆
-
難度 5/5 一週以上 新手友好度 25/100
InfiniteZeroFoundation/DevNet#299 · 1 則留言 ·
維護者通常 1 天內回覆
-
Long run
難度 5/5 一週以上 新手友好度 25/100
InfiniteZeroFoundation/DevNet#298 ·
維護者通常 1 天內回覆
查看 InfiniteZeroFoundation/DevNet 的全部 Issue
相似的 Issue
-
infrastructure
難度 2/5 1-3 小時 新手友好度 76/100
NatLabRockies/H2Integrate#977 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
topoteretes/cognee#6470 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
-
area:docs priority:p2 type:docs wave:9
難度 1/5 1 小時以內 新手友好度 84/100
jejjohnson/radtrax#293 ·
維護者通常 1 天內回覆
-
bug core plugins
難度 2/5 1-3 小時 新手友好度 68/100
bunkerity/bunkerweb#4121 · 1 則留言 ·
維護者通常 1 天內回覆