W3C home > Mailing lists > Public > public-tt@w3.org > November 2015

Use github issues for Timed Text specifications

From: Philippe Le Hegaret <plh@w3.org>
Date: Wed, 4 Nov 2015 14:37:23 -0500
To: Timed Text Working Group <public-tt@w3.org>
Message-ID: <563A5E73.7030909@w3.org>
Following last week discussion on switching to GitHub, I transferred all 
tracker issues (based on a snapshot taken at 11am ET today) into Github 
issues. The only ones that have been left behind are the SDP-US ones [1].

As such, people should use GitHub to raise issues against the drafts.

I updated the dashboard [2] to replace the tracker links with the GitHub 
ones. Specification editors should update the status of their documents 
to indicate the use of Github as well. They should also update the 
dashboard with the proper link to the editor's draft (I did so for IMSC1 
already). Proper redirect should be put in place for dvcs link. See [3] 
for an example on how to do so (note that you can improve it to take 
into account fragments).

If you're new to GitHub, here are some materials for you:

- Git & Github Training
   http://w3c.github.io/wai-gh-training-2015-06-29/
- Using GitHub for Spec Work
  http://w3c.github.io/specs.html

If you're interested in one of the specifications in particular, make 
sure to watch the repository [4] in your github setting (and choose 
email and/or web while doing so).

Philippe

[1] http://www.w3.org/AudioVideo/TT/tracker/products/5/all
[2] https://www.w3.org/wiki/TimedText/Publications
[3] 
https://dvcs.w3.org/hg/webperf/file/d711d1002738/specs/Beacon/Overview.html
[4] https://github.com/watching
Received on Wednesday, 4 November 2015 19:37:25 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:24:25 UTC