GitHub issue tracking and our work

Hi!

At the f2f last week the group agreed to use GitHub as the center of our
work - tracking issues there, etc.  There was some concern during and after
the meeting that it be easy for people who do not have access to GitHub to
still be able to submit issues.  I agreed to look into this.

My conclusion is that it would be relatively easy to create a gateway from
an incoming email address to a specific GitHub issue tracker. So here is
what I propose:

   - If the group believes this is important, I will finish work on the
   gateway code.
   - This code will only create new issues.  In that issue (or somewhere to
   the side of the issue if we are concerned about privacy of the submitter)
   we will keep track of the email address of the submitter.  The issue itself
   will look as if it has been created by some fake GitHub user that we define
   (W3C Issue Daemon?).
   - The submitter will be notified via email when their issue is created,
   with a link to their issue in GitHub.
   - The submitter will get no further emails about the issue - they can
   only track the issue if they look in GitHub.
   - If the issue is a comment that requires resolution, it will be the
   responsibility of the Chair (or their delegate) to close the loop with the
   submitter and ensure their comment has been satisfied.

This last point is important.  W3C process requires that all comments be
resolved, and that we keep track of that and report it to the Director at
certain times (e.g., transition from Draft to Candidate Recommendation).

I don't really want to waste con call time on this sort of administrative
nonsense.  So, my request is that if you have comments, make them on list.
If there is substantial disagreement over the approach, the Chair should
either make a decision or put it on the agenda.

-- 
-Shane