It looks like @Meatball is also a gdscript maintainer
1 Like
If you’re going to work on a WIP track for a while, it might be worthwhile to become a maintainer there. Until the track goes live, you can merge without reviews.
1 Like
I’m up for it — what do I need to do to become a maintainer?
And can one big sync be a single commit?
Generally speaking, I have nothing against you becoming a maintainer. I think longevity-speaking, there is a need for a new maintainer to make the track actually come to a finish line. I generally don’t have the motivation and the time at the moment, frankly speaking, to do a project like that. I also realize that there will be a difficult time to get things to track if none of the maintainers (including myself) is inactive. And with how the system works, if I am removed and you are added, you will still have the same problem. So my idea here is that you can be added as a maintainer and then you can ping me on discord or github (forum works, but I do not regularly check the forum). And I will review your prs and be able to help out with the exercism parts.
As for a single sync, I will discourage that since it is both hard to review and it can make changes hard to track.
1 Like
If you’re removed before launch, the track at launch would be maintained-solitary, and the cross-track reviewers can provide the necessary reviews since a maintainer can’t review their own PRs.
If you’re a maintainer and become inactive after launch , the track would be maintained, and cross-track reviewers can’t help. That becomes a problem with inactive maintainers because they can’t provide the reviews for the one that remains active (one of my tracks is going through that) so track development slows down a lot. Pinging Erik or Jeremy can help in an emergency, but it’s not a sustainable practice.
If everybody gets removed, the track is unmaintained at launch. and then cross-track reviewers can merge without reviews. That’s not great, but that means the track won’t be abandoned.
1 Like
It would be true if I were the sole maintainer at the moment, which I am not.
1 Like
(post deleted by author)
That should only matter after launch. WIP tracks don’t require reviews. You should just need someone with write access. So codingthat as a maintainer would be fine up to launch. Then yeah we’d to take a look at the maintainer team going forward.