W3C

– DRAFT –
WoT Marketing

18 January 2022

Attendees

Present
Daniel_Peintner, Ege_Korkan, Kaz_Ashimura, Tomoaki_Mizushima
Regrets
-
Chair
Ege
Scribe
Ege, kaz

Meeting minutes

Minutes

Jan-11

WoT CG

Ege: cg discussions will be done in main call

Kaz: note that the CG is a different group from the WoT-IG/WG, so the decision on Chair appointment and CG meetings should be made on the CG side.

pull requests

PR 239

<kaz> PR 239 - refactor: replace flaticons with fontawesome

Ege: PR 239 needs to be merged asap. I have reviewed and it looks good

Kaz: just to make sure, all the icons are freely available. right?

Daniel: right

Ege: any objections to merge this PR?

Daniel: there is another related issue somewhere

<kaz> Issue 78 - Icon Set to be used for website

<kaz> (closed)

PR 241

<kaz> PR 241 - refactor: redesign contact page

Daniel: should we put the community group link

Ege: the CGs are not "us" so we should not even link them

Kaz: the logos are publicly available?

Daniel: yes

Kaz: they are fine in the html version but delicate in the screenshot

Daniel: yes but we do not have a good preview mechanism yet

Kaz: should be clear about which mailinglist is for the WoT WG and which is for the WoT IG

PR 243

PR 243 - Adding a template for CG groups

fixes Issue 237 - Updating the CG templates

Ege: the changes are to reformat the document so that a new template can use the correct way of writing it

Ege: actual changes are: removing the alt="", adding div around CGs, adding an s to chair for the wot japanese CG

Ege: I will resolve the conflicts with an editor offline

PR 241 - revisited

Kaz: btw, what about PR 241?
… can we merge it now?

Daniel: have just added minor fixes

Ege: we can merge PR 241

PR 243 - revisited

Ege: PR 243 -> will resolve the merge conflicts in an editor offline however the group has agreed on the change

PR 244

<kaz> PR 244 - add AASX Package Explorer tool

Ege: I also do not like the developers page due to misly organized tools

Kaz: tend to agree
… we should be clear about our policy which tools to be put on the page how

closed issues

Ege: I will quickly these recently closed issues and we can reopen them if needed

<kaz> 28, 45, 4

<kaz> 63

<kaz> 112, 240

<kaz> Issue 28 - WoT can contribute to sustainability (SDGs) by facilitating IoT interoperability

<kaz> Issue 45 - Initial paragraph of the getting started page

<kaz> Issue 4 - Update content of WoT wikipedia

<kaz> Issue 63 - Add link from Web Pages to "PoC" call

<kaz> Issue 112 - WoT Tutorial from TUM for Documentations Page

<kaz> Issue 240 - Adding IIWoT Workshop to the Past Events

Ege: skipping embedded.com article

Issue 62

<kaz> Issue 62 - Add Audio to Node-RED/Node-gen tutorial

<kaz> (closed)

issue 126

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

Ege: what should we do with this explainer text?

Ege: how should we use this text?

Ege: Call of 18.01: We should handle this in steps. 1. Moving the explainer directory to the marketing repository 2. Link the md file on the documentation page 3. Make the md file a jekyll page 4. Rework and update the content so that it becomes a more detailed version of the documentation page which is for now high level

<kaz> [adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).