Privacy Community Group Proposals

This repository is where the Privacy CG discusses proposals before they've been spun off into their on repository.

Proposal workflow

Join the group. Before making a proposal, please join the CG. This is to ensure that all contributions to our work are covered by the W3C Community Contributor License Agreement (CLA).
State your problem and make a rough proposal. File a new issue in which you state the problem you’re trying to address and how you propose to address it. This can be a very rough idea, or something quite a bit more fleshed out. Please be explicit about your requirements, use cases, and rationale.

Evaluation and refinement. As a community, we’ll discuss your proposal in the issue you raise. The Chairs may ask you to write up and iterate on an explainer. They'll help you spin up a repository for your explainer (and, eventually, your spec) to live in.
Adoption as a work item. When your proposal is sufficiently fleshed out and you and the chairs agree, the group may formally adopt your proposal as a work item. This is when the group starts to work on a spec in parallel to the explainer.

Editing and iteration. The group will iterate on the spec and explainer. We’ll discuss the idea, raise issues on it, hammer out the details, and consider feedback from any implementers who prototype the feature.
Migration to the standards track. When the work item is ready for standardization, we’ll migrate it from the CG to the most appropriate standards body (e.g. WebAppSec, the WHATWG or elsewhere).

When we spin up a repository in which you can work on an explainer and spec, we'll use our template repository as a starting base.

Please follow the WHATWG Style Guide when writing explainers and specs.

As a W3C Community Group, all work and communication within the Privacy CG is covered by the W3C Code of Ethics and Professional Conduct.