Meeting minutes
minutes
<kaz> July-12
Ege: review minutes of 07/12
… CG questionnaire, issues, CG vs IG labels
… last issue was about Standict, which we decided to defer for now
Ege: any changes? none, so let's make this official
updates
CG Questionnaire
Ege: are getting some answers to the form
… about 14 responses, but list is old
… almost starting from scratch
… but we decided to organize a meeting
… created an event with the calendar system; note the correct date is the 25th
… has been scheduled to avoid the testfest
Kaz: do you want to use the marketing call as a kind of steering committee meeting for the CG?
Ege: no, more of a collaboration, just some updates
Kaz: putting those items on this call is a bit strange
Kaz: this TF call is a prep call for CG
Ege: don't want to trigger a dicussion on these issues, but to report on collaboration
Kaz: should clarify the relationship
Ege: to decide on what kind of collaboration we should make
McCool: as long as we don't make cg-only decisions in this call I am ok with it
… we do need to spend time sorting out what is in IG and what is in CG
… and we do need updates
Cristiano: agree we need updates, but need to filter first
McCool: agree regular updates are a good thing
Ege: do we need a resolution on doing CG updates here?
McCool: I don't think it really needs a resolution
Kaz: agree, but once CG calls are started need to move CG discussions there
… may need a couple more weeks of preparation
McCool: we should work on a "launch" for the CG and when the meetings should be started
… mid-August may not be ideal
Kaz: CG already exists; but if want to wait until TPAC should make an announcement about that
McCool: also need to think about frequency
Kaz: suggest separating CG and IG topics in github right away, then move CG topics to a new repo
Ege: to be clear intention is not to make this a joint CG/IG call
Kaz: understood, but we do need to decide how to involve CG members
… right now they are just waiting, which is not fair
… already planning to have a charter feedback session, right?
Ege: yes, that is planned
Kaz: ok to use this mtg for prep, however
Kaz: would like to record that Marketing TF would like to support preparation of CG during this call
McCool: I agree
<Ege> I agree
<Mizushima> +1 kaz
<cris> +1
Ege: also agree
PRs
PR 333
<kaz> PR 333 - Remove issue template
Ege: had issue template that was specific to web site, but not used, so this PR deletes the template
Ege: any objections? none...
Ege: (merges)
issue 126
<kaz> Issue 126 - We should link to the existing explainer about WoT
<kaz> PR 331 - Move Explainer to Marketing repo
Ege: about old explainers, reorganize, convert to HTML
… not currently linked under documentation, however
… so PR #331 is a preliminary update
McCool: so we would eventually put this under "historical documents"?
Ege: yes
Daniel: still some todos, should move to new issues
McCool: do we really need to convert things? Can't we just link to them?
Daniel: was not aware we should not remove explainers
… did convert to HTML so it looked like part of the website
Ege: possible to make it fit if use jekyll
McCool: other possibility is to move them all to marketing and convert to HTML
… just think we should avoid having duplicates
Kaz: should be careful about definition of term "explainer"
… from process point of view has a specific meaning, and purpose for wide review
… original explainer for TAG review may be different from ideal summarization document for public
McCool: so we should consider making a "summarization" document *derived* from the explainer
Kaz: agree, and better to have that document in HTML
Ege: ok, put notes under PR 331
<Ege> https://
<kaz> [adjourned]