From 165efcec0f3acaa7cce69a891943d7eb902e84b8 Mon Sep 17 00:00:00 2001 From: George Knee Date: Wed, 9 Oct 2024 18:21:53 +0100 Subject: [PATCH] Update README.md (#124) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2e916cc..9bec83c 100644 --- a/README.md +++ b/README.md @@ -30,7 +30,7 @@ Github [here](https://github.com/ethereum-optimism/design-docs/issues/15). To schedule a design review sesion: - Ensure that you have a pull request that has been reviewed async - [Open an issue](https://github.com/ethereum-optimism/design-docs/issues/new/choose) and click "Schedule a Design Review" then fill in the information -- Ensure that a design review meeting has been added to the [Public OP Stack Calendar](https://calendar.google.com/calendar/embed?src=c_e7b35eadabec39777b28192d371c45b6ef4177e01740517a234e7c768881fbfe%40group.calendar.google.com&ctz=America%2FLos_Angeles) +- A design review meeting will be added to the [Public OP Stack Calendar](https://calendar.google.com/calendar/embed?src=c_e7b35eadabec39777b28192d371c45b6ef4177e01740517a234e7c768881fbfe%40group.calendar.google.com&ctz=America%2FLos_Angeles) by an admin. Please reach out on discord if this hasn't happened. When choosing which stakeholders to invite to a design review meeting, it is good to tag people with high context of the components @@ -53,4 +53,4 @@ time between opening the PR and it getting onto the Design Review agenda: - Short document (e.g., 1-pager): share a minimum of 2 working days prior - Medium-length document (2-5 pages): share a minimum of 3-5 working days prior -- Long document (6+ pages): share at least 1 week prior \ No newline at end of file +- Long document (6+ pages): share at least 1 week prior