W3C home > Mailing lists > Public > public-html-media@w3.org > January 2015

[EME] Using GitHub Issues

From: David Dorwin <ddorwin@google.com>
Date: Tue, 6 Jan 2015 10:21:58 -0800
Message-ID: <CAHD2rshrRFqxFiZmKPJ+LoO+AmfmyuXZQw6CH9seLwr_UXvbXw@mail.gmail.com>
To: "public-html-media@w3.org" <public-html-media@w3.org>
tl;dr:

   - This list will receive notifications when new issues are opened on
   GitHub, just as was the case with Buganizer.
   - If you want to receive email notifications when GiHub issues are
   updated, sign in to GitHub and watch the EME project
   <https://github.com/w3c/encrypted-media>
   - I would like to move to GitHub for new EME issues (link
   <https://github.com/w3c/encrypted-media/issues/new>).


In mid-December, I started experimenting with using GitHub's Issues
functionality for EME. Advantages include automated integration with
commits, rich text using Markdown, and the potential for broader
participation.

One of the downsides was that this email list did not automatically receive
notifications of new issues like new Buganizer issues. Thanks to Dominique
and github-notify-ml <https://github.com/dontcallmedom/github-notify-ml>,
we now have parity (example
<http://lists.w3.org/Archives/Public/public-html-media/2015Jan/0005.html>).
The rich formatting is lost, so it's probably best to click the link at the
bottom of such emails and view the issue in GitHub. As with Buganizer, you
can receive updates for specific issues by clicking the Subscribe button in
the right column of an issue page. (This is not necessary if you are
watching the project - see below.)

If you would like to receive (formatted) email notifications for all issues
and comments, sign in to GitHub and watch the EME project
<https://github.com/w3c/encrypted-media>. See
https://github.com/blog/1204-notifications-stars and
https://help.github.com/articles/about-notifications/ for more information
on notificaitons.


I would like to move to GitHub as the primary issue tracker for EME. There
are still a number of bugs in Buganizer with useful history. I propose that
we continue to track those in Buganizer but file new issues in GitHub. We
can move specific Buganizer issues to GitHub when appropriate (i.e. recent
issues or those with little or no history). I can update the SoTD section
of the spec to reference both issue trackers.
Received on Tuesday, 6 January 2015 18:22:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:33:05 UTC