You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vendor positions are mapped in standard-positions.json. The mapping was done manually. In this issue, we should map more positions (if the first mapping missed some of them, which I'm sure of), and figure out a way to continue mapping more automatically.
Secondly, we should run the update-standard-positions.js script automatically (perhaps monthly) to make sure the list of positions and concerns are always up to date.
The text was updated successfully, but these errors were encountered:
The summary is that they now have a new dashboard showing their positions, and the data for the dashboard comes from issues on the repo and (optionally) additional data in a YAML file.
They also have a build step that generates the dashboard site, and the build step involves generating a merged JSON file with all of the data we need:
We could therefore update the update-standard-positions.js script to pull data from that file instead. Interestingly, that file also contains a rationale field which would be useful to show in the explorer.
Vendor positions are mapped in
standard-positions.json
. The mapping was done manually. In this issue, we should map more positions (if the first mapping missed some of them, which I'm sure of), and figure out a way to continue mapping more automatically.Secondly, we should run the
update-standard-positions.js
script automatically (perhaps monthly) to make sure the list of positions and concerns are always up to date.The text was updated successfully, but these errors were encountered: