Generated `events.json` with the latest events retrieved from the Firebase DB. PR Close #54749 |
||
|---|---|---|
| .. | ||
| about.html | ||
| announcements.json | ||
| api.html | ||
| contribute.html | ||
| contributors.json | ||
| docs.md | ||
| events-contributing.md | ||
| events.html | ||
| events.json | ||
| everyone.md | ||
| features.html | ||
| index.html | ||
| presskit.html | ||
| quick-start.md | ||
| README.md | ||
| resources-contributing.md | ||
| resources.html | ||
| resources.json | ||
| scaling.md | ||
| test.html | ||
Contributors page
We have an official accounting of who is on the Angular Team see [this link](/about?group=Angular), who are "trusted collaborators" see [this link](/about?group=Collaborators), and so on.
The contributors.json should be maintained to keep our "org chart" in a single consistent place.
GDE listings
There are two pages:
-
https://developers.google.com/experts/all/technology/angular
-
Ours which is derived from
contributors.json.
About the data
-
Keys in
contributors.jsonshould be GitHub handles.Most currently are, but not all.This will allow us to use GitHub as the default source for things like name, avatar, etc. -
Keys are sorted in alphabetical order, please keep the sorting order when adding new entries.
-
Pictures are stored in
aio/content/images/bios/<picture-filename>.
Processing the data
Install https://stedolan.github.io/jq/ which is amazing.
for handle in $(jq keys[] --raw-output < aio/content/marketing/contributors.json)
do echo -e "\n$handle\n---------\n"; curl --silent -H "Authorization: token ${TOKEN}" https://api.github.com/users/$handle
| jq ".message,.name,.company,.blog,.bio" --raw-output
done
Relevant scripts are stored in aio/scripts/contributors/.