chore: update instructions for weekly gh reviews (#19)

Addresses #18

Author: moul

README.md

@@ -12,7 +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        |
+| weekly GH 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.
@@ -25,11 +25,32 @@ 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).
+### Bi-weekly public core sync
 
-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.
+> Lead: Michelle
+> Schedule: Wednesdays (2/2); UTC=3pm PST=8am CET=5PM
+
+_TODO: add useful info on events & records_
+
+### Weekly GH review meeting ([meta issue](https://github.com/gnolang/meetings/issues/18))
+
+> Lead: Manfred or Jae
+> Schedule: Thursdays; UTC=4pm PST=9am CET=6PM
+
+We will hold weekly review meetings, with potential exceptions depending on circumstances. All technical staff are encouraged to participate whenever feasible. 
+
+**Meeting Process**:
+1. **Preparation**: Before the meeting, participants are expected to update their own PRs/issues and glance over others'. 
+2. **Leading**: One participant will spearhead the session by sharing their screen, facilitating collaborative discussion and review.
+3. **Commenting**: Feedback should be shared directly within the context of the PRs or issues under review. 
+4. **Meta-Issues**: After the meeting, we will update a designated meta-issue with links to the items reviewed during the session, following [this example](https://github.com/golang/go/issues/33892).
+
+We will use [this board](https://github.com/orgs/gnolang/projects/4/views/1?query=is%3Aopen+sort%3Aupdated-desc) as our starting point for issue/PR selection, but exploring other repositories and identifying pertinent issues is also encouraged.
+This process allows us to stay up-to-date and have dynamic discussions on relevant topics.
+
+---
 
 ## Ponctual meetings and events