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.

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

Adding a clear incubation process and flow #7

Closed
wants to merge 6 commits into from
Closed
Changes from 2 commits
Commits
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
68 changes: 63 additions & 5 deletions charter.html
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ <h2 id=work>Work</h2>
<p>Documents for new features will be accompanied by test cases.


<h3 id=features>Feature Work</h3>
<h2 id=features>Feature Work</h2>

<p>The Community Group will seek to develop a shared understanding of
new features. In addition to improvements to feature design, the
Expand All @@ -205,17 +205,16 @@ <h3 id=features>Feature Work</h3>

<p>Experience with features might lead to Community Group Participants
concluding that the work is no longer likely to be successful. Work on
adopted features can be discontinued if the <a href=#chairs>Chairs</a>
adopted or incubated features can be discontinued if the <a href=#chairs>Chairs</a>
conclude that there is no longer <a href=#consensus>consensus</a> to
continue that work.

<p>Repositories and documents related to discontinued work will be
modified to make their status clear and may be archived.


<h3 id=adopt>Document Adoption</h3>

Community Group Participants may propose that the Community Group adopt
<p>Community Group Participants may propose that the Community Group adopt
a document. The <a href=#chairs>Chairs</a> then seek to determine
whether the document is <a href=#scope>in scope</a> for the Community Group and if
there is <a href=#consensus>consensus</a> amongst Community
Expand All @@ -235,7 +234,10 @@ <h3 id=adopt>Document Adoption</h3>
implementations.
</ul>

This judgment should be guided by documented and agreed principles.
<p>This judgment should be guided by documented and agreed principles.

<p>The group must reach consensus to adopt a document whether or not it comes
in via the incubation process.

<p>The Community Group will adopt a document that records the principles by
which features are judged. During development of this document, the principles
Expand All @@ -251,6 +253,62 @@ <h3 id=adopt>Document Adoption</h3>
<p>Chairs may provide resources, such as repositories, for potential new work or
work that is related to the mission of the Community Group.

<h3 id=incubate>Document Incubation</h3>

<p>Community Group Participants may propose that the Community Group incubate
a document. The <a href=#chairs>Chairs</a> then seek to determine
whether the document is <a href=#scope>in scope</a> for the Community Group and if
there is <a href=#consensus>consensus</a> amongst Community
Group Participants that the work is of interest to this group and, while not necessarily
the basis for a Community Group Report, could eventually develop into a document that
would be a good basis for such a report and therefor is of interest to facilitate discussion
AramZS marked this conversation as resolved.
Show resolved Hide resolved
and work on.

<p>The Community Group recognizes that the incubation process has other venues
such as <a href="https://wicg.github.io/admin/charter.html" target="_blank">WICG</a>.
However, we also see that there is a significant interest in private ad technology-related
proposals that involves stakeholders with little overlap with the existing WICG constituencies
and it would be useful for organizing effort and clarity to provide centralization of these
discussions specifically under this Community Group.

<p>The incubation process acknowledges that not all proposals under incubation may result in
interoperable features or a Community Group Report and that entry into the incubation process
neither implies nor requires broad support by all implementers, but is of interest to
participants involved in implementing features.

<p>For incubation of documents that propose new features, Community Group
Participants also need to reach consensus that the features:

<ul>
<li>address a genuine need for web users, for creators of
advertising-supported websites, for advertisers, or to support an existing need that may
be impaired by advancing privacy properties;
<li>provides or could provide acceptable privacy properties for users;
<li>provides an acceptable web experience for users;
AramZS marked this conversation as resolved.
Show resolved Hide resolved
</ul>

<p>This judgment should be guided by documented and agreed principles.

<p>The Community Group will incubate a document that records the principles by
which features are judged. During development of this document, the principles
it contains might not have consensus. The Community Group will seek consensus
on principles and clearly distinguish which principles have attained consensus.
These advertising-specific principles will be based on or reference work in the
<a href=https://www.w3.org/Privacy/IG/>Privacy Interest Group (PING)</a> and
<a href=https://github.com/w3ctag/privacy-principles/>Technical Architecture
Group (TAG)</a> that defines generic principles.

<p>The Community Group facilitates but does not prioritize time for incubation work.

<p>Chairs may provide resources, such as repositories, for potential new work or
work that is related to the mission of the Community Group.

<p>If a document enters the incubation stage of work it is expected that it will be
clearly marked on the top of the base README or on the document itself, making it
clear that this is a work at the incubation stage and is not yet considered an
output of this group.

<p>All documents under incubation are covered under the Contributed License Agreement.

<h2 id=process>Process</h2>

Expand Down