[name] Maintenance Working Group Charter

The mission of the [name] Maintenance Working Group is to maintain [list the specifications].

Join the [name] Maintenance Working Group.

Start date [dd monthname yyyy] (date of the "Call for Participation", when the charter is approved)
End date 30 September [yyyy]
Charter extension See Change History.
Chairs [chair name] (might be Team Contact as well)
Team Contacts [team contact name] (up to 0.05 FTE)
Meeting Schedule Teleconferences: none
Face-to-face: none

Scope

The Working Group is only intended to maintain the errata pages and update the specifications listed in its deliverables section.

Only changes of class 1, 2, and 3 are in the scope of the Maintenance Working Group.

Out of Scope

Changes that add a new functionality, element, etc. are out of scope, and will not be addressed by this [name] Maintenance Working group.

Success Criteria

In order to advance to Proposed Recommendation, each specification is expected to have at least two independent implementations of any substantive errata.

Deliverables

Normative Specifications

The [name] Maintenance Working Group will deliver Edited Recommendations for the following specifications:

[recommendation title]

[specification abstract].

Other Deliverables

The following non-normative documents will be maintained or created:

This Maintenance Working Group will not adopt new proposals. If the Group wishes to add new Recommendation-track deliverables or new features then it can no longer be a Maintenance Working Group and a new Working Group would need to be chartered. If the Director may issue a Call for Participation for a Working Group (including a new Maintenance Working Group) that contains one or more of the deliverables within its scope, the Director must close this Maintenance Working Group.

Coordination

This Maintenance Working Group must show that the changes to a Recommendation have received wide review. Invitation for substantive errata review must be issued during each major standards-track document transition. Editorial changes to a Recommendation require no technical review of the proposed changes.

For all specifications, this Maintenance Working Group may seek horizontal review for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the TAG.

Participation

To be successful, this [name] Maintenance Working Group is expected to have an active editor for each of its deliverables, including ideally representatives from the key implementors of those specifications. The specification editors are expected to contribute one half of a working day per months towards the Maintenance Working Group. There is no minimum requirement for other Participants.

The group encourages questions, comments and issues as described in Communication.

Communication

Technical discussions for this Maintenance Working Group are conducted in public. Technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Editor's Drafts of specifications will be developed on a public repository, and may permit direct public contribution requests.

This Maintenance Working Group will appear on the list of Maintenance Working Groups.

This Maintenance Working Group does not have teleconferences or face-to-face meetings.

This group primarily conducts its technical work on GitHub issues. The public is invited to review, discuss and contribute to this work.

Decision Policy

This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 3.3). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.

However, if a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote, and record a decision along with any objections.

The Group must not make any resolution in face-to-face meeting or teleconference. A call for consensus (CfC) will be issued for document transitions, with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised in the GitHub repository by the end of the response period, the resolution will be considered to have consensus as a resolution of the Maintenance Working Group.

All decisions made by the group should be considered resolved unless and until new information becomes available, or unless reopened at the discretion of the Chair or the Director.

This charter is written in accordance with the W3C Process Document (Section 3.4, Votes), and includes no voting procedures beyond what the Process Document requires.

Patent Policy

This Working Group operates under the W3C Patent Policy (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.

Licensing

This Maintenance Working Group will use the document license(s) associated with the W3C Recommendations listed as deliverables.

About this Charter

This charter has been created according to section 5.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.

As long as maintenance is needed and active for the deliverables and no other Working Group takes on any of the deliverables, the Director is expected to grant one-year charter extensions.

Charter History

Note:Display this table and update it when appropriate. Requirements for charter extension history are documented in the Charter Guidebook (section 4).

The following table lists details of all changes from the initial charter, per the W3C Process Document (section 5.2.3):

Charter Period Start Date End Date
Initial Charter [dd monthname yyyy] [dd monthname yyyy]
Charter Extension [dd monthname yyyy] [dd monthname yyyy]
Rechartered [dd monthname yyyy] [dd monthname yyyy]