Launch tracking

[kytrinyx]

Edit this issue to keep track of the tasks you're working on towards launch.

We have a rough guide for how to launch a track, which is sorely outdated but quite possibly better than nothing (I'm so sorry, I'm waaaay behind on getting documentation updated). https://github.com/exercism/legacy-docs/blob/main/language-tracks/launch/README.md

Check out https://github.com/orgs/exercism/teams/track-maintainers/discussions/1 for details about the #maintaining-\<track> channels and private #maintainers channel in the exercism-team Slack workspace.

Please ask if you have any questions or if anything is confusing!

[iHiD]

cc @larshp Here you go! :) You should have an invite to join the team. I'd suggest arranging a chat with @erikschierboom to plan this out. Are there any co-maintainers?

---

cc @erikschierboom - This repo will need updating too.

[larshp]

thanks, I got the invite, will have a look, but a bit short on time this weekend 😅

[larshp]

co-maintainers: @mbtools @g-back

[iHiD]

Both of those have been invited.

[ErikSchierboom]

We have just updated the documentation for building a new track! Below you'll find a list of the various tasks you'll work on to implement the track.

• [x] Join our community
• [x] Select programming language variant (if applicable)
• [x] Select testing framework
• [x] Add the first exercise
• [x] Add initial exercises
• [x] Setup Continuous Integration
• [x] Prepare for launch
• [x] Find Maintainers
• [ ] Launch!
• [x] Implement tooling
• [x] Prepare for open source contributions from strangers

Note: as the documentation is brand new™, there might be things that are unclear. Please let us know of any such things, and we'll fix them!

@kytrinyx If you feel like this is useful, you could consider copy/pasting this list in your opening post.

[larshp]

thanks

two more maintainers: @pokrakam @marianfoo

I guess a test runner is also required for each track? can you help creating a "abap-test-runner" repository?

[ErikSchierboom]

That's something @iHiD can only do. Could you open an issue on https://github.com/exercism/exercism for the test runner?

[larshp]

todo: implement 20+ other exercises

currently 9 exercises implemented

[iHiD]

Great progress!

[ErikSchierboom]

Indeed!

[larshp]

@iHiD can you help inviting @pokrakam and @marianfoo as maintainers of this repository?

[larshp]

Now at 21 exercises

Test runner running, CI setup

Multiple maintainers

would like to get https://github.com/exercism/exercism/issues/6186 fixed before launch, and probably https://github.com/exercism/abap-test-runner/issues/38

[ErikSchierboom]

Great stuff!

[larshp]

@iHiD can you help inviting @pokrakam and @marianfoo + @Mamikee + @jung-thomas as maintainers of this repository?

I guess due to https://github.com/exercism/website/pull/2438 they cannot access the content anymore

[iHiD]

Hi @larshp. Sure! I'll add them with write-permission to this repo, but I'd rather not add people as full maintainers until they've contributed, as doing so also gives permissions to other parts of the Exercism ecosystem.

Hi everyone! 🙂

[larshp]

yea, I understand, but on the other side https://github.com/exercism/website/pull/2438 closes inactive tracks for everyone not maintainer, so its difficult to contribute to something that is not visible 🤷‍♂️

[iHiD]

@larshp Yep, for sure. Maybe something we need to think about more generally (we probably want a beta role), but for now Erik's manually enabled that for the people you mentioned.

[pokrakam]

FWIW, @marianfoo and myself have already contributed exercises.

[iHiD]

@pokrakam Thank you 🙂 I'm totally happy for you all to have write access to this repo to build things out.

We have thousands of contributors that contribute code, content and exercises, but only a few are committed enough to warrant maintainer status, and get the kudos and permissions that that entails. So last year we put a fixed process in place for the journey to become and staying as a maintainer. You can read it all here: https://exercism.org/docs/community/maintainers

[pokrakam]

@iHiD Thanks, my comment was in response to "rather not add people as full maintainers until they've contributed", but contributor is perfectly sufficient 🙂 As far as maintainer goes my available time is probably too sporadic, we'll see how it goes.

[larshp]

cool, I think everything is set for launch?

will setting active to true work, as described in https://exercism.org/docs/building/tracks/new/launch ?

I think we would like to set a launch date sometime in the future, so we can make a bit of fuzz about it

[ErikSchierboom]

Yes, almost :) One minor thing that is missing are the key features: https://exercism.org/docs/building/tracks/config-json#key-features

I think we would like to set a launch date sometime in the future, so we can make a bit of fuzz about it

You can release the track anytime when you merge a PR to set active to true. Some buzz sounds good!