feat: weekly review meetings (#16)

README.md

@@ -12,6 +12,7 @@ Happy collaborating!
 | weekly emea staff sync      | private             | AiB's Gno tech staff (EMEA) | Manfred (looking for a new lead) | Wednesdays; UTC=10am CET=12pm (PST=3am)   |
 | bi-weekly private core sync | private             | Core contributors           | Manfred (looking for a new lead) | Wednesdays (1/2); UTC=3pm PST=8am CET=5PM |
 | bi-weekly public core sync  | public (live video) | Core contributors           | Michelle                         | Wednesdays (2/2); UTC=3pm PST=8am CET=5PM |
+| weekly review meeting       | private             | Core contributors           | Manfred or Jae                   | Thursdays; UTC=4pm PST=9am CET=6PM        |
 
 Legend:
 - "AiB's Gno tech staff" is the combination of Gno dedicated developers + lead from other AiB tech products + devrels + tokenomics.
@@ -24,6 +25,12 @@ TODOs
 - consider switching all private meetings to public in some way, i.e., by sharing the outcome publicly.
 - use a machine-readable format, then generate this part of the markdown? could allow generating other formats (.ics?) and ease PR reviews.
 
+### Weekly review meeting
+
+We'll have weekly review meetings, with the possibility of occasional skips. Tech staff are encouraged to join whenever possible. Prior to the meeting, participants are requested to warm up by reviewing PRs, commenting, and updating relevant issues and PRs. At the end of the meeting, we'll share a list of discussions and status similar to [this example](https://github.com/golang/go/issues/33892).
+
+We can utilize [this board](https://github.com/orgs/gnolang/projects/4/views/1?query=is%3Aopen+sort%3Aupdated-desc) as a starting point, but we should also explore other repositories and search for relevant issues. During the meeting, the lead should share their screen for collaborative discussions while reviewing the shared content.
+
 ## Ponctual meetings and events
 
 TODO: workshops, brainstorming sessions, events, ...