– DRAFT –
WoT Marketing

Minutes Review

<kaz> July-5

Ege: we can approve the minutes

CG Questionnaire

Ege: we have sent to the CG mailing list, we have tweeted about it as well

Ege: the link is https://forms.gle/ism8Vt3djqp7Q6eY6

Issues

Kaz: we should talk about which issues should be done by IG and which by CG

Ege: CG is in charter review process

Ege: My opinion is that website and plugfest activities have to stay in IG since the discussion is not over

Kaz: before discussing issues themselves, we should clarify which ones to be handled by this WoT IG's Marketing TF and which ones by the WoT CG

Philipp: I see only one conflict with IG and CG here. "Develop supporting materials such as implementation guidelines and tutorials"
... IG Charter says that tutorials and reading guides are IG activity

<citrullin> https://www.w3.org/2021/12/wot-ig-2021.html

<kaz> new Issue 330 - Identifying CG or IG topic areas

Ege: should we solve issue 330 now
… or kaz: scribenick: kaz, so I think it's easier than expected to clarify which are for IG/WG and which are for CG label issues

Kaz: we should start from issue labelling

Issue 329

<kaz> Issue 329 - JSON Schema Case Study

Ege: issue 329 is IG

Issue 294

<kaz> [CG Collab] Working Style: How does the CG work and how does CG keep in sync with IG?

Ege: adding both CG and IG labels

Issue 326

<kaz> Issue 326 - Unified Readme across WoT repositories

Ege: it feels like a IG activity

Issue 321

<kaz> Issue 321 - Let CG handle (some pages on) website

Philipp: regarding 321 I would like to challenge the assumption, I think the two websites should be separated

<kaz> s/separed/separated/

Ege: the CG can have they own website, but we should not have two brand images

Philipp: I see
… I see the CG more as an outsider
… especially now that the W3C is becoming a no profit org

Kaz: I would like to do a first quick categorization and then move to detailed discussion

Ege: ok

Philipp: ok

Issue 307

<kaz> Issue 307 - Showing Testing Results on the Web page

Ege: Issue 307 IG

Issue 305

<kaz> Issue 305 - API Specifications Conference 2022

Ege: closing, the conference schedule is fixed

Issue 291

<kaz> Issue 291 - How to show non-specification publications

Ege: it is about web pages, IG

Issue 290

<kaz> Issue 290 - Success Story for Standict

Ege: press release IG

<kaz> Issue 285 - Update links to recently published documents

Issue 285

Ege: IG

Issue 281

<kaz> Issue 281 - Netlify Preview URLs

Ege: IG for now

Issue 271

<kaz> Issue 271 - Create a Reading Guide

Ege: it goes under IG topics
… but CG could do that as well

... we can move this issue to the CG

Kaz: yeah, CGs can work on that kind of tasks, but should bring the takeaways back to the IG so that the IG can generate an official group Note, etc.

Kaz: btw, sometimes discussions can happen in different places, i.e., on GitHub issue and on the IRC minutes, but we should record the points on the minutes as well as the GitHub issue directly for record.

Philipp: maybe it is better to mention somewhere that the CG will provide reports to the WG

Ege: yeah, we are saying that on the CG charter

Philipp: ok!

Issue 268

<kaz> Issue 268 - Using W3C Calendar

Ege: again about web page, then IG

Issue 258

<kaz> Issue 258 - Documentation misses proper explanation of Discovery

Ege: website explainers, IG

Issue 235

<kaz> Issue 235 - Feedback for embedded.com article

Ege: any updates on that?

Philipp: not yet
… but it is a CG topic

Issue 232

<kaz> Issue 232 - FAQ for WoT documents

Ege: probably it could be done by both groups

Issue 190

<kaz> Issue 190 - WoT logo on repository READMEs

Ege: involves all the WG repositories IG

Issue 156

<kaz> Issue 156 - Newsletter for WoT

Ege: both, but probably more CG

<citrullin> +1 on cris point

Cristiano: It depends from the content
… it could be managed by both

Kaz: the point here is hat we need to clarify the levels of information, W3C as a whole?, WG?, IG? or CG.

Issue 146

<kaz> Issue 146 - Platforms Communication with Newcomers to WoT

Ege: clearly CG

Issue 127

<kaz> Issue 127 - How to generate Twitter Feed in a GDPR compliant way?

Ege: IG

Issue 126

<kaz> Issue 126 - We should link to the existing explainer about WoT

Ege: about website, IG
… daniel can I assign you to this issue

Daniel: give me some time to read them
… I can try

Issue 79

<kaz> Issue 79 - Tutorials should be easy to find

Ege: mostly CG
… but given the fact that IG can do tutorials also a little bit of IG

Issue 64

<kaz> Issue 64 - Use a consistent template for PPT materials

Ege: IG work

Issue 24

<kaz> Issue 24 - Add Developer Journey

Ege: CG

Cristiano: +1

Issue 18

<kaz> Issue 18 - History of the standardization is unknown

Ege: IG

Issue 290

<kaz> Issue 290 - Success Story for Standict

Ege: delicate issue
… no news from W3C
… but got updates from Marie-Claire

Kaz: did you ask updates to Marie Claire?

Ege: yes

Kaz: in my understaing we are waiting for Coralie answer
… if we are not really sure we can't work on this
… we don't need to force the hand on this
… it is an additional topic
… I would label this issue as pending

AOB?

Ege: aob?

(none)

[adjourned]