Meeting minutes
Minutes
Ege: typo linkeding -> linkedin
Kaz: fixed
Ege: minutes looks fine
… minutes approved
merged PRs
<kaz> merged PRs
Ege: three pull requests
… in the main page we should testing things that people can use to test their applications
… update timelines for recs
… and fix
Cancellations
Ege: next week, Aug 15, is canceled
… week after is not canceled
… because I am available
Kaz: I only join the first call of the month
Cristiano: I'm not available on the 22
Ege: okey meeting canceled
… after TPAC stays for now
… the one before TPAC is canceled
<kaz> WoT calls
Kaz: calendar page on the marketing page is getting obsolete
… we should update the slots
Ege: ok, I'm opening an issue
<kaz> cancel: Profile and Architecture
<kaz> move: Chairs call to Tuesday right after Marketing
<kaz> move: Security one hour later
Ege: the rest looks good
… ok tracked in issue
TPAC topics
Ege: is something to discuss with the chair
… should we do a report of the activities of the marketing task force?
… eg. statistics of the web page
… not that much just maybe 10 min
Cristiano: nice to have this kind of overview at TPAC, but not priority
… maybe quick summary
Kaz: I agree, we don't have much time
<kaz> ack
Who is interested in marketing call but cannot join?
Ege: we have memebers who think marketing is important but they are not regularly join this meeting
… do we need to do a re-evaluation of the current status? maybe after tpac?
… if we don't have enough quorum everything is postponed to main call
Kaz: at this stage (the end of the extended charter period - beginning of the new one), we should concentrate on policy discussion and usecases.
Ege: at the moment Marketing task has a lower priority
… we could keep this pace, and when the initial planning is done we can review
… for example the website cannot totally die
Kaz: as I mentioned during the TD call, we can clarify which problems we see and make the group aware
Ege: good point
Kaz: we can think about resolutions later
Cristiano: I agree that stopping working as marketing task force means that the website will be not updated anymore. That is a possible problem
Kaz: we need to keep in mind the efforts around the recent renewal of the whole W3C Web site.
… interoperability with the official W3C site is important
Ege: we can collaborate
CG relationship
Ege: long standing discussion
… right now the CG is stable
… discord chat platform is getting traction
… old people left, but new people joined
… we have a better picture of what the CG can do
… it is a good time for discussing this point once again
… in the TPAC people will ask about differences between WG and CG and we should answer
… we could say WG -> specification work, CG -> community building
Kaz: other w3c WG groups have their corresponding CG
… sometimes is hard to handle the relationship
Ege: this is the most important thing
… as far I can tell our work as chairs of CG we are doing our best to onboard people
… it is our main goal
Kaz: probably the problem is how to get ideas from outside the WG
… including CG
Ege: WG -> outside communication is easier
… in TPAC we can clearly state this problem
… and explain
<kaz> [adjourned]