TPAC/2015/ad-hoc-meetings

From W3C Wiki
< TPAC‎ | 2015
Jump to: navigation, search

To help schedule ad-hoc meetings at TPAC2015, and to let people know they are taking place, we invite groups to use this space. Ad-hoc time can be used or not used by working groups in their allocated meeting space.

We encourage using the following multiple channels to let others know about ad-hoc meetings:

  • Twitter: #tpacadhoc
  • IRC channel: #tpacadhoc

Note: Looking for Wednesday's Technical Plenary Day breakouts? Use other wiki to propose breakouts.

Please put meetings in chronological order. Also, for readability, please feel free to use some other format (for example a table per day, sorted in time order).


Monday Oct 26 - 15:00-18:00

Web Bluetooth and Web NFC

(the Bluetooth and NFC CGs requested and obtained a dedicated room for their meeting, so this is not exactly a ad-hoc meeting, but is documented here for sake of simplicity)

  • Summary: In this session we seek consensus on selected open issues. Also some uses of the APIs may be demonstrated with running code.
  • Leader(s): Jeffrey Yasskin / Web Bluetooth CG and Anssi Kostiainen / Web NFC CG
  • Participants: Kenneth Christiansen, Rijubrata Bhaumik, Jocelyn Liu, Bruce Sun
  • Time: 15:00-18:00
  • Location: Room 201, 2F (The room is available 8:30-18:00.)
  • IRC channel: #web-bluetooth
  • agenda: start with Web Bluetooth at 15:00 followed by Web NFC
  • background: Web Bluetooth and Web NFC APIs are being worked on in respective Community Groups. Due to overlap in participation and similarities of the APIs, this is a joint session.
  • resources:
  • minutes: Web Bluetooth and Web NFC 26 Oct 2015

Tuesday Oct 27 - 15:00-18:00

Note: the Advisory Committee meeting will also be taking place at this time.

Generic Sensor API

  • Summary: We'll do a quick presentation of the Generic Sensor API and explain how to use it to specify new sensors. Please bring your use cases along so we can make this as concrete as possible.
  • Leader(s): DAP WG / Tobie Langel
  • Participants: Anssi Kostiainen, Rijubrata Bhaumik, Kenneth Christiansen, Ari Keränen, Johannes Hund
  • Time: 15:00-18:00
  • Location: Room 201, 2F (The room is available 8:30-18:00.)
  • IRC channel: #dap
  • agenda: TBA
  • background: The goal of the Generic Sensor API is to promote consistency across sensor APIs and increase the pace at which they can be exposed to the Web by simplifying both the specification and implementation processes.
  • resources: spec | use cases | Issue Tracker | GH repo
  • minutes: Generic Sensor API Ad-hoc meeting at TPAC 2015 27 Oct 2015

Web Bluetooth (cancelled; not necessary)

  • Summary: Any further discussion of just the Web Bluetooth API that wasn't covered in Monday's joint session.
  • Leader(s): Jeffrey Yasskin / Web Bluetooth CG
  • Participants: Jocelyn Liu, Bruce Sun
  • Time: 15:00-18:00
  • Location: Hallway, TBD
  • IRC channel: #web-bluetooth
  • agenda: TBD
  • resources: spec / GH repo / open issues / Community Group
  • minutes: @@link@@

Thursday Oct 29 - 15:00-18:00

Note: the Advisory Committee meeting will also be taking place at this time.

Media Capture Stream with Worker discussion

  • Summary: The Media Capture Stream with Worker specification extends the Media Capture and Streams specification to allow JavaScript developers to process video frame data in workers on the web applications. It also serves as the foundation for other media capture specifications that want to make use of the off-the-main-thread video processing capabilities, such as the Media Capture Depth Stream Extensions.
  • Leader(s): WebRTC WG/Chia-hung Tai(ctai)
  • Participants: Tzu-hao Kuo(kaku), Anssi Kostiainen, Ningxing Hu
  • Time: Thu Oct 29 - 15:30-17:00
  • Location: room 107
  • IRC channel: #@@@@
  • agenda: @@link@@
  • background: Project FoxEye
  • resources: Media Capture Stream with Worker
  • minutes: @@link@@

Friday Oct 30 - 15:00-18:00

Example ad-hoc meeting

  • Summary: @@@@
  • Leader(s): @@Group(s)/people@@
  • Participants: @@@@
  • Time: @@@@-@@@@
  • Location: @@room@@
  • IRC channel: #@@@@
  • agenda: @@link@@
  • background: @@info@@
  • resources: @@links@@
  • minutes: @@link@@

Ideas for the Processes to Manage the Ad-Hoc meetings

Tell Other Groups if you are planning to use Ad-Hoc time

  • Each group will make a decision how they wish to use ad-hoc time.
  • Chairs should let other groups know if they plan to make use of ad-hoc time (both in this wiki and on the chairs list).

Time management

  • A group may choose to use the entire three hours (15:00-18:00) for ad-hoc meeting time, none of it, or in-between. Just let people know your plans.

Space management

  • There are a a variety of spots at the venue for very small ad-hoc meetings.
  • However, for larger ad-hoc meetings, and in general to accommodate a record number of TPAC participants, we ask that groups that take advantage of ad-hoc time to welcome ad-hoc meetings of various sizes within their rooms.
  • To help people stay within meeting room capacity, we plan to post that information in various places (e.g., on the Web, on the printed detailed schedule, and on signage outside of meeting rooms).

Observers

  • In general, ad-hoc meetings should be considered open to observers.
  • People who wish to organize private ad-hoc meetings may do so, but we assume these will be small and not take place in shared meeting space (that is, group meeting rooms).

About Ad-Hoc Meetings at TPAC

Some groups have requested guidance on when to allocate Unstructured time to break into parallel informal discussions within their groups, for more cross-group conversation, or for more hallway conversation. Encouraging all groups to schedule their unstructured time at the same time creates more opportunities for interaction.

We encourage groups to have these informal discussions overlap the AC meeting to minimize hard conflicts for AC reps, and we encourage all groups to schedule their unstructured time at the same time, thus creating more opportunities for interaction.

This year we have scheduled the AC Meeting towards the end of the day from 15:00 to 18:00 on Tuesday and Thursday afternoon. We hope this will minimize the likelihood of conflicts with group meetings.

AC Representatives who would also like unstructured time within their Groups have the opportunity to use Monday and Friday and thus avoid conflict with the AC meeting.

The Working/Interest Group schedule for Monday, Tuesday, Thursday, and Friday will thus be:

  • 08:30-18:00: Traditional Group face-to-face meetings
  • 12:00-14:00: Lunch (each group will determine their lunch time)
  • 15:00-18:00: Unstructured time (for those groups that so choose)