css-meeting-bot
commented
1 month ago The Revising W3C Process CG just discussed #876.
The full IRC log of that discussion
<plh> Topic: #876<plh> Github: https://github.com/w3c/w3process/pull/876
<plh> Florian: there is an article in the Guide about Workshops. We have a section about workshop and symposia and doesn't contain much rules
<plh> ... that section only has one requirement: how far ahead it is announced
<plh> .... I suggest to move the rule into the meeting section, as well as workshop definition
<plh> ... and move the rest into the /Guide
<plh> ... we have rules about recorded meetings unless people disagree, which will apply to workshop as well
<plh> ... currently the rule is 8-weeks advance notice
<fantasai> scribe+
<fantasai> plh: I agree and disagree. I agree in principle, but disagree because more work for me in /Guide
<fantasai> plh: regarding advance notice, could bypass process by calling it something other than "Workshop"
<fantasai> florian: This PR fixes that loophole, because doesn't say for workshops, but says for open events such as workshops.
<fantasai> florian: open-ended meetings should have enough notice to attend
<fantasai> s/florian:/.../
<fantasai> ... could make the edits without generalization, but thought it would be a good idea.
<fantasai> plh: I think need more feedback for this, run it by the Team.
<fantasai> florian: Agree, let's be sure about what we're doing
<plh> ack fant
<plh> fantasai: I think we need an escape hatch
<plh> ... a casual/local meeting for example
<plh> ... like a WG organizing a dev meetup on the side
<plh> ... the pull request is too strict
<plh> florian: should we restrict it to workshop? include an exception mechanism?
<plh> plh: restrict it to workshop
<plh> florian: what about symposia?
<plh> plh: we haven't had one for the past 20 years at least....
<fantasai> ... [missed]
<fantasai> ... but for something like a developer meetup, at most it informs a specific WG, doesn't direct W3C itself
<fantasai> ... that's why I think restriction on Workshop is important, it can impact direction of W3C so need enough notice for Members to be there
<fantasai> ... but for things that are informative, it matters less
<fantasai> ... nowadays also we have a lot of recordings, so if you're not there you can see it afterwards
<fantasai> florian: OK, I'll modify PR to make the advance meeting notice apply only to Workshops
<fantasai> plh: sounds good to me
<fantasai> fantasai: let's come back to this with a new PR
<plh> Florian: I'll update the PR
This PR consolidates the rules about Group meetings with those about Workshop and Symposia, and delegates other discussion and description of Workshops to /Guide.
This makes it clear that rules about minute taking or meeting recording apply to Workshops as well as Group meetings, regroups rules about advance notice on meetings to a single place, and shortens the Process by focusing it on enforceable rules, while letting /Guide provide more elaborate description and non-binding guidance.
See #419
Preview | Diff