diff --git a/steering-committee/meetings/2022/2022-05-04.md b/steering-committee/meetings/2022/2022-05-04.md index b92bd29..601cfc8 100644 --- a/steering-committee/meetings/2022/2022-05-04.md +++ b/steering-committee/meetings/2022/2022-05-04.md @@ -8,7 +8,7 @@ **Note taker:** Jean-Yves -**Agenda** +## Agenda 1. (Estelle) - Meeting administration @@ -36,7 +36,7 @@ - (Florian) We should prepare an announcement post and register for Writing Day (like we did for Prague) - Discussion: Hack on MDN: running, funding, and new name? -**Notes:** +## Notes * **Estelle**: * 2 or 3 Hack on MDN events organized with some conferences. We will speak about it later when we get nearer the time. diff --git a/steering-committee/meetings/2022/2022-05-11.md b/steering-committee/meetings/2022/2022-05-11.md index 05502ea..20eb4a8 100644 --- a/steering-committee/meetings/2022/2022-05-11.md +++ b/steering-committee/meetings/2022/2022-05-11.md @@ -10,7 +10,7 @@ Daniel Appelquist (Samsung), Dominic Cooney (Meta), Rachel Andrew (Google), Jory **Note taker:** Jean-Yves -**Agenda** +## Agenda 1. (Jean-Yves) - Any last feedback about the WTD Announcement @@ -35,7 +35,7 @@ Daniel Appelquist (Samsung), Dominic Cooney (Meta), Rachel Andrew (Google), Jory - Completed a rewire of Cascade. Currently in PR review - Working on !important doc. MDN had none. -**Notes:** +## Notes * **(Ruth)**: re: interactive examples for Web APIs. I'm more interesting about stability: will we have example in every API. (Will) Not on every one, but on a lot of them. **(Ruth)** would like to see the PR from NedziolkaMichal. **(Ruth)** How does this influence the repository we have? **(Will)** Most examples will be pretty small so they don't need in their own repository, so it works well with the current structure The question is which API will responds the best to this model, and which will not. diff --git a/steering-committee/meetings/2022/2022-05-18.md b/steering-committee/meetings/2022/2022-05-18.md index 8b694d0..6a5d46a 100644 --- a/steering-committee/meetings/2022/2022-05-18.md +++ b/steering-committee/meetings/2022/2022-05-18.md @@ -8,7 +8,7 @@ **Note taker:** Estelle -**Agenda** +## Agenda 1. (Jean-Yves) - Issues and PRs @@ -31,7 +31,7 @@ - VSCode is using mdn/data and they use it for experimental flag (see [https://github.com/mdn/data/issues/582](https://github.com/mdn/data/issues/582) ) How to deal with it? Finding the right way to do it, then contacting them? - Logo updates (Lola) -**Notes:** +## Notes **JYP**: Below 6,000 flaws. Last year 17,000. Should be done in a year. The last flaws will take longer. Done with task for next 6 weeks. 833 bad BCD links meaning at least 800 missing pages. Need to figure out which pages need to be written. Some flaws are duplicate: bad BCD and bad link, so may be 2000 flaws that are really 800 issues. diff --git a/steering-committee/meetings/2022/2022-06-01.md b/steering-committee/meetings/2022/2022-06-01.md new file mode 100644 index 0000000..f3f4c7a --- /dev/null +++ b/steering-committee/meetings/2022/2022-06-01.md @@ -0,0 +1,43 @@ +# OWD Steering Committee call, 01-06-2022 + +# 01.06.2022 + +**Present:** William Bamberg (OWD), Dipika Bhattacharya (Mozilla),Eric Meyer (Igalia), Dominic Cooney (Meta), Lola Odelola (Samsung), + +**Regrets:** Estelle Weyl (OWD), Vinyl Da.i'gyu-Kazotetsu (OWD), Ruth John (Mozilla), Rachel Andrew (Google), ,Dominique Hazael-Massieux (W3C), Jean-Yves Perrier (OWD), Robert Nyman (Google), Florian Scholz (OWD), Daniel Appelquist (Samsung), Jory Burson (Guest), Uchi Uchibeke (Coil), Jon Davis (Apple), Kyle Pflug (Microsoft), Brian Kardell (Igalia), Mike Smith (W3C), Piotr Tomiak (JetBrains) + +**Chair:** Will + +**Note taker:** Dipika + +## Agenda + +1. (Will) + - Write the Docs: + 1. Published a blog post: [https://opencollective.com/open-web-docs/updates/write-the-docs-writing-day](https://opencollective.com/open-web-docs/updates/write-the-docs-writing-day), and [ https://inspiring-snyder-9401af.netlify.app/posts/writing-day-wtd-portland-2022/](https://inspiring-snyder-9401af.netlify.app/posts/writing-day-wtd-portland-2022/) + 2. Filed tracking issues to crowd-source removal of `var`in JS and Web/API docs: [https://github.com/mdn/content/issues/16614](https://github.com/mdn/content/issues/16614), [https://github.com/mdn/content/issues/16662](https://github.com/mdn/content/issues/16662) , some uptake… + - Web/API page types: 3000 pages updated: half done (with the easy ones). Will finish this week. Thanks JYP for incredible reviews. What about WebGL extensions? + - CSSSyntax macro update is awaiting dev review. [https://github.com/mdn/yari/pull/4656](https://github.com/mdn/yari/pull/4656) . Would like to blog about this when it is merged. +2. (Estelle) (out of office today) +3. (Vinyl) + - BCD v5.0.0 published yesterday + - Converting BCD internals to TypeScript to help eliminate many code issues + - Working on deprecating mdn-data with Ruth +4. (Jean-Yves) (out of office today) +5. (Other) + +## Notes + +**Will:** published blogpost about WTD, filed tracking issues to track removal of var. 600 pages use var. All in a spreadsheet. Has been bumpy with the contributors. Continuing to work on Web/API page types, updated 3000 pages. JYP has done detailed reviews. Open issues - Web GL extensions in terms of page types + +**Dominic:** Web GL extensions are not going away. Why can't they have their own page type? + +**Will:** Web GL extensions are unlike the other things we have. So maybe we can have them as separate page types. Just a cognitive load of 100s of page types. It should be okay to have their own page type though. + +**Dominic:** Do HTTP have their own page types? + +**Lola:** Ada will be taking over from me. Going to start coding the website. Ada was involved with WebXR stuff when Chris Mills was around. + +**Dominic:** any feedback about diagrams about the CSS syntax? Railroad diagrams for syntax + +**Will:** Interesting idea but would take investment/justification. Previous user research shows not many people use formal syntax, but chicken and egg - it's badly presented so people don't use it. But it is potentially very useful. css-tree might provide good tools for more interactive exploration of formal syntax.