W3C home > Mailing lists > Public > public-wot-ig@w3.org > April 2020

[plugfest/testing] minutes - 11 March 2020

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Wed, 01 Apr 2020 17:04:05 +0900
Message-ID: <877dyzvdhm.wl-ashimura@w3.org>
To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:

also as text below.




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

                               - DRAFT -

                          WoT PlugFest/Testing

11 Mar 2020


          Kaz_Ashimura, Ege_Korkan, Michael_Koster,
          Michael_Lagally, Michael_McCOol, Takahisa_Suzuki,





     * [2]Topics
         1. [3]Agenda
         2. [4]Repo reorg
         3. [5]Next plugfest
     * [6]Summary of Action Items
     * [7]Summary of Resolutions


   McCool: repo reorg
   ... and should talk about the plan for Helsinki
   ... possible virtual plugfest
   ... discovery over VPN
   ... any other topics?

Repo reorg

   McCool: new repo here

   <McCool> [8]https://github.com/w3c/wot-testing

      [8] https://github.com/w3c/wot-testing

   McCool: creating subdirectories here
   ... should update the README
   ... "Systems" includes information on tools

   <McCool> [9]https://github.com/w3c/wot/pull/918

      [9] https://github.com/w3c/wot/pull/918

   McCool: this PR deletes obsolete materials
   ... move then to the wot-testing repo
   ... how do we feel about it?

   Lagally: not really deleting anything?

   McCool: right
   ... just move and restructure it later
   ... there are 5-6 different places about scenarios
   ... would reorganize it

   Lagally: sounds good

   McCool: reorganization will be done separately
   ... may cause several broken links but we can fix them later
   ... anybody feels we should wait?
   ... any objections to merge this?

   (no objections)

   Kaz: let's go for it!

   McCool: PR 918 of the "wot" repo has been merged

Next plugfest

   [10]Helsinki f2f wiki

     [10] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_6-11_June_2020,_Helsinki

   McCool: we should be consistent

   Lagally: agree
   ... we should start with use case scenario and clarify gaps,

   McCool: agree requirements discussion to be done during the
   Architecture call
   ... but some of the information was installed separately so far
   ... I could make a proposal for a better procedure

   Lagally: we should have some more agreement about how to do
   describe that

   Kaz: agree with both of you
   ... and would suggest we should think about what would be
   needed and useful for new participants like Singapore govtech
   ... how to join the PlugFest activity, etc.

   McCool: right
   ... would create 2 kinds of PRs
   ... reorg the structure and add templates
   ... next time we can discuss how to improve the procedure
   ... maybe for the new comers, some additional README should be
   ... (creates two issues)

   [11]Issue 2 - create a "participation" README

     [11] https://github.com/w3c/wot-testing/issues/2

   [12]Issue 3 - reorg existing material

     [12] https://github.com/w3c/wot-testing/issues/3

   Kaz: in addition to the template, maybe there are 3 phases
   ... 1. gather common information about basic logistics and
   system setting
   ... 2. gather each participant's information based on the
   ... 3. how to integrate all the collected information including
   possible demo scenarios

   McCool: yeah
   ... but testing is a bit different from plugfest itself

   Kaz: ah, yes. that's true
   ... however, we still need to think about that kind of 3 phases
   ... the 3rd phase would be how to integrate the information
   without concrete demo, though

   McCool: (updates the Helsinki wiki as well)
   ... due to the Coronavirus issue, there is a possibility we
   need to cancel the Helsinki f2f
   ... in that case, we could try online meeting and online
   ... can we figure out how to set up VPN, etc.?
   ... know it's possible but we need experts
   ... also need a host who provides the service
   ... there are several choices
   ... we can do it ourselves, or hire somebody
   ... in the past, we ever had an online plugfest
   ... but we need to discuss the schedule
   ... what is people's preference?

   Lagally: depends on the complexity of the content

   McCool: right
   ... my expectation is getting prepared beforehand
   ... maybe people can solve issues using one hour from a day
   during the previous week
   ... possibly 2-week VPN is up: week before the plugfest for
   prepration, and the plugfest itself)
   ... participants commit to having all devices online all the
   ... light meeting schedule, e.g., 1h everyday, to resolve

   <inserted> people work offline or have 1:1 meetings to test
   pairs of devices

   McCool: end we gather all test data and create a report
   ... that's what in my mind

   Lagally: VPN set-up is one of the variants
   ... device connected directly with the Internet or via gateway

   McCool: (adds Lagally's point to the wiki)

   Ege: some use cases like hypermedia vocabulary within TD
   ... should assume a bit different network configurations

   McCool: VPN, cloud and NAT traversal

   Kaz: we should have 2 separate sections here
   ... 1. possible connection mechanisms
   ... 2. existing implementations/mechanisms to use

   McCool: yeah
   ... note that VPN is used to simulate the local network

   Kaz: yeah, I know about that
   ... but we should be clear enough for the new comers as well

   Ege: probably we don't have to set up VPN services ourselves

   Kaz: do you mean we can reuse some of the existing VPN

   Ege: we can't reuse it directly but can think about some kind
   of collaboration...

   McCool: we need to think about how to handle it transparently

   Lagally: another comment
   ... if we look into media use cases
   ... input from the ME guys would be useful
   ... let's discuss it in detail tomorrow during the Architecture


Summary of Action Items

Summary of Resolutions

   [End of minutes]

    Minutes formatted by David Booth's [13]scribe.perl version
    1.152 ([14]CVS log)
    $Date: 2020/04/01 07:58:25 $

     [13] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [14] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 1 April 2020 08:04:25 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 1 April 2020 08:04:26 UTC