BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20210322T184406Z
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-MICROSOFT-CDO-TZID:13
BEGIN:STANDARD
DTSTART:20201101T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20210314T100000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:254c5c75-18b1-4cf3-8d38-04f5b24889a2
DTSTAMP:20210322T184406Z
SUMMARY:W3C Process CG Call
DTSTART;TZID=America/Los_Angeles:20210310T070000
DTEND;TZID=America/Los_Angeles:20210310T080000
DESCRIPTION:https://www.w3.org/events/meetings/254c5c75-18b1-4cf3-8d38-04f5
 b24889a2/\n\n[Revising W3C Process](https://www.w3.org/community/w3process
 /): Examine the way W3C works. Propose improvements to the formal processe
 s.\n\n* [Github w3c/w3process](https://github.com/w3c/w3process/blob/main/
 README.md): [issues](https://github.com/w3c/w3process/issues)\, [pull requ
 ests](https://github.com/w3c/w3process/pulls)\, [monthly pulse](https://gi
 thub.com/w3c/w3process/pulse/monthly)\n* [W3C Process Draft](https://www.w
 3.org/Consortium/Process/Drafts/)\n* [Mailing list](https://lists.w3.org/A
 rchives/Public/public-w3process/)\n\nUsual meeting time: SECOND and FOURTH
  WEDNESDAY OF THE MONTH AT 7AM PACIFIC.\n\nAgenda\n\nOverall purpose: stil
 l trying to close down 2021\n\n\n\n1 ) Assign scribe\, etc.\,\n\n2 ) Agend
 a bash. \n\n3 ) The Four Horsemen of the 2021 Process. Where are we\, wher
 e are we going\, and how do we get from here to there?\n\n  3.1) Tooling P
 olicy. AB CfC has closed. <https://github.com/w3c/w3process/pull/436>\n\nI
  think we can settle on\n* should for all except retention of records\n* m
 ust for retention of records\n* say\, for the section “it is a responsib
 ility of the team contact to ensure these rules are followed\, and to brin
 g any group not in compliance\, into compliance\, as soon as possible.”\
 n* say on the retention of records  “The (temporary) lack of a backup do
 es not\, by itself\, make a decision or revision invalid.”\n\n  3.2) Rec
 ording meetings. see <https://github.com/w3c/w3process/issues/334#issuecom
 ment-793173149>\n\n  3.3) Registries. Florian has a pull for the base text
  and a separate commit for the separate publication.\n\n  3.4) Separate tr
 ack for Notes\, in place\, including W3C Statements. see <https://www.w3.o
 rg/Consortium/Process/Drafts/#note-track>\n\n4 ) Issues that  the AC gave 
 us last time we asked for a review\; we should probably try to clean up?\n
 \n<https://github.com/w3c/w3process/labels/AC-review>\n\n5 ) Process 2021\
 , The Milestone <https://github.com/w3c/w3process/milestone/6> (long list)
 \n\nP2021 Priority\, shorter list <https://github.com/w3c/w3process/labels
 /P2021%3A%20Priority>\n\n#130 on enumerating the requirements for Wide Rev
 iew. Covered well enough\, so close? See also <https://github.com/w3c/w3pr
 ocess/pull/401>\n\n(all else is Registries etc. and covered elsewhere) \n\
 n\n6 ) Other Pull Requests (other than agenda+\, Needs AB Feedback\, or a 
 priority)\n\n#299 Any decision can be objected to\n#401 Proposes changes t
 o wide/horizontal review\; lots of discussion\, what can we land?\n#433 Si
 mplify the text on liaisons. Does this go back to the AB\, as it touches o
 n members that are consortia (maybe they should be liaisons with a specifi
 c WG?)\n#434 (face to face) Meetings of new groups are 8 weeks from charte
 r approval\n#485 possible missing link (editorial)\n\n\nThe usual closers:
 \n\n7 ) Next meeting.  24 March\n\n8 ) Any other business.
STATUS:CONFIRMED
CREATED:20210322T184253Z
LAST-MODIFIED:20210322T184406Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=W3C Process Commun
 ity Group:mailto:public-w3process@w3.org
END:VEVENT
END:VCALENDAR