Chapters are local or regional groups set up with the general goal of discussing standards, best described in the original post about it. The general goal is to dramatically increase participation in, and education about, standards in new and manageable ways. In the words of The Extensible Web Manifesto: To tighten the feedback loop between the editors of Web standards and developers. Essentially:
There's no formal definition of how a chapter has to work, it's up to participants to determine what they discuss or do, and how. Ideally, we want chapters to partner where possible with individuals involved in standards, but it isn't a strict requirement. All we ask is that local chapters try to "keep track" of their work or discussions, create very simple distilled notes or summaries and share that feedback back into standards. The jQuery Foundation's issue tracker can be used to collect/collate this feedback. However, if you choose not to directly coordinate with someone in standards land who can carry this information back, it's important that this feedback makes it back to editors or relevant working groups (if there are any) or back to the incubation project (in WICG) as appropriate. The goal is to help both ends of this flow.
If you collected helpful notes for developers, share those too - a github org or gist, a blog post, a post on, or some social media like meetup, G+ or Facebook.
Our pilot partnered with the University of Vermont, who donated a dedicated space for 3 hours, one evening per week. This isn't the only time or place where folks can talk, and not everyone can come every week or stay for the whole 3 hours, but having a place where you can get together for some dedicated and substantial face-time seems helpful. Initially, we introduced a newer people to the world of standards and helpful resources. The model it eventually followed was simply to have people people start reading about things that were new to them, and bring things they were interested in to the group's attention. They would talk about it until they thought they understood it, they would see what state of implementation it was in. If none, they'd look for a polyfill and, if it wasn't listed on helpful resources like MDN or Web Platform Docs, they might submit it. They'd try it out and discuss it some more. In some cases they were interested in potentially contributing Web Platform tests.
If you run a meetup, or you're interested in setting a group, please let the jQuery Foundation's standards group know and we'll try to help link you up with someone who can help or keep track in order to better collaborate and help serve as a conduit.
Feel free to email Brian Kardell and Robin Berjon if you have any private questions or media inquiries.