11:13:28 <RRSAgent> RRSAgent has joined #wot-marketing
11:13:28 <RRSAgent> logging to https://www.w3.org/2022/03/29-wot-marketing-irc
11:13:58 <dape> q+
11:14:12 <McCool> mm: issue 275, time loss when sleeping
11:14:25 <McCool> ... suggest closing unless I figure out how to reproduce it
11:14:35 <kaz> present+ Ege_Korkan, Kaz_Ashimura, Michael_McCool
11:14:37 <kaz> meeting: WoT Marketing
11:14:39 <kaz> present+ Daniel_Peintner
11:14:41 <kaz> present+ Tomoaki_Mizushima
11:14:43 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/Marketing_WebConf#Mar._29.2C_2022
11:14:45 <kaz> present+ Cristiano_Aguzzi
11:15:07 <McCool> issue 268
11:15:13 <dape> ack dape
11:15:20 <McCool> ege: using w3c calendars, issue 268
11:15:24 <kaz> i|issue 275|topic: minutes|
11:15:45 <kaz> i|issue 275|ege: March 8|
11:16:06 <kaz> i|issue 275|... eclipse ditto, tool org, activities tab simplification, CG chairs and pages, jekyll previews, netlify, build status, CG links/template, CG collab, analytics|
11:16:27 <kaz> i|issue 275|... any objections to publish?|
11:16:48 <kaz> i|issue 275|... hearing no objections, will make official|
11:16:53 <McCool> mm: suggest we grab the ICS files periodically, render the coming week
11:17:09 <kaz> i|issue 275|topic: PR 289 - dart_wot|
11:17:14 <McCool> dape: we can use the calendarview tool
11:17:30 <kaz> i|issue 275|ege: PR from Jan Romann|
11:17:47 <kaz> i|issue 275|... working on scripting API in DArt ecosystem|
11:18:00 <McCool> topic: older issues
11:18:04 <kaz> q+
11:18:15 <McCool> ege: issue 145, press release cleanup
11:18:24 <kaz> i|issue 275|... can use like node-wot, but in dart|
11:18:46 <kaz> i|issue 275|... this PR adds just adds a link to the tools page|
11:19:04 <kaz> i|issue 275|... some issue with build, but feel we can merge|
11:19:22 <kaz> i|issue 275|... merging|
11:19:42 <kaz> i|issue 275|topic: easy issues|
11:19:54 <kaz> rrsagent, make log public
11:19:55 <McCool> ... about 2020 press release for REC
11:20:00 <kaz> rrsagent, draft minutes
11:20:00 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/29-wot-marketing-minutes.html kaz
11:20:34 <kaz> chair: Ege
11:20:56 <kaz> i|March 8|-> https://www.w3.org/2022/03/08-wot-marketing-minutes.html Mar-8|
11:20:56 <McCool> mm: I think in general it would be good to have a list of "publications"
11:21:16 <kaz> i|March 8|scribenick: kaz|
11:21:25 <McCool> ... maybe under "Further Reading" in Documentation
11:21:27 <kaz> |Issue 275|scribenick: McCool|
11:21:37 <McCool> ege: would be more inclined to have a new page
11:22:07 <dape> q+
11:22:14 <McCool> ... with a new page
11:22:29 <McCool> mm: agree, just want to think about how to restructure our existing content
11:22:51 <McCool> kaz: not to change the topic, but are we going to talk about CG collab?
11:22:58 <McCool> ege: yes, later on the agenda
11:23:34 <kaz> i|issue 275|-> https://github.com/w3c/wot-marketing/issues/275 Issue 275 - Calendar bug|
11:23:36 <McCool> mm: propose that we table the publication list and let someone come up with a proposal
11:23:39 <kaz> ack k
11:24:02 <dape> ack dape
11:24:25 <McCool> dape: we need to keep specs (what W3C calls "publications" are specs) separate from external references to articles, etc.
11:24:39 <kaz> s/not to change the topic/just to make sure, a question about the agenda for today/
11:24:43 <McCool> mm: agree, need to pick titles to keep clear what is a formal publication of the group
11:24:48 <kaz> rrsagent, draft minutes
11:24:48 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/29-wot-marketing-minutes.html kaz
11:25:22 <kaz> i/issue 275, time/scribenick: McCool/
11:25:41 <McCool> topic: issue 148
11:25:49 <McCool> ege: Jekyll previews
11:26:03 <dape> q+
11:26:03 <kaz> i|issue 268|-> https://github.com/w3c/wot-marketing/issues/268 Issue 268 - Using W3C Calendar|
11:26:06 <kaz> rrsagent, draft minutes
11:26:06 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/29-wot-marketing-minutes.html kaz
11:26:41 <McCool> ege: need to set up in a way that lets other access
11:26:49 <McCool> ... right now is on my personal account
11:27:06 <kaz> q+
11:27:30 <kaz> i|Calendar bug|subtopic: Issue 275|
11:27:51 <McCool> mm: think its ok if you just document it so we can recreate it if necessary, although ideally Systeam takes care of setting this up
11:27:54 <dape> ack dape
11:28:09 <McCool> kaz: probably talking to the wrong person, team contact for accessibility
11:28:35 <McCool> ... need to talk to Systeam directly, send to sysreq@w3.org
11:29:05 <kaz> i|Using W3C Calendar|subtopic: Issue 268|
11:29:13 <kaz> rrsagent, draft minutes
11:29:13 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/29-wot-marketing-minutes.html kaz
11:29:31 <McCool> topic: discussion of CG collab
11:29:38 <McCool> ege: issue 219
11:29:49 <kaz> i/issue 145, p/subtopic: Issue 145/
11:30:05 <McCool> ... in general WoT TFs should work on reports, but this TF does not really do that
11:30:39 <kaz> i|issue 145, p|-> https://github.com/w3c/wot-marketing/issues/145 Issue 145 - Press Release - Cleanup|
11:30:46 <kaz> q+
11:31:09 <McCool> ege: discussion moved to issue 288
11:31:35 <kaz> s/topic: issue 148/subtopic: Issue 148/
11:31:38 <kaz> rrsagent, draft minutes
11:31:38 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/29-wot-marketing-minutes.html kaz
11:31:52 <McCool> ... is a list of activities on task-forces/tf-marketing page
11:32:13 <kaz> i|Jekyll previews|-> https://github.com/w3c/wot-marketing/issues/148 Issue 148 - Jekyll Preview PRs|
11:32:16 <kaz> rrsagent, draft minutes
11:32:16 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/29-wot-marketing-minutes.html kaz
11:32:31 <McCool> ege: have some opinions, e.g. from ml on official communications from WG
11:32:49 <Ege> q?
11:33:02 <cris> q+
11:33:28 <kaz> i|issue 219|-> https://github.com/w3c/wot-marketing/issues/219 Issue 219 - Should Marketing TF be in the Community Group|
11:34:01 <McCool> mm: explainers are probably in the wrong place, if we mean the official ones needed for wide review, etc.
11:34:12 <McCool> kaz: asked for this topic as a starting point
11:34:16 <McCool> q+
11:34:44 <McCool> kaz: if the CG takes over all marketing work, don't need marketing TF
11:34:56 <McCool> ... should start with expectations from our side
11:35:06 <McCool> ... feel this is bigger than one github issue
11:35:15 <kaz> ack k
11:35:22 <McCool> ... and should be one of the main topics
11:35:46 <McCool> ege: so one topic is whether we move the whole Marketing TF or not
11:36:14 <McCool> kaz: ege, what was your own expectation?
11:36:48 <McCool> ege: any kind of "material" that is facing the public should be done via the CG
11:36:58 <McCool> ... would be open to closing the marketing TF
11:37:05 <kaz> i|moved to issue 288|-> https://github.com/w3c/wot-marketing/issues/288 Issue 288 - Collaboration with WoT CG|
11:37:07 <McCool> ... official communications etc. can be done in the main call
11:37:08 <kaz> rrsagent, draft minutes
11:37:08 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/29-wot-marketing-minutes.html kaz
11:37:11 <McCool> ... fairly rare
11:37:25 <McCool> ... just press releases for RECs, etc.
11:37:34 <McCool> ... even web page is not "official" publication
11:37:54 <dape> q+
11:38:18 <kaz> ack c
11:38:24 <McCool> cris: agree with ege that we move everything over to the CG
11:38:40 <McCool> ... it would be easier to handle different relationships, etc.
11:38:47 <McCool> ... wonder if we can do it incrementally
11:39:09 <McCool> q?
11:40:12 <kaz> ack m
11:40:41 <Ege> q?
11:40:57 <McCool> mm: personally think we should just move the Marketing TF over to the CG, then deal with exceptions as they arise
11:41:02 <kaz> q+
11:41:08 <McCool> ... but what do we lose, e.g. staff support?
11:41:08 <kaz> ack d
11:41:26 <McCool> dape: also wonder what we gain, e.g. additional people joining
11:41:37 <McCool> ... needs to be a balance
11:42:03 <McCool> kaz: should have some brainstorming first about expectations
11:42:25 <McCool> ... CGs are different from WGs and IGs, no concrete support from staff
11:42:41 <McCool> q+
11:43:01 <McCool> ... for example, the marketing web page, etc.
11:43:27 <McCool> ... means anyone can make PRs to repo, for instance
11:44:20 <kaz> rrsagent, draft minutes
11:44:20 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/29-wot-marketing-minutes.html kaz
11:44:46 <McCool> ... another example, want to maintain web pages, but don't have time, but would like support
11:44:53 <kaz> ack k
11:44:55 <kaz> ack m
11:45:01 <cris> q+
11:45:16 <McCool> ege: questions regarding infrastructure, as CG we can ask, but they are just not "required" to do so
11:45:27 <McCool> ... possible if we agree
11:45:35 <kaz> q+
11:45:47 <McCool> ... regarding dape's question, we can also "ask" for a WebEx
11:45:56 <McCool> ... more likely if we have a close collaboration
11:46:17 <McCool> ... in some cases, CGs are unrelated to WG/IG; but in this case, there is a collaboration
11:47:12 <McCool> mm: perhaps what we need, as kaz said, is collect a set of expectations, roll up in a collaboration request to W3M etc
11:47:37 <McCool> kaz: definitely need to collect expectations
11:48:08 <McCool> ege: cris and I talked about this; one of the things we want to do is set up events with the community
11:48:16 <McCool> ... e.g. local meetings
11:48:36 <kaz> s/definitely/right. and please note that before asking W3M or Systeam, we /
11:48:39 <McCool> ... would ultimately like the community to be self-sustaining, get more manpower
11:48:42 <kaz> s/collect/collect our own/
11:49:05 <McCool> ... second part is to not be as tied to the constraints of WG/IG
11:49:43 <McCool> cris: similar opinion; regarding social accounts, would rather not split them into different channels, etc.
11:50:12 <kaz> rrsagent, draft minutes
11:50:12 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/29-wot-marketing-minutes.html kaz
11:50:14 <McCool> ... would like one account that everything is published, so then need to clarify when there is an official announcement from the WG, etc.
11:50:37 <McCool> q?
11:50:44 <kaz> q+
11:50:44 <McCool> ack c
11:50:54 <cris> ack c
11:51:17 <McCool> kaz: understand what you want, but need to clarify what we mean by "official announcement"
11:51:31 <McCool> ... these can be made by Systeam, etc.
11:51:57 <McCool> ... But CG members can also make PRs to add news items, etc.
11:52:30 <kaz> ack k
11:52:31 <McCool> cris: for "official" things, I was thinking mostly about transitions, etc.
11:52:33 <kaz> q+
11:52:40 <McCool> q+
11:53:12 <McCool> kaz: everyone should be clear about who is representing
11:53:45 <McCool> ... for instance, Japanese CG holds events, but those are just Japanese CG
11:53:47 <McCool> q+
11:53:50 <McCool> ack k
11:53:50 <kaz> ack k
11:54:06 <McCool> cris: if we have just one channel, need to be clear who is speaking
11:55:10 <McCool> mm: I personally think channels exist for a reason, having separate channels for wg and cg is simplest
11:55:15 <kaz> q+
11:55:20 <kaz> ack m
11:56:03 <cris> q+
11:57:15 <McCool> mm: suggest we just forward from a WG channel to a CG channel, with a prefix
11:57:40 <McCool> ... then people can just subscribe to the wot-cg channels
11:57:52 <McCool> kaz: other factor is people have multiple roles and titles
11:58:05 <McCool> ... so need to be careful about what hats people are wearing
11:58:30 <McCool> kaz: for example, I have multiple hats: prof, w3c staff, japanese-person-at-large, etc.
11:58:52 <McCool> ege: generally fine to be affiliated with companies in the CG?
11:58:59 <kaz> rrsagent, draft minutes
11:58:59 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/29-wot-marketing-minutes.html kaz
11:59:20 <kaz> q?
11:59:22 <kaz> ack k
11:59:44 <McCool> mm: depends on whether you are making an official company announcement or not?
12:00:30 <McCool> ege: right, but company may have some general interest in supporting the community, etc.
12:01:01 <McCool> kaz: think we need to broaden our discussion, create some subtopics/subissues
12:01:36 <McCool> ege: main pillars are expectations of WG towards CG, CG towards WG, practical side (tools, gain/loss), working style
12:02:02 <cris> cris: I still think having two social accounts is not really the optimal solution.. :( it's already hard to build a good follower count on one account, plus it is not so obvious that people will subscribe to both.
12:02:06 <kaz> s/subissues/subissues, and probably we need to generate a separate README.md for our policy as the results of the discussion./
12:02:32 <McCool> mm: suggest create some github issues for these "pillars"...
12:02:34 <Ege> q?
12:03:31 <McCool> cris: should we close this issue?
12:03:44 <McCool> mm: suggest we close, but create a common label for the new issues so we can group them
12:03:57 <McCool> ege: ok (adds comments to existing issue...)
12:04:08 <McCool> topic: other business
12:04:36 <McCool> ege: we did not get to it, but please look at the agenda, there were a number of other things we did not get to, will cover next time
13:06:37 <kaz> [adjourned]
13:06:42 <kaz> rrsagent, make log public
13:06:47 <kaz> rrsagent, draft minutes
13:06:47 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/29-wot-marketing-minutes.html kaz
14:30:25 <Zakim> Zakim has left #wot-marketing