W3C home > Mailing lists > Public > public-webrtc-editors@w3.org > October 2017

Re: Changing editors draft workflow

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Mon, 30 Oct 2017 15:58:00 +0100
To: "public-webrtc-editors@w3.org" <public-webrtc-editors@w3.org>
Cc: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Message-ID: <4fe3f19b-d9a3-433d-caf6-1d5604fbc449@w3.org>
Le 06/10/2017 à 14:41, Dominique Hazael-Massieux a écrit :
> I have thus been working with the Chairs and with Cullen whose specific
> review needs have been a factor to the establishment of the current
> workflow to try and see if we can find a less confusing approach.
> I would thus like us to switch to the following approach after the next
> editors draft get published:
> * any PR will be automatically assigned for Cullen to review - the
> expectation is that this request for review is PURELY from an IPR
> perspective, not on the technical content of the PR (Cullen can and will
> naturally continue to provide feedback on the technical content e.g. via
> PR comments)
> * I'd make it so that PR can only be merged in master if Cullen has
> approved them (using Github PR approval's tool); Cullen has agreed to
> review all open PR at least the day before the scheduled editors call on
> Thursdays and has offered to provide 24h reviews on request (email or SMS)

This is now implemented as I merged
https://github.com/w3c/webrtc-pc/pull/1622 earlier today.

> * I'd change our repo setup so that any PR merged gets reflected on
> github.io - in practice, that means getting rid of gh-pages as a
> separate branch, and use master as the branch used behind github.io; and
> make index.html a symlink to webrtc.html rather than a manually
> generated HTML version.

Now done as part of

I haven't removed gh-pages for now, while we make sure this is working
out as expected.

> This also means we would no longer maintained dated editors draft, nor
> need to run the release.sh script. The expectation is that each new
> editors draft would be published on TR as Working Draft (at least until
> we reach CR).

CR is now planned for Thursday, so it's not clear that there will be any
TR published under this new workflow. I don't know if that means we
would want to keep dated editors draft - I personally feel that git
provides enough versioning, but it would probably be possible to
automate publication of intermediaries static editors draft if that is

> I would want to apply this both to webrtc-pc and mediacapture-main - but
> first to the former.

I've raised https://github.com/w3c/mediacapture-main/issues/496 to track
the need to do this; I'll implement this new workflow there once we're
confident we have a working solution for webrtc-pc.

I have also raised an issue to track the need to provide a mechanism for

Received on Monday, 30 October 2017 14:58:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:19:06 UTC