Skip to content

Latest commit

 

History

History
59 lines (40 loc) · 3.39 KB

README.md

File metadata and controls

59 lines (40 loc) · 3.39 KB
Raw

Meetings

Welcome to the Meetings repository! This repository is dedicated to tracking meetings, storing transcripts, and sharing links and resources related to meetings.

Happy collaborating!

Recurring meetings

Title Visibility Attendees Lead Schedule
weekly world staff sync private AiB's Gno tech staff Manfred (looking for a new lead) Mondays; UTC=3pm PST=8am CET=5PM
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 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.
  • Core contributors is the combination of the "AiB's Gno tech staff" + notable contributors + tech partners + grantees.

TODOs

  • weekly us staff sync
  • review syncs
  • office hours
  • 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.

Bi-weekly public core sync

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)

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.

We will use this board 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

TODO: workshops, brainstorming sessions, events, ...

See gno.land/events.