<kaz> scribenick: dsr

Issue 19

<ege> https://github.com/w3c/wot-marketing/issues/19

Daniel's draft email to be sent to Coralie (head of W3C comms)

This is about finding out the MarComm Team's plans and timeline for the website redesign, and sharing what we are hoping to do for the WoT pages

Kaz: the website redesign work is still at a very early stage, we should collect our suggestions for the WoT IG/WG and pass them on to Coralie
... note that once we've got a consensus about the resolution, the one of the co-Chairs should send it to the W3C MarComm Team

McCool: Sebastian should take the lead on that

Daniel: the URI is publicly available for the website redesign RFP
... we should seek feedback on our plans rather than waiting for the website redesign to be done

Kaz: one question is around what kinds of tools we should be using
... My point is purely procedural, and concerns checking with Coralie if we can continue our discussion on the public github about this point
... probably okay, but want to hear from her first
... Sebastian can send his email once we hear back from Coralie, re use of public github pages

Issue 17

<inserted> Issue 17

Ege: we may want to have a WoT twitter account
... It is important to reach a wider audience

<ege> https://twitter.com/csswg

Dave asks if Ege means an account or a hashtag

Ege: I mean an account
... Open question is how to open the account, not clear which is the best way to go

Daniel: we should check with CSS WG for how their account was created
... I would prefer a W3C official account

Kaz: this would be managed by the W3C MarComm team first
... we can chat with the CSS group for their advice on practical aspects after talking with the MarComm Team

Ege: is our contact Naomi or Coralie?

Kaz: we can talk to Naomi and ask her to transfer our message to Coralie, but the Chair can send our message directly to w3t-comm list with the whole WoT IG/WG feedback

Ege: I propose we bring the twitter account idea to the main call next Wednesday

[no objections]

Issue 18

https://github.com/w3c/wot-marketing/issues/18 covers chronology of WoT standardisation

with a history of important events, e.g. publication of WD, workshops, ...

for use in any web page where appropriate

Ege: I would need help if we agree to move this forward

Taki: I agree that this would be important

Taki offers to help Ege to fill out the list of events by year

Dave: we should provide a brief summary for each listed event

Ege: should we close these issues and continue the discussion on the template?

Daniel: we can close issue 9

Dave: my concern was what we need to do in the very short term

Kaz: right. We should clarify what we want to do

Ege: one example is the table on the WG page

Daniel: the date of the last REC track draft is much more important than the FPWD

RESOLUTION: Daniel to propose changes for W3C staff contacts to apply

Dave: for the /WoT/ page we should provide a concise status for the IG/WG at the top
... I think we were requested to add the link for joining the IG on this page

<kaz> kaz: +1 to add the link for joining the groups within the left column or the center column

(McCool leaves

Issue 2

<ege> https://github.com/w3c/wot-marketing/issues/2

<ege> https://github.com/w3c/wot-marketing/blob/master/posts/draft/2019-10-tpac-update.md

Dave: we should get Michael's blog on the IG page and the main W3C blog

Ege asks Dave to insert the text from the TPAC update to the current IG page via WordPress admin

Dave to copy the content to the W3C blog on behalf of the IG/WG

Issue 19 (revisited)

Daniel: is it now okay to ask Sebastian to proceed with gathering feedback to send to Coralie

<Zakim> kaz, you wanted to report that Coralie is OK with siting the RFP document

Kaz: yes
... we need to summarise the feedback from the whole IG/WG before sending it to MarComm

Dave: this task force should prepare some material for the mail call to discuss

Perhaps Ege could do this with Daniel's help?

Kaz summarises the process to follow

Another possibility is for the main call to approve devolving all responsibility to the marketing task force

Ege: the Task force should be able to update the pages without requiring prior approval from the main call in each case

Ege to propose agenda request for next Wednesday's main call, along with some supporting material

[adjourned]