With so much of the W3C implementation landscape happening in open source projects, there are already many situations where the W3C standardization process plays a direct or indirect role in how some of these projects are governed (e.g. the launch of new features in Chromium).
W3C has learned and benefited enormously from some of the open source practices - there may be value for W3C to also more actively engage with the open source ecosystem in how they could benefit from some of the benefits of the open standardization process - which many large open source projects end up adopting it (e.g. the many "RFCs" processes used in major OSS projects).
It may also be worth writing up more explicitly some of the values that a number of open standardization work and open source projects already share (e.g. the priority of consistuencies) as a way to drive improvements across both ecosystems.
This is a meta issue which hopefully can derive into more specific issues & proposals to make progress.
With so much of the W3C implementation landscape happening in open source projects, there are already many situations where the W3C standardization process plays a direct or indirect role in how some of these projects are governed (e.g. the launch of new features in Chromium).
W3C has learned and benefited enormously from some of the open source practices - there may be value for W3C to also more actively engage with the open source ecosystem in how they could benefit from some of the benefits of the open standardization process - which many large open source projects end up adopting it (e.g. the many "RFCs" processes used in major OSS projects).
It may also be worth writing up more explicitly some of the values that a number of open standardization work and open source projects already share (e.g. the priority of consistuencies) as a way to drive improvements across both ecosystems.
This is a meta issue which hopefully can derive into more specific issues & proposals to make progress.