Meetings are held:
- Thursdays at 15:00 ET (other timezones, accurate at time of viewing, which may vary with Daylight Saving changes)
- Via Jitsi in browser or standalone app
- using this link: meet.w3c-ccg.org/traceability
- With standing agenda to review open Pull Requests, oldest first (trace-interop, trace-vocab), then open Issues, least recentlyl updated first (trace-interop, trace-vocab), unless otherwise noted on the mailing list
Historical archives for meetings can be found here.
Any chair, editor, or other party authorized by CCG to manage recordings and minutes can do the following.
- Duplicate the W3C-CCG Traceability Agenda Email Draft in Google Docs
- Update all the items highlighted in yellow, in particular adding new agenda items for week starting with item 6.
- If there are presentation materials, add them to the appropriate dated meeting archives folder before the meeting.
- Send agenda to [email protected] before each meeting. Use the
following format for the subject (modify date accordingly):
[AGENDA] W3C CCG Traceability Call - 2022-11-22
- Confirm in the CCG mail archives that the agenda was sent correctly
-
Be sure to click
Start Recording
and thenStop Subtitles
-
Read the IPR note
Anyone can participate in these calls. However, all substantive contributors to any CCG Work Items must be members of the CCG with full IPR agreements signed. Information about and links to the required license agreements can be found in the meeting agenda.
-
Make sure to link to the agenda at the beginning of the meeting (
Agenda: ...
) -
Make sure the scribe is identified (
Scribe: ...
orscribe+ ...
identifying someone else, orscribe+
identifying oneself). Scribes, please familiarize yourself with general scribing guidance here and here. -
Make sure topics are labeled when the topic changes (
Topic: ...
) -
Make sure that action items are listed so that they can be added to issues later ("Action: ...")
- Kick everyone from the meeting, and click
Stop Recording
- Publish the minutes
The spec contains documentation on use cases as well as required and optional API operations.