Meeting minutes
minutes
<kaz> Aug-9
Ege: review minutes of Aug 9
… again, would like to expand the initials
Kaz: will also add your name to the chairs
Ege: otherwise looks good, if no objections can publish after fixes
… no objections
PRs
PR #336
<kaz> PR 336 - Adding History of the Standardization
Ege: history of standardization
… some feedback: pictures, second workshop
… made some edits, added some pictures
… however, need to find pictures, workshop
Kaz: will dig into webserver but will take some time
McCool: would be better to archive pictures somewhere we can access, so we solve this problem once
Kaz: when do you need them by?
McCool: I would also like to do an editorial pass, so at least a couple of weeks
Ege: can look at it again at the end of Aug/TPAC
Ege: unfortunately most pictures don't show any women
McCool: true, but we could use the shot showing the entire audience of the second workshop
Kaz: also a space problem with pictures
Ege: right, if put in github will blow up the repo
Kaz: maybe can just store the links, eg. and index page, in the repo
Pr #331
<kaz> PR 331 - Move Explainer to Marketing repo
Ege: about reorganizing explainers, made a checklist last time, worked through
… so there is a new draft
… now explainers are linked, but titled as explainers
McCool: only TD 1.1, do we wait for discovery?
Ege: would like to merge this now, do discovery later
… let me create an issue
McCool: ok let's merge
<Ege> Issue 338 - Add Discovery Explainer
Ege: (merged)
issues
issue #329
<kaz> Issue 329 - JSON Schema Case Study
Ege: json schema case study; draft of case study, under review
IG-CG discussion
Ege: don't plan to do this every week, maybe biweekly or once a month
… propose starting Sept 6 but that is TPAC pre-meeting, people will be busy
McCool: might be ok to have it in pre-TPAC if include discussion of next WG charter items
McCool: seeking input on priorities and use cases
Kaz: as staff, most important point is clarifying responsibilities of each group
… don't think we should continue this discussion, and make final decision about responsibilities
Ege: you mean responsibilities that CG should take?
Kaz: for example, don't necessarily need wot-marketing TF after CG starts
McCool: need to get a clear resolution
Ege: agree, but don't understand exact first step to take
… don't know where resolution should go
McCool: 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
Ege: propose to create an issue right now then
McCool: need to capture and resolve some sticking points, e.g. distinguishing official WG/IG anouncements from CG material
… we just need a policy
Kaz: and from current pages, need to figure out which are managed by which group
… just creating github issues is not enough, need a draft policy
… maybe a diagram, listing of pages
… locations and types of content
McCool: want to make sure the directory structure is clear
Ege: if move repo, will have to update web site redirection as well
McCool: that should not be a problem, the wot-marketing name is troublesome anyway
Kaz: also need to talk to W3M about publishing responsibilities, etc.
Ege: don't understand exact issues here...
Kaz: we did discuss it before
… may need to have another call about process
McCool: we really just need exact steps to go from here to there
Ege: get the feeling the previous discussion was not clear; who has the work, what needs to be done?
Kaz: before creating detailed issues and PRs, need design and policy
Ege: so where do we write that content if we don't use github?
… I felt in particular that we have already clarified our expectations
Kaz: which group is responsible for what resources
McCool: still feel we should use the wot repo to organize a resolution, at least for the IG/WG resolution
… but some homework needs to be done to consolidate prior discussion
Kaz: there are also multiple groups now, including Japanese WoT CG, Ben's group, etc.
Kaz: also, need to have another resolution for "groups" that are involved in WoT
Ege: Publishing@W3C page mentions activities
Kaz: obsolete terminology, unfortunately
McCool: suggest we make a list of things to do in the issue, and Kaz should comment on additional tasks
Kaz: I am a little worried about visibility of this discussion
McCool: we could use a private repo
Ege: ok, let me do that
McCool: let's aim to get a draft done by the pre-TPAC, then get input, then aim to finalize that it that week
… maybe can allocate two slots; first to discuss draft and gather input, second for actual resolution
<kaz> [adjourned]