- From: ddorwin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Nov 2016 23:08:01 +0000
- To: public-html-media@w3.org
ddorwin has just created a new issue for https://github.com/w3c/encrypted-media: == Move gh-pages branch to master == Early on, we created a `gh-pages` branch and deleted the `master` branch so that we could view the spec on `github.io`. It is possible ([documentation](https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/)) to have `github.io` serve from either `master` or `gh-pages`. Working on `gh-pages` is a bit strange and inconsistent with other repositories. More importantly, though, as we think about forking into WICG for incubation, it will probably be clearer if there is a `master` branch rather than focusing on what is on `github.io`. Having a `master` branch would also allow WICG or other forks to create a `gh-pages` branch that displays something special on `github.io`. If we're going to do this, we should probably do it before forking into WICG. @sideshowbarker, @plehegar: Any thoughts on this? Will the history look the same as it does for gh-pages today? Note that this has no impact on PR and is completely transparent to the spec and what is served from https://w3c.github.io/encrypted-media/. Please view or discuss this issue at https://github.com/w3c/encrypted-media/issues/355 using your GitHub account
Received on Thursday, 3 November 2016 23:08:07 UTC