Automated assistance for standup agenda preparation

[mtbcarroll]

A fair chunk of what I do in standup preparation is quite automatable. A helper script should make my life easier by,

1. Getting the list of failing jobs from Jenkins.

2. Getting the list of feedback from QA2, having status "new" and no existing Trac tickets. Might be nice to sort them by submitting IP, then e-mail address. Would be nice to list them differently if they include an error or uploaded files: "File(s)", "Error", or "Comment" if neither, that kind of thing.

3. Unrebased PRs need to be listed, but considering them rebased even if the open rebase PR isn't yet merged. Need to be able to locally mark PRs for not listing again, as most of us can't push to refs/notes/see_also/; that could also generate a file for sending to people who can (maybe shared gdoc).

4. Checking the pulls dashboard for ome and openmicroscopy on GitHub, list the open PRs that are neither on hold nor excluded, but omit those that scc merge conflicts out. Need to be able to locally mark PRs for not listing again until they have changed. PRs have a "last modified" but this has to take account of further commits / force-pushes and change of label on corresponding issue. Would be nice to also be able to locally mark unchanged PRs for re-listing after a certain date.

5. Pushing the list of above items for the standup agenda to a separate small gdoc from which I can copy and paste.

[bpindelski]

Might not give us everything we want yet, but it's still worth following this project - ​http://code.google.com/p/googlecl/.

[mtbcarroll]

Unrebased PRs are at least now easier after sbesson's work on the SCC unrebased PRs Jenkins job. There are other questions about how stand-up could be done: for instance, should opening a PR create a card on Trello? Or, perhaps, reviewers/fixers can be arranged through GitHub's notion of assignees? So, there is broader context around this ticket.

[jamoore]

This is certainly something that could be discussed next week with Chris under the heading of "corgi". For example, when a PR is merged, corgi would know. Then, if we inject the logic to check def needsRebasing(self) and it returns False, we could indeed create a trello card.

[sbesson]

Thoughts about moving this to the DevX board and breaking it into individual items via checklists/cards?

[jamoore]

+1. (Perhaps we should involve the omego column too.)

[mtbcarroll]

Possibly: might "scoping" include casting around for all kinds of ideas and trying to come to a consensus on what to even attempt?

[mtbcarroll]

Stand-up may move from GDocs to Trello.

[sbesson]

With the requirement for team members to list their own PRs, closing this. We can open a RFE card if needed, but there is no need to keep it in Trac.