Process of rewarding and creating the badges to reward is based on trust rather on approval, following these steps:

Assumption:

Coordinators and Stewards from the Coordinators-key contributors channel will be the only ones able to access the badge creation dashboard.

Steps:

  1. Coordinator writes in #badge_giving channel (i) the name of the person to be recognized, (ii) the act to be recognized, (iii) and the badge name to be assigned. For example:

I recognize @Sid for his commitment to (1) building the smart-contract for using NFTs as badges, (2) for linking the front-end with the back-end, (3) for integrating magic.link authentication to the badge system, (4) for helping others to upskill, (5) for auditing and improving the smart contract (6) with Zeppelin upgradeability functions, as well as (7) for being available at both very late and very early hours even in weekends. For all that I promote Sid with the honor of the following badges: (1) Smart-Contract dev, (2) Full-Stack dev, (3) Magic.Link dev, (4) Sensei, (5) Smart-Contract auditor, (6) OpenZeppelin dev, (7) Unstoppable volunteer.

  1. The Coordinator needs to first check if there is a badge that suits the recognition willing to give. An easy way to look up if there is a badge that suits its needs is by looking at its tags. These tags are easily looked up in the Badge Manager dashboard [set link].

In case there already exists a badge for the recognition to be given, each badge name (within the post the coordinator is writing) should be linked to its notion page, found on the List of Badges page.

Assigning:

3.A. Following this same scenario where a badge already exists, the Coordinator needs to see if there are remaining badges to be given of that badge's batch. If there are, then the Coordinator proceeds to assign the badge by inputting the name of the volunteer in the search bar and the corresponding evidence. Evidence should be either a photo or a video that shows the work of the volunteer, if there is no evidence to show, then a screenshot of the Coordinator's public recognition of the volunteer's work will cover this field. A best practice would be to take a screenshot when there have been reactions of emojis or commentaries from other peers, to save that heart-warming emotion in the blockchain.

Minting: 3.B. In case there is no badge for that need, then the Coordinator needs to create a badge following the format of the existing ones as a template. The Coordinator needs to put a reference image in the proposed badge and ask the Design Team for creating the badge image. Once the image has been created, then the Coordinator needs to go to the Badge Creation dashboard [add link] and mint the badge using the same details given in the badge's notion page.

After this, the above assigning process is followed.