- Notifications
You must be signed in to change notification settings - Fork0
How we track participants in the WHATWG
License
Chanran/participant-data
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
This repository hosts the data submitted through theWHATWG Participant Agreement. When someone submits a pull request to a WHATWG repository, automated processes check the data here to determine whether the person submitting has made the required commitments under theIPR Policy.
Whenever an individual or entity signs the agreement, an entry is added to the respective JSON file with theverified field set to false. When they then make a contribution, the respective editor willcheck everything is in order and set theverified field to true or escalate as appropriate. If they do not end up contributing theirverified field likely is not changed.
The automated processes use the GitHub organization identified in the"gitHubOrganization" field in the entity's entry in theentities.json file in this repository to determine whether to accept a pull request. People affiliated with entities that have signed the entity agreement shouldnot sign the Participation Agreement themselves. Instead, they should work with one of the contacts identified in that entry to get themselves added to the appropriate GitHub organization, thenmake sure their membership is public so the automated processes can see it. Similarly, when a person is no longer affiliated with an entity, it is the responsibility of the identified contacts to ensure their entry is removed from the identified GitHub organization.
About
How we track participants in the WHATWG
Resources
License
Uh oh!
There was an error while loading.Please reload this page.