Class name should match ExerciseName.h

[masters3d]

• anagram
• bob
• etl
• grade-school
• hamming
• hello-world
• leap
• nucleotide-count
• perfect-numbers
• phone-number
• robot-name
• space-age
• word-count

[kytrinyx]

Kind of a tangent: take a look at the discussion I had with Peter Tseng in exercism/go#275

We've been talking about how to make small tasks that would be easy for new contributors to come in and tackle (also here: exercism/discussions#8) and even though making individual issues make a bit more noise, it does mean that we can load-balance the solving of it.

We learned (the hard way) that checklists get out of date, and it's hard to verify whether or not something is done. By making an individual ticket for each relevant problem we get a visual "todo" list that shows the status of each problem. Just glancing at it shows us red/purple/green, and we can see the status without having to go back and make an extra effort.

[masters3d]

Ah good point. It crossed my mind but I thought it would be too much noise. Is there a tool to help with creating an issue for each problem in a single track?

On Apr 10, 2016, at 7:07 AM, Katrina Owen [email protected] wrote:

Kind of a tangent: take a look at the discussion I had with Peter Tseng in exercism/go#275

We've been talking about how to make small tasks that would be easy for new contributors to come in and tackle (also here: exercism/discussions#8) and even though making individual issues make a bit more noise, it does mean that we can load-balance the solving of it.

We learned (the hard way) that checklists get out of date, and it's hard to verify whether or not something is done. By making an individual ticket for each relevant problem we get a visual "todo" list that shows the status of each problem. Just glancing at it shows us red/purple/green, and we can see the status without having to go back and make an extra effort.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

[kytrinyx]

Yeah, the https://github.com/github/hub tool lets you post issues from the command line. We put together a bash script to do this:

for slug in anagram bob etl grade-school hamming hello-world leap nucleotide-count perfect-numbers phone-number robot-name space-age word-count; do
        MSG=$(cat ISSUE.md | sed -e "s/PLACEHOLDER/$slug/")
        echo "$MSG"
        hub issue create -m "$MSG"
done

It assumes that the issue describing everything is in ISSUE.md in the directory that you're running it from (presumably the root directory of this repo), and that the first line of that file says PLACEHOLDER: Class name should match ExerciseName.h or something like that.

It's worth also putting a link to a top-level issue (such as this one), e.g. See https://github.com/exercism/xobjective-c/issues/48, because then you get a handy visual todo list that shows the current status of each of those issues.

[masters3d]

Thanks! I like this better.

[kytrinyx]

Yeah, this is great!