Open
Description
Purpose: This issue compiles meeting notes for the Gno Core Staff's recurring meetings.
Process:
- Drafting: Notes are initially taken in Hackmd or Google Docs during meetings.
- Posting: Finalized notes are posted here as comments for easy tracking.
- Linking Issues: Include links to related GitHub issues for back-references.
Template
# Weekly Gno Staff Sync
Previous Syncs: https://github.com/gnolang/meetings/issues/36.
Welcome to our Weekly Gno Staff Sync. Our goals are to showcase progress, identify risks, align with stakeholders, and lay the groundwork for strategic discussions related to Gno. This meeting helps us make decisions and focus on critical issues and goals.
**First 10 Minutes: Silent Meeting Style**
> [Learn about Silent Meetings](https://www.eficode.com/blog/silent-backlog-refinement-meetings-a-more-effective-agile-meeting#:~:text=In%20a%20silent%20meeting%2C%20you,communication%20than%20talking%20and%20listening.)
For the first 10 minutes, we'll have a silent meeting. This lets team members add discussion points, review the meeting's scope, and make quick comments. We'll start with general updates and callouts before discussing points and addressing comments. Each meeting should end with action items and noting key decisions.
> If you have no discussion points or they've already been covered, please state so, like "no new updates since the last sync" or "already covered by xyz."
**This document is reused periodically. The first section has instructions. After the first horizontal line, you'll find the content section. Remember, the content will be shared on GitHub later, so only input content after the first horizontal line.**
---
<!-- Silent Meeting -->
## Discussion Points
### Your Name...
- foo
- bar
- ...
### Your Name...
### Your Name...
---
<!-- Discussion -->
## Callouts
1. Foo
- Outcome of callout (discussion) (GH issue / textual explainer...)
- ...
2. Bar
3. ...
## Action Items
1. Foo
2. Bar
3. ...