This repo is for administration of the community group.

• Home page - wicg.io - includes links to active incubations.
• Transferring a repo to WICG
• Charter
• Intent to migrate
• State of incubations

Instructions for connecting to Gitter over IRC.

• See the Proposals repo.
• See all the WICG repositories.

The following is given as guidance. It's is not a requirement for starting work on a proposal.

Please join the WICG before submitting new proposals.

1. Join the group: Before bringing the above to the group's attention, join the community group, which means you agree with the terms of the W3C's Community Contributor License Agreement (CLA). It's critical if you first join the group or else key members won't be able to review or discuss your proposal.
2. State the problem, make a rough proposal: Write an informal description of a limitation with the Web platform and post it as an issue to the proposals repository. This should be something you believe is missing in the platform and would make the lives of developers significantly easier if it were added. It can also be something you've noticed is a recurring development pattern which would benefit from standardization. If you have a rough proposal for a solution, spinning up a public GitHub repo from your own account is probably the best way to disseminate it. It's fine if your proposal is totally rough and informal - include code examples, diagrams, or whatever you think helps explain the problem best. Be sure to examine use cases. This can be informally in the proposals repository or you create an "explainer" document. Such a document can help prove to the community that there is indeed a need for a solution that needs standardization (see the Use Cases and Requirements for Standardizing Responsive Images, for example).
3. Evaluation: As a community, we will use the proposals repository to evaluate interest and ask for potential editors for the proposal. As soon as sufficient interest is shown in the issue (notably from potential implementers), the WICG chairs will enable a team of editors to manage the proposal, and those team members can move ownership of the GitHub repo (if any) to WICG. We will expect all previous contributions to the proposal to have been made by WICG members, or will need explicit CLAs from other contributors - ask the chairs for assistance if needed.
4. Editing and Refinement: The community should incubate and refine the proposal, through discussion on GitHub issues on the repo until they feel the proposal has sufficient support and resolution to move to an appropriate Working Group; at that point, the editing team should contact the chairs, and the chairs will help do an "intent to migrate": where we move the spec to a W3C Working group to seek royalty free licensing commitments from W3C members (you know, the "free" in "free and open"). As part of that transition, the WICG should seek an FSA commitment from any contributors to the incubation that choose not to join the WG to which it has been transitioned; this will provide the broadest possible IP coverage.
5. (Bonus points) Implementation: Help turn the ideas from words on paper into working features in modern browsers.

If you need to be added as a "collaborator" on GitHub (to manage a Github repo, be able to close issues, etc), please open an issue in the admin repo asking for permission. One of the Chairs will add you.

As a W3C Community Group, the WICG operates under the W3C's Code of Ethics and Professional Conduct.

W3C is committed to maintain a positive work environment. This commitment calls for a workplace where participants at all levels behave according to the rules of the following code. A foundational concept of this code is that we all share responsibility for our work environment.

If you experience any violations to the above by any participant, please contact the Chairs or the W3C Head of Communications (Coralie Mercier). To make amendments to the W3C's Code of Conduct, please post to the W3C Positive Work Environment mailing list, or email Coralie Mercier directly.