Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2022 Report Outline #43

Closed
4 tasks done
thescientist13 opened this issue Aug 21, 2022 · 1 comment · Fixed by #53, #59 or #61
Closed
4 tasks done

2022 Report Outline #43

thescientist13 opened this issue Aug 21, 2022 · 1 comment · Fixed by #53, #59 or #61

Comments

@thescientist13
Copy link
Collaborator

thescientist13 commented Aug 21, 2022

From our most recent meeting, I believe we came to a consensus on what the report structure for this year would be

  1. I) Introduction - Motivations / Aspirations (can re-reuse existing text)
  2. II) Browser Parity - Specs that just need that one final implementor to obtain ubiquitous cross-browser support. Will focus on the open questions for each one.
    • FACE
    • Constructible Style Sheets
    • CSS Modules
    • Imperative slots
  3. III) Spec Alignment - Key specs we hope we to get cross-implementor buy-in on
    • Aria
    • Scoped Registries
    • Declarative Shadow DOM
  4. IV) Appendix - All the specifications (any particular order?) - see 2022 Appendix Backlog #44

I figure we can use this a top level tracking ticket to update the report with each section, so maybe multiple folks could help put it all together.

For reference, here is the wiki for putting together SessionIdeas for TPAC.


Somewhat related maybe, but what about issues still open from last years report? Should we close them out and / or port them over to this year's report instead, if applicable?

@thescientist13 thescientist13 changed the title 2022 Report Structure 2022 Report Outline Aug 21, 2022
@thescientist13 thescientist13 pinned this issue Aug 21, 2022
@thescientist13
Copy link
Collaborator Author

thescientist13 commented Aug 21, 2022

Also not sure if we want to keep this "ToC" at the top for handy reference? I think it could be useful, but if we do, maybe we scrub the Priority column from it?
Screen Shot 2022-08-21 at 5 35 09 PM

Not sure what order in the document it should come in though, specifically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant