bazelbuild
rules_scala maintainership
Continuation of the discussion started in https://github.com/bazel-contrib/rules_scala/issues/1763
To be completely transparent, @liucijus is stepping down as a maintainer, and we’re looking for new maintainers to help keep rules_scala healthy and active.
I want to personally thank @liucijus for all the incredible work you’ve done on rules_scala. It’s been amazing collaborating with you, and I wish you the best on your new journey. I hope to continue seeing your contributions in the future ❤️
Thanks also to @BillyAutrey for raising this and suggesting possible maintainers.
Based on past contributions, I would like to propose the following initial invitations to join as maintainers:
- @mbland for his excellent work on bzlmod, bringing rules_scala into bcr, and for his expertise in Bazel.
- @WojciechMazur for keeping rules_scala up to date with the latest Scala versions, and for his expertise in Scala.
With this setup, we would have diverse representation from three organizations: EngFlow, VirtusLab, and Wix.
@romanowski, as I understand you and @WojciechMazur are colleagues at VirtusLab. You mentioned @tgodzik as a possible maintainer — could you coordinate internally and confirm who from VirtusLab would like to represent your team?
There were other suggestions for maintainers, and I’m open to considering them. For now, I’d like to start by inviting the most active contributors first, as described in our governance document.
Finally, I’m open to discussion about the ideal number of maintainers for rules_scala. While anyone interested is welcome, it may be helpful to keep the group manageable to maintain effective collaboration. I welcome thoughts from everyone here.
@WojciechMazur is probably the best person here. @romanowski suggested me as a backup, but if you feel that would be too many maintainers, it's perfectly reasonable to just add Wojciech.
I'm great with Mike and Wojciech, I know them both personally and think they'd be great to add to the mix. Let's keep rules_scala marching forward! Excited to see the continuous work here, especially with the recent interest from the scala community.
I asked around internally and got the green light all around. Count me in.
As always, I'll need a bit of help, but I'll do what I can to help keep things moving along.
@simuons I see that #1766 landed, but do you also need to update the repo configuration via the GitHub UI to add @WojciechMazur and me as admins?
@simuons I see that #1766 landed, but do you also need to update the repo configuration via the GitHub UI to add @WojciechMazur and me as admins?
Hi, @mbland, you are right. Added you both as admins.
Related question - should we consider adding a role to help with PRs, and maybe a related one to triage tickets? The backlog looks pretty deep.
@simuons Thanks! I seem to have GitHub admin access now. But it seems my access to Buildkite is limited. For example, I seem to lack permissions cancel the current build #5770 for #1768 (not that I want to). Is that something you can update?
@BillyAutrey Are you volunteering for either or both of those proposed roles? 😉
@mbland I don't have permissions on Buildkite either. I think Buildkite is managed by Bazel team and we should ask them for permissions. Or migrate to GitHub Actions as described in Transfer Process
@BillyAutrey Are you volunteering for either or both of those proposed roles? 😉
Wherever you need me, boss. 🙃