Create new track for GDScript

@BNAndras @meatball We’re so close to launch, if we can get the last bits of #97 closed out; #5 and PowerShell can come post-launch whenever anyone is ready to add all the pieces for that.

Once #97 is in place I can handle one last update to the latest Godot and configlet sync and any fallout from that, and then we can launch.

Post-launch, adding exercises that have been waiting in the queue one at a time — can that be done by any individual maintainer? (I’m OK if the track moves to maintained-solitary if that’s where we stand at the moment, BTW.)

I haven’t been involved in the GDScript track in over two years, but I can take a look later.

Have the maintainers taken a look and tested out the test runner and docs? That’s typically one of the big steps right before launch.

After launch, the track will be maintained since there is more than one maintainer and not all maintainers are cross-track-reviewers. maintained-solitary is only if there’s only one maintainer who also isn’t a cross-track-reviewer as well. All PRs on a launched track will need a review before merging. For maintained repos. that will be one of the other maintainers for that track. For maintained-solitary, you wouldn’t have another maintainer to review things for you so a cross-track-reviewer can come in and provide your review.

Thanks for your quick reply. Actually it’s your review comments from last July (here and the thread just beneath it) I was still waiting to hear back about, plus one similarly from @meatball .

Thanks for clarifying. Yes, the test runner and docs were accurate back then, it was a question of what to cover where and how in the docs. But I would do a final manual run from both student and maintainer perspectives of everything in the repos, and complete my beta run, just before launch. I’ve rerun the tests against the latest Godot and updated metadata and docs via configlet. It’s really just #97, bumping the Godot version in the test runner repo, and final re-checks of everything and we should be set to launch, unless anyone is seeing any new blockers.

@pfertyk you’re still officially on the repo maintainers team, what’s your status nowadays for this?

Hi! :smile: For now, I am not going to participate in this. It’s possible that I will rejoin the GDScript track in the future, but you can make all decisions without me.

Thanks for reactivating the track BTW, I really appreciate all your work! :heart:

2 Likes

@pfertyk You should be able to drop yourself from the GDScript team.

Hi there. Can you finally launch this? It has been inactive for so long.

Hi there. Please try and do the final push now for GDScript. You are almost done!

Do you want to help out with the track?

I can try… but I am still a novice at GDScript

You don’t need to be an expert to build a track :slight_smile: A lot of tracks were built by people learning the language! But you do need some dedication to put in the time needed to get it launched! Tracks don’t launch themselves and it takes volunteers to get them launched. You can read about building a track here: https://exercism.org/docs/building/tracks/new. If you’d like to see a GDScript track launch, you can help make it happen! If that sounds like something you’d like to do, you can share your GitHub handle and we can add you to the track maintainer list.

zeektvbox01-hub

@ErikSchierboom ^^ another GDScript volunteer

Consider it done.

1 Like

Err…so…am I a contributor now?

You’re a maintainer on the GDScript track :slight_smile:

Go forth and help launch it! https://exercism.org/docs/building/tracks/new should help. If you have any questions, other maintainers will be happy to help answer them. Or come chat with us on the Exercism Discord!

Err…Where is the member’s tag

Err…Anyone?@IssacG?

You’re not listed in Sign in to GitHub · GitHub. It’s been a while, but I think you need to accept the emailed invite to the Exercism org.

joined(did not see inbox invite)

2 Likes