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

Publish first Working draft of the layers spec #202

Closed
cabanier opened this issue Sep 14, 2020 · 9 comments
Closed

Publish first Working draft of the layers spec #202

cabanier opened this issue Sep 14, 2020 · 9 comments

Comments

@cabanier
Copy link
Member

/agenda The layers spec hasn't changed much in a while and implementation in the Oculus browser is proceeding. Can we publish a WD?

@probot-label probot-label bot added the agenda label Sep 14, 2020
@cabanier
Copy link
Member Author

#201 should be submitted before WD.

@Yonet Yonet removed the agenda label Sep 22, 2020
@himorin
Copy link
Member

himorin commented Nov 16, 2020

@Yonet have we processed call for consensus in the IWWG on this??
https://www.w3.org/2020/09/15-immersive-web-minutes.html#t03
CG call minutes say no objection, but could not find pointer(s) in the WG.

@cabanier
Copy link
Member Author

Are you saying that it doesn't count because it was a CG call?
If so, we should do it in the next WG call.

@himorin
Copy link
Member

himorin commented Nov 16, 2020

per our WG charter, we need to open formal CfC. and it's a duty of chairs.
https://www.w3.org/2020/05/immersive-Web-wg-charter.html#decisions

To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. A call for consensus (CfC) will be issued for all resolutions (for example, via email and/or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised on the mailing list by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.

@cabanier
Copy link
Member Author

OK. How can I do that?

@AdaRoseCannon
Copy link
Member

AdaRoseCannon commented Nov 16, 2020

I'll do it now.

Edit: This was my bad, one of the chairs should have done this after the September call. Manish put one out for hands but layers got missed as I thought the issue was resolved I did not follow up.

@AdaRoseCannon
Copy link
Member

Sent out.

@cabanier
Copy link
Member Author

Thanks @AdaRoseCannon !

@himorin
Copy link
Member

himorin commented Nov 16, 2020

Thank you so much for catching this @AdaRoseCannon ! (will take care for following procedure in transitions repo)

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

4 participants