Meeting minutes
previous minutes
<Ege walks over minutes>
Ege: Minutes approved
<kaz> s/@kaz do you hear me?//
Quick Issues
<Ege> /github.com/w3c/wot-marketing/issues/216//github.com/w3c/wot-marketing/issues/216
Activities tab
Issue 216 - Activities tab is misleading
Ege: missed to close
… should have done that month ago
Netlify Open Source Plan
Issue 304 - Netlify Open Source License Checklist
Ege: Sent Email to system team
<Ege> https://
Ege: asked team whether we can use it
… no response yet
… license would be W3C license
Report for WoT Workshop
<Ege> Issue 124 - Second W3C Workshop on the Web of Things misses report
Ege: found this old issue
… propose to remove button
Daniel: uri posted in issue should point to actual content
Kaz: This is an obsolete issue and suggest we simply close it
(the HTML files fixed and the issue closed)
Discussion Issues
API Specification Conference
Issue 305 - API Specifications Conference 2022
Ege: I presented WoT at this conference
… video is on our webpage
Ege: i think we should try to particpate again
… it is after TPAC
… deadline is May 27
… need to discuss content
… ideas for content should be mentioned in issue
Daniel: Topics?
Ege: generally about APIs
… fits well to web developers
Readme for having info on where to update stuff
Issue 72 - README should have links to important lists for updating current information
Ege: clean-up issue
… don't think we need it in readme
… rather on webpage
Daniel: articles have been discussed to be put on website
Ege: Yes, but this issue is also about tools
Daniel: I agree with Ege.. information on website should be kept up-to-date
Ege: agree -> closing
Wiki pages comparison
Issue 85 - Identifying content of IG/WG Wiki Page
Ege: we used this issue to track status when changing to website
… I think we have done this also
… propose closing
Daniel: +1
Kaz: obsolete -> I am Okay for closing
… however, should check whether we miss anything important or not .. like news capability
Ege: I think we can close it.. checked old pages
… maybe "Testing" is something we can deal with in new issue
<Ege> Issue 307 - Showing Testing Results on the Web page
Kaz: Question: all task force pages have links to wiki pages
… maybe it make sense to have a link to main wiki as well
Ege: correct, good point
… however, there is not much gain in doing so
Kaz: What do you mean by that?
Ege: Why do we actually need this link?
Kaz: I mean the main call wiki
<kaz> WoT Main call wiki
Ege: I see
https://github.com/w3c/wot-marketing/issues/308
WoT WG page compatibility
Issue 84 - New WoT WG page should be upper-compatible to the current one
Ege: Similar to previous issue
… everything done by now
… propose closing
Daniel: +1
Ege: Okay let's close the issue
Process for updating Events
Issue 179 - Process/Tooling to Keep WoT Events Up to Date
Ege: again an old issue
… about events
Ege: did not understand Kaz's comment on the Issue
Kaz: would propose working / improving W3C calendar system
… BTW: as already mentioned, would suggest we simply close obsolete issues, e.g., staying longer than 6 months at least for the marketing purposes, because it would not make sense.
Ege: Okay, let's close this issue 179
CG Collab
Ege: https://
… don't get anymore updates
… not sure how to continue
… shall we talk about this in main call
Cristiano: We can try... but announced it in main call already
Ege: should clarify what CG expected from IG
Kaz: You (Ege) and Cristiano should think about your own opinions first
… a similar mechanism like it is done in Japanese CG
Ege: Making proposals?
Kaz: Yes, putting ideas on the agenda
Cristiano: Good plan
… we have some opinions
… and ask for feedback
Ege: alright
<Mizushima> +1 kaz
Ege: we are working on charter anyway
… will look into Japanese CG also
<kaz> [adjourned]