---
# System prepended metadata

title: About the weekly technical meeting

---

# About the weekly technical meeting

## Before the meeting

It's better to propose ahead of the meeting in the HackMD. When proposing,
please add the expect discussion time for the topic. For example:

> [] Rust-for-Linux async roadmap (5 min)

Besides if the topic is optional for this week, in other words it can be
postponed later, appreciate a marker, e.g.

> [] Rust-for-Linux async roadmap (5 min, optional)

It's `Ok` to overtime for a topic as long as we have enough time for topics of week ;-)

Topic example:
  * **Status Report**: Something people are curious about the status
  * **Idea**: Something one thinks it's good to have, need to check with others' opinion, usually take less than 5 min.
  * **POC/demo**: Similar to **Idea**, but with actually code or demo, can use a longer discussion.
  * **News**: Something happens either in Rust community (e.g. language features) or in Linux community that one thinks should be brought up.

## In the meeting

Routine topic (for every week):
  * **Agenda for next week**: Usually make sure a few **Status Report**s needed next week
  * **Maintainer update**: Maintainers' **Status Report** ;-) 

