[PlugFest/Testing] minutees - 13 May 2020

available at:
  https://www.w3.org/2020/05/13-wot-pf-minutes.html

also as text below.

Thanks a lot for taking the notes, Sebastian!

Kazuyuki

---
   [1]W3C

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

                               - DRAFT -

                            PlugFest/Testing

13 May 2020

Attendees

   Present
          Kaz_Ashimura, Daniel_Peintner, Ege_Korkan,
          Farshid_Tavakolizadeh, Kunihiko_Toumura, Michael_Koster,
          Michael_Lagally, Michael_McCool, Ryuichi_Matsukura,
          Sebastian_Kaebisch

   Regrets

   Chair
          McCool

   Scribe
          sebastian, kaz

Contents

     * [2]Topics
         1. [3]Review minutes
         2. [4]Softether vpn
         3. [5]PlugFest venue
         4. [6]Use cases
     * [7]Summary of Action Items
     * [8]Summary of Resolutions
     __________________________________________________________

   <kaz> scribenick: sebastian

Review minutes

   <kaz> [9]May-06

      [9] https://www.w3.org/2020/05/06-wot-pf-minutes.html

   <kaz> [10]Apr-22

     [10] https://www.w3.org/2020/04/22-wot-pf-minutes.html

   <kaz> [11]Apr-15

     [11] https://www.w3.org/2020/04/15-wot-pf-minutes.html

   no objections

   <kaz> all the minutes approved

Softether vpn

   next topic: SoftEther VPN

   Kaz: W3C System Team can host the software, but the question is
   by when

   McCool: we should clearify if they are ready by May 25

   Koster: would test this, however, he is busy
   ... can someone else test the VPN software?

   <kaz> ACTION: kaz will create a doodle poll on updated
   candidate dates mentioning a few promising times

   <kaz> scribenick: kaz

   McCool: should start with f2f dates including earlier candidate
   dates June 4-5
   ... are there any holidays in June?

   Sebastian: my question is still what kind of features to be
   tested

   (Sebastian leaves)

   McCool: looking at the week of June 14th
   ... could something like starting plugfest on June 9
   ... how about just putting days first and then times next?

   Kaz: fine by me since that was my original proposal

   McCool: and let's start with just f2f

   Kaz: ok

   McCool: June 4, 5, 9, 10, 15, 16, 17, 18
   ... also the following week, i.e., 22, 23, 24, 25
   ... let's fix the f2f part first, and then revisit the plugfest
   part

   Kaz: ok

PlugFest venue

   McCool: any thoughts?
   ... so far, talking with SFU and UBC
   ... not very sure about the rate yet
   ... let's see the detail about TPAC offline
   ... features to be tested mentioned by Sebastian
   ... Lagally mentioned use case scenario
   ... and then experimental things

   McCool: use cases and scenarios are related to demos

   <Ege>
   [12]https://github.com/w3c/wot-thing-description/tree/master/pr
   oposals/hypermedia-control

     [12] https://github.com/w3c/wot-thing-description/tree/master/proposals/hypermedia-control

   Ege: something to be checked mentioned within the new Charter
   ... using some prototype?

   McCool: Prototype: new prototypes for proposed functionality,
   e.g., discovery links, hypermedia
   ... (adds some items under the prototype category)
   ... discovery, hypermedia controls, event history, OAuth2

   <Ege>
   [13]https://github.com/w3c/wot-thing-description/issues/892

     [13] https://github.com/w3c/wot-thing-description/issues/892

   Ege: issue generated by Ben above

   McCool: do you want to include that link on the plugfest wiki?

   <Ege> [14]https://www.w3.org/2020/01/wot-wg-charter.html

     [14] https://www.w3.org/2020/01/wot-wg-charter.html

   Ege: new charter above

   McCool: (adds resources to the item list)
   ... ok
   ... on the other hand, "PoC" is more experimental

   <scribe> ... new functionality for node-wot includes OAuth2

Use cases

   McCool: Lagally has brought up use case ideas

   Lagally: we started home use cases and scenarios
   ... would deal with some interesting flow

   McCool: three things to worry
   ... we have use cases, testing and prototypes/proposals
   ... would be productive if we could organize scenarios
   ... what kind of scenarios would make sense for each feature
   and prototype/poc?

   Lagally: (mentions some idea)

   McCool: we could brainstorm about possible scenarios
   ... what do we want to showcase in October?
   ... (mentions several possible ideas)
   ... discovery - end-user programming in smart retail using
   Node-RED and EdgeX
   ... also smart city/building dashboard

   Lagally: smart city should go beyond the "discovery" topic

   McCool: that's true
   ... would start with something simple
   ... any other ideas?
   ... maybe we can add another category than "possible demos"
   ... (adds "Possible Scenarios" as a sub category under "Us
   Cases and Scenarios")
   ... (and adds "Smart Store")
   ... and what else?
   ... what about "Smart Agriculture"?
   ... (and adds "Eventing" to "Possible Demos")
   ... make sense?

   Daniel: University of Bologna was also interested in smart
   agriculture

   Ege: the scenarios should be actual entities?

   McCool: would see some devices
   ... please add your ideas on the wiki

   Kaz: could think about digital twins for them?

   McCool: should describe the scenario

   Lagally: yes, concrete scenario description should be clarified

   McCool: let's talk about that next time

   [adjourned]

Summary of Action Items

   [NEW] ACTION: kaz will create a doodle poll on updated
   candidate dates mentioning a few promising times

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [15]scribe.perl version
    1.152 ([16]CVS log)
    $Date: 2020/05/18 11:27:21 $

     [15] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [16] http://dev.w3.org/cvsweb/2002/scribe/

Received on Tuesday, 2 June 2020 07:15:31 UTC