Meeting minutes
<dape> Agenda:
previous minutes
<dape> https://
Daniel: review minutes
McCool: we should follow up on how we are going to take care of the logos
Daniel: yes there is an issue to track this
Daniel: also need to track implementations
… and talked about further dissemination; ongoing activity
Daniel: any objections to approving the minutes?
… hearing none, let's make these public
website review
Daniel: noticed we have some updated tweets, startup out of TUM
… also is a PR to update the "upcoming" events, which are now past
McCool: may as well add TPAC to this PR
Daniel: do people agree I should add this and then merge it?
… sounds like it, yes
<dape> https://
Daniel: some more PRs as well... Ege added WADE to the list of implementations
<dape> https://
Daniel: no objections, will merge
… this also reorders the implementations to put more conformant ones higher in the list
Daniel: another PR that archives older content on the wiki
<dape> https://
https://
(delete entry for 87)
<dape> https://
McCool: let's also update the content on the wiki to point also to the main web page
Daniel: ok (edits wiki)
Daniel: will also merge the above PR to archive old content to keep it in an archive on the wiki
Kaz: not strictly necessary to use the same license as in the charter
McCool: although it would be consistent
… and before we merge we should check with Coralie and Wendy
web analytics
Daniel: matamo can be used, can be set to not use cookies
McCool: so do we just ask the system team to set this up?
Kaz: but some concern that we would rather not share it publically
McCool: I think the purpose is just to review, but not put the data in the minutes
Kaz: can archive data in a private list; will let sebastian continue talking to them
Daniel: agree, no cookies
McCool: we care about the trend, not about the absolute number
Philipp: nothing special about this, matamo does the right thing, good for our purposes
social media icons
<kaz> Issue 188 - Adding Social Media Icons on WoT Pages
Daniel: ege is proposing we add icons and links to all the READMEs for the github repos
McCool: while we are at it, it would be good to point to the web page from each repo
Cristiano: there is a github feature to point at the web site
McCool: but currently used for github.io...
Daniel: let's agree on a consistent header across all our repos
Kaz: agree
McCool: we should at least put the link to the web page, putting icons on each page is a second-order, reduces the number of links
Kaz: right. regarding the addition of icons from external services, I'd suggest we check with Coralie
McCool: we also have to decide which badges we want; twitter and stackoverflow?
… too many different badges just makes more work for us, so harder to generate content for/stay on top of
… so I'd keep it to a smallish number
Daniel: and then there's the question of YouTube
… Dom asking about this
McCool: also, regarding StreamFizz, etc. I think we only need an alternative channel to make things available in China
… so an alternative that is also not available in China is no use
McCool: so right now we do use streamfizz for the alternative video source
… need to test if it works in China...
McCool: (timecheck)
Action: kaz to talk to dom about getting access to video server credentials
https://
WoT Implementations
<dape> https://
McCool: I think we need to at least add SayWoT and WebThings
… best to leave ECHONET off for now
workshops
Kaz: I will be speaking at workshop in Korea proposed by Gyu Myoung Lee from ITU-T SG20.
Daniel: time to adjourn
<kaz> [adjourned]