You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As with other sbt/* repos, I can sometimes help — within limits.
I'm really not a front-line maintainer on sbt-git or any other sbt/* repo (that I can think of right now). I don't use this plugin and I've never looked at the code.
But I am an admin of the overall sbt org (subordinate to @eed3si9n, naturally), so I'm one of the people who can help with administrative stuff.
Things I can do:
I can review PRs that only affect simple build-level stuff and/or administrative stuff like naming and publishing — the sort of thing any experienced Scala OSS maintainer can review in almost any repo.
I can grant the maintainer bit to a volunteer who has at some sort of track record of helping out here or on other sbt plugins and is willing to keep the overall health of the plugin in mind and not just, like, merge their own pet PR
I can merge a PR that's been reviewed and doesn't seem controversial. If you want your PR merged, try to recruit reviewers, if none appear of their own accord!
I'm also happy to merge a PR that's been sitting for a while where it seems like a reasonable effort to find reviewers has been made and no one took the trouble to review and/or object to a change.
Things I can't do:
Deal with Sonatype stuff — we need @eed3si9n for that. (Now that sbt-ci-release in place, hopefully there will be no need, since releasing only involves pushing a tag.)
Hope this clarifies my involvement. Anyone interested should feel free to use this discussion thread to self-organize around improving the maintenance situation here.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
As with other sbt/* repos, I can sometimes help — within limits.
I'm really not a front-line maintainer on sbt-git or any other sbt/* repo (that I can think of right now). I don't use this plugin and I've never looked at the code.
But I am an admin of the overall sbt org (subordinate to @eed3si9n, naturally), so I'm one of the people who can help with administrative stuff.
Things I can do:
Things I can't do:
Hope this clarifies my involvement. Anyone interested should feel free to use this discussion thread to self-organize around improving the maintenance situation here.
Beta Was this translation helpful? Give feedback.
All reactions