w3c / w3c/cg-program

Facilitating continued participation in a Working Group

Open
#18 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

revamp-2024
Dominant language
HTML
Stars
9
Forks
4
PR merge metrics
No merged PRs in 30d

Description

We want CG Specifications with traction to be taken up in a Working Group in order to secure additional guarantees. In some cases, a CG may be reluctant to transfer a Specification with traction to a Working Group, and one of the primary reasons appears to be that non-Members who have made significant contributions to the CG Specification will face a sudden cost increase (W3C Membership) in order to continue.

How can we facilitate continued participation in a Working Group for those non-Members who have already made significant contributions? (I note that W3C has benefited from those contributions without incurring any direct cost and would do well to express appreciation to those contributors.)

Some ideas:

  • Any mechanism involving non-member participation is undoubtedly going to involve organizational IPR commitments.
  • Ideas for participation:
    • The IE mechanism
    • Reduced participation fee as non-Member.

Contributor guide

No contributing guide indexed for this repository

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

The issue does not identify files, tests, or an implementation entry point. Start by reviewing the proposed IE mechanism and reduced non-Member participation fee, then determine the organizational IPR requirements and what concrete policy change would address continued participation.

Written by the indexing model from the issue text.

Assessment

Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.