The Pointer Events group has two types of meetings and this document includes general information about the meetings:
- Distributed meetings, aka teleconferences and voice conferences
- Face-to-face (f2f) meetings
- The WG's Code - describes how the group actually operates including links to various resources
- Bugzilla Bug and Issue Tracking - Bugzilla is used for bugs and issues
- Tracker Action Tracking
- Hg/Mercurial Repository - used for all specifications and tests
- public-pointer-events - archive of the group's Public mail list
Draft agendas for distributed meetings are sent to the group's public-pointer-events mail list at least 24 hours before the meeting starts.
F2f meetings are announced at least eight weeks before the start of the meeting. Draft agendas for f2f meetings are sent to the group's public-pointer-events mail list at least two weeks before the meeting begins.
IRC and Meeting Resources
IRC will be used for every meeting to record minutes. The group's IRC channel is #pointerevents (irc://irc.w3.org/).
If you do do not have an IRC client, or have trouble connecting to IRC from behind a firewall, W3C offers a browser-based IRC Web interface (note: you must have a Member or Invited Expert account to use this).
Some resources regarding meeting bots, minute taking and the teleconference bridge:
- Tips for Taking Minutes (thanks to Mark Nottingham)
- RRSAgent IRC Bot Description
- Zakim IRC Teleconference Bot
- How to Use the W3C's "Zakim" Teleconference Bridge
- Zakim Bridge Status
Each meeting will have one or more Scribes that are responsible for recording the meeting's minutes directly in the group's IRC channel. The group will use the RRSAgent IRC bot to facilitate taking minutes.
When someone joins the meeting via the phone bridge, the Zakim bot will announce the participant by their phone number or some other identifier. To associate a person's name with a phone number, use the following, assuming Zakim reports someone is using phone number +1.519.880.aaaa and that someone is Rick Byers:
zakim, aaaa is Rick_Byers(Note: only the last four digits/letters of the phone number is used)
If Zakim reports a person has joined with an identifier such as +[IPCaller] or +[Microsoft], those ids can be mapped to names via the following, assuming the former is actually Olli Pettay and the later is Jacob Rossi:
zakim, [IPCaller] is Olli_Pettay
zakim, [Microsoft] is Jacob_Rossi
Among the general expectations of the Chair or Scribe are:
- Record meeting boilerplate via the following keywords:
Date: Day Month Year
Date: 27 November 2012
Meeting: Pointer Events WG Voice Conference
- Use the Present macro to record all meeting participants. The general syntax to add one person is Present+ Firstname_Lastname and a comma-separated list is used to add additional attendees. For a list of the group's participants, see Public group list. Examples:
Present+ Art_Barstow, Doug_Schepers
- Use the Regrets macro to record the names of those members that sent advanced regrets. Examples:
Regrets: Art_Barstow, Doug_Schepers
- Note the start of a new discussion Topic via the "Topic: Title of the topic ..." macro. Example:
Topic: Bug 12345: Event X's Y attribute is underspecified
- Create new Actions via the "ACTION: last_name Title of the action ..." macro (see group participation list for a list of last_names). Example:
ACTION: barstow Start a CfC for ...
- Record Resolutions via the "RESOLUTION: Description of the resolution ..." macro. Example:
RESOLUTION: Event X's Y attribute will be a DOMString
The general expectations regarding the scribing of the actual discussion are:
- Scribe: try to capture the general flow of the discussion, citing the person that speaks and use "..." at the start of a line to capture the continuation of a person's input. The name assigned to a person can be their first name e.g. Art or their initials e.g. AB or their IRC nick e.g. ArtB. If you use initials and two or more participants have the same initials, create some type of unique id for each participant. Examples:
AB: One line captures my comment
Art: One line captures this comment
ArtB: the 1st thing I want to say is ...
... 2nd thing is ...
... 3rd thing is ...
- All: use the "s/text that was recorded/text that should have been recorded/" macro (possibly with "g" appended to the end to signify the change should be made to the entire minutes) to update the meeting minutes. Examples:
s/change attribute to unsigned long/change attribute to long/
s/Bug 1234/Bug 1235/g
- All: every person that attends the meeting is responsible for the accuracy of the minutes. This means that if the Scribe did not accurately capture an attendees' input, or missed an important input, the attendee is responsible for correcting the meeting record, preferably by making the correction directly in the ongoing meeting's IRC channel.
Generating and Announcing Minutes
The Chair or Team contact will ensure all of the relevant meeting bots are invited to the meeting before the meeting starts and they will send the Draft meeting minutes to the group's Public mail list.
To generate the minutes, the Scribe must issue the following command:
RRSAgent, make log Public
RRSAgent, make minutes
The minutes announcement sent to the mail list should include both the URL of the minutes as well as a copy-and-paste of the minutes. See example.
Although the group may have up to three face-to-face meetings per year, currently, no f2f meetings are scheduled.
Logistics for Distributed Meetings
For additional time zone data see TimeZone Converter.
The definitive time for the teleconference will always be listed on the W3C Calendar, so check there if there's some uncertainty about the time (NB search for "RWC_PEWG").
- Phone: +1-617-324-0000
- Code: 641 509 404
- URL: https://mit.webex.com/mit/j.php?MTID=m520d894aa4fde233becf4963995ce493
All meeting minutes are Public unless, on an exceptional basis, there is consensus for the minutes to be Member confidential. Links to all of the meeting minutes are consolidated in the Minutes Wiki.
The general expectation is a meeting's Chair will send the minutes to the group's mail list within 24 hours of the end of the meeting.