W3C

WoT Marketing

20 April 2021

Attendees

Present
Daniel_Peintner, Ege_Korkan, Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool, Philipp_Blum, Sebastian_Kaebisch, Tomoaki_Mizuhima
Regrets
-
Chair
Sebastian
Scribe
kaz, McCool

Meeting minutes

minutes review

<kaz> Apr-13

for vF2F and minutes from last meeting before F2F

note that regarding "task force", I recall the decision was to always use two words, but it's not recorded in the minutes

Kaz: I will add a note to the minutes to record the decision

McCool: also liaison is misspelled in several places

<kaz> [note added and typos fixed]

McCool: regarding tutorials, we did discuss in plugfest call, and can do that again this week

Sebastian: any objection to publishing the minutes?

<kaz> (none; approved)

Sebastian: hearing no objections, these minutes will be published

Blog post

Sebastian: just one comment on the size of the thumbnail picture

McCool: I'll have to figure out how to do it, wordpress is a little weird
… also looks like the alt tag might be missing
… it was in the HTML but...
… also "alt" might be expanded to "if youtube does not work for you, click here"

Sebastian: 50% looks ok

McCool: will have to update formatting, then will click on post when I'm done

Resolution: when W3C provides a tweet which is relevant to WoT, @W3C_WoT is allowed to re-tweet directly

<Ege> @w3c is the account name to be precise :)

McCool: I'll also update the policy, and we should mention in the main call tomorrow

web page updates

Sebastian: daniel has provided some PRs
… issue 161

<kaz> Issue 161 - Add WoT Liaisons to IG page

Daniel: there were a number of broken links on the liaison page
… and also strange ones, like a link pointing to a french wikipedia site
… also logos would be nicers, but formatting is tricky
… for now do without logos

Kaz: let's start with text names, can work on logos later

Daniel: I also listed three issues regarding links, please take a look
… hypercat is broken, etc.
… when you look on the official liaison page

McCool: and if we find broken links on the official page, those should be fixed

Kaz: regarding broken links on the official page, we can send an email to the liaison team

Sebastian: feel that we *should* include logos
… logos will look more professional and easier to read

McCool: just a question of timing; do we do text first, and then add logos, or wait until we have logos?

Sebastian: ok to do it incrementally

Ege: issue with logos not being consistent sizes, etc

McCool: also logos typically come with rules about white space, etc.
… let's get the logos first, then figure out how to design the page to display them
… logo capture will be tracked in issue 164

Daniel: new pr 164, addresses issue to move icons before text, and also fixes "task force" spelling
… fixes issue 153

Daniel: note also some decisions made about text alignment

Ege: note binding templates are a tf in the charter
… not necessarily useful any more
… and it does not have its own meeting
… instead it is part of the TD call
… if someone goes looking for the binding template call they won't find it

Sebastian: the description of the TD TF does say that binding templates are handled by the TD TF

Kaz: note there is no official list of TFs managed by the W3C as a whole
… it is up to each group to manage TFs

Sebastian: ege, maybe you can do some research to see if we have to fix anything

Ege: ok, but for now the web page looks ok

Sebastian: back to this PR, I think it looks good
… shall we merge it?

Sebastian: hearing no objections, will merge

<sebastian> https://github.com/w3c/wot-marketing/pull/160

Sebastian: merged

Sebastian: another pr 161, still in progress

conferences

Ege: issue 163, API Specification Conference

<sebastian> https://github.com/w3c/wot-marketing/pull/154

Sebastian: this PR just provides sources for the images used in the web page
… as a PPTX
… note it is under docs/material/wot-figures.pptx

<kaz> Issue 163 - API Specification Conference 2021

Ege: API Specification Conference

Ege: would like to discuss what kind of content we want
… we can't do exactly the same as last year as it will get rejected
… so maybe this year we can focus on a different aspect
… we could also focus on new things, but need to know previous work
… then there is scripting, maybe look at specific examples

McCool: I personally would like to see a deep dive into a specific use case and use in products

Sebastian: will have some mention in June

<citrullin> +1 on what Seb said

McCool: and I think we should avoid emphasizing "maker" scene, etc.
… rather should look at commercial applications

Ege: participants are commercial vendors

Sebastian: have to close, let's follow up on this next week

<kaz> [adjourned]

Summary of resolutions

  1. when W3C provides a tweet which is relevant to WoT, @W3C_WoT is allowed to re-tweet directly
Minutes manually created (not a transcript), formatted by scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).