- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Wed, 2 Oct 2019 10:09:31 +0900
- To: Public Web of Things IG <public-wot-ig@w3.org>, public-wot-wg@w3.org
- Message-ID: <CAJ8iq9X4sYTodyquf+K7m18oJN+Vyu0rtC1KBzcWssZO48K7oQ@mail.gmail.com>
available at:
https://www.w3.org/2019/09/30-wot-marketing-minutes.html
also as text below.
Thanks a lot for taking the minutes, Dave!
As I mentioned, I've created a GitHub repo for wot-marketing at:
https://github.com/w3c/wot-marketing
also I've created a wiki page at:
https://www.w3.org/WoT/IG/wiki/Marketing_WebConf
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT-Marketing
30 Sep 2019
Attendees
Present
Kaz_Ashimura, Daniel_Peintner, Dave_Raggett,
Michael_McCool, Sebastian_Kaebisch, Taki_Kamiya,
Tomoaki_Mizushima, Ryuichi_Matsukura
Regrets
Chair
Sebastian
Scribe
dsr
Contents
* [2]Topics
* [3]Summary of Action Items
* [4]Summary of Resolutions
__________________________________________________________
<kaz> ACTION: kaz to create a wiki page for WoT-Marketing TF
<scribe> scribenick: dsr
Sebastian introduces the aims of the Marketing task force
McCool: in the short term we need to sort out organisational
details
e.g. to decide where the pages are and to identifiy a wiki page
for this task force
Sebastian: yes, indeed.
one thing is the web page, and the second is the wikipedia page
Sebastian: we need to appoint someone to take the lead for the
web page
McCool: the landing page for WoT should have the shortest URL
We should clean up out of data stuff
Does the curent wikipedia page talk about the old idea for WoT?
Sebastian: yes, and the history stops in 2014
McCool: so yes it is stale
Sebastian: Ege has agreed to work on the wikipedia page
<kaz> [5]Marketing repo
[5] https://github.com/w3c/wot-marketing
Kaz: we should first think about the logistics for this task
force, e.g. I’ve already created a marketing repo on GitHub as
above
<inserted> kaz: we should consider how to work on the topics
before starting the concrete discussions
McCool: we could certainly use the issue track on GitHub
The internal wiki page is handy for meeting agendas
What time would be good to invite Naomi?
Kaz: this time conflicts with the W3C comms telecon
McCool: let’s make a doodle poll to set up a joint call
Kaz: yes
She attended the Osaka meeting and says she is happy to help us
McCool: let’s keep this time slot for now
Sebastian: what help can she offer us?
Kaz: we could ask her to act as liaison with the W3C Comms &
Marketing folks
McCool: one of the things to discuss is the plan for
autogenerating IG and WG pages
<kaz> Dave: there are plans for automatic generation pages like
the ones of IETF
<kaz> ... but would avoid confusion due to that plans
<kaz> McCool: automatic generation for WG, IG, CG?
<kaz> ... but we still need manually built entry point page as
well
It would be timely for us to provide feedback to PLH for the
auto generated pages and try to minimise confusion for people
coming to WoT
McCool: we definitely need a landing page for people new to WoT
Kaz: we would still need manually generated content to describe
the relationships between the IG and WG
our landing point should point to intro pages for the IG and
WG, not directly to the auto generated pages
Kaz: we can raise issues with the marketing staff initiative
<kaz> [6]WoT Landing page
[6] https://www.w3.org/WoT/
Dave: we should invite someone from the team working on
autogenerated pages to give us more information and answer our
questions.
<Zakim> dape, you wanted to auto-generation is fine.. but we
might need some "good" looking pages also..
<dape> IG page could simlpy forward to
[7]https://www.w3.org/WoT/IG/
[7] https://www.w3.org/WoT/IG/
Daniel: we should include navigation cues for where people are
McCool: autogeneration is for consistency across groups
we should focus in the short term on keeping our pages up to
date
later on we can work on the graphics and styling
Daniel: if we start from autogenerated pages we will be stuck
Kaz: I have been working with PLH on the auto generation of
pages, but suggest that in this call we focus on what we need
in the short term
McCool: okay, let’s start with collecting issues on GitHub
we have some really obvious short term actions to clean up
<kaz> [8]WoT landing page
[8] https://www.w3.org/WoT/
Dave: the /WoT/ page is a regular HTML page that we can update
Sebastian: Matthias made a proposal 2 years back, can anyone
remember why it was rejected
Daniel: it was based upon some other website, not sure why it
was rejected
Sebastian: I like the shared style
McCool: it wasn’t rejected, more it didn’t get the support
needed
we should re-explore that with the W3C MarCom
<kaz> [9]https://www.w3.org/WoT
[9] https://www.w3.org/WoT
Kaz: we need to clarify our needs
<dape> idea borrowed from
[10]https://w3c.github.io/web-roadmaps/media/
[10] https://w3c.github.io/web-roadmaps/media/
McCool: we need to insist a clean up to make the page simpler
Kaz: my point is do we want to use the design sebastian pointed
to for the WoT landing page?
Sebastian: it is nice and clear for newcomers
the design isn’t critical, it is more about being a nice
overview and easy to find out more
<kaz> Dave: separately from the design, how to fit within W3C,
how to find the information?
who is the target audience and what are they looking for and
what do we want to tell them
McCool: we should update the landing page this week with the
current design
and then we should work with MarCom on the longer term plan
<dape> [11]https://w3c.github.io/web-roadmaps/media/
[11] https://w3c.github.io/web-roadmaps/media/
Dape: the media group are also unhappy about the wordpress page
model
Kaz: the page above looks nice but please note that it is
proposed by Francois but not confirmed to be used for the MEIG
page or the Media landing page
Sebastian: we have to rely on the W3C to help us
<kaz> [12]WG page
[12] https://www.w3.org/WoT/WG/
Dave: I am happy to update the current pages this week if we
can gather what needs to be done
kaz summarises the plan
McCool: let’s decide some actions
1. let’s start a doodle poll for a joint call with MarCom
2. Ege and propose content for the Wikipedia page for review by
us
3. Dave can update the /WoT page this week for us to review
The /WoT/ page when redesigned becomes out landing page
McCool: the IG and WG page need links to the landing page and a
brief explanation
Dave: I see this task force as responsible for driving regular,
topical updates
McCool: the IG page should indicate it is a sub-page under the
landing page
Kaz: please note that we should avoid certain words, e.g.
“Activity”
Dave: using activity in lower case may be okay
Kaz: we could collectively work on improved wording
I strongly suggest we continue this discussion as GitHub issues
Dave: I will include a link to
[13]https://github.com/w3c/wot-marketing so people can find it
[13] https://github.com/w3c/wot-marketing
<kaz> [14]wot-marketing repo as the starting point to raise
issues
[14] https://github.com/w3c/wot-marketing
Sebastian: we can then work on a plan for what we really want
in the redesign
Kaz: I encourage sebastian to make an issue and link to design
idea pages
sebastian should have admin rights for the repo
currently he doesn’t have push access
(now fixed)
<kaz> [adjourned]
Summary of Action Items
[NEW] ACTION: kaz to create a wiki page for WoT-Marketing TF
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [15]scribe.perl version 1.154 ([16]CVS log)
$Date: 2019/10/02 01:04:05 $
[15] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[16] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 2 October 2019 01:10:37 UTC