Meeting minutes
Approve previous minutes
Feb 15
Ege: <walks over minutes>
Ege: anything to change?
… none --> minutes approved
Feb 22
<Ege> https://
Ege: postponed, Kaz works on integrating scribed minutes
Pull Requests
PR #263
PR 263 - WIP Developer Journey
Ege: Got some feedback during the call
… will work on these comments
… SK pointed me to Industrie 4.0 PDF which provides something similar
<cris> 1+ I like the approach too
Ege: I like the approach taken
McCool: Not exactly the same as developer journey
… more spec guideline
McCool: like a reading guide
Ege: Will create issue for a "reading guide"
McCool: Should look at architecture document, is it enough for business people?
… or some sections
Ege: w.r.t. to comments in PR, will work on it
McCool: Where does the content go?
Ege: in top of developers page there is a new para pointing to a new site
Easy Issues
CG Page Links
https://
Ege: each page has own web-page
… our CG page does not point to it
… wonder whether we need all these other links like participants
McCool: Wonder whether we should note chair selection process
Ege: I think we should just update once it happened
Kaz: chairs will be decided tomorrow
Ege: Not sure how to nicely show this *new* link
… shall we remove mailing list?
McCool: one link to the CG page is enough
Daniel: w.r.t. layout, we can use HTML tabs
Cristiano: Okay having just one link
<McCool> (comment was that it is better to have one link going somewhere useful rather than four links, only one of which goes somewhere useful...)
Daniel: Wonder whether we can remove "participants" and add Website link at the top
Ege: I noticed also several mailing-lists on CG pages
Kaz: Community groups are different groups. Hence I suggest to just add the link to each group
… Links can change and maintained on their side
Ege: not sure about tabbing
McCool: Tabs are not needed if the entries are short
Ege: Daniel will provide a proposal
Marketing TF place
https://
Ege: Japanese CG has even different task forces
… Comment from CA: "Assume that the TF inside the WoT CG decides a new style from READMEs (which are inside repositories controlled by WoT WG) can we apply the changes without asking again for consensus inside the WG? or do we have to wait for another approval.... ?"
McCool: Should stick to current template
… okay if they are distinct
Cristiano: do we have control on other groups document?
… do we need a special approval each time?
McCool: depends on activity?
… should make clear which task belongs to which group
Kaz: community groups are different groups. Chairs are responsible
… if the published content is incorrect is problematic
… chairs from both groups should collaborate
McCool: Next week chair election is closed. Hence we should put it on hold for now
McCool: PlugFest part of CG?
… would vote not make it CG
… should discuss that soon
Minutes from Feb-22 meeting - revisited
<kaz> Feb-22
<kaz> kaz: generated the HTML version minutes based on your IRC log
Kaz: minutes missed attendance list
Ege: all of us, plus P. Blum
Ege: minutes are short, but correct.
… any changes needed?
… no objections -> minutes approved
Discussion Issues
Jekyll PRs
Issue 148 - Jekyll Preview PRs
Ege: contacted hawna-slh, did not get any response yet
… maybe she was on holiday
Ege: let's wait until she replies
Daniel: could also create a private (free) account
… in case one person disappears we create yet another account
Ege: Yes, store script somewhere
Activities Tab
Issue 216 - Activities tab is misleading
Ege: "Activities" is misleading
McCool: brainstorm ... "work"
… "meetings" vs "events"
… maybe 3 pages, "Task-foces", "Events" and "Meetings"
… will add my comments to issue
Twitter Embedding
Issue 127 - Check if we can generate thumbnails from the latest Twitter news
Ege: problem with cookie agreement
… idea to put static thumbnail
… don't like that because of user experience
… found jekyll plugins that may help
Cristiano: plugin run on server side?
Daniel: Don't think
… the content would be static
Cristiano: Maybe it is static. there might be such use-cases
… not sure though
Ege: I think CA is correct, looks like it creates static page
Cristiano: We would need a GitHub action that runs regularly
Ege: will check this for next week and report
<kaz> [adjourned]