w3c / w3c/process

Enhancing the W3C REC Update Process for Greater Efficiency and Engagement

Open
#866 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
262
Forks
194
PR merge metrics
No merged PRs in 30d

Description

The updatable REC process at the W3C has historically been a source of significant frustration due to its complexity and the excessive manual work required from editors. This issue aims to address these concerns by proposing a series of alternatives that could potentially streamline or replace the current process.

Here are the challenges and a variety of proposed solutions for discussion at TPAC 2024:

Core Challenges
  1. Complex Manual Markup: The requirement for detailed manual markup (e.g., <ins>, <del>, specific classes) is not only time-consuming but also prone to errors, frustrating many editors.
  2. Detailed Change Tracking: Extensive documentation and linking for each change add unnecessary overhead, often leading to mistakes and confusion.
  3. Inflexible Class System: The rigid classification system complicates the editing process and increases the potential for errors.
Proposed Alternatives
  • Enhanced Automated Tooling: Develop tools that automatically generate the necessary markup from simpler inputs, reducing the manual burden on editors.
  • Streamline the Existing Process: Simplify the current markup requirements to lower the entry barrier and reduce the time spent on updates.
  • Educational Support: Increase training and support for editors to improve efficiency and understanding of the process.
Additional Strategic Alternatives
  • Discontinue the Updatable REC Process: While this process has proven to be effective from an Intellectual Property Rights (IPR) perspective, ensuring compliance and protection across contributions, it is clear that it is not fit for purpose from an editorial standpoint. The excessive manual labor and complexity required have made it impractical for editors, who often face significant difficulties in navigating and implementing the required markup and procedural demands. This has led to a process that, despite its theoretical benefits, ends up being overly burdensome in practice. We need to consider phasing it out in favor of a system that better aligns with the working realities of editors while still maintaining the necessary IPR protections.
  • Discourage Use of the Current Process: Officially recommend that the current updatable REC process be used only when absolutely necessary, due to its complexity and the high overhead involved.
  • Introduce a 'Living Recommendation' Model: Adopt a model similar to the WHATWG living standards, which allows for more dynamic and less formal updates. This approach would involve continuous updates without the need for detailed version tracking and complex markup, addressing many of the current frustrations.

As documented in w3c/w3process#589,
these issues have long plagued the community, leading to widespread
dissatisfaction and calls for change. This discussion aims to transform the REC update process into a more practical and user-friendly system, enhancing the efficiency and satisfaction of all stakeholders involved in maintaining W3C standards.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the alternatives in this issue and the referenced w3c/w3process#589 discussion. A useful outcome would be an agreed direction for the updatable REC process, with a concrete proposal for streamlining, replacing, or discouraging it; no implementation file or test is identified here.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.