12:00:04 RRSAgent has joined #wot-marketing 12:00:04 logging to https://www.w3.org/2021/03/09-wot-marketing-irc 12:00:31 Meeting: WoT Marketing 12:00:54 present+ Kaz_Ashimura, Philipp_Blum, Cristiano_Aguzzi 12:01:13 ktoumura has joined #wot-marketing 12:01:19 present+ Xiaoqian_Wu, Kunihiko_Toumura 12:01:25 citrullin has joined #wot-marketing 12:01:56 present+ Coralie_Mercier 12:02:28 xiaoqian has joined #wot-marketing 12:02:36 sebastian has joined #wot-marketing 12:02:45 mlagally has joined #wot-marketing 12:03:08 present+ Jack_Dickinson 12:03:20 present+ Daniel_Peintner 12:03:29 present+ Michael_Lagally 12:03:34 zakim, who is on the call? 12:03:34 Present: Kaz_Ashimura, Philipp_Blum, Cristiano_Aguzzi, Xiaoqian_Wu, Kunihiko_Toumura, Coralie_Mercier, Jack_Dickinson, Daniel_Peintner, Michael_Lagally 12:03:46 present+ 12:03:53 present+ Sebastian_Kaebisch 12:04:17 scribenick: kaz 12:04:28 present+ Junde_Yhi 12:05:04 kaz: I don't think I have the permission 12:05:12 Agenda: https://www.w3.org/WoT/IG/wiki/Marketing_WebConf#Feb_23.2C_2021 12:05:28 topic: Guests 12:06:18 Mizushima has joined #wot-marketing 12:06:41 sk: Junde Yhi, who volunteered to work on the Chinese captions 12:07:59 kaz: thanks 12:08:27 xw: Xiaoqian Wu, W3C Beihan site manager 12:09:03 present+ Tomoaki_Mizushima 12:09:08 zakim, who is on the call? 12:09:08 Present: Kaz_Ashimura, Philipp_Blum, Cristiano_Aguzzi, Xiaoqian_Wu, Kunihiko_Toumura, Coralie_Mercier, Jack_Dickinson, Daniel_Peintner, Michael_Lagally, xiaoqian, 12:09:11 ... Sebastian_Kaebisch, Junde_Yhi, Tomoaki_Mizushima 12:09:47 topic: prev minutes 12:10:12 -> https://www.w3.org/2021/03/02-wot-marketing-minutes.html Mar-2 12:10:19 sk: (goes through the minutes) 12:10:33 ... new WoT welcome page and the explainer video published 12:10:39 ... working on blob post 12:10:54 ... PR 134 on TFs 12:11:07 ... we'll look into the detail today 12:11:12 ... any objections? 12:12:21 McCool has joined #wot-marketing 12:12:21 (none) 12:12:23 approved 12:12:29 present+ Michael_McCool 12:12:46 topic: Basic marketing policies for publication 12:13:05 sk: our policy to publish information publicly like the WoT Welcome page 12:13:22 ... several options 12:13:38 ... Marketing TF to entitled to make updates 12:13:54 ... or getting back to the main call 12:14:17 ... is clear Resolution needed every time? 12:14:29 ... we need a good guideline here 12:14:42 q? 12:14:42 q+ 12:14:59 ack m 12:15:12 ml: outbound messaging is always sensitive 12:15:35 ... Marketing TF is a subgroup of the WoT IG 12:16:10 ... so it would be dangerous in case the intention of the whole group were not reflected 12:16:28 ... we've been careful to handle our meeting minutes as well 12:16:29 dape has joined #wot-marketing 12:16:43 ... thorough review before publishing them 12:16:44 q+ 12:16:45 sk: ok 12:16:45 q+ 12:16:53 ... how should we improve the procedure then? 12:17:24 ... for example, we've been mentioning the Marketing TF's plan during the main calls 12:17:36 ... should we record our decision using "RESOLUTION" as well? 12:18:04 ml: for significant things, we should do so 12:18:17 ... there could be some "border" cases, though 12:18:56 ... specifically, if we make a completely new change, we need to record it clearly 12:19:21 q? 12:19:52 sk: maybe there was some confusion 12:20:15 mm: would agree we should have made a resolution for the big release like the one we made the other day 12:20:37 ... but would also suggest we ask people to review the content within some specific review period, e.g., 2 weeks 12:20:38 q+ 12:20:38 q+ 12:20:44 acm mc 12:20:57 s/2 weeks/1 week/ 12:20:58 ack Mc 12:21:03 ack ci 12:21:16 pb: also mentioned that W3C is a bit slow about marketing 12:21:33 ... can be problematic to output standards 12:21:43 ... so would like to agree with McCool 12:21:52 ... one week review period would be OK 12:21:57 q? 12:22:00 ack d 12:22:05 dp: agree 12:22:17 ... 1 week might be too long but OK 12:22:46 q? 12:22:52 q+ 12:23:19 dp: note that if there is any problem, we should/can improve it 12:23:25 ... don't have to be perfect 12:23:34 q? 12:23:36 ml: tx for your hard work first 12:23:36 q+ 12:23:37 cris has joined #wot-marketing 12:23:39 ack ml 12:24:01 s/output standards/output marketing for the standard/ 12:24:21 s/standard/standards/ 12:24:36 ... one week review period proposed by McCool is fine 12:24:53 q? 12:25:44 ack kaz 12:26:28 ack McCool 12:26:47 kaz: we're getting a conclusion while I've been waiting :) 12:27:15 mm: another question is how to handle the PR and branch to merge 12:27:20 ... also how to run the review 12:27:23 s/one week review period would be OK/one week review period would be OK, even though it isn't ideal to move forward fast./ 12:27:47 sk: it's a generic question 12:28:20 mm: what is the current process? 12:28:43 sp: the PR is merged to the "master" branch and it will be applied directly 12:28:58 q+ 12:29:19 mm: not merge PR until the review is done 12:29:33 q+ 12:29:54 mm: we can decide which is major and which is minor 12:30:06 ... we should be conservative to manage the repo 12:30:16 ... nice to have a preview, though 12:30:42 dp: can look into it 12:30:54 ack c 12:31:02 ca: this is a right way 12:31:17 ... but we have great features to review the PR 12:31:27 ... every PR should be open until the review is done 12:33:05 kaz: to see previews, we might want to have several sub repos 12:33:30 ... and copy the contents from those sub repos to the main wot-marketing repo after the content was approved 12:34:01 mm: Marketing TF can categorize the PRs into major and minor 12:34:16 ... and major ones need detailed review 12:34:17 q? 12:34:23 q+? 12:34:25 ack k 12:34:27 ml: +1 12:34:37 ack kaz 12:34:39 ack ? 12:35:00 q+ 12:35:06 sk: we'll use two labels, "major" and "minor" 12:35:34 ... major requires one week review and resolution at the main call 12:35:51 ... minor requires one-day review 12:35:53 q? 12:35:56 ack c 12:36:54 ca: possibly up to 2 weeks? 12:37:00 mm: yeah 12:37:16 ... possible one week delay 12:37:52 ml: editorial fixes like typo can be handled quickly 12:38:08 mm: so we should use three levels, editorial, minor and major 12:38:27 ... editorial means typos, etc. 12:38:29 +1 12:38:57 q+ 12:39:00 mm: another question is twitter, etc. 12:39:19 ... would propose 3-day review 12:39:23 q? 12:39:27 ack c 12:39:45 pb: if we need to get approval, the good timing would be gone 12:40:07 ... should have some restriction, though 12:40:11 +1 12:40:19 mm: yeah, one week should be too long for that 12:40:39 ... one day review for twitter 12:40:49 ... one week review for Web pages 12:41:25 sk: (add those proposed three labels on the agenda wiki) 12:41:50 mm: "editorial changes" to be used bug fixes 12:42:02 sk: is that ok? 12:42:25 ml: should call it "bug fix" 12:43:33 mm: and twitter news for one day announcement in the mailinglist 12:43:37 ml: which list? 12:45:12 kaz: Marketing work belongs to the IG, so should go to the IG list, but can be CCed the WG list 12:45:19 s/CCed/CCed to/ 12:45:29 mm: ok 12:46:19 sk: (record it on the agenda) 12:46:31 [[ 12:46:32 major changes: PRs (e.g., new page content or new web pages, Blog Post) needs 1 week preview time of the WoT group (will be announced in the main call) 12:46:32 minor changes: PRs (e.g., small extension) will be also announced latest one day before the main call 12:46:32 bug fixes: PRs (e.g., typos, links update) can be merged directly 12:46:32 twitter news: one day announcement in the mailing list (wot-ig & wot-wg) 12:46:34 we will introduce three labels minor / major / editorial 12:46:36 ]] 12:46:54 resolution: we'll use the above as our policy from now on 12:47:05 s/should have some restriction, though/I think Twitter retweets etc. should be handled by some people trusted by the group. They should have some restrictions on that, of course./ 12:47:46 topic: PR 134 12:48:18 -> https://github.com/w3c/wot-marketing/pull/134 PR 134 - Webpage: Adding TF info to WG and IG overview pages 12:48:32 ml: the table is not really great, though :) 12:48:46 sk: can be improved later 12:48:56 mm: is this a major change? or minor 12:49:00 sk: should be minor 12:49:15 mm: ok 12:49:24 +1 for minor 12:49:25 ... we should fix the table style before merging 12:49:37 mm: can we fix it before the main call tomorrow? 12:49:44 ml: will try 12:50:14 +1 for labels 12:50:28 dp: wondering whether to use, "Task Force" or "Taskforce" 12:50:47 mm: we use "TF" as the acronym, so should use "Task Force" 12:50:56 ... let's put a label 12:51:29 q? 12:51:30 q+ 12:52:29 q- 12:53:15 topic: Multiple language support of the video + alternative publication platform 12:53:19 sk: two topics here 12:53:53 -> https://github.com/w3c/wot-marketing/issues/141 issue 141 - Multiple language support for the animation video 12:54:21 sk: Junde Yhi has volunteered to work on the Chinese captions 12:54:33 Junde: very interested in this 12:54:35 sk: tx! 12:54:40 mm: fantastic 12:55:05 q+ 12:55:23 ... should we look for another caption for traditional Chinese? 12:55:50 ... also Junde, can you work with the GitHub repo? 12:55:55 Junde: think so 12:56:12 kaz: if needed, you can send it by email to me and I can install it for you 12:56:14 q? 12:56:36 q+ 12:57:25 sk: we have Italian captions as well 12:58:30 xiaoqian: happy to have Chinese captions as well 12:58:51 ... regarding the traditional captions, we have contacts in Taiwan 12:59:25 https://www.w3.org/2021/02/wot-explainer-video.html 13:00:04 I will drop off for the use cases call 13:00:25 kaz: regarding the video server, we've already installed the explainer video on the W3C side as above 13:00:30 [I need to go to my next meeting too :/] 13:00:38 q+ 13:00:44 [Coralie departs] 13:01:14 xiaoqian: these days bilibili is more popular for younger people in China 13:02:08 sk: unfortunately, we need to continue the discussion next week... 13:09:29 ... please join the next call 13:09:38 xiaoqian: ok 13:09:40 [adjourned] 13:09:46 rrsagent, make log public 13:09:52 rrsagent, draft minutes 13:09:52 I have made the request to generate https://www.w3.org/2021/03/09-wot-marketing-minutes.html kaz 14:04:47 zkis has joined #wot-marketing 15:30:32 Zakim has left #wot-marketing