The w3c.json file

Projects operating under the w3c organisation (or related to W3C even if under other umbrellas) are encouraged to specify a w3c.json file at the root of their repository. The purpose of this file is to provide some metadata about repositories so that they can be processed automatically by a variety of tools layered atop the organisation. They can also help humans figure out who to contact for a given problem.

Here is an example:

        "group":      40318
    ,   "contacts":   ["darobin", "sideshowbarker"]
    ,   "shortName":  "html5"

The fields that are understood at this point are:

The numeric ID of the group in charge of this repo. While it is inconvenient for humans to find such IDs they are the best thing we have to programmatically create links between repositories and a whole lot of other data we have that are using this type of identifier.
An array of people who are considered points of contact for the repository for administrative requests. They aren't necessarily the primary contributor and they aren't necessarily from the W3C Team. Whatever works for any given repository is acceptable. For integration purposes, please use your GitHub ID.
If the repository contains a specification, this is its short name (as in This allows for automatic linking between repositories and the published specification.
This is essentially a W3C-internal flag. If set to open, any W3C Team member should feel empowered to help with the management of this given repository. This can be set to restricted to indicate that for whatever reason, it is preferable to let the repository be handled only by team contacts directly associated with it. The default value is open.