<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><blockquote type="cite"><span style="-webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);">… About the item 2, the W3C CG has </span><a href="https://www.w3.org/community/about/process/" class="" style="-webkit-text-size-adjust: auto;">some lightweight requirements about the process</a><span style="-webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);"> and it’s largely up to us to decide the exact process (talking about this in a bit); …</span><br></blockquote><div><br></div><div>Oh I meant to talk about some ideas about the process based on Florian’s CG chairing crash course, but then this email became too long (even the TL;DR part is pretty long… 🤦🏻♂️) and I forgot about that part…</div><div><br></div><div>But you know what, Simon already has the draft charter ready for everyone’s review (he’ll share it in a separate message), and the charter is a more natural context for discussing those process details (how to reach a consensus, when to utilize the mailing list, how to record meeting minutes, how to utilize the IRC channel, …).</div><br><div dir="ltr"><div>Best,</div><div>梁海 Liang Hai</div><div>https://lianghai.github.io</div></div><div dir="ltr"><br><blockquote type="cite">On Aug 28, 2020, at 03:28, Dave Crossland <dcrossland@google.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div class="gmail_quote">THANK YOU LIANG AND SIMON! <br>
</div><div class="gmail_quote"><br></div><div class="gmail_quote">All makes sense to me, great stuff :) </div><div class="gmail_quote"><br></div><div class="gmail_quote">Looking forward to seeing the charter draft PR. </div></div>
</div></blockquote></body></html>