immersive-web/administrivia

A repo for managing the adminstrative tasks of the Immersive Web Group.

administrivia's Issues

Create HTML for immersiveweb.org

Update the existing pages from webvr.rocks for the new site at immersiveweb.org

Send out an email notifying current subscribers of the change and give them an opportunity to opt-out.

Move Layers to WG

Let's discuss if it's time to move Layers to Working Group from Community Group.

Related issue Layers 148

Change repo default branches from master to main

WG

• WebXR
• WebXR Gamepad Module
• WebXR AR Module
• Dom Overlays
• Hit Test
• AR Common

CG

• Anchors
• Computer Vision
• Geo Alignment
• Layers
• Lighting Estimation
• Navigation
• Performance Improvements
• Real World Geometry
• Spatial Favicons
• WebXR Hands Input

Others

• Administrivia
• ImmersiveWebDev
• homepage
• WebXR Samples
• WebXR Inputs Profiles
• WebXR Polyfill
• WebVR Polyfill
• Cardboard VR Display
• WebXR Test API
• Immersive Web Github.io
• WebVR Polyfill dpdb
• WebXR Reference(Archive?)
• Privacy and Security
• WebVR Rocks
• Proposals
• Community Resources(?)
• WebVR

Add general readme for teleconferences

from homepage repository #2

Add readme.md file to keep information on two bi-weekly (WG and CG) teleconferences in the meetings directory with regular schedule and links (also procedures?).

Create a PR for the proposals README that fleshes out the rest of the process of moving from idea into active CG repo

Rough idea:

Gates for moving spec into WG:

• Proposal Issue
• Three implementer +1s
• Create repo and stabilize IDL
• Review by WG and react to feedback
• Chairs of the appropriate WG agree to take it on

Build/publish roadmap

Need a roadmap of spec/implementation landscape.

Transfer immersivewebweekly.com domain registration to the same system as the other IWCG domains.

Create guidance for how to get the WG to take new deliverables on in the XR spec - e.g. "promoting incubations"

Should go in this repo for now, then possibly move to XRDA readme.

Request TAG review of WebXR (post-FPWD).

Publicize IRC/Zakim/RRSAgent guidelines

Talk with Mozilla about domain name hosting.

Add Oculus Quest to supported devices on WebVR.com

Currently only Oculus Rift and Go are shown as supported but Oculus Quest is possible now one of the most popular devices for VR and features WebVR experiences in the build in browser.

Remove the WebXR Reference repo

https://github.com/immersive-web/webxr-reference

Now that the API has started to ship in browsers, long-term the developer-facing content should be the MDN content. The Repo in this working group can only ever be distracting and out of date.

It looks like I have the authority to delete this repo. I'm opening this ticket so that link to it may be removed or changed to MDN.

Set up next FTF post-TPAC.

Current suggestion: San Jose, Jan 28-29th.

File requests for wide review of WebXR Device API

(from Dom)

Next month will come the wide review
https://www.w3.org/wiki/DocumentReview

We should start to list which groups we want to get review from, and how
stable the document needs to be before we can get these reviews started
(my suggestion would be to stage our requests over time - only wait for
asking a review from a given group until we think our content is stable
enough for that specific group).

My first guess would be:

• Accessible Platform Architecture WG for accessibility - probably ASAP
  since I don't think there are specific plans to address accessibility at
  the API level at the moment; would be good to see if we can meaningfully
  address anything in http://w3c.github.io/apa/fast/checklist.html

• Technical Architecture Group (they've reviewed part of the work
  already, but lots will have changed) - this usually requires a first
  pass at the security & privacy self-review
  https://w3ctag.github.io/security-questionnaire/

• Privacy Interest Group - likewise re self-review

• Security Interest Group - likewise re self-review

• Media & Entertainment IG? - they're interested at least in 360 video,
  and would probably be keen on understanding how much WebXR helps with it

• Web Platform WG - for integration with rAF, usage of WebIDL (probably
  ASAP?)

• Audio WG - for audio integration

• Devices & Sensors - for comparison with Generic Sensor framework

• Khronos WebGL WG? (for sanity check? can probably be done ASAP?)

Given that we don't handle human-readable content in any particular way,
I think for I18N, we can give mostly a heads-up that we think we're out
of their scope:
https://www.w3.org/International/techniques/developing-specs?collapse

Once we have a more up to date editors draft, we should also review our
normative dependencies to check if some of these deserve a specific
request for review from their producers.

Home for Depth API proposal

Hi Immersive Web!

I'd like to start some work related to introducing Depth API to WebXR. The main question then is whether it should be a separate repository, or should it be included as a part of our existing repos (real-world-geometry comes to mind).

I've put my initial thoughts about the API in my personal, publicly visible repository, please take a look at the explainer in case that is something that could help with making a decision: https://github.com/bialpio/webxr-depth-api/blob/master/explainer.md.

So far it seemed that we tended to create new repository for each new feature. In this particular case, I do not see any problems with that approach as I do not think depth API will need to strongly depend on something from other repositories apart from WebXR Device API, but I'd still like to hear what people think.

Tracking loss followup

@AdaRoseCannon , you were going to follow up with app developers to see how they typically handle tracking loss.

Label issues to be addressed at TPAC FTF

Update the privacy policy to reflect the IWCG's policies.

https://immersivewebweekly.com/privacy/

Unconference topics for TPAC - add them here

Update redirect link on w3c org 1.1 spec URL

From @jsantell on December 11, 2017 19:44

The URL is broken for the link in the repo move it looks like: https://w3c.github.io/webvr/spec/1.1/ -- redirects to https://example.com/spec/1.1

Copied from original issue: immersive-web/webxr#306

Post a publishing calendar in a public place. Include info about when submitted news/links are due, editorial policy, and general expectations.

Follow up on inviting a few select Invited Experts.

Write up proposals repo etiquette document.

Rough draft:

• on creating a repo, send group email about its creation
• proposal repos should ideally but not necessarily have two admins from two orgs
• there is a bootstrapping period with self-reviewed and merged PRs during initial setup and until other interested parties sign up for review
• then PRs that are reviewed and signed off by someone from another org

Max to review session options

@lincolnfrog, you were going to review immersive-web/webxr#388 and identify any other issues separately.

Establish logos

Both for WebXR and the Immersive Web
Hire a designer
Set up voting for the community

Launch the Working Group

List

• Email Dom, about pushing back launch until:
• Update Github Readme
• Launch Web Site
• Detail Transparency plans
• Write Blog Post

Then

• Publish W3C Blog Post
• Social Media

Frame the intentions for TPAC

Write a paragraph framing what our intentions are for TPAC, to lead in to the goals we want to achieve and the CFP.

Fix dates and Minutes

• The latest CG date is wrong. I will fix it after the meeting today.
• Some of the previous meeting minutes links are broken.

Move Repos to Repository Manager

This issue is to keep track of all the spec repos that need to meet the IPR requirements and imported to the tool.

• dom-overlays

• hit-test

• layers

• webxr

• webxr-ar-module

• webxr-gamepads-module

• lighting-estimation

• anchors

• webxr-hands-input

• real-world-geometry

• performance-improvements

• geo-alignment

• spatial-favicons

• navigation

• computer-vision

Send out hotel info for 9/17 F2F

Transfer the source repo to the IW GitHub org

Set up immersiveweb.org

Sub tasks may include:

• Pointing all already registered domain names to immersiveweb.org
• Updating webvr.rocks content for the brave new WebXR world
• Reimburse folks who paid for domains?

Demos at TPAC F2F

As per our discussion on the WG call today, I'm creating an issue so that we can schedule demos during the WG F2F at TPAC and also see what we could offer to Coralie at W3C. I'm there Mon - Wed and would be happy to help organize this part.

Cloud Anchor discussion at TPAC?

This was mentioned on this morning's editors call as something that has seen a fair amount of interest from users but which we don't have line-of-sight to a solution for. It may be productive to start a conversation on the topic at TPAC, and ideally we could convince some individuals with knowledge of how the current proprietary systems work engage with us as well. It's unlikely that we will be able to find any solutions at this point, but getting people thinking about it is worthwhile.

Set up implementers "check in"

Schedule a meeting recurring every 6 weeks to check in with the folks implementing WebXR.

Write up agenda/minuting plan and send to group

Include commitment to sending agenda or cancelling meetings by Fridays EOD before a call.

Move hit-testing and dom-overlay to WG

These are pretty stable should probably be moved across to make a standard, this issue is to keep track of that.

Consolidate CG domain names into Mozilla MR's Route53 account.

Collect topics for TPAC schedule

File issue on stating number of supported displays

@AdaRoseCannon you put in the notes:
" ACTION: file issue to allow developers explicitly state the amount view ports they support." during the Multiview discussion, related to issue https://github.com/immersive-web/webxr/issues/317?

Write transition process document

In progress...

Set up hosting and publishing using GitHub Pages and Actions

Set up a form for community members to submit news and links

Which AR features are planed in the upcoming API spec?

Apologies in advance if this is not the right place to ask.
As I understand the focus of this draft is to reach feature parity with the previous webVR API. I was wondering about which AR features are going to ship in this release since, as I understood it, even features that were usable in previous versions like hit-test are still discussed as proposals.
Are AR features like hit-test or anchors included in the upcoming specs and do the proposed anchors also include image targets?

Kind regards

Virtual TPAC???

/agenda to work out what we want to do for tpac.

Put together agenda-building/minuting plan.

Put together schedule for TPAC

TBD once the CFP is out and issues are labeled, e.g. week of Oct 8th.

FaceMesh Extraction Explainer

I've recently created an Explainer for what an API to extract a FaceMesh from a camera stream that can be rendered to/over would look like. While my current proposal is that it not (at first) integrate with WebXR (and thus would likely be promoted to the WICG rather than here if/when it is ready), I know that the topic is of interest to people in this CG, so I wanted to mention it and share a pointer during the next CG call.

The Explainer can be found at https://github.com/alcooper91/face-mesh

/agenda