OWD Q3 projects

[Elchi3]

We met last Wednesday (June 9th, 2021) to go through current OWD project proposals and ideas.
This issue summarizes them so we can discuss which projects to take on in Q3 2021 (the months July, August, September).

Continued projects

These project have been started and it makes sense to continue them in Q3.

• Markdown conversation for more of MDN (CSS docs)
• Finish mixin work (for workers, events, etc.)

Proposed projects

Proposed projects are defined ideas that are clear in scope. They are ready to be worked on.

• WebXR Browser Compatibility
• Fix how MDN distributes Polyfills
• WebView information on MDN
• ARIA roles reference docs
• Modernizing the Learning Area JavaScript modules
• Use webref as the source for CSS formal syntax, instead of mdn/data
• Documenting HTTP/2 and HTTP/3 (discussion)

Ideas

These ideas aren't proposals yet as more details are needed.

• Documenting WebDriver (needs scope, rough outline)
• Web Testing strategies (needs scope, rough outline)
• Fixing MDN page titles (needs decision)
• Fixing how MDN documents dictionaries (needs decision, issue, list of pages affected)

Submit ideas

You can still submit ideas until the end of June and we will take a look!

[foolip]

Finish mixin work (for workers)

Should this also include events? See mdn/browser-compat-data#8929 (comment) for everything that remains to be done to eliminate mixins.

[Elchi3]

Yes, ideally, we fix all issues related to mixins.

[foolip]

What's the right place to discuss WebView? @tomayac was enthusiastic about WebView, but there's no issue for it, just mdn/content#3918 which added the linked RFC.

[tomayac]

"Enthusiastic" as in "good to have this documented". The best browser still is an actual browser, and not a WebView :-) Just to set this straight.

[foolip]

Sorry to overstate your love of WebViews :)

[Elchi3]

What's the right place to discuss WebView? @tomayac was enthusiastic about WebView, but there's no issue for it, just mdn/content#3918 which added the linked RFC.

I think we should open a new issue here so we can discuss this project some mor, outline a plan, and scope the work that we want to do.

(As soon as the vacations are over and new OWD employees have been onboarded, I plan to go over all projects, too, but it doesn't hurt to get into some of this stuff beforehand already).

[Elchi3]

Forgot to post this here: Results from the stack ranking we did in June:

1. WebXR Browser Compatibility
2. Fix how MDN distributes Polyfills
3. Documenting HTTP/2 and HTTP/3
4. WebView information on MDN
5. Modernizing the Learning Area JavaScript modules
6. Use webref as the source for CSS formal syntax, instead of mdn/data
7. ARIA roles reference docs

We talked about this ranking in the last SC call and I did not hear any reservations, so this order should be a guiding principle when assigning work in our team. We're planning to onboard two new folks soon and we will then get together and look at these to determine what is achievable in the quarter. In the meantime, we're trying to finish continued projects.

[Elchi3]

We had a planning check-in call yesterday and here's a summary of where we are with Q3 projects:

WIP with the goal to finish

• Markdown conversation for more of MDN (CSS docs) (Will)
• WebXR Browser Compatibility (Florian)
• Documenting HTTP/2 and HTTP/3 (Jean-Yves)

Aiming to make progress (at least)

• Mixin work (for workers, events, etc.) (help to unstuck, Florian)
• Fix how MDN distributes Polyfills (start discussions/ make plan that can be executed in Q4, Jean-Yves)
• Use webref as the source for CSS formal syntax, instead of mdn/data (exploration, Will)

[foolip]

@Elchi3 do you consider representing support of events in scope for Q3, or just the bits that get entangled with mixins? From my work on API data with @vinyldarkscratch, I would say that events are the most problematic part of the data, and while the model we have makes it possible to represent support for different facets of events, I don't think the result is very clear to web developers.

Spending some cycles on events would be great, if OWD could :)

[foolip]

Predicting that the answer is "no not yet" my follow-up question would be where I can park the suggestion for Q4 review.

[Elchi3]

I'm still busy with WebXR docs, but unblocking mixins when I can is in scope. The top of my to-list includes mdn/browser-compat-data#11518. Let me know what other things are pressingly needed and I will try to get to it.

mdn/browser-compat-data#7545 looks like a larger effort, though (and maybe it is separate enough from mixins?). So, it would be really great if you could file that as new project for OWD to consider for Q4. You can file an issue on this repo and we can flesh it out this quarter, so it is ready to be considered in the next planning call (September 8).

[Elchi3]

In Q3 we,

• Got MDN to 75% in markdown, involving tons of cleanup PRs prior to migration
• Created all of the WebXR reference docs
• Fixed all of the mixin problems except for event related docs
• Onboarded Jean-Yves and Estelle
• Made progress on HTTP and Accessibility & ARIA docs
• Made progress on using webref for css formal syntax

Well done, team! 💯

The Q4 issue is #55. See you over there :)