Introduction

The W3C Process describes the lifecycle of chartered groups. At a high level, W3C closes a work Group once it has completed its work.

Normal closure

Sometimes, after successful completion, the Group is left open to perform maintenance; other times, it is closed and a Community Group performs this function.

Early closure

Exceptionally, a group may be closed before it has completed its work:

Insufficient resources
There is insufficient developer or implementer interest to sustain the group, and the Team proposes to close it.
PAG outcome
A Patent Advisory Group has determined that essential claims exist which cannot be circumvented; so it will not be possible to create a Recommendation which can be freely implemented under the W3C Royalty-Free Patent Policy; thus, it is proposed that the group should be closed.
Considered detrimental
The AB or the TAG has determined that continued operation of the group would be harmful to the Web or to W3C; thus, it is proposed that the group should be closed.
Finished early
All the Recommendation-track deliverables have been completed early, and no other work in scope of the current charter remains to be done. The options are to just let the charter run until it expires, or to formally close the group early.

A proposal to close a Group before the end of its chartered term must be explained. An Advisory Committee review takes place and, if that confirms that the group should be closed, a W3C Decision announces closure of the group.

Note that, if the Group has Recommendation-track specifications in development, and they have not yet reached W3C Recommendation status, closing the group terminates Disclosure Obligations for those specifications.

There is Team-only documentation of the detailed steps for closing a group.

Feedback is to @w3c/guidebook and is welcome on GitHub