<div dir="ltr">If you are wondering what the strange automated pings are, I'm just experimenting looking at stale issues in various states and what we should do about them. (The tool is clever enough to ignore its own comments etc). I'm just running the tool manually at the moment. The idea is it will ping issues where appropriate and do reports and generally end up being a way we can monitor to make sure our project is healthy.<br><br>For example, nothing should be in a state waiting for an OMC decision for more than a few weeks - it should be decided upon and moved to whatever state the outcome of the decision is. We had three of these (and looking at them they all should just be in a different state). For every issue it ought to be very clear what the next action is (I'm a big fan of GTD (Getting Things Done) process!)<br><br>So, right now, we have 82 PR's that have not been touched in the last 180 days. I picked 180 just for an example because it creates a shorter list and in practice I imagine 30 days will be the reports we do:<div><br></div><div>So of the 82:</div><div><br></div><div>* deferred after 1.1.1 ( 5 issues)<br></div><div> - this is a valid state for stale PRs. An item falls here if it's set to the milestone for 1.1.1 or it's marked branch 1.1.1 and not master</div><div><br></div><div>* waiting for OMC ( 2 issues) </div><div> - as discussed above, we'll just comment them to ping the OMC<br></div><div><br></div><div>* waiting for OTC/waiting for review ( 0 issues)</div><div> - similar to OMC, we'll just autocomment them to ping the OTC/committers</div><div><br></div><div>* cla required ( 22 issues)<br></div><div> - if something has been waiting for a CLA for 30 days or more we probably ought to ping it a couple of times, but then reject the PR as it's unlikely we'll get a CLA if none have been supplied after a couple of pings and a couple of months.</div><div><br></div><div>* failed CI ( 14 issues)<br></div><div> - if it's not in any of the states above but it failed CI it ends up here. Some of these might be known false positives, so no action other than interesting to monitor? Maybe we need some label for "it failed CI but that's expected and not a blocker"? that way there's an action on the PR creator to "get this in a state where CI passes" and we could auto comment anything that's failed CI and not been touched for a month (and perhaps even close it as rejected the next time).</div><div><br></div><div>* all the rest ( 39 issues)</div><div> - most of these have no labels or milestones. Some have milestone:Assessed (but not sure how that helps). Some have branch labels. This is just the backlog.</div><div><br></div><div>Mark<br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">openssl-machine</strong> <span dir="auto"><<a href="mailto:notifications@github.com">notifications@github.com</a>></span><br>Date: Tue, Feb 25, 2020 at 9:00 AM<br>Subject: Re: [openssl/openssl] A nonce does not have a minimum length (#5909)<br>To: openssl/openssl <<a href="mailto:openssl@noreply.github.com">openssl@noreply.github.com</a>><br></div><br><p>Automated Ping: This issue is in a state where it requires action by <a href="https://github.com/orgs/openssl/teams/omc" target="_blank">@openssl/omc</a> but the last update was 607 days ago</p>
<p style="font-size:small;color:#666">—<br>You are receiving this because you are on a team that was mentioned.<br>Reply to this email directly, <a href="https://github.com/openssl/openssl/pull/5909?email_source=notifications&email_token=ABJSZVYOTC365JGLUQ6PPD3RETMZFA5CNFSM4EZOPWL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM3DYDY#issuecomment-590756879" target="_blank">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABJSZVZWLSNLZGOYBS2CN3TRETMZFANCNFSM4EZOPWLQ" target="_blank">unsubscribe</a>.<img src="https://github.com/notifications/beacon/ABJSZV24K2KFZLGSX4NFASTRETMZFA5CNFSM4EZOPWL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM3DYDY.gif" height="1" width="1" alt=""></p>
</div></div></div>