Meeting minutes
previous minutes
Ege: last week we started with minutes review then we looked in two WoT implementations like WoT dart
… after that we reviewed issues
… one was about where to store articles
Ege: I had to contact sys team
… but I didn't
… I'll do it
… finally we discussed about CG collaboration
… now we have three issues
… we also openly discussed about expectations
… minor issues with links to issues
McCool: I would like to discuss about the issues I think they did not represent what we discussed about
Ege: minutes approved
Pull requests
PR 297
<kaz> PR 297 - Add Netlify and Daylight Saving information to readme
Ege: netlify configuration
… anything against merging it?
Daniel: looks good
Kaz: JP comunnity group is using doc zarus as documentation engine
… it might be an alternative
… we should look at it
<kaz> Docusaurus
Ege: I think is an alternative to jekill
… thanks I'll look into it
… quite nice
PR 300
<kaz> PR 300 - Unify tool information and reorg categories
Ege: related to issue 280, there are different styles in the list of the tools
… I format the list to have a consistent code style
… I also moved some tools
… I updated also some tool description, I'll ask feedback to the implementers
… is it fine?
Daniel: didn't have time to look into it, but looks fine
Ege: we can wait
… and merge it during the week
… adding reviewers
PR 301
<kaz> PR 301 - Add edit page button on all pages
Ege: I saw in different projects that they have an edit on github button
… so I added it with this PR
… it should be in every page
McCool: is there some way to gather information about people?
… do we want more than the github handle?
… email?
Ege: I think anonymous is fine
McCool: we need to be careful to merge random content
Ege: I agree
… the feature is meant to easy fixes
McCool: It might be better to reprase the button to suggest changes
Daniel: is not really anonymous
… you still have github handle
Cristiano: we can use PR templates to ask questions to people right after the create the suggestion
… plus I would suggest to improve the look of the edit button
Kaz: I want to understand the purpose of this addition
… do we really want to give everybody the ability to change pages?
Ege: they can already do this
Kaz: not really they need to join the WG/IG and follow the procedures
… people need to understand how to edit the page
… we should rather think about how to manage resources etc.
Ege: I think we can allow everybody to edit the page
Kaz: yeah exactly but is this something that we want? will the group by ok with it?
… it might be problematic to handle PRs from outsiders
Cristiano: I agree defining a policy would be nice
Lagally: question about the policy. Previously we had a resolution that every changes in the marketing pages should follow a resolution in the main call
Ege: we edited some content without resolutions
… like tooling etc.
Lagally: I'd be cautious to do significant changes without group agreement
Ege: I agree, for example the next PR will be subject to a resolution in the Main call
Ege: added a page about articles (maybe even scientific one)
Lagally: this is an important difference
… Press release is different from Scientific Article
… it would be questionable if it should be listed here
Ege: we'll have two different tabs
Lagally: everybody can write an article
Ege: shouldn't we have this 3rd parties articles?
Lagally: it should be very clear that the content is not published by us
Ege: to me it will be a tab like 3rd party articles
Kaz: two comments
… press release is not done by the WoT WG by W3C as a all
… what is the purpose of this article page?
… W3C has a feed mechanism to import all the resources mentioning "WoT", which was already implemented within the old WoT WG page
… we might want to re-use it
Ege: yes we want to list all possible articles
… any kind of article that contains WoT related information
… the goal is to represent the community interest about WoT
<kaz> s/mechanism to list scientific articles/import all the resources mentioning "WoT", which was already implemented within the old WoT WG page/
Ege: about HOW to include it, it would be interesting to re-use the tool you mentioned
McCool: ml's comment reminded to me if the website is a product of the WG or CG
… it would automatically solve some of the issues that we've just discussed
Lagally: I agree
… CG is very free
McCool: the default could be CG, but we can have WG pages
… regarding articles we can use reverse cronological order to keep them updated
CG collaboration
Ege: last week we closed an issue
… I'm talking about issue #288
<kaz> Issue 288 - Collaboration with WoT CG
Ege: now we have three different discussions about the point spawned last week
… mc do you wanted to review the topics?
McCool: I would expected to see working style in the title
Ege: updated
Kaz: if we (marketing TF) would like to ask the CG to work about the maintenance of the Website
… we should discuss it right now
Ege: ok, then you are suggesting to clarify the expectations about the editing of the Webpages
Kaz: not only maintaining the Web pages should be included in the expectation discussion
Ege: ml what do you think about CG as Web page maintainer?
Lagally: I would not advice to have it as the maintainer more like an active outreach of the community
… like talking, socialize etc.
… maybe forming an implementers group
Ege: ok then no expectations about the webpages
Lagally: right
McCool: to be clear maitaining the web page is not between the WG/IG duties too
… there's a fuzzy line between outreaching the community and update pages
… I think some pages should be updated by the CG
Ege: I agree
… wg/ig should work only on technical report
Kaz: I'm not suggesting anything myself, but we should clarify our own expectations as the WoT IG the expections of ourselves as members of the IG
… for example, the WoT Japanese CG is working on 4 topics, outreach, deployment, use cases and translation
… in my opionion we should create a list of topics like that
Ege: I agree
Cristiano: I agree with having a list of topics, plus giving the ability to edit the website
Lagally: why don't we create a page dedicated to the CG?
Ege: there is more content related to the CG/IG than WG
<kaz> (we'll continue the discussion)
<kaz> [adjourned]