You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Ensure that you have a pull request that has been reviewed async
32
32
-[Open an issue](https://github.com/ethereum-optimism/design-docs/issues/new/choose) and click "Schedule a Design Review" then fill in the information
33
-
-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)
33
+
-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.
34
34
35
35
When choosing which stakeholders to invite to a design review meeting,
36
36
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:
53
53
54
54
- Short document (e.g., 1-pager): share a minimum of 2 working days prior
55
55
- Medium-length document (2-5 pages): share a minimum of 3-5 working days prior
56
-
- Long document (6+ pages): share at least 1 week prior
56
+
- Long document (6+ pages): share at least 1 week prior
0 commit comments