Skip to content

Commit

Permalink
Merge pull request #556 from w3c/simoneonofri-sing-typos
Browse files Browse the repository at this point in the history 
[ig/security] Typos
  • Loading branch information
@simoneonofri
simoneonofri authored Jul 28, 2024
2 parents 0aad479 + 8d07a99 commit 51eab39
Showing 1 changed file with 15 additions and 14 deletions.
29 changes: 15 additions & 14 deletions 2024/ig-security.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@


<main>
<h1 id="title"><i class="todo">PROPOSED Security</i> Interest Group Charter</h1>
<h1 id="title">PROPOSED Security Interest Group Charter</h1>
<!-- delete PROPOSED after AC review completed -->

<p class="mission">The <strong>mission</strong> of the <a href="https://www.w3.org/groups/ig/security">Security Interest Group</a> is to improve Security on the Web by advising groups developing standards on how to avoid and mitigate security issues with their technologies. Security Interest Group also suggests changes to existing standards and technologies to improve the security of existing systems.</p>
Expand All @@ -85,9 +85,9 @@ <h1 id="title"><i class="todo">PROPOSED Security</i> Interest Group Charter</h1>

<!-- delete the GH link after AC review completed -->
<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <i class="todo"><a href="https://github.com/w3c/charter-drafts/blob/gh-pages/2024/ig-security.html">GitHub</a>.
on <a href="https://github.com/w3c/charter-drafts/blob/gh-pages/2024/ig-security.html">GitHub</a>.

Feel free to raise <a href="https://github.com/w3c/charter-drafts/issues/new?title=%5Big/security%5D">issues</a></i>.
Feel free to raise <a href="https://github.com/w3c/charter-drafts/issues/new?title=%5Big/security%5D">issues</a>.
</p>

<div id="details">
Expand All @@ -105,23 +105,23 @@ <h1 id="title"><i class="todo">PROPOSED Security</i> Interest Group Charter</h1>
Start date
</th>
<td>
<i class="todo">[dd monthname yyyy] (date of the "Call for Participation", when the charter is approved)</i>
[dd monthname yyyy] (date of the "Call for Participation", when the charter is approved)
</td>
</tr>
<tr id="CharterEnd">
<th>
End date
</th>
<td>
<i class="todo">[dd monthname yyyy]</i> (Start date + 2 years)
[dd monthname yyyy] (Start date + 2 years)
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Patrick Shaller (ETH Zurich)<br/>
Patrick Schaller (ETH Zurich)<br/>
Denis Roio (Dyne.org)<br/>
Tommaso Innocenti (Invited Expert)
</td>
Expand All @@ -131,7 +131,7 @@ <h1 id="title"><i class="todo">PROPOSED Security</i> Interest Group Charter</h1>
Team Contacts
</th>
<td>
<span class="todo"><a href="mailto:simone@w3.org">Simone Onofri</a></span> <i class="todo">(0.25 <abbr title="Full-Time Equivalent">FTE</abbr>)</i>
<a href="mailto:simone@w3.org">Simone Onofri</a> (0.25 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
Expand Down Expand Up @@ -241,6 +241,7 @@ <h3 id="external-coordination">External Organizations</h3>
<h2 id="participation">
Participation
</h2>

<p>To be successful, this Interest Group is expected to include Security Researchers, Threat Modeling experts, Cryptographers, Cryptoanalysts, and active Editors for each deliverable. The Chairs and Editors are expected to contribute half of a working day per week. There is no minimum requirement for other Participants.</p>
<p>Participation in discussions via mailing lists and GitHub is free, as described in <a href="#communication">Communication</a>.</p>
<p>Participation in reviews, deliverable development, and meetings requires joining the group. The group welcomes and encourages all participants with proven specific expertise, even if they do not represent a W3C Member. In that case, they should join as <a href="https://www.w3.org/invited-experts/">Invited Experts</a>. Invited Experts in this group are not granted access to Member-only information.</p>
Expand All @@ -252,19 +253,19 @@ <h2>
Communication
</h2>
<p id="public">
Technical discussions for this <i class="todo">Interest</i> Group are conducted in <a href="https://www.w3.org/policies/process/#confidentiality-levels">public</a>: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests.
The meetings themselves are not open to public participation, however.
Technical discussions for this Interest Group are conducted in <a href="https://www.w3.org/policies/process/#confidentiality-levels">public</a>: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests.
However, the meetings themselves are not open to public participation.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href=""><i class="todo">Security</i> Interest Group home page.</a>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="https://w3.org/groups/ig/security">Security Interest Group home page.</a>
</p>
<p>
Most <i class="todo">Security</i> Interest Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
Most Security Interest Group teleconferences will focus on discussion of particular specifications and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work <i class="todo">pick one, or both, as appropriate:</i> on the public mailing list <a class="todo" id="public-name" href="mailto:public-[email-list]@w3.org">public-<i class="todo">[email-list]</i>@w3.org</a> (<a class="todo" href="https://lists.w3.org/Archives/Public/public-[email-list]/">archive</a>)
<i class="todo">or</i> on <a class="todo" id="public-github" href="[link to Github repo]">GitHub issues</a>.
The public is invited to review, discuss and contribute to this work.
This group primarily conducts its technical work:</i> on the public mailing list <a id="public-name" href="mailto:public-security@w3.org">public-security@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-security/">archive</a>)
on <a id="public-github" href="">GitHub issues</a>.
The public is invited to review, discuss, and contribute to this work.
</p>
<p>
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
Expand Down

0 comments on commit 51eab39

Please sign in to comment.