DRAFT Agenda for the Process Call 25 August 2021 7am Pacific Time

Event at <https://www.w3.org/events/meetings/28d91e83-bc19-408e-816b-32ed7e9bd52e/20210825T070000>
Webex at <https://lists.w3.org/Archives/Member/internal-w3process/2019May/0000.html>

IRC is #w3process

Log of prior meeting at <https://www.w3.org/2021/07/28-w3process-minutes.html>

Usual meeting time: SECOND and FOURTH WEDNESDAY OF THE MONTH AT 7AM PACIFIC. See <https://www.w3.org/groups/cg/w3process/calendar>

1) Assign scribe, etc.,

2) Agenda bash. (Nothing agenda+ at the time of writing <https://github.com/w3c/w3process/labels/Agenda%2B>)

3) Process AC ballot closes 24 August midnight. Results at <https://www.w3.org/2002/09/wbs/33280/Process-2021/results> may not be visible to everyone. We have (at least) 
   3.1) one objection (BBC): 

This all looks good, but one minor thing: Aside from the description in 2.2, the document doesn't refer to Team Decisions anywhere else, so the scope of these decisions is unclear. Also, should the description come under section 5 somewhere? 

   3.2) One formal objection (51Degrees):

The document references many other external documents. For example the Code of Ethics and Professional Conduct (CEPC) in section 3.1.1.1. The Process is referenced in Appendix 1 of the Membership Agreement. Therefore any change to the Process impacts on the Membership Agreement. It is not clear to me how we should interpret a change to a document referenced by the Process in the context of the Membership Agreement. The Process document should therefore reference specific versions with dates and unique URLs rather than the latest version. This will avoid the possibility of a change to a referenced document both altering the Process and the Membership Agreement without W3C Membership approval.

Clause 16 of the Membership Agreement defines the entire agreement to include the W3C Process. This would seem to include the documents referenced from the Process document. It is possible that the authors of these documents do not consider the impact their work will have on the entire Membership Agreement. Conflicts might exist between the Membership Agreement, Process document and referenced documents. The Process should define how such conflicts are resolved. This could be as simple as stating "in the event of a conflict between the Membership Agreement and the Process the Membership Agreement prevails. In the event of a conflict between the Process and referenced documents the Process prevails". Ideally such order of precedence definition should appear in the Membership Agreement but I understand there is not an appetite to alter that document at this time.

4) Open Pull Requests <https://github.com/w3c/w3process/pulls>. Editor to alert us to any that need consensus to pull, or action.


5) Process 2022 triage. Try not to discuss the issues per se, but discuss whether (and how) we hope to address them in this revision, or whether we’ll never get to them and they should be closed.

5.1) Already labeled P2022 <https://github.com/w3c/w3process/labels/P2022> (one, at the time of writing). (I also created a Milestone we can use).

5.2) Director-free. <https://github.com/w3c/w3process/labels/Director-free%20%28all%29>. Probably no discussion needed, as it’s clear it needs attention.

5.3) Proposed to address (mostly proposed by the chair+editors): <https://github.com/w3c/w3process/labels/P2022%20Proposed%20to%20address>. If we agree, we’ll assign the P2022 label.

5.4) Proposed to close (mostly proposed by the chair+editors): <https://github.com/w3c/w3process/labels/P2022%20Proposed%20to%20close>

5.5) Other proposals to focus on, or close, from the floor?

  Here are the non-Editorial, non-Director-free issues  <https://github.com/w3c/w3process/issues?q=is%3Aopen+-label%3A%22Type%3A+Editorial+improvements%22+-label%3A%22Director-free+%28all%29%22+>

The usual closers:

6) Next meeting. Wed Sept 8th. The chair has a CONFLICT. Can someone else chair, or should we cancel? Maybe monthly is a good cadence for now and we’ll ramp up as summer ends?

7) Any other business.





Dave Singer
Multimedia and Software Standards, Apple

singer@apple.com

Received on Tuesday, 24 August 2021 17:26:41 UTC