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

Jump to bottom

Fix #9 and rename Work Item to Specification. #23

Closed
wants to merge 4 commits into from
Closed

Fix #9 and rename Work Item to Specification. #23

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ddf2091
Since Work Items are Specifications, let's call them that.
hober Apr 2, 2020
53308b4
Don't show an extraneous hash.
hober Apr 9, 2020
2d9da77
s/work item/specification/ on the home page too.
hober Apr 9, 2020
e8d2ac9
Try to address #9. (#25)
hober Apr 14, 2020
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
161 changes: 83 additions & 78 deletions charter.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,9 +143,9 @@ <h2 id=chairs>Chairs</h2>
<li>ensuring the group adheres to its <a href=#process>Process</a>,
<li>judging features or ideas as in or <a href=#out-of-scope>out</a>
of <a href=#scope>scope</a>,
<li>focusing the group's limited time on the Proposals and Work Items
most likely to positively impact privacy on the web via wide
implementation and adoption,
<li>focusing the group's limited time on the Proposals and
Specifications most likely to positively impact privacy on the web via
wide implementation and adoption,
<li>moderating the group's discussions, whatever the forum (GitHub,
mailing lists, face to face, etc.),
<li>running teleconferences and
Expand Down Expand Up @@ -220,8 +220,8 @@ <h3 id=chair-selection>Chair Selection</h3>
<h2 id=proposals>Proposals</h2>

<p>A <dfn>Proposal</dfn> is an idea brought to the Community Group for
consideration and potential adoption as a <a href=#work-items>Work
Item</a>.
consideration and potential adoption as
a <a href=#specifications>Specification</a>.

<p>Any Community Group Participant may make a Proposal by filing
<a href=https://github.com/privacycg/proposals/issues>an issue</a> in
Expand All @@ -248,7 +248,8 @@ <h2 id=proposals>Proposals</h2>
<p>Proposals begin as or evolve into
<a href=https://w3ctag.github.io/explainers>explainers</a> which
describe the proposed changes to the web platform, and which may serve
as the basis for a Work Item (should the Proposal be adopted as one).
as the basis for a Specification (should the Proposal be adopted as
one).

<p class=note>While explainers are Community Group Reports as defined in
the <a href=https://www.w3.org/community/about/agreements/>Community and
Expand All @@ -259,22 +260,23 @@ <h2 id=proposals>Proposals</h2>
the Chairs (if, for example, the Chairs deem the Proposal to
be <a href=out-of-scope>out of scope</a> or the Proposal fails to gain
sufficient <a href=#implementer>implementer</a> support to be adopted as
a Work Item). If such a Proposal has a dedicated repository, the Chairs
should take steps to ensure the data is not lost, perhaps by transferring
the repository to a different organization or user, or by archiving it.
a Specification). If such a Proposal has a dedicated repository, the
Chairs should take steps to ensure the data is not lost, perhaps by
transferring the repository to a different organization or user, or by
archiving it.

<h2 id=work-items>Work Items</h2>
<div id=work-items><!-- keep old links working --></div>
<h2 id=specifications>Specifications</h2>

<p>The Community Group may produce <dfn>Work Items</dfn>—Specifications
as defined in the
<a href=https://www.w3.org/community/about/agreements/>Community and
Business Group Process</a>—a special kind of Community Group Report
<p>The Community Group may produce <dfn>Specifications</dfn>—as defined
in the <a href=https://www.w3.org/community/about/agreements/>Community
and Business Group Process</a>—a special kind of Community Group Report
whose purpose is to enable interoperability between independent
implementations of the features it defines. Each Work Item has one
implementations of the features it defines. Each Specification has one
or more <a href=#editors>Editors</a>, who are appointed by
the <a href=#chairs>Chairs</a>.

<p>The current set of Work Items of the Community Group are:
<p>The current set of Specifications of the Community Group are:

<table>
<thead>
Expand All @@ -294,45 +296,47 @@ <h2 id=work-items>Work Items</h2>
</table>

<p>This list will be kept <a href=#amendments>updated</a> by the Chairs
to reflect the current set of Work Items of the Community Group.
to reflect the current set of Specifications of the Community Group.

<p>The Chairs may add Work Items, but must not add Work Items which lack
the support of at least two <a href=#implementer>implementers</a>.
<p>The Chairs may add Specifications, but must not add Specifications
which lack the support of at least
two <a href=#implementer>implementers</a>.

<p>Each Work Item should be accompanied by an explainer describing its
proposed changes to the web platform. Editors should keep the Work
Item's explainer up-to-date with the Work Item as it evolves.
<p>Each Specification should be accompanied by an explainer describing
its proposed changes to the web platform. Editors should keep the
Specification's explainer up-to-date with the Specification as it
evolves.

<p class=note>Since Work Items typically begin life as a Proposal before
being formally adopted, they usually start out with an explainer.
<p class=note>Since Specifications typically begin life as a Proposal
before being formally adopted, they usually start out with an explainer.

<p>When a Work Item's Editors deem the Work Item ready for migration,
they will notify the Chairs. The CG may produce a Final Community Group
Report at this time. The Editors and Chairs will identify the best
destination standards body or bodies, and will then work with those
bodies to successfully migrate the Work Item.
<p>When a Specification's Editors deem the Specification ready for
migration, they will notify the Chairs. The CG may produce a Final
Community Group Report at this time. The Editors and Chairs will
identify the best destination standards body or bodies, and will then
work with those bodies to successfully migrate the Specification.

<p class=note>When migrated to the standards track, Work Items might
<p class=note>When migrated to the standards track, Specifications might
become standalone specifications, they might be integrated into one or
more existing specifications, or they might result in a combination of
these options.

<p>The Chairs may remove Work Items. The Chairs
must <a href=#notices>notify the group</a> of the removal of Work Items,
and this notice must include rationale. Some possible reasons for
removing a Work Item are:
<p>The Chairs may remove Specifications. The Chairs
must <a href=#notices>notify the group</a> of the removal of
Specifications, and this notice must include rationale. Some possible
reasons for removing a Specification are:

<ul>
<li>because the Work Item has been migrated elsewhere
<li>because the Work Item no longer has the support of
<li>because the Specification has been migrated elsewhere
<li>because the Specification no longer has the support of
multiple <a href=#implementer>implementers</a> and is unlikely to regain
it
<li>because the Work Item no longer has an <a href=#editors>Editor</a>
and a replacement cannot be found
<li>because the Specification no longer has
an <a href=#editors>Editor</a> and a replacement cannot be found
</ul>

<p>The Chairs should take steps to ensure the repositories of removed
Work Items are not lost, perhaps by transferring the repository to a
Specifications are not lost, perhaps by transferring the repository to a
different organization or user, or by archiving it.

<h2 id=coordination>Coordination</h2>
Expand All @@ -345,10 +349,10 @@ <h2 id=coordination>Coordination</h2>
<a href=https://www.ecma-international.org/>Ecma</a>,
<a href=https://ietf.org/><abbr
title="Internet Engineering Task Force">IETF</abbr></a>, and elsewhere,
and will migrate <a href=#work-items>Work Items</a> to them when they’re
ready for the standards track. Groups most likely to be close partners
are listed below, but this group is expected to coordinate with other
groups as relevant.
and will migrate <a href=#specifications>Specifications</a> to them when
they’re ready for the standards track. Groups most likely to be close
partners are listed below, but this group is expected to coordinate with
other groups as relevant.

<h3 id=w3c-coordination>W3C Groups</h3>

Expand All @@ -357,21 +361,21 @@ <h3 id=w3c-coordination>W3C Groups</h3>
(PING)</a>
<dd>This group will coordinate with PING and will take into
consideration outputs of PING when
evaluating <a href=#proposals>Proposals</a> and <a href=#work-items>Work
Items</a>.
evaluating <a href=#proposals>Proposals</a>
and <a href=#specifications>Specifications</a>.

<dt><a href=https://www.w3.org/2011/webappsec/>Web Application Security
Working Group (WebAppSec)</a>
<dd>WebAppSec is expected to be a destination for transitioning CG Work
Items to the standards track.
<dd>WebAppSec is expected to be a destination for transitioning
Specifications to the standards track.

<dt><a href=https://www.w3.org/community/wicg/>Web Platform Incubator
Community Group (WICG)</a>
<dd>WICG is expected to be a major source of Work Items for this
<dd>WICG is expected to be a major source of Specifications for this
group.
<p class=note>Only privacy-related WICG proposals which have the support
of at least two <a href=#implementer>implementers</a> are eligible for
this group to take up as Work Items.
this group to take up as Specifications.
</dl>

<h3 id=external-coordination>External Organizations</h3>
Expand Down Expand Up @@ -400,8 +404,8 @@ <h2 id=process>Process</h2>
Professional Conduct</a>.

<p>Contributions to <a href=#proposals>Proposals</a>
and <a href=#work-items>Work Items</a> can only be made by Community
Group Participants who have agreed to the
and <a href=#specifications>Specifications</a> can only be made by
Community Group Participants who have agreed to the
<a href=https://www.w3.org/community/about/agreements/cla/>W3C Community
Contributor License Agreement (CLA)</a>.

Expand All @@ -417,9 +421,9 @@ <h2 id=process>Process</h2>
<h3 id=editors>Editors</h3>

<p><dfn>Editors</dfn> are responsible for the technical content of
their <a href=#work-items>Work Item</a> and have sole authority to
modify the Work Item (though their decisions may be overridden by the
<a href=#chairs>Chairs</a>; see <a href=#decisions>below</a>).
their <a href=#specifications>Specification</a> and have sole authority
to modify the Specification (though their decisions may be overridden by
the <a href=#chairs>Chairs</a>; see <a href=#decisions>below</a>).

<p>Editors are responsible for
<ul>
Expand All @@ -430,13 +434,13 @@ <h3 id=editors>Editors</h3>
<li>helping to manage the corresponding tests.
<li>ensuring (together with implementers) implementations follow the
requirements and vice versa. (The “don’t write fiction” rule.)
<li>ensuring contributions to their Work Item are only made by
<li>ensuring contributions to their Specification are only made by
Community Group Participants who have agreed to the
<a href=https://www.w3.org/community/about/agreements/cla/>W3C Community
Contributor License Agreement (CLA)</a>, and
<li>ensuring that there are no unresolved substantive objections from
Community Group Participants before merging contributions or otherwise
modifying their Work Item.
modifying their Specification.
</ul>

<p>Changes of an editorial nature can be made, accepted, or rejected by
Expand All @@ -446,7 +450,7 @@ <h3 id=editors>Editors</h3>
consider and respond to comments, suggestions, and objections from
Participants and the public.

<p>Editors may commit changes to their Work Items without further
<p>Editors may commit changes to their Specifications without further
review, provided they adhere to the requirements in this document.

<h3 id=work-mode>Work Mode</h3>
Expand All @@ -464,13 +468,13 @@ <h3 id=work-mode>Work Mode</h3>
<a href=https://github.com/privacycg/.github/blob/master/SECURITY.md>posted
on GitHub</a> and kept up-to-date.

<p>Any change to a <a href=#work-items>Work Item</a> that represents a
feature addition must have the support of at least
<p>Any change to a <a href=#specifications>Specification</a> that
represents a feature addition must have the support of at least
two <a href=#implementer>implementers</a>.

<p>For any change that removes a feature from a Work Item, the feature
being removed must either be not widely implemented, or must be in the
process of being removed from implementations.
<p>For any change that removes a feature from a Specification, the
feature being removed must either be not widely implemented, or must be
in the process of being removed from implementations.

<h4 id=meetings>Meetings</h4>

Expand All @@ -488,8 +492,8 @@ <h4 id=meetings>Meetings</h4>
<h3 id=decisions>Decision Policy</h3>

<p><a href=#editors>Editors</a> must respond to substantive issues
raised on their <a href=#work-items>Work Item</a> by Community Group
Participants. Editors have discretion to resolve issues based on
raised on their <a href=#specifications>Specification</a> by Community
Group Participants. Editors have discretion to resolve issues based on
available information.

<p>To afford asynchronous decisions and organizational deliberation, any
Expand Down Expand Up @@ -540,24 +544,24 @@ <h3 id=decisions>Decision Policy</h3>
possible, be consistent with our goal to increase user privacy and align
with <a href=#implementer>implementer</a> majority.

<p>Work Items should not make references to or rely on specific browser
engine implementation details.
<p>Specifications should not make references to or rely on specific
browser engine implementation details.

<h4 id=appeals>Appeals</h4>

<p>Community Group Participants may raise substantive issues for
resolution by the <a href=#chairs>Chairs</a>.

<p>To raise an issue on a <a href=#work-items>Work Item</a> for review
by the <a href=#editors>Editors</a> and other Community Group
<p>To raise an issue on a <a href=#specifications>Specification</a> for
review by the <a href=#editors>Editors</a> and other Community Group
Participants, a Community Group Participant must:

<ol>
<li>Identify the issue clearly (technical problem, interoperability
issue, inconsistency with the
<a href=https://www.w3.org/2001/tag/doc/ethical-web-principles/>W3C
TAG Ethical Web Principles</a>, etc.) and recommend a solution;
<li>Post the issue for review in the Work Item’s repository; and
<li>Post the issue for review in the Specification’s repository; and
<li>Endeavor to resolve the issue with the Editors or in concert with
other Community Group Participants.
</ol>
Expand Down Expand Up @@ -587,19 +591,19 @@ <h2 id=patentpolicy>Patent Policy</h2>
with the following understanding: W3C will seek and expect an
organizational commitment under the CLA starting with the individual’s
first request to make a contribution to a
group <a href=#work-items>Work Item</a>.
group <a href=#specifications>Specification</a>.

<h2 id=licensing>Licensing</h2>

<p>Work Items of this Community Group will use the
<p>Specifications of this Community Group will use the
<a href=http://www.w3.org/Consortium/Legal/2015/copyright-software-and-document>W3C
Software and Document License</a>, unless
the <a href=#editors>Editors</a> expect the <a href=#work-items>Work
Item</a> to transition to a standards body which uses a different
license. In such cases, the Editors may use the license of the target
standards body.
the <a href=#editors>Editors</a> expect
the <a href=#specifications>Specification</a> to transition to a
standards body which uses a different license. In such cases, the
Editors may use the license of the target standards body.

<p class=example title="Example: HTML Pull Request">A Work Item
<p class=example title="Example: HTML Pull Request">A Specification
expected to end up as a pull request on the
<a href=https://html.spec.whatwg.org>HTML Living Standard</a> could be
licensed under the
Expand All @@ -610,8 +614,9 @@ <h2 id=amendments>Amendments to this Charter</h2>

<p>This Charter may be amended at any time by unanimous consent of the
<a href=#chairs>Chairs</a>. The Chairs will periodically update this
Charter to reflect the addition and removal of <a href=#work-items>Work
Items</a>, <a href=#editors>Editors</a>, and Chairs.
Charter to reflect the addition and removal
of <a href=#specifications>Specifications</a>, <a href=#editors>Editors</a>,
and Chairs.

<p class=note>Per the
<a href=https://www.w3.org/community/about/agreements/>Community and
Expand Down