Launch tracking

[kytrinyx]

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/docs/blob/master/language-tracks/launch/README.md

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

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

[JimLynchCodes]

Woohoo, a new track?! 🥳

I love Clojure too so I'm excited for this!

[bobbicodes]

Great! All 76 exercises and tests from the Clojure track have been ported over. All that remains is a bit of plumbing for the test integration.

Documentation is a strong priority, and fortunately the babashka readme is an incredibly valuable guide to onboarding, with a directory full of example scripts and links to a wide range of projects and tools.

One of these is 4bb, a port of 4clojure which is a solid set of over 100 problems in a logical order for learning syntax and functional patterns. This will be good to include in the intro/learning section(s) to get folks quickly up to speed.

Setup guides for the currently developed editor integrations will be helpful, as many users will not have previous experience with a REPL-driven workflow. Clients are available for Emacs and Atom, the latter through the Chlorine package which I believe has also implemented autocompletion.

The babashka user base is showing to be almost curiously diverse, attracting a new branch of programmers and cases where full JVM-Clojure would be impractical, particularly in shell scripting and system tools commonly implemented, in Bash, Python, Rust or Go. I expect babashka to do to scripting what Clojure did for Java, and what Clojurescript did for the web. Just look at all the people Rich Hickey has gotten to use Lisp! So it will be good to expect and cater to a wide variety of backgrounds and target domains.

[ErikSchierboom]

What needs to happen to get Babashka live? It looks like there are a lot of exercises already, so that is great! If any help is needed, do let me know!

[bobbicodes]

@ErikSchierboom I'm not sure, actually. I followed the steps here and I think all it needs is CI and to be added to the site, however that works. I'll take a look at the others and see if I can figure it out.

[ErikSchierboom]

@porkostomus I've did a quick check, and the following things need to be done:

• Adding tags to the config.json file. See [v3] Add tags #11
• Adding content to the docs/ABOUT.md, docs/RESOURCES.md, docs/TESTS.md
• Creating a docs/SNIPPET.txt file
• Creating a test runner. This is a separate tool that allow running the tests on our website. See https://github.com/exercism/docs/blob/main/building/tooling/test-runners/README.md for more information. We have a generic test runner repo template that can be used as the basis of the test runner: https://github.com/exercism/generic-test-runner/ I've also built quite some test runners, so feel free to ask me any questions.
• Add CI. There already is a workflow to run configlet, but a separate workflow should be added that verifies that each practice exercise's example solution passes the tests.

Let me know if you have any questions. Feel free to contact me on Slack too.