@kenneth: Postponed until I got a bit more feedback.

@travisleithead: I would like to take a look and give some feedback.

@torgo: Me too. Bumped until 29th.

KC: I have some new text, just need to put it back into the doc.

Kenneth: i want to move this to a more proper place.

Hadley: mdn artifcle?

Hey:Kenneth: it's a spec like thing - rather than an article.

Hadley: turn it into a note?

Peter: we have other things like the API design guidelines document - which we are just publishing on github [ta\g] We can host it on tag.w3.org - we can publish a finding or note.

Kenneth: Relative difference in standing between them?

Dan: I think a finding has more weight because TAG publishes findings, but NOTEs generally don't. But NOTEs have more process around them than finding so maybe has more standing. I think should be more like promises guide or API design guidelines -- something that's more fluid. We could then decide to takesnapshots. I think we should publish like we published the promises guide.

Kenneth: repo?

Dan: I think youshould beaould be able to make a repo on TAG github yourself; if cannot ping Peter.

Peter: OK, Kenneth will make a repo, and people need to start reviewing and giving feedback.

Kenneth: People read at face-to-fcae, but more review is good. Name web components guidelines ok for repo?

Alex: Web Components design guidelines?

Peter: sounds fine

Peter: Everyone can review, come back in 2 weeks