Launch tracking

[kytrinyx]

Overall documentation for building an Exercism track lives at https://exercism.org/docs/building/tracks/new

This issue helps keep track of the tasks you're working on towards launching this track.

The next steps are:

• [x] Join our community
• [x] Select programming language variant (if applicable)
• [x] Select testing framework
• [x] Add the first exercise
• [x] Add initial exercises
• [x] Setup Continuous Integration
• [x] Prepare for launch
• [x] Find Maintainers
• [x] Launch!
• [x] Implement tooling
• [x] Prepare for open source contributions from strangers

Once you've finished a task, you can check them in this list.

Questions

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

[BNAndras]

We're getting pretty close. I count 16 exercises done besides hello-world with another two for Bethany's review when she has time. I requested the track icon last week so we just need to work out the Docker kinks for the CI. There's also the issue of highlight.js not supporting Pyret, but that's being discussed on the forums.

[BNAndras]

@kytrinyx, as of this morning, we're pretty close to launch. I just need to make another pass through the track documents. Do I need a track icon before launch? I made a request at https://github.com/exercism/website-icons/issues/157, but if I need to wait, that's fine. I have some more exercises I can port.

[ErikSchierboom]

I think having a track icon would be sensible.

@iHiD Would you look at the icon or do you want @dem4ron to do that?

[BNAndras]

@ErikSchierboom, when you have a chance, can you take a look at the track? No rush, but I think we're largely there. I was considering upgrading the test runner to v2, but I won't get to it for a few weeks. v1 is likely enough for now.

[ErikSchierboom]

@BNAndras I've looked at the track and tested a couple of exercises, and I think we're good to go!

[BNAndras]

All merged exercises and ones still under review have pending test support so I think we're ready for another review whenever you're ready. The test runner image just needs to be bumped to pyret-npm 0.27 per exercism/pyret-test-runner#16.

[ErikSchierboom]

I've commented on that test runner issue. Once the version has been bumped, I'll give it another look.

[BNAndras]

Isaac noted last month that the documentation around the test runner and printing/spying could be restructured. For example, at the moment, I explain what the test runner does with the test suite, but I should be more explicit and show how to work with the test suite like turning tests on/off. I'll work on that the next few days.

[BNAndras]

@ErikSchierboom, the documentation is updated. I think we're ready for a final review.

[ErikSchierboom]

Okay! I'll have a look.

[ErikSchierboom]

I think we're good to go! Feel free to open a PR to set the track to active.