Meeting minutes
minutes review
<kaz> Aug-16
Ege: we discussed about moving the explainer, almost done, we have a follow up issue
… we talked about a discovery explainer, too
… nick names are wrong
… but it looks good
Kaz: fixed
… anything else to fix?
… ok, minutes approved
Agenda wiki clean-up
Ege: I have a question, we have a long list of agendas in the wiki
… do we have a rule of thumb about how to garbage collect this old agenda items?
Kaz: you can move the old content to a subdirectory or a sub file based on the year, e.g., 2020 and 2021, like the main call wiki does
Ege: ok,
… is everybody fine with this chage?
Cristiano: +1
Ege: ok, I'll do it after the call
Pull requests
PR 336
<kaz> PR 336 - Adding History of the Standardization
Ege: I worked on the history of the standardization process
… got a bunch of reviews
… I removed pictures to free a little bit of space
Cristiano: I like the page, we can use it also to create a timeline with key events during the standardization
Kaz: it is fine if you have extra time
… However
… that kind of diagram is time consuming
… So from my viewpoint, just putting information using HTML lists is fine. Technically, we can render the list as a timeline table later if really needed.
Ege: adding also an issue about PR reviews
Daniel: there is a problem with links
<Ege> https://
Ege: there is also a problem in how we configure the base url
… we can merge it as it is for now
Daniel: agreed
PR 342
<kaz> PR 342 - Delete wikipedia directory
Ege: I removed old content
… about a draft for the wikipedia page
Kaz: why are removing the content?
Ege: because the repository is easy to navigate
Kaz: but now we remove the history
… I'd keep everything
Ege: if we keep the content then we have to maintain it
Kaz: from my point of view these documents are still part of the deliverables produced by the WoT Marketing Task Force
… therefore is important to keep track of them
Ege: ok then I'll close the PR
Daniel: maybe it makes sense to add a warning saying that the content is outdated
Ege: I created a PR with that change
Kaz: we can also create an OBSOLETE directory, and move the old contents to that area.
<Ege> https://
PR 349
<kaz> PR 349 - Update README.md
Ege: I applied the feedback
… the PR adds a warning
PR 342 - revisited
<kaz> PR 342 - Delete wikipedia directory
Ege: we moved the content of the deleted readmes to the website
… therefore the PR is cleaning the old files
… ok merging
Issues
Issue 332
Ege: it seems it outdated
… tpac is over
… can we close the issue?
Cristiano: +1
Daniel: +1
issue 285
Ege: daniel already did some work on this
… he updated arch link
Ege: is any other link that we should update?
Kaz: Discovery updated WD has been published
Ege: daniel can you do the update?
Daniel: yes
issue 326
Ege: the issue is about unify the look and the content of Readmes
… we should start from a template
… today I started working on it
… and I found a lot of additional information to be published
… I'm going to start working on this template
<kaz> W3C on GitHub guideline
Ege: with content listed in the issue
Kaz: are you aware of the w3c Github guidelines
Ege: no
issue 328
<kaz> Issue 328 - Identifying W3C crawlable pages
Ege: w3c generates group pages automatically
<Ege> https://
<Ege> https://
Ege: they contain some information that we also have in our website
… the only thing that the automatic content does not have is the task force list
… my suggestion is to create a crawler to sync changes between the two pages
… we have the tools to do this
… w3c also has apis
Kaz: I asked everybody to think about the relationship between these two pages
… and analyse what we should automatically generated or manually curated
Ege: what do you mean about relationships?
Kaz: for example we don't need to embed the participant list in our website
Ege: we don't want to refer people to external pages
… because the two websites do not have the same look and feel
Daniel: we can use a script
… it is already there
… we discussed during the last main call
… we should not go back to the situation where we had multiple pages
Kaz: my priority and priority of the whole group is publication work
Ege: I belive in marketing work to bring people on wot tech
Kaz: at the moment we should focus on the spec work given our Charter has been extended both for the WG and the IG.
Ege: I personally think marketing work is even more important than the spec work.
Kaz: If the WoT IG Marketing TF as a whole really think this marketing work is even more important than the spec work, please make the TF resolution. And then we should bring that proposal to the main WoT WG/IG meeting, and we should see the whole groups' intention.
Ege: aob?
[adjourned]