# Gamedev WG Meeting 2021-11-02
###### tags: 'meeting'
Rust Gamedev WG Meeting
Tuesday, November 2 · 8:00 – 9:00am
Google Meet joining info
Video call link: https://meet.google.com/bfw-bbgc-qms
## Agenda
- Can we close [Official Rust Gamedev Discord #99](https://github.com/rust-gamedev/wg/issues/99)
- Need to add to website
- Should we host meetings on the Discord?
- Meetings are still in "prototype" phase
- Could be done later, but higher quality audience will likely come to Google Meetings (for now)
- Should announce meetings on Discord?
- Action item:
- Comment with link to issues about adding to website
- Close issue
- Discuss yearly gamedev survey [Revive yearly Rust gamedev survey #106](https://github.com/rust-gamedev/wg/issues/106)
- Is it useful?
- Last surveys were similar
- Figure out why it is useful first
- Would would be stakeholders?
- Teams (Embark, Bevy)
- Upstream Rust teams
- Can see into the problems of the Rust working groups
- They have very little context into the use cases
- How do they get this information?
- https://rust-ctcft.github.io/ctcft/
- Zulip
- A blog post to inside Rust
- Ecosystem of "all" of Rust ecosystem
- Ozkriff tried this
- What would be useful to know?
- How this survey compares to the last one
- This is the most important to not have a "stale" survey
- Find best times for other WG leads to meet
- Doodle poll send out to team leads
## Action items
- Talk to Alice/Erlend about list of questions from previous survey
- What do they think about contrasting questions
- Get PR made for Discord link on website, close issue
- Run a doodle poll to find ideal times for people
- This should go out to just team leads
(From last time)
- Look through previous meeting minutes, learn from how things were done before
- Find a good way to prepare meetings
- Github discussions
## Potential future meeting items
- arewegameyet discussions by Ozkriff
- Support game jam separatly
- Pull data separatly for items
- gamedev.rs
- blog post section is really empty
- what content could go there?
## Meeting data
Attendence count: 2
Meeting time: