I would like to write the lists concept for the kotlin track. I didn’t realize I needed to make a post here first, so here is my (closed) pr.
Docs I have read:
I will keep working on it in the meantime, looking foreward to a response.
I made a start on this last year, but then I got sick and everything stopped. Most unfortunate!
My lists draft is here, but it’s probably too late for you to use it. There are a few other drafts in the same repo that may help you get started on other concepts. Feel free to use as much or as little of these as you want. This assumes that @SleeplessByte (the track maintainer) still wants to pursue a Kotlin syllabus.
I still hope to get back to Kotlin at some point, but currently my limited bandwidth is saturated by trying to sort out 3-year-old drafts of an R syllabus.
Thank you for the reply
Yeah I saw you author some of the existing concepts.
I took a very different approach to the about files… (you can find my draft for introduction.md here), I would appreciate feedback. Keep in mind its a very early draft.
One question: How should I go about making PRs in general? Make a post like this with the programming tag?
How do I get my pr reopened? (I assume that would be SleeplessByte)
PRs preferably are made by the request of a maintainer after they ask you to do so. Discussing possible PRs on the forums here makes that process a lot easier and leads to less wasted effort by both the contributor and the maintainer, who are both people volunteering their time and effort.
Someone with read-write access can reopen the PR. There are some nuances to that, but generally only Exercism staff or the maintainers of a particular track can do that. SleeplessByte is the track maintainer so assuming he wants to move forward, he’ll reopen the PR.
Ok, thank you. I didn’t know that before.
So you are suggesting me to start a discussion next time before doing anything and then, after being told to do so, open a pr?
Yes, this can save time for both you and the maintainer. It is frustrating to create a PR if nobody is going to review and merge it. Best to check first.
Thanks, I will do so next time!
Am I allowed to tag maintainers when asking or should I rather just wait?
Nothing is mechanically stopping you, but my working assumption is that an active maintainer generally would be receiving notifications in the Programming sub-category for their track. So I wouldn’t initially ping the maintainer because they might then receive two notifications in short order. However, if I haven’t heard an initial response them in say a week, I might go ahead and politely ping them in case they didn’t see the original post.
One problem you’ll encounter is that maintainer teams don’t have high discoverability. The teams are managed on GitHub, and I don’t believe the members’ identities are public-facing there. Even then, their GitHub handle may not be the same as their Exercism foum handle. It’ll sort itself out after a while since the maintainer introduces themselves or someone references them as the maintainer.
Another common way to figure out the maintainers is to see if a particular person is repeatedly pinged on threads about a track. That tends to happen when threads are started outside the track’s sub-category so someone like me might ping the maintainers in case they don’t see it.
Thank you for reopening and I’ll probably see you in the pr.