Could we track actions with github issues?

Hi folks,

I recognize that this incurs a slightly higher administrative overhead,
but I think it would have benefits. I would like to move to a model
where the actions we generate in meetings are recorded in GitHub issues
and resolved by individual pull requests that address those issues.
(With the understanding that sometimes issues are closely related and we
may end up with a single PR that fixes more than one issue.)

I observe, for example, that the minutes of the 22 March meeting say
that Steven resolved eight actions. But I have no easy way of
identifying what those actions were or how each was resolved. (I
appreciate that I can look at previous minutes, but that’s not always
terribly clear (I feel free to say that in part because *I’m*
responsible for the previous meeting minutes)). And since we don’t have
change tracking for the spec, I can diff the 22 Feb draft and the 17
March draft, but I can’t tell which changes were related to which
issues.

For what it’s worth, this is how the XProc CG manages the XProc drafts
and it has worked very well for us.

The discipline of managing issues this way would make it easier for
reviewers to track changes to the spec and to the test suite. It would
also tie in nicely with continuous integration as we could have a public
“editor’s draft” that reflects all the pull requests that have been
merged. And then we could use tags to publish official updates to the
status quo.

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica