Tracking Actions

There was some discussion at the last teleconference [1] about the various tracking options/systems we currently use.

I would like to suggest we simplify the options to:
1) W3C Tracker for Actions (Open and Closed states only) - remove all Issues
2) GitHub Issues

The W3C Tracker would be used for actions from meetings that WG members must undertake and report back to the WG.
GitHub Issues for actions that lead directly to Editor updates of the Deliverables.
(Github issues can also include tracking of relevant discussions of that update.)

In many cases, a W3C Tracker Action may lead to the creation of a GH Issue later.

For example, Sabrina has this Action [2] to propose the definition of a new policy type and report back to the WG.
The result of this, if the WG agrees, will be the creation of a new GH Issue to track the changes for the Vocab deliverable.

Comments and views welcome..

Renato Iannella, Monegraph
Co-Chair, W3C Permissions & Obligations Expression (POE) Working Group

[1] https://www.w3.org/2016/10/17-poe-minutes <https://www.w3.org/2016/10/17-poe-minutes>
[2] https://www.w3.org/2016/poe/track/actions/28 <https://www.w3.org/2016/poe/track/actions/28>