12:31:06 <RRSAgent> RRSAgent has joined #wot-marketing
12:31:10 <RRSAgent> logging to https://www.w3.org/2023/02/28-wot-marketing-irc
12:31:10 <kaz> meeting: WoT Marketing
12:31:29 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/Marketing_WebConf#February_28.2C_2023
12:31:39 <kaz> present+ Ege_Korkan, Kaz_Ashimura, Tomoaki_Mizushima
12:32:50 <kaz> topic: Minutes
12:33:01 <kaz> -> https://www.w3.org/2023/02/07-wot-marketing-minutes.html Feb-7
12:33:33 <Ege> Ege has joined #wot-marketing
12:34:35 <kaz> present+ Luca_Barbato
12:34:53 <luca_barbato> luca_barbato has joined #wot-marketing
12:37:22 <kaz> approved
12:37:30 <kaz> rrsagent, make log public
12:37:46 <kaz> present+ Cristiano_Aguzzi
12:37:50 <kaz> present+ Daniel_Peintner
12:38:03 <kaz> topic: PRs
12:39:03 <kaz> -> https://github.com/w3c/wot-marketing/pulls?q=is%3Apr+is%3Aclosed+label%3Aminor Closed minor PRs
12:39:20 <kaz> ek: (goes through the PRs with "minor" label)
12:39:40 <kaz> topic: CG collaboration
12:40:06 <kaz> q+
12:40:55 <kaz> -> https://hackmd.io/@egekorkan/allaboutcg draft policy
12:41:08 <kaz> kaz: the MD should be installed on the wot-marketing repo later
12:41:30 <kaz> s/the MD/can't see the MD above. also the MD/
12:41:35 <kaz> ek: (changes the permission)
12:41:47 <kaz> ... will put it on GitHub later
12:42:10 <kaz> ... (goes through the "Issues about Collaboration")
12:42:22 <kaz> [[
12:42:22 <kaz> How CG makes suggestions to WG: https://github.com/w3c/wot-marketing/issues/363
12:42:22 <kaz> How to handle the Twitter account: https://github.com/w3c/wot-marketing/issues/362
12:42:22 <kaz> WoT Mastodon Account: https://github.com/w3c/wot-marketing/issues/360
12:42:23 <kaz> Identifying topics: https://github.com/w3c/wot-marketing/issues/330
12:42:23 <kaz> CG Handle some parts of the Website: https://github.com/w3c/wot-marketing/issues/321
12:42:24 <kaz> Expectations: https://github.com/w3c/wot-marketing/issues/292
12:42:26 <kaz> How to keep in sync: https://github.com/w3c/wot-marketing/issues/294
12:42:28 <kaz> CG Collab in the WG charter: https://github.com/w3c/wot-charter-drafts/pull/41
12:42:30 <kaz> ]]
12:42:39 <kaz> subtopic: Issue 362
12:43:03 <kaz> -> https://github.com/w3c/wot-marketing/issues/362 Issue 362 - How to handle the Twitter Account
12:43:17 <kaz> ek: Kaz suggested we clarify the ownership of each resource
12:43:47 <kaz> ... on the other hand, we can reference some information on another channel from each other
12:44:05 <kaz> ... any opinion about the basic working mechanism?
12:44:08 <cris_> cris_ has joined #wot-marketing
12:44:12 <cris_> q?
12:44:16 <cris_> q+
12:44:30 <kaz> ack k
12:44:42 <dape> dape has joined #wot-marketing
12:44:43 <kaz> kaz: as I mentioned to you, that would be important
12:44:48 <kaz> ek: tx
12:44:59 <kaz> ca: the separation is clear
12:45:00 <luca_barbato> q+
12:45:22 <kaz> ... on the other hand, would like to have one specific place
12:45:33 <kaz> ... would not complain to the proposed method, though
12:46:14 <kaz> lc: identifying the resources using prefixes would be confusing
12:46:16 <kaz> q+
12:46:17 <kaz> ack c
12:46:19 <kaz> ack l
12:46:35 <kaz> ... probably we could use some hash tag instead
12:46:50 <kaz> ... also
12:47:13 <kaz> ... we could think about some aggregator mechanism
12:48:03 <kaz> ... possibly could provide some blog post as well
12:48:21 <Ege> q?
12:48:36 <kaz> ... to aggregate resources like retweeting
12:49:52 <kaz> kaz: so different groups should provide their resources using different channels
12:50:07 <kaz> ... then we can think about how to aggregate all the related information later
12:50:17 <kaz> ack
12:50:22 <kaz> s/ack//
12:50:24 <kaz> ack k
12:51:16 <cris_> q+
12:51:47 <kaz> lc: if you think about something like MATTER, people talk about it much. However, there is not much information about what MATTER itself is like, etc.
12:52:27 <kaz> ek: separation of channel is important
12:52:47 <kaz> ... but people tend to follow some specific channel, e.g., the main WoT channel
12:53:05 <kaz> ... so reposting related resources on the main channel would be useful
12:53:19 <kaz> ca: ok
12:53:45 <kaz> ... we'll split the resources for each group
12:53:52 <kaz> q+
12:53:55 <kaz> ack c
12:54:12 <kaz> ... but it might cause some problem
12:54:31 <luca_barbato> q+
12:54:33 <kaz> ... people may loose their interest in the end
12:55:21 <kaz> ek: note that currently I provide information using my private account
12:55:26 <kaz> ... but that's not ideal
12:55:40 <kaz> ... would be better to have another resolution
12:56:18 <kaz> ca: why don't we simply say this account is not only for the WoT WG but also all the WoT-related groups
13:00:58 <kaz> kaz: Please note that the WoT CG is a different group from the WoT WG
13:01:19 <kaz> ... WoT WG has its own resources and WoT CG also its own resources
13:03:07 <kaz> ca: what about aggregation?
13:03:22 <kaz> kaz: aggregation would be possible, I think
13:03:47 <kaz> ... but aggregation of related information is different from letting everybody use the same channel
13:04:07 <kaz> lc: wondering who owns what, and who want to use it
13:04:50 <kaz> ... we should agree on what our work on WoT Marketing means
13:05:14 <kaz> ... who is producing the content and who is promoting it
13:05:39 <kaz> ... the content should be completely split
13:05:52 <kaz> ek: unfortunately, we're out of time
13:05:53 <Ege> https://github.com/w3c/wot-marketing/issues/362
13:05:59 <kaz> ... would continue the discussion
13:06:08 <kaz> [adjourned]
13:06:13 <kaz> rrsagent, make log public
13:06:19 <kaz> rrsagent, draft minutes
13:06:21 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/28-wot-marketing-minutes.html kaz
13:11:52 <luca_barbato> luca_barbato has left #wot-marketing
15:03:14 <Zakim> Zakim has left #wot-marketing