Re: [csswg-drafts] Rechartering 2022-2024 (#7468)

The CSS Working Group just discussed `Introductions`.

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Introductions<br>
&lt;florian> Florian, Invited Expert<br>
&lt;Rossen_> Rossen, Microsoft<br>
&lt;emilio> emilio, Mozilla<br>
&lt;astearns> Alan Stearns, Adobe<br>
&lt;fantasai> Elika J Etemad aka fantasai, Invited Expert<br>
&lt;miriam> Miriam, Invited Expert<br>
&lt;TabAtkins> Tab Atkins: Google<br>
&lt;iank_> Ian Kilpatrick, Google<br>
&lt;lea> Lea Verou, Invited Expert<br>
&lt;lea> Chris Lilley, W3C<br>
&lt;lea> prsent+ ChrisL<br>
&lt;rachelandrew> Rachel Andrew, Google<br>
&lt;fremy> Francois REMY, Invited Expert<br>
&lt;jfkthame> Jonathan Kew, Mozilla<br>
&lt;oriol> Oriol Brufau, Igalia<br>
&lt;dbaron> David Baron, Google<br>
&lt;TabAtkins> ScribeNick: TabAtkins<br>
&lt;TabAtkins> chris: We have a charter, but it's running out<br>
&lt;TabAtkins> ChrisL: We have two years (tried for three once, but people complained)<br>
&lt;TabAtkins> ChrisL_: kinda pointless, this is a permanent group, but whatever<br>
&lt;TabAtkins> ChrisL_: made a new charter based on the new template<br>
&lt;TabAtkins> ChrisL_: it's supposed to list all our drafs and status and such, been done<br>
&lt;TabAtkins> ChrisL: last year we had 10 specs we said would get to rec. 3 of them made it, 7 didn't<br>
&lt;TabAtkins> ChrisL: it's worthwhile discussing what specs we do think can get to Rec this year<br>
&lt;Rossen_> q?<br>
&lt;florian> q+<br>
&lt;TabAtkins> ChrisL: also there was some lang in th enew template that i actually prefer the old lang. you can se ein the diff<br>
&lt;TabAtkins> ChrisL: anything else that people think should be changed - tried ot keep it as simple as possible<br>
&lt;TabAtkins> ChrisL: AC doesn't like changes, they'll want  justification<br>
&lt;TabAtkins> ChrisL: So that's it. shouldn't take long to get this agenda done<br>
&lt;Rossen_> ack florian<br>
&lt;TabAtkins> florian: Two comments. You say you started from the template<br>
&lt;TabAtkins> florian: But to the extent we can I'd like to keep our existing text. and template isn't a requirement<br>
&lt;TabAtkins> ChrisL: normally when i do a new charter i'd start from template. here we started from existing, changed to template, looked at diff, and chose piece by piece<br>
&lt;TabAtkins> fantasai: changes look fine to me<br>
&lt;TabAtkins> florian: You also said we need to list milestone<br>
&lt;TabAtkins> florian: charter says milestone dates "when avaialble" if not available we can skip, and that's intentional<br>
&lt;TabAtkins> astearns: we tried to do that in the last charter iteration, but wasn't allowed<br>
&lt;TabAtkins> florian: AC or PLH?<br>
&lt;TabAtkins> ChrisL: both, we were asked why no milestones<br>
&lt;TabAtkins> ChrisL: just the path of least resistance<br>
&lt;Rossen_> q?<br>
&lt;TabAtkins> florian: thanks for doing this, btw<br>
&lt;TabAtkins> chrishtr: I think we have more specs in our charter than all other WGs combined; we're >50% of the entire official output of the W3C<br>
&lt;TabAtkins> s/chrishtr /chrisl/<br>
&lt;TabAtkins> ChrisL: So like Variables I'd like to take to Rec today, maybe MQ4.<br>
&lt;TabAtkins> ChrisL: Deciding can be done in the issue, if people want to shift timelines<br>
&lt;TabAtkins> ChrisL: meanwhile charter is doing horiz review, that takes a few weeks<br>
&lt;TabAtkins> ChrisL: then it'll go to W3M, then AC for comments<br>
&lt;TabAtkins> ChrisL: That may run out our charter time, if so we'll get 3mon extension, no big deal<br>
&lt;TabAtkins> florian: If you get pushback on boilerplate rather than substance, happy to pushback from the AB side<br>
&lt;TabAtkins> ChrisL: So that's it unless there's questions<br>
&lt;florian> github: https://github.com/w3c/csswg-drafts/issues/7468<br>
&lt;TabAtkins> ChrisL: Part of th enew process requires, if you have a CR, you ahve to repub every 6 months, otherwise you ahve to publish a heartbeat explaining why<br>
&lt;TabAtkins> ChrisL: New thing.<br>
&lt;TabAtkins> ChrisL: So for the next year I'm gonna be a huge pain in the ass<br>
&lt;TabAtkins> florian: Just fyi the process req is a SHOULD, and that's good if things have changed. if they haven't changed, not required and probably shouldn't<br>
&lt;TabAtkins> chrishtr: Right, anything that is in the ED but not in the CR isn't covered by patent policy. If it hasn't change,d we're missing nothing<br>
&lt;dbaron> s/chrishtr/ChrisL/<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7468#issuecomment-1201235455 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 1 August 2022 13:51:46 UTC