-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
We need topics for each exercise for the new prototype #61
Comments
Looks like the config.json is updated. |
I added some topics, but I'd really like someone who knows more bash to go through and consider what topics are relevant.
I don't understand the question. Would you elaborate please? |
Sorry, I meant to say, do we still need the opened issues on /bash that are related to what is each exercise about, ex: "Topics: what is raindrops about? #68"? |
Got it. My take is "yes, we do". I made up some topics, but I'm not a credible source. I'd prefer it if people who are familiar with the language and are invested in the track would discuss each individual exercise to determine topics. |
We are working on a redesign of Exercism, which will have a much richer way of structuring the exercises.
The short version is that we'll have a handful of "core" exercises that are essential for learning about the language (typically 15-20), where completing each exercise unlocks a bunch of optional exercise that let you dive more deeply into different topics and practice different aspects of the language.
You can read more about this design choice in https://github.com/exercism/docs/blob/master/about/conception/progression.md
In order to make this possible, we need to figure out which topics each individual exercise covers. We have a list of potential topics that we can draw from, but this is by no means an exhaustive list, and the topics might not be relevant to Bash at all.
As an experiment I'm creating a separate issue for each exercise so that I can ping people who have solved it to help figure this out.
The text was updated successfully, but these errors were encountered: