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.

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

distinguish standards-track drafts vs proposals #684

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

distinguish standards-track drafts vs proposals #684

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cd33fba
distinguish standards-track drafts vs proposals
tantek Sep 1, 2022
01a19cb
incorporate suggestions from @jgraham
tantek Sep 1, 2022
267eced
add abbr to expand IPR
tantek Sep 1, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,12 @@ _See [the dashboard](https://mozilla.github.io/standards-positions/) for Mozilla
## What is this Repository?

This repo is where [Mozilla](https://mozilla.org/) decides and documents what it thinks about
emerging technical specifications for the Web. Typically they're draft documents in the
[IETF](https://ietf.org/), [W3C](https://w3.org/) (including the [WICG](https://wicg.github.io/)),
[WHATWG](https://whatwg.org/), and [Ecma TC39](https://github.com/tc39), but they could come from
elsewhere too.
emerging technical specifications for the Web. Typically they're standards-track drafts in the
[IETF](https://ietf.org/), [W3C](https://w3.org/),
[WHATWG](https://whatwg.org/), and [Ecma TC39](https://github.com/tc39),
but they could come from elsewhere such as proposals
from W3C Community Groups (like [WICG](https://wicg.github.io/))
or other community incubation efforts with well-understood IPR terms.
tantek marked this conversation as resolved.
Show resolved Hide resolved

Having a clear Mozilla position on these specifications helps us align our thinking and communicate
it clearly to these standards bodies, as well as other browsers.
Expand Down