Poll: Do you want a more strict PR policy

sphinxc0re · (This post was last modified: 02-25-2017, 07:47 PM by sphinxc0re.)

As I already mentioned:

I'd like to propose a more strict handling of open pull requests: When a PR is opened it will be getting closed after one month if it didn't got merged until then. This keeps out old and untouched PRs and might even speed up the development process. We could add a notice to the PR template on github. Thoughts?

xoft · (This post was last modified: 02-26-2017, 02:06 AM by xoft.)

A bit too strict. How about "one month after the last activity"? I don't think any kind of ahead-notice is needed, just a good message when closing the PR, along the lines of "Changes were requested before this PR could be merged, but there has been no activity for a month. Please consider changing the code as requested and then re-opening the PR."

sphinxc0re · 02-25-2017, 11:40 PM

@xoft You are right. Just going for the creation date of a PR won't do it. So 'last activity' seems fine to me. @bearbin would it be possible to make bearbot close PRs automatically with a notice?

yangm97 · 02-26-2017, 03:06 AM

Taken from github:

sphinxc0re Wrote:If your code is not ready

What’s ready?

LogicParrot · (This post was last modified: 02-26-2017, 05:47 AM by LogicParrot.)

proposal:
1. if last activity > X days && !status/blocked then consider inactive and close.
2. Prior to closing, manually review, and if code deemed interesting, mark with status/extract useful bits

NiLSPACE · 02-26-2017, 04:02 AM

I don't think there is anything wrong with closing a PR. It can always be reopened once people start working on it again. It just means there the PR is inactive for quite a while, not abandoned, but inactive.

sphinxc0re · 02-26-2017, 04:03 AM

So why not mark those PRs as status/inactive and close them?

LogicParrot · 02-26-2017, 05:43 AM

I don't mind this anymore. As long as no useful code is lost do whatever you want.
If a closed abandoned PR has useful code, I think marking it with "status/extract useful bits" is a good idea.

xoft · 02-26-2017, 06:31 AM

"Extracting code" may be problematic authorship-wise.

LogicParrot · 03-03-2017, 07:06 PM

Good point.
I marked some of my closed PRs, no authorship problem there.

Poll: Do you want a more strict PR policy You do not have permission to vote in this poll.
Yes	83.33%	5	83.33%
No	16.67%	1	16.67%
Total		6 vote(s)	100%