11:29:42 <RRSAgent> RRSAgent has joined #wot-marketing
11:29:47 <RRSAgent> logging to https://www.w3.org/2023/04/04-wot-marketing-irc
11:29:53 <kaz> meeting: WoT Marketing
11:30:08 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/Marketing_WebConf#April_4.2C_2023
11:32:16 <kaz> chair: Ege
11:32:26 <kaz> present+ Kaz_Ashimura, Ege_Korkan, Daniel_Peintner
11:33:30 <dape> dape has joined #wot-marketing
11:34:07 <dape> scribe: dape
11:34:31 <dape> TOPIC: Minutes Review
11:34:46 <kaz> -> https://www.w3.org/2023/02/28-wot-marketing-minutes.html Feb-28
11:34:48 <dape> -> April 4, 2023 -> https://www.w3.org/2023/02/28-wot-marketing-minutes.html
11:35:09 <dape> s/-> April 4, 2023 ->/
11:35:40 <dape> <Ege walks through the minutes>
11:35:48 <dape> EK: Any changes/objections?
11:35:52 <kaz> rrsagent, make log public
11:35:56 <kaz> rrsagent, draft minutes
11:35:57 <RRSAgent> I have made the request to generate https://www.w3.org/2023/04/04-wot-marketing-minutes.html kaz
11:36:13 <dape> ... none -> Minutes are approved
11:36:33 <kaz> s|https://www.w3.org/2023/02/28-wot-marketing-minutes.html||
11:36:35 <kaz> rrsagent, draft minutes
11:36:37 <RRSAgent> I have made the request to generate https://www.w3.org/2023/04/04-wot-marketing-minutes.html kaz
11:36:51 <dape> TOPIC:  Merged PRs
11:37:00 <Ege> https://github.com/w3c/wot-marketing/pulls?q=is%3Apr+is%3Aclosed+label%3Aminor
11:37:32 <dape> EK: 5 issues have been merged
11:37:38 <dape> ... video ordering
11:37:47 <dape> ... TPAC added to events
11:37:58 <dape> ... add eclipsecon video
11:38:16 <dape> ... updated twitter plugin
11:38:33 <kaz> q+
11:39:33 <dape> Kaz: Not sure whether we should add TPAC 2023 to the same event list
11:39:53 <dape> ... maybe have another list. A different category?
11:39:59 <dape> q+
11:40:15 <dape> ... since TPAC is member-only
11:40:32 <kaz> ack k
11:41:00 <dape> DP: BTW, we did have TPAC 2021 etc also in this list in the past
11:41:03 <dape> ack dape
11:41:31 <dape> Kaz: TPAC might still miss a proper page
11:41:41 <dape> EK: Correct, link points to wiki
11:42:30 <dape> EK: Maybe we can separate the event list
11:42:48 <dape> q+
11:44:33 <dape> DP: could also use badge/label next to each event to indicate whether event is "public", "member-only" etc
11:44:44 <dape> EK: Created issue 392
11:45:50 <dape> Kaz: Should also mention that link to TPAC will be updated
11:46:08 <dape> EK: Created issue 393 to track this
11:46:35 <dape> TOPIC: Twitter Account Handling
11:46:43 <dape> ... see https://github.com/w3c/wot-marketing/issues/362
11:46:50 <dape> ack dape
11:47:03 <dape> ...  and potentially LinkedIn
11:47:40 <dape> EK: discussed not mixing accounts (WG vs CG)
11:48:13 <dape> ... important to tackle the following point: "We should agree on who is producing the content and who is promoting the content."
11:49:14 <kaz> q+
11:49:17 <dape> ... example: Cristiano makes a tweet ... and the WoT account just promotes the tweet
11:49:50 <dape> Kaz: Correct, we should distinguish the WG, marketing and CG work
11:49:54 <dape> ... that makes sense
11:50:04 <dape> EK: Yes, that is one aspect
11:50:40 <dape> ...What if we tweet about CG events, pointing to calendar entry
11:51:08 <dape> ... again it is clear that CG (or other event organizer) is responsible
11:51:10 <kaz> ack k
11:51:14 <kaz> q+
11:52:10 <dape> Kaz: using Calendar page itself for announcement is great
11:53:52 <dape> EK: Policy should allow sharing events
11:54:08 <kaz> ack k
11:54:10 <dape> Kaz: Correct
11:54:47 <dape> ... and we should make clear "who" is doing the event
11:58:21 <Ege> Proposal: The social media accounts managed and owned by the WoT IG / WG can promote the work of other WoT-related groups and events. To do so, the link to the content owner has to be inserted and the owner should be indicated in the message (tweet, post etc.) itself. Valid Example "Check out the event from WoT CG: https://www.w3.org/events/meetings/322db7e4-1a9f-44c6-8ddf-af601043dfb9". Another Valid example is retweeting/reposting other posts [CUT]
11:58:23 <Ege> https://twitter.com/relucri/status/1642937903939567635
11:59:02 <Ege> Invalid Example: Check out this event "Check out the event from WoT CG: https://www.w3.org/events/meetings/322db7e4-1a9f-44c6-8ddf-af601043dfb9"
11:59:38 <Ege> Invalid Example: "Check out this WoT event: https://www.w3.org/events/meetings/322db7e4-1a9f-44c6-8ddf-af601043dfb9"
12:01:23 <Ege> Resolution: Proposal: The social media accounts managed and owned by the WoT IG / WG can promote the work of other WoT-related groups and events. To do so, the link to the content owner has to be inserted and the owner should be indicated in the message (tweet, post etc.) itself. Examples are in https://github.com/w3c/wot-marketing/issues/362
12:01:47 <Ege> Resolution: The social media accounts managed and owned by the WoT IG / WG can promote the work of other WoT-related groups and events. To do so, the link to the content owner has to be inserted and the owner should be indicated in the message (tweet, post etc.) itself. Examples are in https://github.com/w3c/wot-marketing/issues/362 @kaz dape Ege RRSAgent Zakim
12:02:05 <Ege> Resolution: The social media accounts managed and owned by the WoT IG / WG can promote the work of other WoT-related groups and events. To do so, the link to the content owner has to be inserted and the owner should be indicated in the message (tweet, post etc.) itself. Examples are in https://github.com/w3c/wot-marketing/issues/362
12:02:26 <kaz> rrsagent, draft minutes
12:02:28 <RRSAgent> I have made the request to generate https://www.w3.org/2023/04/04-wot-marketing-minutes.html kaz
12:02:41 <dape> [adjourned]
14:01:45 <Zakim> Zakim has left #wot-marketing