docs: surface community channels on README and docs landing page#369
Conversation
Communication info was only in CONTRIBUTING.md and missing the weekly community call and the PQ Interop coordination pointer. Mirror a consistent Community section across README.md, docs/introduction.md and CONTRIBUTING.md so newcomers find it without digging. Closes the follow-up noted in #368 (comment)
🤖 Claude Code ReviewHere is my review of PR #369: PR #369 — docs: surface community channels on README and docs landing pageOverview: Pure documentation change. Adds a "Community" section to What this PR does
ReviewContent and consistency The four-item list is identical across Placement
Link durability The PQ Interop pointer links to Writing quality Clean, friendly tone that fits a community-facing section. Sentence-casing on bullet labels is consistent. The semicolon usage in the Telegram entry ("daily updates; drop by…") is correct. No issues with rendering: Markdown links are well-formed; the mdBook will pick up SummaryThis is a well-scoped, low-risk documentation change. The only actionable question is whether Automated review by Claude (Anthropic) · sonnet · custom prompt |
Greptile SummaryThis PR surfaces community channels in three places —
Confidence Score: 5/5Documentation-only change adding community links; no code or configuration is touched. All three files receive the same four community-channel bullets, the wording is consistent, the external links point to the correct destinations, and no existing content is removed. There is nothing here that could introduce a regression. No files require special attention.
|
| Filename | Overview |
|---|---|
| README.md | Adds a new "Community" section between Contributing and Philosophy with four consistent bullet points covering Telegram, X, weekly call, and PQ Interop. |
| docs/introduction.md | Adds the same four-bullet Community section before the Related projects section; content is identical to README.md. |
| CONTRIBUTING.md | Expands the existing Communication section with matching wording: richer Telegram description, weekly call bullet, and PQ Interop pointer; drops "Follow" from the X entry. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Newcomer visits project] --> B{Which entry point?}
B --> C[README.md]
B --> D[docs/introduction.md]
B --> E[CONTRIBUTING.md]
C --> F[Community section\nTelegram · X · Weekly call · PQ Interop]
D --> F
E --> G[Communication section\nTelegram · X · Weekly call · PQ Interop · GitHub Issues]
F --> H[Telegram group]
F --> I[X @ethlambda_lean]
F --> J[Friday community call via @class_lambda]
F --> K[PQ Interop calls]
Reviews (1): Last reviewed commit: "docs: surface community channels on READ..." | Re-trigger Greptile
🤖 Kimi Code ReviewThis PR contains documentation-only changes (no Rust code). Consequently, standard consensus-layer security review criteria (XMSS verification, SSZ encoding, fork choice, etc.) do not apply. Review SummaryStatus: Approved with minor formatting notes. Non-code observations
No blockers. The changes improve contributor onboarding and community visibility without introducing technical debt. Automated review by Kimi (Moonshot AI) · kimi-k2.5 · custom prompt |
🤖 Codex Code ReviewNo findings. PR 369 is documentation-only. The changes are limited to the new community/contact section in README.md, CONTRIBUTING.md, and docs/introduction.md, so there is no effect on fork choice, attestation handling, justification/finalization, state transition logic, XMSS verification, SSZ encoding, security-critical paths, or runtime performance. The only minor maintainability risk is that the same block is now duplicated in three places, so future edits will need to keep them synchronized. I did not run tests because this diff does not change executable code. Automated review by OpenAI Codex · gpt-5.4 · custom prompt |
Link to the title-filtered ethereum/pm issues list so the reference stays valid as new weekly issues open, and note that the meeting links are posted on each issue.
2 participants
Summary
docs/introduction.mdso newcomers find the Telegram group, the weekly Friday community call, and the PQ Interop calls without digging intoCONTRIBUTING.md.CONTRIBUTING.mdto match (adds the weekly call and PQ Interop pointers, tightens the Telegram description).Triggered by the follow-up in #368 (comment).
Test plan
README.mdrenders the new Community section between Contributing and Philosophy.docs/introduction.mdrenders the new Community section before Related projects (will show up in the mdBook).CONTRIBUTING.mdCommunication block stays consistent with the other two.