rust-gamedev/wg

[Meeting] 19th Feb, 2020

Lokathor opened this issue · 4 comments

Lokathor commented
Wodann commented

I've created issue #88 for the second topic.

ozkriff commented

Ask @ozkriff to put a link to our working group into the r/rust_gamedev sidebar.

Done.

I guess, r/rust_gamedev's description wasn't updated for a while. I've asked Efraet if the WG could propose an updated version.

aclysma commented

I missed the meeting so I may be out of the loop, but I think a roadmap for 2020 sounds great. I think it would be helpful to go through the responses to the question "What do you think should be the game-dev working group's priorities for the next 3-6 months" in the survey to identify a few high-priority things

  • 👍3
msiglreith commented

We had a bit of a conversation with @aclysma regarding the possible content of the roadmap based on the survey:

  • Ecosystem maturity: Provide an overview for people to see where we are and what to work on (C/C++ bindings, Rust libraries, etc.). Asset pipeline an interesting topic to help people starting.
  • Iteration times: Difficult to tackle imo beside scripting languages, general compiler optimizations, or dynamic linking
  • Documentation: Driven by individuals, gamedev wg should providing a place to link resources and promote them in monthly newsletters (as already done by @ozkriff ❤️ )
  • Game Engines: Nope - for others to tackle
  • Consoles: Trying to push in the background for people with access, just mention on the roadmap that the workgroup is actively working on it and try to gather people for working on it
  • Ecosystem coordination: we had some success here, it’s something we want to continue. Bringing people together for windowing, threading, async, allocator, etc. Library blessing difficult beside saying 'hey these are libs many people use'.
  • Foundational libraries: Splitting of libraries into 'ugly low level' and 'rusty-opinionated high level' often helpful. For example audio libraries, input handling or math.
  • 👍5