W3C home > Mailing lists > Public > public-wot-wg@w3.org > November 2019

[wor-marketing] minutes - 31 October 2019

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Mon, 4 Nov 2019 16:44:20 +0900
Message-ID: <CAJ8iq9Wzy_Vor78BbpG5pCeQxRCnKdH+ccv9ft8p1JJOinBsfg@mail.gmail.com>
To: Public Web of Things IG <public-wot-ig@w3.org>, public-wot-wg@w3.org
available at:
  https://www.w3.org/2019/10//31-wot-marketing-minutes.html

also as text below.

Thanks,

Kazuyuki

---
   [1]W3C

      [1] http://www.w3.org/

                               - DRAFT -

                             WoT Marketing

31 Oct 2019

Attendees

   Present
          Kaz_Ashimura, Ege_Korkan, Taki_Kamiya, Tomoaki_Mizushima

   Regrets
          Daniel_Peintner, Sebastian_Kaebisch

   Chair
          Ege

   Scribe
          TK

Contents

     * [2]Topics
         1. [3]Basic needs/requirements and how to proceed
         2. [4]Issue #13
         3. [5]Issue #8
         4. [6]Issue #10
     * [7]Summary of Action Items
     * [8]Summary of Resolutions
     __________________________________________________________

   <kaz> scribenick: taki

   <kaz> [9]Marketing issues

      [9] https://github.com/w3c/wot-marketing/issues

   Ege: Daniel is on holiday, Sebastian has time conflict today.

   Kaz: Do you want to Chair today's call for them then?

   Ege: Sure.

Basic needs/requirements and how to proceed

   Ege: we have a website, rendered from github repository.

   <ege> [10]https://github.com/w3c/wot-marketing

     [10] https://github.com/w3c/wot-marketing

   Ege: It is rendering the whole repository, including folders.

   <ege> [11]https://w3c.github.io/wot-marketing/posts/

     [11] https://w3c.github.io/wot-marketing/posts/

   Ege: we have to setup so that github displays only "posts"
   folder.
   ... I can show another example.
   ... "asd-2019" repository, it was setup to show only "docs"
   folder.
   ... It can setup from GitHub Pages setting.

   Kaz: I think technically this setting should be possible.
   ... However, from my W3C team contact viewpoint, it would be
   confusing to create a WoT WG "blog post" site on the
   GitHubside, because the W3C site already have a blog site for
   WoT.

   <inserted> [12]WoT landing page already has the blog post area

     [12] https://www.w3.org/WoT/

   Kaz: So not sure if we (=W3C as a whole) want to/should have an
   additional blog post area on the GitHub side.

   Ege: Blog post is an example.

   Kaz: We need to get consensus among the whole WoT WG/IG and the
   W3C Team (Dave, W3C MarComm Team, etc.), before starting the
   actual blog post services.

   Ege: about Blog post?

   Kaz: Blog post is part of the WoT marketing topics. We need to
   work with the W3C Team for the "W3C WoT IG/WG marketing"
   purposes.
   ... BTW, do you really want to have a blog post site on GitHub?

   <ege> [13]https://danielpeintner.github.io/wot-pages/

     [13] https://danielpeintner.github.io/wot-pages/

   Ege: Yes, sort of. We want to use the layout Daniel created.
   ... currently pages are built all differently.
   ... New design is homogeneous.
   ... Currently, it is difficult for people to change. It has to
   go through a specific person.
   ... Using GitHub, it is much easier for people to make changes,
   suggestions.

   Kaz: Before creating content or prototype, we should clarify
   our actual needs and requirements and discuss with W3C Team as
   well to get consensus.
   ... That's why I've been asking you all to file your
   needs/requirements using GitHub Issues.

   Ege: Yes, I agree. Requirements are transparency, same design
   language, non-dependence on a specific person. Currently, we
   are failing on all of them.

   Kaz: I can understand your feeling from the current situation
   and desire for making the WoT pages look better.
   ... However, as I repeatedly mentioned, the original design
   Daniel is referring to has not been approved as the basis of the
   whole W3C group pages yet.
   ... So if we want to use the design for all the WoT-related
   pages, we need to get consensus within the whole WoT-IG/WG and
   also with the W3C MarComm Team, etc.

   Ege: Short time goal has not been executed. Centrally managed
   approach does not work.

   Kaz: If we want to update the [14]WoT-IG page and the
   [15]WoT-WG page, that would be simpler.
   ... As I repeatedly mentioned, the WoT-WG page is already
   maintained on the GitHub side and we can change the content.
   ... Also we can move the WoT-IG page content as well to the
   GitHub side.
   ... Maybe we can even use Daniel's proposed design.
   ... However, we need to talk with the W3C MarComm Team about
   the [16]WoT Landing page, which includes the WoT blog post
   part.
   ... Group pages should be OK if we get IG/WG group consensus
   (though I think we should check with the MarComm Team if the
   drastic changes on the style would be OK).

     [14] https://www.w3.org/WoT/IG
     [15] https://www.w3.org/WoT/WG
     [16] https://www.w3.org/WoT

   Ege: so we need to talk with the W3C MarComm Team before making
   the actual changes.

   Kaz: Right. That's why I've been asking you all to file GitHub
   Issues about your needs/requirements first, and have invited
   Naomi from the MarComm Team to this Marketing call.
   ... Note that we the WoT WG ourselves are encouraged to
   maintain the WG page including the design and the content, so
   we can do that.
   ... As Dave also mentioned the other day, the W3C Project
   Management Team is working on a tool to generate WG pages
   automatically based on the W3C Database and the GitHub
   repositories.
   ... Considering those background situations, we need to clarify
   what our needs and requirements are.
   ... For example, do we want to maintain pages manually
   ourselves? Or do we want to try the automatic generation tool
   as well?

   Ege: Daniel's proposed page is generated from GitHub
   repository.

   Kaz: As I mentioned, the W3C Project Management Team and the
   W3C System Team have been working on such an automatic tool.
   ... If Daniel is also working on a similar tool, it may be
   overlapping with the W3C Team's work, and it would be better to
   merge both the efforts.

   <kaz> FYI, there is a separate repo for automatic page
   generation system, Gargantua:
   [17]https://github.com/w3c/gargantua

     [17] https://github.com/w3c/gargantua

   Ege: How to proceed with this?

   Kaz: We should start with our requirements and needs, and bring
   that to the W3C MarComm Team, Project Management Team, etc.

   Ege: For example, how to deal with Issue #1, 2 and 3 opened by
   Dave?
   ... WG/IG page, requirement is change content through GitHub.

   [18]https://github.com/w3c/wot-marketing/issues/1

     [18] https://github.com/w3c/wot-marketing/issues/1

   [19]https://github.com/w3c/wot-marketing/issues/2

     [19] https://github.com/w3c/wot-marketing/issues/2

   [20]https://github.com/w3c/wot-marketing/issues/3

     [20] https://github.com/w3c/wot-marketing/issues/3

   Kaz: Dave also wants to know about our needs and requirements.
   ... So as I already mentioned, what we should do is (1) we
   clarify our needs/requirements, (2) we get the whole group
   consensus on the issues and (3) bring the requirements to the
   W3C Team.

   Ege: Can we also have requirements for the WoT Landing page as
   well?

   Kaz: Sure, but we should create another issue for the WoT
   Landing page.

   Ege: Consensus should be made in marketing call? main call?

   Kaz: First within the Marketing TF, then brought to the WoT
   Main call. After that, we can bring our requirements to the W3C
   Team.

   Ege: Twitter account. Twitter can display landing page content.

   Kaz: We can create an Issue about that like the Issue on
   Wikipedia.

   Ege: Should I list requirements in issue 1, 2 and 3?

   Kaz: We need concrete template for creating issues to clarify
   our requirements.

   Ege: What to be described within the template?

   Kaz: For example, descriptions on (1) problems, (2)
   requirements and (3) solution proposal
   ... We should clearly state those points for each issue.
   ... existing issues, e.g., Issue 1, Issue 2 and Issue 3,
   should also use that kind of template.

   Ege: I will create three new issues using the template.

   Kaz: you can start creating a template, make a PR for that.

   Ege: I will look at TAG's template.
   ... I will put it in marketing repo.

   Kaz: "Template.md" can be the name, and people can start using
   it for creating issues.

   Ege: I talked with Dominique. He supports us. I can forward to
   the group.
   ... He made suggestions. The email is long.

   Kaz: Lagally started on use cases, created sub-folder for that.
   We can do similarly.

   <kaz> [21]wot-architecture repo

     [21] https://github.com/w3c/wot-architecture

   Ege: I will create Wikipedia folder.
   ... I will create issues for WG/IG pages, twitter, etc.
   ... We first discuss in the Marketing call after that. Then
   bring to main call, then the W3C Team.

   Kaz: Great.
   ... Now we can review several issues using the remaining part
   of this call.

Issue #13

   [22]https://github.com/w3c/wot-marketing/issues/13

     [22] https://github.com/w3c/wot-marketing/issues/13

   Ege: Issue #13.

   <ege>
   [23]https://www.w3.org/blog/wotig/2017/02/27/w3c-web-of-things-
   joint-igwg-meeting-in-santa-clara-5-9-february-2016/

     [23]
https://www.w3.org/blog/wotig/2017/02/27/w3c-web-of-things-joint-igwg-meeting-in-santa-clara-5-9-february-2016/

   Ege: Full size pictures take time to load.
   ... Couple of megabytes in some cases.
   ... GitHub does not compress image in background.
   ... I compressed photos.

   <kaz> [24]TPAC f2f photos

     [24] https://www.w3.org/2019/09/wot-f2f/photos/0917/

   Ege: We can use compressed images.
   ... This results in better use examples.

   Kaz: I usually put several sizes for photos.
   ... thumb nail, medium size, etc.
   ... We can create a folder for each image.

   Ege: I was not aware of this folder structure.

   Kaz: We can discuss more on permission.

   Ege: medium size looks ok for website purposes.

   Kaz: I can upload my Perl script to make midsize images.

   Ege: I started working on TD wikipedia page.
   ... This is a new page.
   ... I also made a logo proposal.
   ... in PNG and SVG format.

   <ege>
   [25]https://github.com/w3c/wot-marketing/blob/master/images/td.
   pdf

     [25] https://github.com/w3c/wot-marketing/blob/master/images/td.pdf

   Ege is showing proposed TD logo.

   Ege: Wikipedia has its own markdown markup.
   ... I will put Dom's email in this folder.

   Kaz: Should I put comment in GitHub issue #13?

   Ege is writing what was discussed... and put it in a GitHub
   issue #13 comment...

Issue #8

   [26]https://github.com/w3c/wot-marketing/issues/8

     [26] https://github.com/w3c/wot-marketing/issues/8

   Ege: Issue #8. Implementations should be listed.
   ... I agree. We can point to implementation report.
   ... We can also include Wotify.

   Ege is adding a comment in GitHub issue #8 about what was
   discussed...

   Ege: We first need to decide on what to do with website.

Issue #10

   [27]https://github.com/w3c/wot-marketing/issues/10

     [27] https://github.com/w3c/wot-marketing/issues/10

   Ege: Issue #10.
   ... About history of standardization.
   ... I do not know the clear picture how it started.

   Kaz: We should be careful how we describe the details, because
   people may have different views about the details.
   ... Not sure it is best to describe the ancient time history.

   Ege: First plugfest showed some level of interoperability, etc.
   First working draft, etc.

   Kaz: Showing some history is more social. The WoT Landing page
   has some information, but we should clarify what kind of
   information need to be included first.

   scribenick: kaz

   Kaz: For example, we can add f2f records, telco records, TF
   activities, ..., etc., like the Media&Entertainment IG wiki

   <kaz> [28]MEIG wiki

     [28] https://www.w3.org/2011/webtv/wiki/Main_Page

   Ege: ok
   ... can do that

   [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [29]scribe.perl version 1.154 ([30]CVS log)
    $Date: 2019/11/04 07:36:14 $

     [29] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [30] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 4 November 2019 07:45:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:27:54 UTC