11:55:53 RRSAgent has joined #wot-marketing 11:55:53 logging to https://www.w3.org/2022/11/08-wot-marketing-irc 11:56:50 meeting: WoT Marketing 11:56:58 present+ Kaz_Ashimura 11:58:33 Ege has joined #wot-marketing 12:00:41 present+ Ege_Korkan 12:04:02 present+ Daniel_Peintner 12:04:08 dape has joined #wot-marketing 12:05:48 scribenick: Ege 12:06:08 topic: Minutes 12:06:12 -> https://www.w3.org/2022/10/18-wot-marketing-minutes.html Oct-18 12:07:30 ek: minutes are approved 12:07:45 topic: agenda cleanup 12:08:04 q+ 12:08:35 agenda: https://www.w3.org/WoT/IG/wiki/Marketing_WebConf#November_8.2C_2022 12:09:01 ek: I have created subpages, I would like to delete the main page content 12:09:01 s/agenda clea/agenda wiki clea/ 12:09:22 ack k 12:09:28 dp: how does this work? 12:10:09 ek: they are available at https://www.w3.org/WoT/IG/wiki/Marketing_WebConf/2021 and so on 12:10:14 ek: you can create any page there 12:10:21 q+ 12:10:22 dp: how is the table of contents generated? 12:10:36 ek: it is automatic but you can manually disable it 12:11:10 ack k 12:11:42 ek: there are some tutorials at https://www.mediawiki.org/wiki/Manual:Table_of_contents 12:11:49 dp: we should not do it manually then 12:11:58 kaz: you can follow the tutorial as well 12:12:33 cris_ has joined #wot-marketing 12:13:19 ek: I would like to delete them now 12:13:55 ek: (deletes the wiki pages) 12:14:27 topic: New Timeslot? 12:15:10 ek: we have less people lately, should we change the timeslot? 12:15:21 dp: it is a bit problematic but I can manage 12:15:55 q+ 12:16:04 dp: also people might think that we have quite a lot already, so less importance on this 12:16:40 kaz: changing the timeslot is fine but we should clarify the remaining tasks of the TF 12:16:55 kaz: and who is needed for the work 12:18:26 ek: I will create an issue and we can comment here until next week 12:20:11 topic: remaining tasks 12:20:21 ek: (lists the tasks in the github issue) 12:23:19 q+ 12:24:06 kaz: should this TF generate the explainers? 12:24:11 cris_ has joined #wot-marketing 12:24:28 ack k 12:25:39 ek: I will create the issue, as there are no objections to this initial list 12:25:47 s/should this TF generate the explainers?/I'm not sure if the Marketing TF needs to generate explainer documents. Probably each spec TF and the moderator should generate an Explainer document for their spec./ 12:26:01 ek: we should not generate explainers, just integrate them to this page style. So a copy-paste work 12:27:24 topic: JSON Schema Case Study 12:27:43 ek: it is tracked at https://github.com/w3c/wot-marketing/issues/329 12:28:14 ek: it is public now at https://json-schema.org/blog/posts/w3c-wot-case-study 12:28:46 ek: I have tweeted it from our account too: https://twitter.com/W3C_WoT/status/1587461362434842624 12:30:34 dp: It would be nice to get some statistics about it 12:30:45 ek: I will reach out to them. Our tweet got the usual amount of likes 12:31:10 ek: their tweet has more interactions than ours, which is nice 12:31:41 ek: closing the issue 12:32:36 topic: Issues 12:32:41 subtopic: Issue 353 12:32:43 https://github.com/w3c/wot-marketing/issues/353 12:33:07 q+ 12:33:45 dp: my machine picks the html, gh takes the md version 12:35:02 q+ 12:35:08 ack k 12:35:22 kaz: the width, it is not an issue from our point but from accesibility point of view would have issues with the text in the iamge 12:35:29 dp: we also have two images 12:36:10 ek: are svgs fine? 12:36:24 kaz: we should simply split the image into the guy with the question and simple text 12:36:57 kaz: or use alt text worst case 12:37:05 ek: we should split it, also problematic for font size 12:38:07 cris_ has joined #wot-marketing 12:38:12 q+ 12:39:43 ack dape 12:40:52 ek: we should have 1.1 only 12:41:36 ... we should merge issues 353 and 340 12:41:51 kaz: it is not clear why we need the detailed explainer here 12:42:05 kaz: we can have an abstract text here and point to the td 12:42:14 ... repository 12:43:16 q+ 12:43:51 ek: it is better that people stay on this page 12:44:53 ... and writing something new would mean more work to us 12:45:34 ack k 12:45:39 q+ 12:46:31 kaz: I am objecting copying over resources to the marketing area 12:46:54 s/copying over/copying the existing/ 12:48:41 dp: I think we should have a single place 12:48:47 ... we can remove from one or the other 12:49:29 ek: we cannot remove from the TD repository 12:49:46 kaz: it is problematic since the resource is generated by the TD TF 12:50:21 ca: is it fine if we link to the resource? 12:50:33 kaz: we should clarify who is responsible for which resource 12:52:02 ek: can you symlink to the td explainer and let jekyll render it still? 12:53:39 ek: we should avoid problems. Let's link to it 12:55:30 ek: can I close issue 353? 12:55:42 dp: yes sure, I was not aware of 340 12:56:02 dp: what is the decision now? 12:56:15 ek: if we can let jekyll render it from a link it would be nice 12:56:28 ca: We should link to the source in any case 12:58:10 kaz: we should not have duplicates 13:00:49 s/we should not have duplicates/It would not be really useful to the readers to provide a copy of the existing explainer. It would be more useful to provide some abstract description under the Marketing area and links to the existing explainer document and the spec itself than that./ 13:02:06 rrsagent, make log public 13:02:10 rrsagent, draft minutes 13:02:10 I have made the request to generate https://www.w3.org/2022/11/08-wot-marketing-minutes.html kaz 13:02:44 chair: Eg 13:02:59 s/chair: Eg/chair: Ege/ 13:03:01 ek: in order to avoid problems, we should simply link to it. I will document it in the issue 13:03:08 present+ Cristiano_Aguzzi 13:03:13 dp: why do you want to link to branch? 13:03:20 ek: so that we can have a static link 13:03:28 dp: but then, we need to track the changes all the time 13:03:37 ek: true, we can simply link the main branch then 13:04:10 ek: aob? 13:04:16 ek: meeting is adjurned 13:05:25 s/adjurned/adjourned/ 13:05:28 rrsagent, draft minutes 13:05:28 I have made the request to generate https://www.w3.org/2022/11/08-wot-marketing-minutes.html kaz