Summary

  • W3C's second Open Source Program pilot is a WebMCP polyfill. W3C says it could phase out gradually if the specification advances and interoperable native browser implementations emerge.
  • The Community Group launched in October to design a full program for mid-2028, but its charter expressly excludes selecting pilots. Current published policies assign hosting, resources, brand and funding decisions to W3C staff.

The cleverest part of this launch is the off switch

W3C announced the WebMCP polyfill pilot on 27 October with a modestly practical list: publish an npm package, support lifecycle events and declarative use, and keep the code aligned with the developing specification and web-platform tests. Its most useful promise is that it need not become permanent. If the specification moves through the standards track and browsers acquire interoperable native implementations, W3C says the polyfill can be phased out gradually. The two conditions are doing work. A progressing spec without browser parity leaves users needing code; browser experiments without an agreed spec leave another compatibility problem.

The software has a route out. The institution has a route in progress. W3C's first pilot arrived in September: Can I VC?, a verifiable-credentials dashboard contributed by W3C Member Digital Bazaar. The second pilot is a different kind of object, an implementation bridge rather than a status dashboard. Both now occupy a program whose final governing structure is being designed after the projects have entered. That order gives the pilots real code and real users before the eventual program committee exists.

The Community Group announced on 21 October is supposed to help build a full Open Source Program by mid-2028. Joining does not require W3C Membership. Its charter gives it a broad assignment: study project scope and lifecycle, status changes, dispute escalation, donations, security posture, licensing and the possible constitution of a program committee. It expects a successor governing body when the full program launches. That is serious design work, with a clock and a public discussion channel.

Then comes the sentence that determines today's power: the group does not decide which pilots join the program. W3C staff will keep it informed of pilot progress. The difference between being informed and admitting a project is the difference between reviewing the guest list and holding the door. It is an explicit allocation, not a scandal smuggled into a footnote. It also makes it impossible to describe a new pilot as having been selected by the community simply because a community group now exists.

A provisional constitution with a working keyring

The program's published general policies spell out what “W3C” means when it makes a decision: W3C Staff. They do not specify how management delegates particular decisions inside the staff. The project lifecycle section says a fuller definition is still in progress. Staff monitor project health and can work with a weakening project on recovery. Staff decide whether to stop hosting, responsibly wind down or export a project, and whether to restart a discontinued one. W3C also controls project intellectual property, logos, domains, its own infrastructure, staff time and brand use.

Those powers are not administrative wallpaper. For a developer, a project's license and repository may be visible, while its future as a W3C-hosted project depends on access to staff time, hosting, legal stewardship and the W3C name. A shutdown can move the code elsewhere; it can also break the continuity that attracted contributors. An appeal route matters most when resources run thin, because “project health” and “minimum resource requirements” then become decisions about whose work keeps its institutional address.

Money follows the same map. W3C's policy says the organisation will decide whether to accept cash and in-kind support, involve staff early in discussions with possible supporters, and seek to separate contributions from direct control of project strategy or technical decisions. It authorizes reserving 20% of contributions for program expenses and promises regular general reporting and annual audit. That is an expense authority, not a report that either pilot has paid a 20% levy. The interesting question is who publishes the allocation and the conditions attached to support before a project becomes dependent on it.

There is a defensible reason for W3C to retain these keys during a pilot. It takes on legal, brand and operational responsibilities when it hosts code. The current documents say so, and they give the Community Group the job of designing a more scalable arrangement. The problem would arise if a pilot's provisional habits hardened into permanent authority without a dated decision transferring or confirming the keys. A governance program can end up inheriting a constitution written by the first two admissions.

The next document worth reading is the handover, not the launch post

The group can recommend a lifecycle framework, including who changes project status and how disputes rise above a project. The policies already assign concrete stop and restart powers to staff. A future program committee therefore needs a published boundary: which decisions it actually makes, which staff retain for fiduciary or legal reasons, what evidence must accompany a discontinuation, and who hears a challenge. Merely listing a committee on an organisation chart would leave today's keyring intact.

The WebMCP polyfill makes the choice unusually visible. Its technical sunset is conditional and gradual; no source says it has begun. When native implementations eventually satisfy those conditions, a decision maker will still have to decide what happens to packaging, security fixes, archived tests, project status and the W3C name. The code can become unnecessary before the institution's responsibility for its history disappears. A sunset clause is useful only if someone is named to operate it.

The charter provides one clean measure of progress. By mid-2028, can a developer identify the public rule for admission, a project maintainer the rule for losing hosted status, and a supporter the line between funding and control? The sources currently lack a published internal staff delegation for pilot admission and a final appeal path for lifecycle disputes. A dated successor charter or delegation would settle that question. Until then, the second pilot is a useful piece of code under a provisional, staff-held constitution.

Sources