– DRAFT –
WoT Marketing

Minutes

Dec-14

approved

CG voting

Issue 236 - Have Regular CG Meetings - OpenDay

McCool: need to see who is nominated

Ege: Cristiano has also volunteered

Kaz: note that the CG and the WG are different groups
… so we need to send the Call for Nomination message to the CG
… I asked Cristiano to join the CG too

McCool: let's talk about the procedure during the Chairs call and the main call tomorrow

Update on article for embedded.com by Philipp Blum

pending

WebThing CG

Issue 224 - Add Web Thing Protocol community group

Ege: should we ask Ben to provide some text?

McCool: we need to look into the CG's resources
… appropriate to be added, though
… btw, are the links within the page on the WoT-related CGS working properly?
… regarding the concrete text for the WebThing CG, asking Ben would make sense

CG page in general

Kaz: having the detail information like CG Scope, Mailing List, Participants and Join might be redundant given the W3C CG page above
… all the information on that page is automatically generated using the W3C API

McCool: tend to agree

Kaz: maybe we can simply have a link to the CG home pages

Ege: would create an issue about that before asking Ben to provide a text on the WebThing CG
… need to update the template for the wot-marketing page

Issue 237 - Updating the CG templates

Ege: will revisit this issue after updating the template

Issue 231

Issue 231 - Add Description to Top of Each TF Wiki Page

McCool: Security and Discovery are done
… will discuss this during the Chairs call tomorrow

Ege: then let's revisit this issue next week

Issue 234

Issue 234 - Redesigning the Contact Page

McCool: would mention our ML as part of the contact methods

Kaz: note that our specs mention within the Status section that our basic contact channel is the WoT public mailing list
… then spec work is done on the GitHub and comments on the GitHub Issues are welcome
… we should consistent with that policy
… and then if we really would like to use additional communication channels like Stack Overflow, Slack, etc., we should check with the Comm Team about the usage beforehand

McCool: tend to agree given the possibility of getting many messages

Kaz: have you confirmed the usage of StackOverflow?

Ege: thought we had got confirmation at some point
… will check it offline to make sure

Issue 156

Issue 156 - Newsletter for WoT

McCool: only the Chairs can submit a blog post

<dape> https://www.w3.org/blog/group/ig-wot/

Kaz: sorry but I have difficulty with what you really want to do...
… could you elaborate what you want a bit more?
… integration of mailing list and the blog?

Ege: let me list the requirements

consolidated expectations

[adjourned]