Tracking issue for what we need to do before opening this project now soon! Let's link relevant issues and have checkboxes for them here and drive discussions about it here

What to do before:

• Some real running "hello world" shader
• Go through issues and docs and make sure we don't have anything in it we DON'T want to share
  • @repi
  • @arirawr
• Good enough initial onboarding experience Good project onboarding experience #28
• Include small example Rust shader and screenshot in top of README
• @repi may have thoughts about "Build system" #48, it'd be nice to have those before opensourcing (and so vaguely public API)
• Draft an announcement post to GH releases.
• Clean up the README: move background/"why embark" sections to post? That would help get the "scope" section more visible, which seems to be a priority.
• Go through README and tweak some language (mention @MaikKlein and RLSL prototype connection more also?) @repi

CUT for v0.1 release (may do later):

• Ideally some Ark shaders Convert all Ark shaders to Rust GPU #36 (we have a simple similar sky shader instead)
• Sketch out "Compiler Engineer" job ad would be excellent to have posted when we open source the project

Release checklist:

• Open repo
• Open discord
• Un-draft the release post
• Announce in Discord, link release post
• @repi tweet it out, link release post
• Add project to embark.dev and embark.rs - @arirawr
• Post on users.rust-lang.org and r/rust - who?

Once released:

• Automerge PRs (Add CI automerge of PRs #54) @repi
• RLSL update (blog post, link to rust-gpu) @MaikKlein