11:07:24 <RRSAgent> RRSAgent has joined #wot-marketing
11:07:24 <RRSAgent> logging to https://www.w3.org/2021/04/13-wot-marketing-irc
11:07:53 <Citrullin> present?
11:08:06 <kaz> present+ Kaz_Ashimura, Daneil_Peintner, Kunihiko_Toumura, Michael_McCool, Philipp_Blum, Tomoaki_Mizushima
11:09:14 <Citrullin> topic: Minutes
11:09:30 <kaz> https://www.w3.org/2021/03/09-wot-marketing-minutes.html
11:11:05 <kaz> https://www.w3.org/2021/03/15-25-wot-minutes.html
11:13:03 <Citrullin> sk: We showed the new website and the subtitles for the video. Some discussion about Twitter publication.
11:13:25 <Citrullin> Resolution about the Twitter discussion -> https://github.com/w3c/wot-marketing/issues/151
11:13:33 <Citrullin> sk: Any concerns about it?
11:14:17 <Citrullin> mm: I have a blog post. I cannot publish it, since there isn't a main call. We should have an exception for these kind of cases.
11:14:28 <Citrullin> sk: I think that is a rare exception.
11:14:29 <kaz> present+ Sebastian_Kaebisch
11:14:33 <kaz> Chair: Sebastian
11:14:38 <Citrullin> mm: We should have an exception handling for it.
11:14:48 <Citrullin> sk: Let's discuss this in the main call.
11:14:50 <dape> q+
11:14:51 <kaz> i/Minutes/scribenick: Citrullin/
11:14:55 <kaz> rrsagent, make log public
11:14:59 <kaz> rrsagent, draft minutes
11:14:59 <RRSAgent> I have made the request to generate https://www.w3.org/2021/04/13-wot-marketing-minutes.html kaz
11:15:10 <dape> q-
11:15:13 <Citrullin> sk: Any concerns?
11:15:24 <kaz> s/https/-> https/
11:15:25 <kaz> s/https/-> https/
11:15:30 <Citrullin> sk: I don't hear any concerns, so the minutes are getting published.
11:15:46 <Citrullin> topic: wot-marketing minutes
11:15:56 <kaz> s/09-wot-marketing-minutes.html/09-wot-marketing-minutes.html March-09/
11:16:00 <Citrullin> s/topic: Minutes/topic: F2F Minutes/
11:16:24 <kaz> s/15-25-wot-minutes.html/15-25-wot-minutes.html vF2F Day 6/
11:16:34 <kaz> rrsagent, draft minutes
11:16:34 <RRSAgent> I have made the request to generate https://www.w3.org/2021/04/13-wot-marketing-minutes.html kaz
11:16:53 <Citrullin> sk: We had some discussions about the new policy. We discussed this also in the main call.
11:17:59 <kaz> q+
11:18:21 <Citrullin> mm: The chinese captions have been reviewed.
11:19:20 <kaz> ack k
11:19:41 <Citrullin> sk: Any concerns about the marketing minutes?
11:19:53 <Citrullin> sk: I don't hear any concerns, so they get published.
11:20:06 <Citrullin> topic: Blog post
11:20:12 <dape> q+
11:20:25 <kaz> rrsagent, draft minutes
11:20:25 <RRSAgent> I have made the request to generate https://www.w3.org/2021/04/13-wot-marketing-minutes.html kaz
11:20:39 <Citrullin> mm: I held of publishing it, because it kind of a launch blog post.
11:20:52 <Citrullin> ... there are also some images, I don't know where to put them.
11:21:23 <Citrullin> ... I reorganized the structure as well.
11:21:24 <kaz> -> https://github.com/w3c/wot-marketing/pull/159 PR 159 - Add screenshot of web site
11:21:45 <kaz> Agenda: https://www.w3.org/WoT/IG/wiki/Marketing_WebConf#Apr_13.2C_2021
11:22:41 <Citrullin> q+
11:23:36 <Citrullin> mm: There is some discussion about the wording "locked into frameworks". Maybe we should rename it to proprietary.
11:24:08 <kaz> -> https://github.com/w3c/wot-marketing/pull/158 PR 158 - Blog prep - animation announcement
11:24:16 <kaz> q?
11:24:50 <Citrullin> dp: For me it would be okay to say locked into framework. I am fine with the text.
11:25:08 <Citrullin> ... there is no need to merge the blog, because there is a blog area on the website.
11:25:11 <dape> ack dape
11:25:26 <Citrullin> s/merge the blog/merge the blog post/
11:30:57 <Citrullin> pb: You might use nodeJS or something and still be locked into that framework. So, from a technical perspective you are still locked into a framework. So, I would rather call it locked into a platform.
11:31:02 <Citrullin> mm: propritary is meaning vendor specific. I would use the wording narrow vertical framework.
11:31:11 <Citrullin> pb: Without the context of the W3C, I wouldn't know what narrow vertical framework means. So, I would rather use something else.
11:31:17 <Citrullin> mm: I am fine with vendor specific framework.
11:31:24 <Citrullin> sk: Maybe we should remove this part of the blog post.
11:31:30 <Citrullin> mm: I think it is a very important topic, so we should mention it.
11:32:04 <Citrullin> sk: So, your recommendation is to call it not locked into narrowed vertical frameworks.
11:33:26 <Citrullin> pb: Just a second. Kaz and me prefer the wording "vendor-specific".
11:33:42 <Citrullin> mm: I am fine with vendor-specific. So, what do the others think?
11:33:48 <Citrullin> dp: I think it also sounds better.
11:34:08 <Citrullin> sk: I don't have any passion about this.
11:34:34 <Citrullin> mm: The opening text on the webpage uses the same text. We should change it there as well.
11:34:48 <Citrullin> sk: Which one do we use?
11:34:51 <kaz> present+ Ege_Korkan
11:35:00 <Citrullin> mm: We can use vendor specific and propose that in the main call.
11:35:36 <Citrullin> sk: Let's make a final decision in the main call then.
11:35:42 <sebastian> q?
11:35:50 <Citrullin> q-
11:36:13 <Ege> Ege has joined #wot-marketing
11:36:23 <Citrullin> topic: Multiple language support for the animation video
11:36:41 <Citrullin> sk: There is the need for a japanese translation. Kaz, you take care of it?
11:36:47 <Citrullin> ka: Yes
11:37:23 <Citrullin> sk: We can ask Viktor for the french translation.
11:37:37 <kaz> s/Viktor/Victor/
11:37:57 <Citrullin> Translation issue -> https://github.com/w3c/wot-marketing/pull/152
11:38:27 <Citrullin> s/https://github.com/w3c/wot-marketing/pull/152/https://github.com/w3c/wot-marketing/issues/141
11:38:53 <Citrullin> Translation github issue -> https://github.com/w3c/wot-marketing/issues/141
11:39:15 <kaz> s/for the/to review the/
11:39:30 <kaz> s/Translation issue/French translation/
11:39:32 <Citrullin> mm: We need a german reviewer. And also one reviewer for Japanese.
11:39:41 <Citrullin> dp: I can do it for german.
11:40:11 <kaz> rrsagent, draft minutes
11:40:11 <RRSAgent> I have made the request to generate https://www.w3.org/2021/04/13-wot-marketing-minutes.html kaz
11:41:08 <Citrullin> kz: tm and kt can take a look review it.
11:41:29 <Citrullin> tm and kt: Yes, can do.
11:41:40 <Mizushima> @chachamimm
11:41:53 <Citrullin> sk adds the username as reviewer to the github issue.
11:42:19 <Ege> q+
11:42:25 <kaz> s/@chachamimm//
11:43:08 <Citrullin> sk: You had some issue with the naming of task force?
11:43:31 <kaz> Meeting: WoT Marketing
11:43:32 <Citrullin> s/sk: You had some issue with the naming of task force?/ /
11:43:44 <Citrullin> topic: Renaming task force
11:43:47 <Citrullin> sk: You had some issue with the naming of task force?
11:44:02 <Citrullin> dp: Yes, sometimes we write it together, sometimes in two words.
11:44:22 <Citrullin> sk: Just make a PR with a proposal.
11:44:29 <Citrullin> dp: I will do it.
11:44:57 <Citrullin> topic: Liason partners on the website
11:45:08 <Citrullin> sk: I think we should list our liason partners on the website.
11:45:29 <kaz> q?
11:45:31 <kaz> q+
11:45:43 <Citrullin> ... question is how we want to do it? We can add the logos of the partners.
11:46:11 <Citrullin> ... I am open for suggestions. Should we do it or rather not do it?
11:46:17 <McCool> q+
11:46:47 <kaz> ack k
11:46:52 <Citrullin> ka: It should be listed under the Interest group page.
11:46:53 <kaz> ack m
11:47:14 <Citrullin> mm: We should go to the official liason page and list it under there.
11:47:43 <kaz> https://www.w3.org/2001/11/StdLiaison official liaison table
11:48:00 <kaz> s/official/official W3C/
11:48:09 <Citrullin> mm: The icons are also below the task forces. We should fix that.
11:48:13 <Citrullin> dp: I will do that as well.
11:49:12 <Citrullin> mm: We can also just put a link to this list.
11:49:33 <Citrullin> dp: I just wanted to say the same. We can just link with the right filter.
11:49:59 <Citrullin> mm: We should double check, if the list is still correct.
11:50:14 <Citrullin> sk is checking the list.
11:50:37 <Citrullin> mm: There are some liasons missing. We should add them.
11:51:57 <Citrullin> ka: We can list our liasons and link to this list. Problem with this list is that there is a longer process behind it changing the page.
11:52:26 <Citrullin> s/can list our liason/put the liasons on our website/
11:52:27 <kaz> s/our liaisons/liaisons on the WoT welcome page,/
11:52:37 <kaz> s/this list/this official liaison table/
11:52:44 <Citrullin> sorry... ^^
11:52:58 <kaz> rrsagent, draft minutes
11:52:58 <RRSAgent> I have made the request to generate https://www.w3.org/2021/04/13-wot-marketing-minutes.html kaz
11:53:49 <Citrullin> dp: Do we want to have the logos on our website or do we want to link to it?
11:54:08 <Citrullin> mm: Mentioning it besides the list is good. Getting logos can be a bit more complicated.
11:54:17 <kaz> s/Problem with this list/Problem with the official liaison table/
11:54:40 <kaz> s/sorry... ^^//
11:54:47 <kaz> rrsagent, draft minutes
11:54:47 <RRSAgent> I have made the request to generate https://www.w3.org/2021/04/13-wot-marketing-minutes.html kaz
11:56:50 <kaz> q?
11:57:50 <McCool> q+
11:57:56 <kaz> ack e
11:59:32 <Citrullin> topic: TUM lectures
11:59:39 <Citrullin> ek: I created the TUM lecture slide set. They don't contain any TUM related information.
11:59:46 <Citrullin> sk: Is this material we can put on the website?
11:59:53 <Citrullin> ek: I tried to convert it to proper pdf.
12:01:37 <kaz> mm: let's continue the discussion during the PlugFest call tomorrow
12:01:42 <kaz> [adjourned]
12:01:46 <kaz> rrsagent, draft minutes
12:01:46 <RRSAgent> I have made the request to generate https://www.w3.org/2021/04/13-wot-marketing-minutes.html kaz
12:58:20 <Mizushima> Mizushima has left #wot-marketing
14:01:53 <Zakim> Zakim has left #wot-marketing