-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when closing stale PRs, link to an explanation of our PR queue practices #577
Comments
Good idea. I would suggest a page in https://github.com/scala/scala-dev/wiki (to avoid having a wiki in the scala/scala repo), much like the community build uses the GitHub wiki, but then you'd have to change the policy stated in https://github.com/scala/scala-dev/wiki/Home. |
I would to chime in with a proposal. The trouble with closing such stale PRs is that they are still different from PRs closed due to other reasons such as invalidity. I propose one of the following:
|
I'm fairly sure the Scala Team would be fine with labelling them as stale for reaping reasons. |
Dotty repo uses a "t:revisit" label. |
I just happened to notice an old label, "needs attention," which I would use all the time, obviously. Maybe shorten it to "needy". |
I'm against any solution that involves keeping abandoned PRs open indefinitely. (I'm prepared to argue the point if necessary.) I think I like the label idea. I'm not sure about
But I'm not sure I have a better idea than (hmm, I kinda like "dormant", I think? idk, though) |
perhaps "undecided" |
shelved? Git inspired.
…On Wed, 17 Mar 2021, 17:21 Bjorn Regnell, ***@***.***> wrote:
perhaps "undecided"
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#577 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAISMD4UEK4TDPLDMPDMW3DTEDP2JANCNFSM4GCHWH3Q>
.
|
My main concern is not to be too negative. We want to encourage, rather than discourage, resumption of work on the PR. Closing a PR already runs the risk of being discouraging, which is why this ticket exists. That's my main reservation about most of the possible choices here. I keep trying to come up with something like "candidate-for-resurrection" or "needs-new-owner" or "adopt-me" or "resumption-welcome" or.... something I'm probably trying too hard to make a label name do so much work... |
That's why i think "undecided" might be god. It's not negative, just say "we don't know enough yet". |
"revisit" as in dotty is also not negative, and perhaps more encouraging than "undecided" |
available?
Janek
…On Wed, 17 Mar 2021, 18:56 Bjorn Regnell, ***@***.***> wrote:
"revisit" as in dotty is also not negative, and perhaps more encouraging
than "undecided"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#577 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAISMD6CMLXY5MOHXDHUMTLTED3NZANCNFSM4GCHWH3Q>
.
|
Note that "tabled" means neither "on the table" nor "off the table". Oh, wikipedia explains: "In parliamentary procedure, the verb to table has the opposite meaning in different countries." So that makes it especially useful for a PR label intended to be multivalent. |
Another suitably ambiguous label: Does that mean "ready for review" or "the smell of bit rot demands that we close this PR". Someone will either say looks good or just close it and open a window. |
Orphaned? |
Seth's list includes "orphaned", capturing the vibe in the room. I also like his suggestion ":shrug:". |
deserted, forsaken, forgotten, forlorn, disowned, vacant |
Any of Seths suggestions sounds good to me. When a PR closes as stale, a comment explaining what exactly should still happen to bring it to fruition might be more important than the tag. |
The older idiom for putting a WIP into a dormant state was to call it a SIP. |
Or maybe simply R.I.P. |
That's what we call a Scala 3 SIP. |
taking inspo from the sex bots of twitter. |
README.md
orCONTRIBUTING.md
should have an explanation we can link to, in case someone is curiousas per discussion starting at https://gitter.im/scala/contributors?at=5be19ca96494cd16731f7e3b
The text was updated successfully, but these errors were encountered: