w3c / w3c/process

W3C Process Document does not define method of disclosure for affiliations

Open
#1,148 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe the bug affecting interpretation of the document

I have recently received a grant from Bluesky Social PBC, and as part of that I notified the FedID Working Group Chairs and Staff contact of that change in conflict of interest disclosure. However, as a person working within the W3C the process for what I need to do to disclosure in accordance with Section 3.1.1.2. Conflict of Interest Policy was not clear.

Further, I had a conversation with the Social Web CG, who are not at all covered by this grant and my work there has no relationship to the grant, and some people wanted disclosure of my affiliation.

I could not find the documented process for disclosure of affiliation or conflict of interest for Community Groups, and there isn't a process from that CG that I can see.

Further more, when I did update my W3C profile to specify an affiliation, it misrepresented the nature of my affiliation in a way that is not compatible with the legal terms in my grant: It made it look like I was an Employee or Consultant of Bluesky Social PBC, and I am explicitly prohibited from making any such declaration like that.

Image Image Image

The issue comes from the presentation when joining a CG, as I just did with the Process CG:

Image

This clearly states that I'm an employee or representative of Bluesky Social PBC, and that is absolutely not the case, per the contract clause cited above. I'm more than happy to privately share the complete contract with the W3C Staff if necessary.

I think the form for declaring affiliations should be multiple organisations (one or more), and the type of relationship should be declared: employee, contractor, consultant, investor, shareholder, or grant recipient, and then that type of relationship is displayed along side the affiliation.

The should also be a written process for what disclosure means. Is it just an email to the affected WG's chairs and staff contact (if so, I've done that). Do I need to disclose to unrelated W3C groups to the work that my grant is for? If so, how do I do that disclosure? Email to Staff Contact + Chairs? Email to the public mailing list? What is the process I need to follow here?

Thanks!

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 Section 3.1.1.2, the current Community Group affiliation flow, and the disclosure expectations described in the issue. Done means the disclosure process is explicitly documented and affiliation relationships can be represented without mischaracterizing grant recipients as employees or consultants.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
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.