From d157f95bb21299a377f20f670d2041c267b32e9e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C3=A1rio=20Havel?= <61149543+taxmeifyoucan@users.noreply.github.com> Date: Fri, 3 May 2024 10:45:48 +0200 Subject: [PATCH] update notes 2 --- .../2024-05-02_release_plan.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/notes/wiki_contributors_meeting/2024-05-02_release_plan.md b/notes/wiki_contributors_meeting/2024-05-02_release_plan.md index 54cd66a3..28a72952 100644 --- a/notes/wiki_contributors_meeting/2024-05-02_release_plan.md +++ b/notes/wiki_contributors_meeting/2024-05-02_release_plan.md @@ -29,29 +29,29 @@ - Mario: Rahul, great work on Formal verification. Ethereum's history is an important topic. The DAO and Parity hack provide important context. Anyone - feel free to pick that up. - Mario to Nagu: Thank you for the quick response on SSZ and Merkleization. I'm open to merging it. - Nagu: Sounds good. -- Mario: Gorondan, you've added warning stubs to some documents. +- Mario: Gorondan, you've created issue for adding warning artifacts to research pages. - Gorondan: I believe it's fair to have a warning that content is subject to change. -- Mario: I recall discussing with someone that important wiki pages should be future-proof. Feel free to add these warnings to relevant details pages. Let's also add instructions to `contributing.md` so we have it in one place. +- Mario: I recall discussing with someone that important wiki pages should be future-proof. Feel free to add these warnings to relevant detail pages. Let's also add instructions on using various artifacts to contributing.md so we have it in one place. - Siddharth: I'm wondering how to prioritize work, like the block building from week 1. I've been doing a lot of research lately. I was thinking of tackling EL Architecture next week, but it's a huge document. I think we should break it down for easier review. - Mario: For things you have ready, feel free to submit a PR. The architecture is crucial for specs. Kira worked on Consensus architecture, so it would be nice if both architectures follow the same structure. The lowest priority would be the Geth thing. - Siddharth: Then I'll finish the EL Architecture, specs, and then Geth. Specs are fairly simple. As an aside, I learned a lot from reviewing Geth. - Mario: Rory is working on testing. - Gorondan: Hopinheimer is working on the protocol design. -- Mario: Right. Some of the suggested topics are not necessary. I'll comment on the issue. It's important to cover design rationale. It's not covered anywhere. +- Mario: Some topics from the proposed protocol design structure are not necessary. I'll comment on the issue. It's important to cover design rationale. It's not covered anywhere. - Mario: We should ensure single pages are lean for maintainability. -- Gorondan: I'm interested in Light client. If we start a page, Dirk can work on it. +- Gorondan: Light clients page is interesting. If we start a page, Dirk can work on it. - Mario: There is a stub page. Feel free to open an issue and work on it. - Gorondan: Is the page about execution or..? -- Mario: It's explained in the page. It's just an RPC verifier using data from an independent beacon node. +- Mario: It's explained in the page. It's just covering an RPC verifier using data from an independent beacon node. - Rahul: Protocol overview is a priority for me. I got nerd sniped by Mario's lecture on Linux history and cryptopunks. - Mario: The biggest missing piece is testing. We should document hive or different testing mechanisms. - Kira: I kind of [wrote a condensed version of the yellow paper](https://hackmd.io/@kira50/H1O4tO6WC). In case someone would like to review it. - Mario: Very cool. We should have it in the wiki. Feel free to open an issue and work on it. - Hopinheimer: I have an open issue on dev-p2p and am planning to catch up with it this weekend. -- Mario: I would suggest Angus. He worked on networking and consensus and spent a lot of time on dev-p2p. +- Mario: I would suggest checking with Angus. He worked on networking and consensus and spent a lot of time on dev-p2p. - Hopinheimer: Sure. I'll ping him. -- Kira: Prism has a really cool search bar. Can we have something similar I worked on? -- Mario: We always had a search bar. With the new UI, it's improved. If there's nothing else, I think we're ready to share the wiki! Feel free to share it. With EPF starting soon, I think the wiki should serve as a good learning resource. Also, should we version releases? We want to offer people more stable content and maybe archive it. Thoughts? +- Kira: Prysm has a really cool search bar. Can we have something similar I worked on? +- Mario: We always had a search bar. With the new UI, it's improved. If there's nothing else, I think we're ready to share it! Feel free to share the wiki publically. With EPF starting soon, I think the wiki should serve as a good learning resource. Also, should we version releases? We want to offer people more stable content and maybe archive it. Thoughts? - Rahul: We could semver it. - Gorondan: Maybe we should do bi-weekly updates until it's mature, then after 1.0, we could version it. - Mario: I think most changes are behind us, so it makes sense to somehow track changes. Two weeks seems like a big window. I think we should do a weekly release.