Re: IWCG Coordination Thread for Sept 22, 2018 (A new approach to every-other-week CG call)

Thank you Trevor. Just a very minor suggestion for the summary: add links
to the issues/prs for quick access.

Regards,
Iker

On Sat, Sep 22, 2018 at 3:52 PM Trevor Flowers <trevor@trevor.smith.name>
wrote:

> Hello, immersive web folks!
>
> After speaking with a few people about the most effective use of the
> community group call time, we're going to try something new.
>
> Instead of defaulting to attending a CG call every other Tuesday, we're
> going to switch to a weekly email thread like this one to coordinate
> ongoing work in the repos. We'll use the every-other-Tuesday CG call slot
> only when we're blocked and async text fails us.
>
>
> *The every-other-Tuesday reservation on WebEx will remain in case we need
> it, but by default we'll use a weekly email thread like this one to
> coordinate work in the repos.*
>
> Each week I'll write up an activity summary (as below) and if there is an
> Issue or PR that needs attention then we can use the weekly email thread to
> request attention and to tag people who you feel need to weigh in.
>
> If you feel that an Issue or PR is stalled and we're talking past each
> other then reach out directly to me. I'll coordinate a CG call and send out
> an email to the list announcing that the call is happening and the topics
> that we'll cover.
>
> *Note: This change applies only to the community group call, not the
> alternating Tuesday working group calls that are organized by Ada Rose
> Cannon.*
>
> As always, if you have feedback, concerns, or questions then feel free to
> reach out to me or any IW chair or editor.
>
> - Trevor
>
> p.s. If you're ever curious, the chairs and editors are using a project
> in the Administrivia repo
> <https://github.com/immersive-web/administrivia/projects/1> to track our
> work. It's a lot more detail than most folks want, but if you're a process
> nerd like I am then it's pretty interesting.
>
> *Activity Summary for Summary 22:*
>
>
> *(includes WebXR Device API work until the WG is formed)*
>
> *webxr*
> - Nell and Brandon set up a new Issue tagging and milestone system
> - Ada updated the README to reflect the new working group
> - Jordan added oninputsourceschange event to XRSession
> - Blair and Leonard discussed Brandon's WebXR modes Issue #394
> - The WebXR repo hit Issue #400 (!!!) with DOM Overlays
> - Max filed Issue #402 for Lite AR Mode
> - Max also files Issue #403 for XRFrame lifecycle
>
> *working group charter*
> - Chris changed the FPWD date from October to November
>
> *polyfill*
> - Jordan continues to field bug reports and knock down bugs
>
> *proposals*
> - Nell opened Issue #27 for lighting estimation
> - Blair opened Issue #25 for eye tracking
> - Nell moved "encapulated XR apps" from webxr into Issue #26
>
>
> *geo-alignment*- Blair filed an initial README and explainer
>
>
> *hit-test*- Max added a section on backface culling to the explainer
>
> *anchors*
> - no activity
>
>
>