-
-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
config.json: review exercise difficulty/unlocks/ordering #128
Conversation
I think this is pretty good - let me know what you think as soon as, and then we can re-assess where we are in terms of a launch 🎉 🎆 |
My opinion on this is that we should get at least 2-3 opinions for each exercise regarding difficulty and topics, and when we reach something that looks like an agreement we can commit to those numbers/strings. I'll give my suggestions in a few days if this is still open. I don't see any harm in merging everything right now, but let's see what others think. |
Existing ratings (not including your commits): hello-world = 1 1 gigasecond = 3 4 4 grains = ? |
Why do some have more than one? |
Based on all the ratings, from other people that are on the existing opened PR. |
Ah OK cool, makes sense to me! |
Looks like we'll also have to wait before we agree on the core exercises as well in #109, before integrating this one. |
It might be work following the request from: exercism/ruby#689
|
Makes sense to me. Which few exercises do we think we should leave as (core: false, unlocked_by: null)? I'll then amend this and we can keep this up to date with all our latest thinking 🙂 I think |
|
Cool, I'll change this PR to reflect those in a bit |
config.json
Outdated
}, | ||
{ | ||
"core": false, | ||
"difficulty": 1, | ||
"slug": "acronym", | ||
"difficulty": 2, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should change this to 4.
We have the following scores: 2 3 4 4.
Cool, I'll change that with the We want to keep this from going stagnant! 🙂 |
With those changes and if we complete #109 , this is pretty much ready to be merged. |
I agree. I think that this is probably the largest thing stopping the track from being launched at this moment in time. I am not too sure what else needs to be done before then. |
I've altered the core exercises as in #109 and have made the changes discussed previously here too. Think this could be ready to merge. |
Yes, looks good. Thank you very much for your effort and patience on this one. |
Massive
config.json
overhaul!Quick review:
Fixes #61, #62, #63, #64, #65, #66, #67, #68, #69, #70, #71, #72, #73, #74, #75, #103, and #109