11:02:12 <RRSAgent> RRSAgent has joined #wot-marketing
11:02:12 <RRSAgent> logging to https://www.w3.org/2022/08/16-wot-marketing-irc
11:02:38 <Ege> Ege has joined #wot-marketing
11:03:21 <Mizushima> Mizushima has joined #wot-marketing
11:03:37 <kaz> meeting: WoT Marketing
11:03:41 <kaz> chair: Ege
11:03:51 <kaz> present+ Kaz_Ashimura, Ege_Korkan
11:05:59 <kaz> present+ Tomoaki_Mizushima
11:06:40 <kaz> present+ Michael_McCool
11:06:55 <McCool> McCool has joined #wot-marketing
11:08:42 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/Marketing_WebConf#August_16.2C_2022
11:09:01 <McCool> topic: minutes
11:09:16 <McCool> ege: review minutes of Aug 9
11:09:26 <kaz> i|review|-> https://www.w3.org/2022/08/09-wot-marketing-minutes.html Aug-9|
11:10:29 <McCool> ... again, would like to expand the initials
11:10:38 <McCool> kaz: will also add your name to the chairs
11:11:10 <McCool> ege: otherwise looks good, if no objections can publish after fixes
11:11:13 <McCool> ... no objections
11:11:21 <McCool> topic: PRs
11:11:28 <McCool> subtopic: PR #336
11:11:36 <McCool> ege: history of standardization
11:12:12 <McCool> ... some feedback: pictures, second workshop
11:13:12 <McCool> ... made some edits, added some pictures
11:13:23 <kaz> q+
11:13:47 <McCool> ... however, need to find pictures, workshop
11:14:49 <McCool> kaz: will dig into webserver but will take some time
11:15:28 <McCool> mm: would be better to archive pictures somewhere we can access, so we solve this problem once
11:15:51 <McCool> kaz: when do you need them by?
11:16:53 <McCool> mm: I would also like to do an editorial pass, so at least a couple of weeks
11:17:06 <McCool> ege: can look at it again at the end of Aug/TPAC
11:17:40 <kaz> q+
11:18:17 <McCool> ege: unfortunately most pictures don't show any women
11:18:43 <McCool> mm: true, but we could use the shot showing the entire audience of the second workshop
11:19:06 <McCool> kaz: also a space problem with pictures
11:19:19 <McCool> ege: right, if put in github will blow up the repo
11:19:45 <McCool> kaz: maybe can just store the links, eg. and index page, in the repo
11:19:57 <McCool> subtopic: Pr #331
11:20:02 <kaz> ack k
11:20:11 <kaz> rrsagent, make log public
11:20:16 <kaz> rrsagent, draft minutes
11:20:16 <RRSAgent> I have made the request to generate https://www.w3.org/2022/08/16-wot-marketing-minutes.html kaz
11:20:24 <McCool> ege: about reorganizing explainers, made a checklist last time, worked through
11:20:32 <McCool> ... so there is a new draft
11:21:27 <McCool> ... now explainers are linked, but titled as explainers
11:22:03 <McCool> mm: only TD 1.1, do we wait for discovery?
11:22:48 <McCool> ege: would like to merge this now, do discovery later
11:22:53 <kaz> i|ege: history of standardization|-> https://github.com/w3c/wot-marketing/pull/336 PR 336 - Adding History of the Standardization|
11:22:55 <McCool> ... let me create an issue
11:23:03 <kaz> rrsagent, draft minutes
11:23:03 <RRSAgent> I have made the request to generate https://www.w3.org/2022/08/16-wot-marketing-minutes.html kaz
11:23:04 <Ege> q?
11:23:32 <McCool> mm: ok let's merge
11:23:46 <Ege> https://github.com/w3c/wot-marketing/issues/338
11:23:54 <McCool> ege: (merged)
11:23:57 <kaz> i|ege: about reorganizing explainers, made a checklist last time, worked through|-> https://github.com/w3c/wot-marketing/pull/331 PR 331 - Move Explainer to Marketing repo|
11:24:03 <McCool> topic: issues
11:24:05 <kaz> s/https/-> https/
11:24:12 <McCool> subtopic: issue #329
11:24:27 <McCool> ege: json schema case study; draft of case study, under review
11:24:38 <kaz> s/338/338 Issue 338 - Add Discovery Explainer/
11:24:53 <McCool> topic: IG-CG discussion
11:25:13 <McCool> ege: don't plan to do this every week, maybe biweekly or once a month
11:25:33 <McCool> ... propose starting Sept 6 but that is TPAC pre-meeting, people will be busy
11:25:46 <kaz> q+
11:26:29 <McCool> mm: might be ok to have it in pre-TPAC if include discussion of next WG charter items
11:26:47 <kaz> i|ege: json schema case study;|-> https://github.com/w3c/wot-marketing/issues/329 Issue 329 - JSON Schema Case Study|
11:27:41 <McCool> mm: seeking input on priorities and use cases
11:28:06 <McCool> kaz: as staff, most important point is clarifying responsibilities of each group
11:28:43 <McCool> ... don't think we should continue this discussion, and make final decision about responsibilities
11:29:03 <McCool> ege: you mean responsibilities that CG should take?
11:29:34 <McCool> kaz: for example, don't necessarily need wot-marketing TF after CG starts
11:30:58 <McCool> mm: need to get a clear resolution
11:31:55 <McCool> ege: agree, but don't understand exact first step to take
11:35:24 <McCool> ... don't know where resolution should go
11:37:55 <McCool> mm: suggest create issue in wot repo, draft a resolution, schedule time to discuss in TPAC pre-meeting, in the meantime label issue in wot-marketing
11:38:11 <McCool> ege: propose to create an issue right now then
11:40:33 <McCool> mm: need to capture and resolve some sticking points, e.g. distinguishing official WG/IG anouncements from CG material
11:40:59 <McCool> ... we just need a policy
11:41:25 <McCool> kaz: and from current pages, need to figure out which are managed by which group
11:42:20 <McCool> ... just creating github issues is not enough, need a draft policy
11:42:53 <McCool> ... maybe a diagram, listing of pages
11:43:41 <McCool> ... locations and types of content
11:44:41 <McCool> mm: want to make sure the directory structure is clear
11:45:37 <McCool> ege: if move repo, will have to update web site redirection as well
11:45:51 <McCool> mm: that should not be a problem, the wot-marketing name is troublesome anyway
11:46:17 <McCool> kaz: also need to talk to W3M about publishing responsibilities, etc.
11:46:48 <McCool> ege: don't understand exact issues here...
11:46:58 <McCool> kaz: we did discuss it before
11:49:26 <McCool> ... may need to have another call about process
11:49:45 <McCool> mm: we really just need exact steps to go from here to there
11:50:27 <McCool> ege: get the feeling the previous discussion was not clear; who has the work, what needs to be done?
11:50:46 <McCool> kaz: before creating detailed issues and PRs, need design and policy
11:51:13 <McCool> ege: so where do we write that content if we don't use github?
11:51:58 <McCool> ... I felt in particular that we have already clarified our expectations
11:52:22 <McCool> kaz: which group is responsible for what resources
11:55:27 <McCool> mm: still feel we should use the wot repo to organize a resolution, at least for the IG/WG resolution
11:55:45 <McCool> ... but some homework needs to be done to consolidate prior discussion
11:56:28 <McCool> kaz: there are also multiple groups now, including Japanese WoT CG, Ben's group, etc.
11:57:38 <McCool> kaz: also, need to have another resolution for "groups" that are involved in WoT
11:58:41 <McCool> ege: Publishing@W3C page mentions activities
11:58:54 <McCool> kaz: obsolete terminology, unfortunately
12:03:41 <McCool> mm: suggest we make a list of things to do in the issue, and Kaz should comment on additional tasks
12:07:08 <McCool> kaz: I am a little worried about visibility of this discussion
12:07:24 <McCool> mm: we could use a private repo
12:09:07 <McCool> ege: ok, let me do that
12:10:23 <McCool> mm: let's aim to get a draft done by the pre-TPAC, then get input, then aim to finalize that it that week
12:10:43 <McCool> ... maybe can allocate two slots; first to discuss draft and gather input, second for actual resolution
12:17:29 <kaz> [adjourned]
12:17:32 <kaz> rrsagent, draft minutes
12:17:32 <RRSAgent> I have made the request to generate https://www.w3.org/2022/08/16-wot-marketing-minutes.html kaz
13:35:34 <Zakim> Zakim has left #wot-marketing