11:30:27 RRSAgent has joined #wot-marketing 11:30:27 logging to https://www.w3.org/2022/07/19-wot-marketing-irc 11:30:31 meeting: WoT Marketing 11:30:40 Mizushima has joined #wot-marketing 11:30:51 present+ Kaz_Ashimura, Cristiano_Aguzzi, Ege_Korkan, Michael_McCool 11:31:42 present+ Tomoaki_Mizushima 11:32:10 dape has joined #wot-marketing 11:32:21 Ege has joined #wot-marketing 11:32:38 present+ Daniel_Peintner 11:32:43 chair: Ege 11:33:25 McCool has joined #wot-marketing 11:33:25 agenda: https://www.w3.org/WoT/IG/wiki/Marketing_WebConf#July_19.2C_2022 11:33:47 scribenick: McCool 11:33:48 topic: minutes 11:33:56 ege: review minutes of 07/12 11:34:11 i|rev|-> https://www.w3.org/2022/07/12-wot-marketing-minutes.html July-12| 11:34:56 ... CG questionnaire, issues, CG vs IG labels 11:35:13 ... last issue was about Standict, which we decided to defer for now 11:35:28 q? 11:35:45 ege: any changes? none, so let's make this official 11:35:54 topic: updates 11:36:04 subtopic: CG Questionnaire 11:36:13 ege: are getting some answers to the form 11:36:47 ... about 14 responses, but list is old 11:36:54 ... almost starting from scratch 11:37:03 ... but we decided to organize a meeting 11:37:26 ... created an event with the calendar system; note the correct date is the 25th 11:37:30 q+ 11:37:46 ... has been scheduled to avoid the testfest 11:38:09 kaz: want to use the marketing call as a kind of steering cmte for the CG? 11:38:20 ege: no, more of a collaboration, just some updates 11:38:50 kaz: putting those items on this call is a bit strange 11:39:11 q+ 11:39:19 kaz: this TF call is a prep call for CG 11:39:51 q+ 11:39:54 ege: don't want to trigger a dicussion on these issues, but to report on collaboration 11:40:01 kaz: should clarify the relationship 11:40:55 ege: to decide on what kind of collaboration we should make makke 11:41:09 q? 11:41:09 q 11:41:11 ack k 11:41:19 mm: as long as we don't make cg-only decisions in this call I am ok with it 11:41:22 ack m 11:41:32 ack c 11:41:35 ... we do need to spend time sorting out what is in IG and what is in CG 11:41:39 ... and we do need updates 11:42:02 cris: agree we need updates, but need to filter first 11:42:23 mm: agree regular updates are a good thing 11:42:46 rrsagent, make log public 11:42:51 rrsagent, draft minutes 11:42:51 I have made the request to generate https://www.w3.org/2022/07/19-wot-marketing-minutes.html kaz 11:43:04 q+ 11:43:20 ege: do we need a resolution on doing CG updates here? 11:43:33 mm: I don't think it really needs a resolution 11:43:48 kaz: agree, but once CG calls are started need to move CG discussions there 11:44:02 ... may need a couple more weeks of preparation 11:44:55 mm: we should work on a "launch" for the CG and when the meetings should be started 11:45:04 ... mid-August may not be ideal 11:45:30 kaz: CG already exists; but if want to wait until TPAC should make an announcement about that 11:46:07 mm: also need to think about frequency 11:46:30 kaz: suggest separating CG and IG topics in github right away, then move CG topics to a new repo 11:46:49 ege: to be clear intention is not to make this a joint CG/IG call 11:47:13 kaz: understood, but we do need to decide how to involve CG members 11:47:38 ... right now they are just waiting, which is not fair 11:47:54 ... already planning to have a charter feedback session, right? 11:47:59 ege: yes, that is planned 11:48:35 kaz: ok to use this mtg for prep, however 11:48:59 kaz: would like to record that Marketing TF would like to support preparation of CG during 11:49:04 mm: I agree 11:49:16 I agree 11:49:17 +1 kaz 11:49:17 s/CG during/CG during this call/ 11:49:20 +1 11:49:23 ege: also agree 11:49:39 topic: PRs 11:50:02 subtopic: PR 333 11:50:23 ege: had issue template that was specific to web site, but not used, so this PR deletes the template 11:50:34 i|had issue|-> https://github.com/w3c/wot-marketing/pull/333 PR 333 - Remove issue template| 11:50:38 ege: any objections? none... 11:50:41 ege: (merges) 11:50:54 subtopic: issue 126 11:51:13 ege: about old explainers, reorganize, convert to HTML 11:51:22 ... not currently linked under documentation, however 11:51:39 ... so PR #331 is a preliminary update 11:51:46 q] 11:51:53 q+ 11:52:03 ack k 11:52:03 mm: so we would eventually put this under "historical documents"? 11:52:05 ege: yes 11:52:37 daniel: still some todos, should move to new issues 11:52:42 s/q]/ 11:52:56 q+ 11:53:17 ack d 11:53:43 mm: do we really need to convert things? Can't we just link to them? 11:53:57 daniel: was not aware we should not remove explainers 11:54:14 i|about old ex|-> https://github.com/w3c/wot-marketing/issues/126 Issue 126 - We should link to the existing explainer about WoT| 11:54:20 ... did convert to HTML so it looked like part of the website 11:54:40 i|about old ex|-> https://github.com/w3c/wot-marketing/pull/331 PR 331 - Move Explainer to Marketing repo| 11:54:51 ege: possible to make it fit if use jekyll 11:55:45 q? 11:55:56 mm: other possibility is to move them all to marketing and convert to HTML 11:56:08 ... just think we should avoid having duplicates 11:56:20 kaz: should be careful about definition of term "explainer" 11:56:45 ... from process point of view has a specific meaning, and purpose for wide review 11:57:18 ... original explainer for TAG review may be different from ideal summarization document for public 11:58:14 mm: so we should consider making a "summarization" document *derived* from the explainer 11:58:41 kaz: agree, and better to have that document in HTML 11:59:05 ege: ok, put notes under PR 331 11:59:19 https://hackmd.io/@egekorkan/json-schema-wot 11:59:26 [adjourned] 11:59:32 rrsagent, make log public 11:59:36 rrsagent, draft minutes 11:59:36 I have made the request to generate https://www.w3.org/2022/07/19-wot-marketing-minutes.html kaz 12:09:30 dape has left #wot-marketing 14:04:22 Zakim has left #wot-marketing