12:20:03 RRSAgent has joined #wot 12:20:07 logging to https://www.w3.org/2023/04/12-wot-irc 12:20:07 dape has joined #wot 12:20:20 ... up to 16 hours if we use all slots, but need to worry about remote participants 12:20:20 q? 12:20:23 q+ Ege 12:20:27 ... so probably can only use afternoons 12:20:59 ege: so topics are one thing, physical presence 12:21:56 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda WoT TPAC 2023 wiki 12:21:56 ... I do plan to go 12:21:58 seb: I also plan to go 12:22:03 mm: I am not sure yet 12:22:04 ... let 12:22:16 s/let/let's add a section to the wiki to track this/ 12:22:35 seb: (edits wiki to add link to qs, etc) 12:22:40 s|-> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda WoT TPAC 2023 wiki|| 12:23:11 seb: also need to clarify plugfest 12:23:12 q+ 12:23:18 i|edits|-> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda WoT TPAC 2023 wiki| 12:23:23 rrsagent, make log public 12:23:27 rrsagent, draft minutes 12:23:29 I have made the request to generate https://www.w3.org/2023/04/12-wot-minutes.html kaz 12:23:36 ... personally think demo table was very good, but need prep time 12:23:36 q? 12:23:38 q? 12:23:39 ack e 12:23:39 ack e 12:23:44 q+ 12:24:43 mm: propose we take the weekend before for a demo-development plugfest, and then also schedule a demo breakout 12:24:55 ... however this qs does not ask about breakouts - that will come later 12:25:40 kaz: please remember breakout sessions will be handled separately, will come later 12:26:10 ... having demos and plugfest like in Lyon would be useful but situation is still a hybrid meeting 12:26:20 q? 12:26:23 ack m 12:26:25 ack k 12:26:27 ack m 12:26:39 rrsagent, draft minutes 12:26:41 I have made the request to generate https://www.w3.org/2023/04/12-wot-minutes.html kaz 12:26:47 ... will have to organize carefully, agree, can support remote demos as well 12:27:10 mm: but can organize later 12:27:19 zakim, who is on the call? 12:27:19 Present: (no one) 12:27:21 seb: any other topics? 12:27:33 ege: marketing task force resolutions 12:27:44 https://lists.w3.org/Archives/Member/member-wot-ig/2023Apr/0003.html 12:27:53 i/any other/subtopic: AOB/ 12:28:07 1. Collecting articles about WoT from the Web with a strict selection policy: As you can see in the Pull Request [1] and its rendering [2], we are adding a new page with list of articles from the Web. The policy to select them can be also seen at [3]. If you do not have any objections, we would like to merge the Pull Request. 2. Social Media Management: We have decided [4] that the social media accounts owned by the IG/WG such as our Twitter ac[CUT] 12:28:42 present+ Kaz_Ashimura, Sebastian_Kaebisch, Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Kunihiko_Toumura, Michael_McCool, Tetsushi_Matsuda, Tomoaki_Mizushima 12:28:58 ege: good to look at related PRs and policy documents; for example, review policy for listing articles 12:29:08 ... only links, not rehosting 12:29:38 s|[CUT]|count, or others in the future, can promote WoT content created by other entities. We have detailed the policy in a comment at [5]. After a group resolution, we will change the current policy [6] to reflect this.| 12:29:47 rrsagent, make log public 12:29:50 rrsagent, draft minutes 12:29:51 I have made the request to generate https://www.w3.org/2023/04/12-wot-minutes.html kaz 12:30:11 q? 12:30:28 mm: need actual resolution for this... 12:30:33 i|Collecting|[[| 12:30:39 i/good to/]]/ 12:30:41 rrsagent, draft minutes 12:30:42 I have made the request to generate https://www.w3.org/2023/04/12-wot-minutes.html kaz 12:31:19 proposal: we agree to merge PR 357 of the marketing repository to have an articles page on our web page 12:31:19 q+ 12:31:19 proposal: we agree to merge PR 357 of the marketing repository to have an articles page on our web page. See PR: https://github.com/w3c/wot-marketing/pull/357 12:31:19 kaz: also good to link email 12:31:19 https://lists.w3.org/Archives/Member/member-wot-ig/2023Apr/0003.html 12:31:31 s/https/-> https/ 12:31:37 ack k 12:32:02 mm: to confirm, this covers only item 1, right? 12:32:02 s/003.html/003.html Mrketing TF proposal/ 12:32:04 ege: right 12:32:11 RESOLUTION: we agree to merge PR 357 of the marketing repository to have an articles page on our web page. See PR: https://github.com/w3c/wot-marketing/pull/357 12:32:14 seb: any objections? 12:32:32 seb: then there is the second request 12:32:45 ege: this is about twitter, but also social media in general 12:32:46 i|right| 1. Collecting articles about WoT from the Web with a strict selection policy: As you can see in the Pull Request [1] and its rendering [2], we are adding a new page with list of articles from the Web. The policy to select them can be also seen at [3]. If you do not have any objections, we would like to merge the Pull Request.| 12:32:57 s/Collecting/[[/ 12:33:00 i/right/]]/ 12:33:04 rrsagent, draft minutes 12:33:06 I have made the request to generate https://www.w3.org/2023/04/12-wot-minutes.html kaz 12:33:19 meeting: WoT-IG/WG 12:33:25 ... whether we can post content on the WoT twitter account, which belongs to the WG, can come from other groups 12:34:14 i|this is about| 2. Social Media Management: We have decided [4] that the social media accounts owned by the IG/WG such as our Twitter account, or others in the future, can promote WoT content created by other entities. We have detailed the policy in a comment at [5]. After a group resolution, we will change the current policy [6] to reflect this.| 12:34:20 i/Social/[[/ 12:34:35 i/this is about t/]]/ 12:34:51 q? 12:34:56 q+ 12:35:26 mm: as the policy is stated, feel a little uncomfortable allowing groups outside WoT (JP) CG to post 12:35:48 seb: so this is a policy it that we will share the twitter account, correct? 12:36:01 ege: right, as long as the group posting is identified 12:36:24 seb: ok with this approach, would rather not have a separate social media account, too messy 12:37:16 q? 12:37:18 seb: generally agree 12:37:19 ack k 12:37:47 q+ 12:37:48 kaz: what we discussed in the marketing call was having separate accounts for each group, can do their own posts 12:37:51 q+ 12:38:12 ... so would then *retweet* on the main WoT WG twitter account 12:38:16 q? 12:38:21 ack k 12:38:28 dezell has joined #wot 12:38:38 present+ David_Ezell 12:39:10 ege: that is correct; we didn't say that other groups would have own account, can be any resource, but retweeting is easiest way 12:39:44 ... general idea however is to only reference content, not duplicate it 12:39:49 mm: sounds good to me 12:39:53 s/own posts/own posts about their own properties./ 12:40:23 proposal: We have decided [4] that the social media accounts owned by the IG/WG such as our Twitter account, or others in the future, can promote WoT content created by other entities. We have detailed the policy in a comment at https://github.com/w3c/wot-marketing/issues/362#issuecomment-1495900883. After a group resolution, we will change the current policy to reflect this. 12:40:50 proposal: The social media accounts owned by the IG/WG such as our Twitter account, or others in the future, can promote WoT content created by other entities. Detailed policy is available in a comment at https://github.com/w3c/wot-marketing/issues/362#issuecomment-1495900883. After a group resolution, we will change the current policy to reflect this. 12:41:03 q+ 12:41:13 ack e 12:41:15 ack m 12:41:31 ack e 12:41:33 ack m 12:41:59 kaz: if our intention is to do what is discussed in this call, but is dangerous to mix things up do much 12:42:26 ... mechanism is that anyone can refer to any resources 12:42:57 ... this proposed policy is still a bit vague 12:43:21 mm: want to modify the resolution or the policy doc? 12:43:38 kaz: should be more explicit about using only references, not copies, of content 12:43:47 proposal: The social media accounts owned by the IG/WG such as our Twitter account, or others in the future, can refer to WoT content created and owned by other entities. Detailed policy is available in a comment at https://github.com/w3c/wot-marketing/issues/362#issuecomment-1495900883. After a group resolution, we will change the current policy to reflect this. 12:44:08 ... someone may wrongly understand if they only see this resolution 12:44:47 seb: anyone objecting to current proposal? 12:44:48 resolution: The social media accounts owned by the IG/WG such as our Twitter account, or others in the future, can refer to WoT content created and owned by other entities. Detailed policy is available in a comment at https://github.com/w3c/wot-marketing/issues/362#issuecomment-1495900883. After a group resolution, we will change the current policy to reflect this. 12:45:17 topic: New WG Charter 12:45:18 q? 12:45:19 ack k 12:45:31 seb: have draft, have submitted for horizontal review 12:45:34 q+ 12:45:40 i|have|-> https://w3c.github.io/wot-charter-drafts/wot-wg-2023-draft.html Proposed Charter| 12:45:52 ... still fresh, so no reviews yet 12:46:41 kaz: created strategy pipeline, first horizontal review, then W3M review 12:47:05 s/W3M review/W3M review, and then AC review/ 12:47:11 seb: next, need resolution to publish minutes for charter discussion 12:47:25 q+ 12:47:30 ack k 12:48:02 topic: Charter meeting minutes 12:48:13 q+ 12:48:30 mm: I have done a full review, sent a list of corrections 12:48:43 ack k 12:48:43 kaz: have corrected all the ones McCool mentioned 12:48:52 seb: any other corrections? 12:49:46 i|done|-> https://github.com/w3c/wot-charter-drafts/blob/main/README.md Charter meeting page including the links for the draft minutes| 12:49:46 proposal: publish corrected charter discussion minutes at https://github.com/w3c/wot-charter-drafts/blob/main/README.md 12:49:46 rrsagent, draft minutes 12:50:17 I have made the request to generate https://www.w3.org/2023/04/12-wot-minutes.html kaz 12:50:24 resolution: publish corrected charter discussion minutes at https://github.com/w3c/wot-charter-drafts/blob/main/README.md 12:50:38 topic: Testimonials 12:51:05 mm: suggest we push to testing call, but in general need to contact AC rep, so may take time 12:51:12 ... if have questions, please email me 12:51:23 topic: Societal Qs 12:51:32 seb: still need to review, but McCool has updated 12:51:36 topic: Planning 12:51:47 seb: have been planning Dev meetings 12:51:48 q+ 12:52:11 s/Planning/Dev meetings/ 12:52:24 q+ 12:52:33 ... note that Arch Dev meeting will be tomorrow 12:52:42 i|have been|-> https://lists.w3.org/Archives/Member/member-wot-wg/2023Apr/0002.html slides info (Member-only)| 12:52:53 q+ 12:52:57 ack m 12:54:06 mm: have updated at-risk items in both of these 12:54:27 s/these/these. we should make sure external developers will join the events./ 12:54:34 ek: will invite them 12:54:41 i/will/scribenick: kaz/ 12:54:46 scribenick: McCool_ 12:55:50 mm: would also like to send email to CG to invite; I will do IG/WG 12:56:00 ... also, I will chair Arch Dev mtg if necessary 12:56:04 q+ 12:56:20 ack e 12:56:22 ack k 12:56:35 kaz: Mizushima will be working on JP Dev meetings; still to be scheduled 12:56:40 topic: Testfests 12:56:57 seb: please be aware week of April 24, three days, 1h each day 12:57:43 zakim, who is on the call? 12:57:43 Present: Kaz_Ashimura, Sebastian_Kaebisch, Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Kunihiko_Toumura, Michael_McCool, Tetsushi_Matsuda, Tomoaki_Mizushima, David_Ezell 12:58:08 i|please|-> https://github.com/w3c/wot-testing/tree/main/events/2023.03.Online Testfest page| 12:58:09 q+ 12:58:11 mm: this is our last testfest this charter, and last chance to resolve at-risk items 12:58:28 ... note date for finalizing test results really May 10 12:59:10 ack k 12:59:11 mm: also, scope is all deliverables, not just profiles 12:59:21 topic: Binding Meetup 12:59:25 seb: any news? 12:59:37 mz: no new news 12:59:40 q+ 13:00:02 kaz: we need to wait a bit to see feedback from other dev mtgs and testfest first 13:00:17 topic: Detailed Work Items 13:00:51 i/Binding M/kaz: so I asked the Profile TF to think about the Teftfest prep during the Profile call right before this main call today./ 13:01:02 i/so I/scribenick: kaz/ 13:01:15 mm: propose we do this only after testing is done 13:01:19 i/any news/scribenick: McCool_/ 13:01:34 rrsagent, draft minutes 13:01:35 I have made the request to generate https://www.w3.org/2023/04/12-wot-minutes.html kaz 13:01:52 seb: also think it is ok for TFs to merge items 13:02:00 mm: for their own work items, sure, that is fine 13:02:09 topic: AOB? 13:02:25 seb: many cancellations due to Easter, so don't expect many TF reports 13:02:26 i|propose|-> https://github.com/w3c/wot-charter-drafts/labels/Detailed%20Work%20Items remaining PRs| 13:02:45 seb: adjourn, thanks 13:02:52 i|propose|-> https://github.com/w3c/wot-charter-drafts/blob/main/wot-wg-2023-details.html details doc| 13:02:57 [adjourned] 13:03:02 rrsagent, draft minutes 13:03:04 I have made the request to generate https://www.w3.org/2023/04/12-wot-minutes.html kaz 13:43:00 ktoumura has left #wot 13:49:40 Mizushima has left #wot 14:14:30 Mizushima has joined #wot 15:26:34 Zakim has left #wot