From c8a783029c5fc020617668168ae7ffdc916f9927 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tom=C3=A1s=20Gr=C3=BCner?= <47506558+MegaRedHand@users.noreply.github.com> Date: Thu, 14 May 2026 12:46:19 -0300 Subject: [PATCH 1/2] docs: surface community channels on README and docs landing page 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 https://github.com/lambdaclass/ethlambda/pull/368#issuecomment-4452169978 --- CONTRIBUTING.md | 8 +++++--- README.md | 7 +++++++ docs/introduction.md | 7 +++++++ 3 files changed, 19 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f9679061..cd84b2b3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -144,9 +144,11 @@ If you discover a security vulnerability, **do not open a public issue**. Instea ## Communication -- **Telegram**: [ethlambda group](https://t.me/ethlambda_client) — questions, discussion, coordination -- **X (Twitter)**: Follow [@ethlambda_lean](https://twitter.com/ethlambda_lean) for updates -- **GitHub Issues**: Bugs, feature requests, and technical discussion +- **Telegram**: [ethlambda group](https://t.me/ethlambda_client), where we post daily updates; drop by to ask questions or chat about anything Lean-related. +- **X (Twitter)**: [@ethlambda_lean](https://twitter.com/ethlambda_lean) for occasional updates. +- **Weekly community call**: every Friday, streamed live on [@class_lambda](https://x.com/class_lambda); the call link is posted on Telegram beforehand. +- **GitHub Issues**: bugs, feature requests, and technical discussion. +- **Ecosystem coordination**: the [open PQ Interop calls](https://github.com/ethereum/pm/issues/2055) cover cross-client Lean Ethereum work. ## License diff --git a/README.md b/README.md index 336d2271..74f063e7 100644 --- a/README.md +++ b/README.md @@ -55,6 +55,13 @@ For custom devnet configurations, go to `lean-quickstart/local-devnet/genesis/va We welcome contributions! Please read our [CONTRIBUTING.md](./CONTRIBUTING.md) for guidelines on how to get involved. +## Community + +- **Telegram**: [ethlambda group](https://t.me/ethlambda_client), where we post daily updates; drop by to ask questions or chat about anything Lean-related. +- **X (Twitter)**: [@ethlambda_lean](https://twitter.com/ethlambda_lean) for occasional updates. +- **Weekly community call**: every Friday, streamed live on [@class_lambda](https://x.com/class_lambda); the call link is posted on Telegram beforehand. +- **Ecosystem coordination**: the [open PQ Interop calls](https://github.com/ethereum/pm/issues/2055) cover cross-client Lean Ethereum work. + ## Philosophy Many long-established clients accumulate bloat over time. This often occurs due to the need to support legacy features for existing users or through attempts to implement overly ambitious software. The result is often complex, difficult-to-maintain, and error-prone systems. diff --git a/docs/introduction.md b/docs/introduction.md index c1c3c50f..9b409beb 100644 --- a/docs/introduction.md +++ b/docs/introduction.md @@ -29,6 +29,13 @@ into the rendered output: - [3SF-mini infographic](./infographics/3sf-mini-infographic.html) - [ethlambda architecture infographic](./infographics/ethlambda_architecture.html) +## Community + +- **Telegram**: [ethlambda group](https://t.me/ethlambda_client), where we post daily updates; drop by to ask questions or chat about anything Lean-related. +- **X (Twitter)**: [@ethlambda_lean](https://twitter.com/ethlambda_lean) for occasional updates. +- **Weekly community call**: every Friday, streamed live on [@class_lambda](https://x.com/class_lambda); the call link is posted on Telegram beforehand. +- **Ecosystem coordination**: the [open PQ Interop calls](https://github.com/ethereum/pm/issues/2055) cover cross-client Lean Ethereum work. + ## Related projects ethlambda is one of several Lean Ethereum consensus clients under active development. From ffff4bef39757c57e31e45dcaecd6e9972c041d4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tom=C3=A1s=20Gr=C3=BCner?= <47506558+MegaRedHand@users.noreply.github.com> Date: Thu, 14 May 2026 13:14:41 -0300 Subject: [PATCH 2/2] docs: point PQ Interop link at the call issues list 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. --- CONTRIBUTING.md | 2 +- README.md | 2 +- docs/introduction.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index cd84b2b3..e9afb826 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -148,7 +148,7 @@ If you discover a security vulnerability, **do not open a public issue**. Instea - **X (Twitter)**: [@ethlambda_lean](https://twitter.com/ethlambda_lean) for occasional updates. - **Weekly community call**: every Friday, streamed live on [@class_lambda](https://x.com/class_lambda); the call link is posted on Telegram beforehand. - **GitHub Issues**: bugs, feature requests, and technical discussion. -- **Ecosystem coordination**: the [open PQ Interop calls](https://github.com/ethereum/pm/issues/2055) cover cross-client Lean Ethereum work. +- **Ecosystem coordination**: the [PQ Interop calls](https://github.com/ethereum/pm/issues?q=is%3Aissue+%22PQ+Interop%22+in%3Atitle) on `ethereum/pm` cover cross-client Lean Ethereum work and related updates; the meeting links are posted on each issue. ## License diff --git a/README.md b/README.md index 74f063e7..64a86661 100644 --- a/README.md +++ b/README.md @@ -60,7 +60,7 @@ We welcome contributions! Please read our [CONTRIBUTING.md](./CONTRIBUTING.md) f - **Telegram**: [ethlambda group](https://t.me/ethlambda_client), where we post daily updates; drop by to ask questions or chat about anything Lean-related. - **X (Twitter)**: [@ethlambda_lean](https://twitter.com/ethlambda_lean) for occasional updates. - **Weekly community call**: every Friday, streamed live on [@class_lambda](https://x.com/class_lambda); the call link is posted on Telegram beforehand. -- **Ecosystem coordination**: the [open PQ Interop calls](https://github.com/ethereum/pm/issues/2055) cover cross-client Lean Ethereum work. +- **Ecosystem coordination**: the [PQ Interop calls](https://github.com/ethereum/pm/issues?q=is%3Aissue+%22PQ+Interop%22+in%3Atitle) on `ethereum/pm` cover cross-client Lean Ethereum work and related updates; the meeting links are posted on each issue. ## Philosophy diff --git a/docs/introduction.md b/docs/introduction.md index 9b409beb..4b54ffc6 100644 --- a/docs/introduction.md +++ b/docs/introduction.md @@ -34,7 +34,7 @@ into the rendered output: - **Telegram**: [ethlambda group](https://t.me/ethlambda_client), where we post daily updates; drop by to ask questions or chat about anything Lean-related. - **X (Twitter)**: [@ethlambda_lean](https://twitter.com/ethlambda_lean) for occasional updates. - **Weekly community call**: every Friday, streamed live on [@class_lambda](https://x.com/class_lambda); the call link is posted on Telegram beforehand. -- **Ecosystem coordination**: the [open PQ Interop calls](https://github.com/ethereum/pm/issues/2055) cover cross-client Lean Ethereum work. +- **Ecosystem coordination**: the [PQ Interop calls](https://github.com/ethereum/pm/issues?q=is%3Aissue+%22PQ+Interop%22+in%3Atitle) on `ethereum/pm` cover cross-client Lean Ethereum work and related updates; the meeting links are posted on each issue. ## Related projects