Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New shortname #257

Closed
4 tasks
marcoscaceres opened this issue Mar 25, 2020 · 15 comments
Closed
4 tasks

New shortname #257

marcoscaceres opened this issue Mar 25, 2020 · 15 comments
Assignees

Comments

@marcoscaceres
Copy link
Member

With this spec now covering screen wake lock, we should:

  • request a new shortname.
  • change the repo name.
  • check all documents to make sure the new shortname is used.
  • update w3c.github.io repo to redirect also.
@anssiko anssiko assigned xfq and unassigned anssiko Mar 26, 2020
@xfq
Copy link
Member

xfq commented Mar 27, 2020

So we need to:

  • Rename this repo from wake-lock to screen-wake-lock
  • Change the shortname from wake-lock to screen-wake-lock and publish an updated CR (or WD) with shortname redirection
  • Rename the WPT directory to screen-wake-lock
  • Check all documents to make sure the new shortname is used
  • Redirect https://w3c.github.io/wake-lock/ to https://w3c.github.io/screen-wake-lock/
  • Create a new repo system-wake-lock for System Wake Lock API
  • Publish System Wake Lock API as FPWD

Am I understanding correctly?

@marcoscaceres
Copy link
Member Author

That all sounds correct to me.

@anssiko
Copy link
Member

anssiko commented Mar 27, 2020

Thanks! LGTM, with comments:

Change the shortname from wake-lock to screen-wake-lock and publish an updated CR with shortname redirection

If the process flexibly allows us to publish a revised CR great, if not, WD in between.

Redirect https://w3c.github.io/wake-lock/ to https://w3c.github.io/screen-wake-lock/

Do we want to redirect anchors? In such case would need to recreate a gutted wake-lock repo for the redirect script. Cool URLs don’t change and all that.

Create a new repo system-wake-lock for Screen Wake Lock API

Nit: for System Wake Lock.

@xfq
Copy link
Member

xfq commented Mar 28, 2020

Redirect https://w3c.github.io/wake-lock/ to https://w3c.github.io/screen-wake-lock/

Do we want to redirect anchors? In such case would need to recreate a gutted wake-lock repo for the redirect script. Cool URLs don’t change and all that.

I have renamed this repo to screen-wake-lock and created a new wake-lock repo for redirection. Feel free to add a redirect script.

chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue Apr 13, 2020
WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock. Besides,
due to there's no w3c spec for system wake lock at present, this
CL removes the idlharness tests for system wake lock temporarily.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue Apr 14, 2020
WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to http/tests/wake-lock because `fetch()` idl files
requires http server.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue Apr 15, 2020
WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue Apr 16, 2020
WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue Apr 20, 2020
WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760380}
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue Apr 20, 2020
WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760380}
pull bot pushed a commit to Yannic/chromium that referenced this issue Apr 20, 2020
WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760380}
@Honry
Copy link
Contributor

Honry commented Apr 20, 2020

Rename the WPT directory to screen-wake-lock

@xfq, I've done this task.

@xfq
Copy link
Member

xfq commented Apr 20, 2020

Thanks @Honry!

moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this issue May 1, 2020
…screen-wake-lock, a=testonly

Automatic update from web-platform-tests
[wake-lock] Rename wpt/wake-lock to wpt/screen-wake-lock

WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760380}

--

wpt-commits: 229773d606f8b9603046580b32935968a4326004
wpt-pr: 22883
xeonchen pushed a commit to xeonchen/gecko that referenced this issue May 1, 2020
…screen-wake-lock, a=testonly

Automatic update from web-platform-tests
[wake-lock] Rename wpt/wake-lock to wpt/screen-wake-lock

WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760380}

--

wpt-commits: 229773d606f8b9603046580b32935968a4326004
wpt-pr: 22883
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this issue May 1, 2020
…screen-wake-lock, a=testonly

Automatic update from web-platform-tests
[wake-lock] Rename wpt/wake-lock to wpt/screen-wake-lock

WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760380}

--

wpt-commits: 229773d606f8b9603046580b32935968a4326004
wpt-pr: 22883
xeonchen pushed a commit to xeonchen/gecko that referenced this issue May 1, 2020
…screen-wake-lock, a=testonly

Automatic update from web-platform-tests
[wake-lock] Rename wpt/wake-lock to wpt/screen-wake-lock

WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760380}

--

wpt-commits: 229773d606f8b9603046580b32935968a4326004
wpt-pr: 22883
gecko-dev-updater pushed a commit to marco-c/gecko-dev-comments-removed that referenced this issue May 3, 2020
…screen-wake-lock, a=testonly

Automatic update from web-platform-tests
[wake-lock] Rename wpt/wake-lock to wpt/screen-wake-lock

WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.linintel.com>
Reviewed-by: Reilly Grant <reillygchromium.org>
Reviewed-by: Robert Ma <robertmachromium.org>
Cr-Commit-Position: refs/heads/master{#760380}

--

wpt-commits: 229773d606f8b9603046580b32935968a4326004
wpt-pr: 22883

UltraBlame original commit: 25d4a6fe968026dd0bff9b9e02f7a06aa2f5d5ab
gecko-dev-updater pushed a commit to marco-c/gecko-dev-comments-removed that referenced this issue May 3, 2020
…screen-wake-lock, a=testonly

Automatic update from web-platform-tests
[wake-lock] Rename wpt/wake-lock to wpt/screen-wake-lock

WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.linintel.com>
Reviewed-by: Reilly Grant <reillygchromium.org>
Reviewed-by: Robert Ma <robertmachromium.org>
Cr-Commit-Position: refs/heads/master{#760380}

--

wpt-commits: 229773d606f8b9603046580b32935968a4326004
wpt-pr: 22883

UltraBlame original commit: 1504db210b53e2f479df9ff40ce6f86d80c49bda
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified-and-comments-removed that referenced this issue May 3, 2020
…screen-wake-lock, a=testonly

Automatic update from web-platform-tests
[wake-lock] Rename wpt/wake-lock to wpt/screen-wake-lock

WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.linintel.com>
Reviewed-by: Reilly Grant <reillygchromium.org>
Reviewed-by: Robert Ma <robertmachromium.org>
Cr-Commit-Position: refs/heads/master{#760380}

--

wpt-commits: 229773d606f8b9603046580b32935968a4326004
wpt-pr: 22883

UltraBlame original commit: 25d4a6fe968026dd0bff9b9e02f7a06aa2f5d5ab
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified-and-comments-removed that referenced this issue May 3, 2020
…screen-wake-lock, a=testonly

Automatic update from web-platform-tests
[wake-lock] Rename wpt/wake-lock to wpt/screen-wake-lock

WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.linintel.com>
Reviewed-by: Reilly Grant <reillygchromium.org>
Reviewed-by: Robert Ma <robertmachromium.org>
Cr-Commit-Position: refs/heads/master{#760380}

--

wpt-commits: 229773d606f8b9603046580b32935968a4326004
wpt-pr: 22883

UltraBlame original commit: 1504db210b53e2f479df9ff40ce6f86d80c49bda
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified that referenced this issue May 3, 2020
…screen-wake-lock, a=testonly

Automatic update from web-platform-tests
[wake-lock] Rename wpt/wake-lock to wpt/screen-wake-lock

WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.linintel.com>
Reviewed-by: Reilly Grant <reillygchromium.org>
Reviewed-by: Robert Ma <robertmachromium.org>
Cr-Commit-Position: refs/heads/master{#760380}

--

wpt-commits: 229773d606f8b9603046580b32935968a4326004
wpt-pr: 22883

UltraBlame original commit: 25d4a6fe968026dd0bff9b9e02f7a06aa2f5d5ab
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified that referenced this issue May 3, 2020
…screen-wake-lock, a=testonly

Automatic update from web-platform-tests
[wake-lock] Rename wpt/wake-lock to wpt/screen-wake-lock

WPT test directories should named after the shortname of the spec,
this CL renames wpt/wake-lock to wpt/screen-wake-lock and moves
system wake lock related tests to web_tests/wake-lock since
there's no w3c spec for system wake lock at present.

This CL also moves the idlharness tests for system wake lock
to wpt_internal/system-wake-lock to use wptserve.

Relevant spec issue: w3c/screen-wake-lock#257

Bug: 1064685
Change-Id: I77939065ca82257fc261dcdfd07c9e7608fc9c92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147352
Commit-Queue: Wanming Lin <wanming.linintel.com>
Reviewed-by: Reilly Grant <reillygchromium.org>
Reviewed-by: Robert Ma <robertmachromium.org>
Cr-Commit-Position: refs/heads/master{#760380}

--

wpt-commits: 229773d606f8b9603046580b32935968a4326004
wpt-pr: 22883

UltraBlame original commit: 1504db210b53e2f479df9ff40ce6f86d80c49bda
@marcoscaceres
Copy link
Member Author

@xfq, how we looking for for just getting screen-wake-lock on TR again?

@xfq
Copy link
Member

xfq commented Aug 5, 2020

I think we should wait until #262 is fixed. I've been busy with my other groups recently, but I will try my best to move it forward.

@rakuco
Copy link
Member

rakuco commented Sep 16, 2020

With the new Process 2020 in place, do we need to wait for a new CR in order to update the TR? I'm not in a hurry, it just sucks that our CI is failing and ReSpec complains because of the lack of a screen-wake-lock TR.

@anssiko
Copy link
Member

anssiko commented Sep 16, 2020

@xfq please see what could be done, can we snapshot a fresh WD as an interim solution to the CI fails?

@xfq
Copy link
Member

xfq commented Sep 17, 2020

The fastest way to update the /TR version is returning the spec to WD. Director's approval (and wide review) is not needed. Only a group resolution and a draft transition announcement (to explain why the document is returned to WD) is needed.

@anssiko
Copy link
Member

anssiko commented Sep 17, 2020

Let this issue be the group resolution. If someone has concerns with the proposal below, please let us know by 24 September, 2020.

Proposal: Publish a Working Draft of the Screen Wake Lock API at https://www.w3.org/TR/screen-wake-lock/, snapshotting the latest Editor's Draft at https://w3c.github.io/screen-wake-lock/

Rationale (for transition announcement): The Devices and Sensors Working Group requests a Working Draft of the Screen Wake Lock API to be published to address an issue with the CI system that depends on the /TR space. The group plans to advance this specification to Candidate Recommendation subsequently, and this interim WD publication does not change that plan.

@reillyeon

@anssiko
Copy link
Member

anssiko commented Sep 25, 2020

No concerns were raised for the proposal to publish a Working Draft of the Screen Wake Lock API at https://www.w3.org/TR/screen-wake-lock/, snapshotting the latest Editor's Draft at https://w3c.github.io/screen-wake-lock/

@xfq please proceed with the publication practicalities at your earliest opportunity.

@xfq
Copy link
Member

xfq commented Sep 30, 2020

@xfq please proceed with the publication practicalities at your earliest opportunity.

Published.

@anssiko anssiko closed this as completed Sep 30, 2020
@rakuco
Copy link
Member

rakuco commented Sep 30, 2020

Thanks, @anssiko and @xfq! I can confirm that our CI is finally happy and green again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants