Skip to content

Issues: w3ctag/explainer-explainer

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.

Sign up for GitHub

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

18 Open 0 Closed
18 Open 0 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Optionality of sections is not clear to proposers
#1 opened Mar 5, 2025 by matatk
Optional section on roadmap (future version plans) for the spec
#2 opened Mar 5, 2025 by matatk
Terminology: "Non-goals" meaning
#3 opened Mar 4, 2025 by matatk
1
Discuss involving participants from multiple skill sets and global locations in the explainer
#4 opened Jan 29, 2025 by csarven
Discuss the ideal granularity for explainers
#5 opened Jan 27, 2025 by jyasskin
1
Discuss the lifecycle of explainers
#6 opened Jan 27, 2025 by jyasskin
2
Update the WebIDL guidance for explainers
#9 opened Jan 27, 2025 by jyasskin
1
Explain why to focus on the end-user's need, and/or moderate that advice
#7 opened Jan 27, 2025 by jyasskin
Explain why to write an explainer
#8 opened Jan 27, 2025 by jyasskin
Suggest linking to developer-facing materials or research
#11 opened Jan 27, 2025 by jyasskin
Ask for multi-stakeholder review in the Explainer Explainer
#10 opened Jan 27, 2025 by jyasskin
1
Consider turning the Explainer Explainer into a Note
#13 opened Jan 24, 2025 by jyasskin
Explainer template needs to make it clear you don't need to fill out everything for every review
#12 opened Aug 3, 2023 by torgo
@torgo
Explainer explainer should explicitly encourage folks to write explainers in plain text or markdown in their spec repro & discourage folks from writing explainers in tools like Google Docs enhancement New feature or request
#14 opened Jan 26, 2021 by hober
1
2
IDL in explainers?
#15 opened Jun 24, 2020 by alice
Explainers should be written for a general audience
#16 opened Mar 16, 2020 by alice
@cynthia @atanassov
1
Explainer explainer should more strongly encourage authors to surface security and privacy considerations
#17 opened Dec 18, 2019 by hober
@jyasskin
4
Add Section in Template for Synergy/Alignments?
#18 opened Nov 27, 2018 by ChristopherA
1
ProTip! Exclude everything labeled bug with -label:bug.