Meeting minutes
minutes
ege: minutes of 17 May: https://
ege: added plugfest tf page, PoC issue, source license, charter draft goals
mm: small typos, strong, too, Should
ege: propose publishing after fixing the typos
… any objections?
… none, will publish after typos are fixed
PRs
PR 322
ege: https://
… slides for pres, PR also renames files; just pres, no link from web page yet
… will add link to events once merged
ege: bit annoying to have large files though, increases download time
mm: could put presenations in wot, but if going to link to web page, probably best in wot-marketing
PR 323
ege: on Tools; https://
<Ege> https://
ege: badges, two options; badges with hovering text, but a bit messy, won't work in mobile
… alt 2 puts the badges in a table with text next to them
dape: prefer option 2, but using table to indent text consistently would be nice
… or we could just remove it
cris: I think the explanation is useful, but keep the mouseover on badges as well
… wonder if we can make it work for mobile somehow, e.g. click on badge goes to explanation (e.g. in popup)
ege: tried using popups, but don't work
mm: I guess people often block them
mm: also I like alt 2, but also think there are a lot of badges and we should resist adding too many more; 11 is already a lot
kaz: don't really understand why we need these
ege: recorded in PR, issue is some tools belong to multiple categories
kaz: in that case, perhaps original categorization is not ideal
… also think these are similar to github labels, perhaps confusing
ege: also not just a matter of adding more categories, some tools belong to more than category
ege: let me show you a table
mm: I think part of this is the way the badges run into the text
… maybe if we laid out the tool name, desc, and badges in a table
dape: similar to google mail
… do ideally we would be able to filter by badges
mm: could also just change the rendering when a badge is clicked, i.e. grey out the ones that do not have the selected category
kaz: maybe we can rethink the categories, have fewer?
ege: tried that, but did not work; these were minimum
kaz: should think about original list of tools again, then think about categories
ege: thought we did this already...
kaz: do we have to put the categories at all?
mm: I think kaz is suggesting we should just have badges
… having two ways to categorize things is confusing
ege: well, we did do that, and it got very messy
ege: also this PR was open for a while
kaz: still think having two different categorizations on the same page is confusing
mm: I think we should try a badge-only approach and see how it works
… but also look at tools to sort or filter by badges
… ultimately we will have to deal with hundreds of things
… could also use key at top as a selectors for which badges to show
ege: ok, let me try
PR 302
ege: script to update news feed
… pulls from W3C feed, selects WoT articles
… so acts like a blog
<kaz> old WoT WG page
mm: so basically we have some criteria to select articles, and right now looks at the index for "Web of Things", but we could add other criteria
ege: right; also, just W3C articles
ege: right now result is empty however
kaz: no recent articles...
ege: so is either empty or out of date
… would like to capture third party articles
kaz: what do we want to do?
ege: I want to collect third-party blogs
kaz: do want to put global news on our website
ege: for example the survey article
mm: I'm not sure we need a list, a simple list of links to articles would be fine
kaz: so we need to clarify our needs and expectations first
mm: we *could* just write a w3c blog post every time we see an external article and link to it
… then it would show up in the feed
… but that is kind of roundabout
ege: what do we do with old articles, though? We don't want to start with ten blogs
mm: I personally feel we should start with a simple reverse-chronological list
… because we want such a complete list anyway
ege: also last list included the charter which was too much
kaz: included procedures not just goals
(correction to minutes: were actually talking about expectations in charter, not putting charter in blog)
cris: not sure having just a list that is manually maintained is a good idea, making it automatic would lead to less argument
mm: can avoid argument my having policies, saying inclusion does not mean endorsement, and keeping bar fairly low
Issues
Issue 221
ege: want to close, PoC TF does not exist
mm: sure
Updates
Netlify
ege: invites out, but right now just ege and daniel, that is ok
sutopic: Analytics
ege: see issue #177
… https://
… talking to Systeam about options, logistics to set up
kaz: pls keep me in the loop on emails
… and also team-wot
Discussion
ege: issue #321
… https://
<kaz> ack
mm: suggest we discuss this in the main call again; thanks for updating the description
<Ege> @kaz could you mark https://
<kaz> [adjourned]