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

Drop e2e #649

Merged
merged 1 commit into from
Apr 3, 2024
Merged

Drop e2e #649

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 0 additions & 6 deletions admin/webappsec-charter-2023.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -556,11 +556,6 @@ <h3>
following documents:
</p>
<dl>
<dt class="spec"><a href="https://github.com/w3c/webappsec/blob/main/meetings/2023/2023-09-14-TPAC-minutes.md#end-to-end-encryption">End-to-End Encryption email</a></dt>
<dd>
This idea would allow end-to-end encryption of emails, without exposing key content,
in Web applications.
</dd>
<dt class="spec"><a href="https://github.com/w3c/webappsec/blob/main/meetings/2023/2023-09-15-TPAC-minutes.md#source-code-transparency-sketch">Source Code Transparency</a></dt>
<dd>
The goal would be to have a mechanism to verify that the source code of a web app
Expand Down Expand Up @@ -1015,7 +1010,6 @@ <h3>
<td>
<p>Moved all specs to snapshot (evergreen) publication.</p>
<p>Added new Rec track deliverables:
End-to-End Encryption email,
Source Code Transparency,
Passkey Endpoints Well-Known URL,
Securer Contexts.</p>
Expand Down