Launch tracking

[kytrinyx]

The next steps are roughly:

• Select programming language variant (if applicable)
• Select testing framework
• Select assertion framework Assertion library #3
• Write first exercise
• First ~20 optional exercises [long-lived] Exercises #2
• Add the track to the site as inactive
• Request a track icon Request a track icon #7
• Write "getting started" instructions for people using the track
• Launch!
• Prepare for open source contributions from strangers

---

Polish/cleanup:

• Move wren-testie work back into main repo and add script to vendor it or use git subwhatever
• Review all test docs to make sure nothing JS specific is there
• Expect.that ... toBe doesn't read quite right
• Finish writing overall track docs

---

Edit this issue to keep track of the tasks you're working on towards launch.

We have a rough guide for how to launch a track, which is sorely outdated but
quite possibly better than nothing (I'm so sorry, I'm waaaay behind on getting
documentation updated).
https://github.com/exercism/legacy-docs/blob/main/language-tracks/launch/README.md

Check out https://github.com/orgs/exercism/teams/track-maintainers/discussions/1
for details about the #maintaining-<track> channels and private #maintainers channel in the exercism-team Slack workspace.

Please ask if you have any questions or if anything is confusing!

[iHiD]

@joshgoebel You're in the game! :)

[iHiD]

@joshgoebel Maybe organise a 1-1 with @ErikSchierboom to get started

[joshgoebel]

I think we made it (since launch is tomorrow), so I'm closing this.