Getting the Ruby track in better shape for the new site

[iHiD]

The new site has now launched and despite Ruby being one of the most popular Tracks, it's lagging behind in terms of being correctly configured on the new experience.

Specifically we're missing:

• Topics
• Difficulties
• An unlocking path

All of these things are defined in the config.json.

We should have 4 or 5 exercises that are "core": false, "unlocked_by": nil. These are bonus exercises that will be available as soon as you join the track, along with the first core exercise.

Then, each core exercise should have a handful of exercises that will be unlocked when you complete it. So if hamming is a core exercise, then you might have 6 or 7 exercises that are core: false, "unlocked_by": "hamming".

We have a tool, Configlet, that you can download to help structure the unlocking. Run the tree command with the path to the root of a track repository (or . from within the root of the repo). This will show you which exercises depend on which core exercises.

$ configlet tree .

It would be incredibly helpful if people could provide PRs with topics and difficulties. If anyone wants to take responsibility for structuring some or all of the unlocking behaviour that would be amazing too.

The following Tracks are good examples:

• Go
• C#
• R

Thanks!

(cc @exercism/ruby)

[guygastineau]

This is great information. I just made a pull request and followed the convention that I saw in the config.json of low difficulty rating and nothing requiring a core exercise to unlock. I also saw no topics so I didn't add any. The atbash exercise, which would be good for unlocking my affine-cipher exercise, is not core so I could set that up.

[Insti]

It would be good if someone could copy the topics and unlock tree from the Go track so we have a better starting point.

Note that we can't just copy the config.json file directly since we need to keep our own UUIDs

[emcoding]

Is it okay if I start some 'unlockings' for the earlier exercises only?

[Insti]

Yes 👍

[koppen]

I have submitted #818 which basically does what @Insti suggests in #815 (comment) by copying pretty much everything from the Go track, preserving the Ruby-only exercises and UUIDs.

[emcoding]

O cool @koppen ! Are you also going to fill in the 'unlocked_by's' or shall I work on that after your PR is merged?

[koppen]

I have filled them in to the best of my knowledge based on the progression in the Go track. It could probably do with some more work but I wasn’t sure how to decide what unlocks what. Den 27. juli 2018 kl. 12.52.48, Maud de Vries (notifications@github.com) skrev:

…

O cool @koppen <https://github.com/koppen> ! Are you also going to fill in the 'unlocked_by's' or shall I work on that after your PR is merged? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#815 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAZUGSqC_PpNy1gSSO2JTBF5-WM8GBAks5uKvEAgaJpZM4VWjjH> .

[Insti]

Working on the unlocks after we get #818 merged is probably best.

[minaslater]

It seems that #818 has already been merged. Has anyone begun work on the unlocks?

[emcoding]

Yes, I am on it. Planning to do a PR this weekend, for the first few exercises.