Skip to content

Latest commit

 

History

History
160 lines (117 loc) · 6.2 KB

GLOSSARY.md

File metadata and controls

160 lines (117 loc) · 6.2 KB

Angularians

Everyone who has contributed to the Angular repositories, ranked by a score of what they did. These are the words the site, the code and the docs use for it.

People

Angularian: A person on the board: anyone whose work in a repository on the board earned points. Avoid: contributor (outside the code and the translation badge), user, member, developer

Angular team: The public members of the Angular organization on GitHub. Avoid: core team, maintainers, Googlers

Bot: An account that acts automatically, or one that no longer exists; left off the board entirely. Avoid: service account

Renamed account: An Angularian whose GitHub username changed; they stay the same Angularian, and their old name still leads to them. Avoid: alias, old user

Contributions

Contribution: One thing an Angularian did for Angular that the score counts: a landed pull request, an issue, a comment, a review comment, a security advisory credit or a translation. It belongs to the day it was made. A reaction received earns points but is not a contribution. Avoid: activity, event, commit

Landed pull request: A pull request whose change reached the default branch, whether or not GitHub shows it as merged. "Merged" is fine on the page, where readers expect it. Avoid: commit

PR type: The kind of a landed pull request (feat, fix, docs or chore), from its title or, failing that, its labels. Avoid: category, kind of change

Scope: The part of a PR title in parentheses (fix(router): …), naming the package it changed. Avoid: area, component

Package: A published part of Angular a landed pull request counts toward: an npm package, or an area of angular/angular such as router. What a profile's "Contributed to" lists. Avoid: library, module, project

Issue: An issue or a GitHub Discussion an Angularian opened. Avoid: ticket, bug report, thread

Helpful issue: An issue the community found worth it: closed as completed, or with enough reactions or comments. Avoid: good issue, popular issue

Comment: A message in the conversation of an issue, a pull request or a discussion, replies included. Avoid: reply, post

Helpful comment: A comment with enough reactions, or chosen as a discussion's answer. Avoid: upvoted comment

Review comment: An inline comment on the code of a pull request; a review's summary is not one. Avoid: review, code comment

Translation: A community translation of angular.dev into a language, credited to each of the people who translated it. Avoid: localization, i18n

Reaction received: An emoji reaction someone left on an Angularian's issue, pull request, discussion or comment. It earns the writer points on the day of what got it, but is not a contribution of its own. Avoid: like, upvote

Security advisory credit: An accepted credit on an Angular security advisory, counted once per person and advisory using their highest-valued role. A security report is the finder or reporter role; analysis, remediation and review are other credited roles. It belongs to the advisory's publication date. Avoid: CVE (an advisory may have none), security report when referring to every role

Advisory severity: The advisory's published severity: low, moderate, high or critical. Every credited role receives the same severity multiplier; an unspecified severity has multiplier 1. Counts keep role and severity together.

Ranking

Score: The sum of the points an Angularian earned in one period. Avoid: XP, karma

Points: What one contribution, or one reaction received, is worth toward the score. Avoid: weight (outside the code), credits

Rank: An Angularian's place by score in one period, on the whole board or within a country (the country rank). Avoid: position, place

Period: The span a score counts: all time, the last 30 days, the last 12 months, or one calendar year from 2014. The last 12 months is the default. Avoid: timeframe, range, window

Board: The ranked list of Angularians for one period, and optionally one country. Avoid: leaderboard table, ranking list

Repository on the board: One of the Angular repositories whose contributions count; archived ones whose code moved elsewhere count too. Avoid: tracked repo, project

Country: The country an Angularian's GitHub location names, if it names one. Avoid: location, region

Badges

Badge: A mark on a profile and its card: for a rank or a kind of work on the board, for a role (the Angular team, Shieldwall), for a recognition, or for a project (a custom badge). Avoid: achievement, award, trophy

Recognition: A badge for a title someone else gives: Angular GDE, GitHub Star or Nx Champion. Avoid: certification

Translator: A badge for the lead of a community translation of angular.dev. The others with five or more translation commits are its helpers, and wear its contributor badge. Avoid: localizer, i18n badge

Translation contribution: A helper's part in a community translation of angular.dev: five or more translation commits, without leading it. It scores less than a translation. Avoid: partial translation

Shieldwall: The badge of an Angularian credited on an Angular security advisory, in any role, using their collected all-time advisory count. Avoid: security badge

Custom badge: A badge for the creators, maintainers or organizers of an Angular project: its logo, a short playful title and its colour. Avoid: project badge, sponsor badge, partner badge

Smith of ng-halla: The badge of an Angularian who created a project the site itself is built on. Avoid: builder badge, credit

The site

ng-halla: The site's name for the hall where every Angularian is remembered. Avoid: Valhalla

Angie: The site's Viking guardian, who brings down a storm when called. Avoid: logo, the mark

Angularian card: The image of an Angularian's rank, score, stats and badges for one period, for a README or a link preview. Avoid: OG image, share image, banner

Profile: An Angularian's own page: their stats in every period, packages and badges. Avoid: user page, account

Collection: One nightly gathering of every contribution from GitHub, which replaces the board's data. Avoid: sync, crawl, scrape, import