This issue aims at moving the current events table from https://github.com/badging/event-diversity-and-inclusion/blob/main/README.md#badges-granted-version-3 to https://badging.chaoss.community/event-badging

But before the front end is implemented, there is a need to create a database table that will store these events. the table will have the same columns as the current table above and rely on the bot automation to save events to the database.

there is a need to find a way to populate the database table with all the previous events. This may call for scrapping the readme table and manually filling the table.

Tools and tech:

1. MySQL
2. Node
3. GitHub API

the help.js code has placeholder comments that need to be fixed to add meaningful information to both the reviewer and the applicant. by the user issuing the /help command, the help code can trigger information in the comment section that is helpful to them whether they are applicants or reviewers.

link to placeholder file -> https://github.com/badging/badging-bot/blob/main/src/help.js

A good starting point for that information would be here.

Is your feature request related to a problem? Please describe.
Currently when there is a new deployment/build, the old docker container is deleted and the process creates a downtime which fails some requests from processing.

Describe the solution you'd like
The solution is to implement a message queue that handles and monitors the success of requests separately. this will be done with RabbitMQ

Describe alternatives you've considered
I had also considered load balancing which is a faster approach but would require some extra resources but didn't look into into extensively.

The bot should not issue another badge when a project repository has been badged. Instead, an error message should be returned indicating that the project has already been issued a badge.

Currently when someone successfully authenticates with gitlab to github, via https://badging.chaoss.community/badge and refreshes, the web treats that as a fresh session that needs a new token even when the previous authenticated token is still valid and not expired.

some github emails are private and the database doesn't allow for blank email fields so there is need to create that check and possibly return and error or information to the user about why their email should be public

this aims at updating the contents of CONTRIBUTING.md and README.md to include the latest changes in this repo. This issue is not code-related but needs a basic understanding of the programming language used and backend development.

since there was an integration of the badging bot repository into this repository, consider adding the necessary information from the badging bot readme and contributing files too

I am happy to share details of the changes so that we can come up with a detailed README that captures all changes.

refer to point one of badging/badging#35

Summary

This issues highlights some problem areas using the "Search for Project Repository" after logging in with GitLab on https://badging.chaoss.community/badge

Major problems

1. No pagination - search is only returning first page of results and no pagination preventing full list of repositories from appearing
2. No exact match prioritization - search does not have exact match prioritization preventing search for exact repository

Minor annoyances

3. No repeat search - after entering in the search box the search cannot be used again and no results appear in the dropdown
4. Spaces required between slashes - when searching for a path directory a space is required before and after slashes. (E.g. GitLab.org / gitlab works but GitLab.org/gitlab brings up nothing)

Source code links relevant for 1 & 2 above:

• Code fetching the repos:

  BadgingAPI/providers/gitlab/APICalls.js

  Line 45 in 28fcabd

  const getUserRepositories = async (access_token) => {

• OAuth flow:

  BadgingAPI/providers/gitlab/auth.js

  Line 68 in 28fcabd

  const handleOAuthCallback = async (req, res) => {

• Call for repos scan:

  BadgingAPI/providers/gitlab/auth.js

  Line 101 in 28fcabd

  const { repositories, errors: repositories_errors } =

Notes

Per @zillemarco: "The list of repo is fetched right after the user logged id and an access token was retrieved. After the OAuth generated a token, it scans the repos with the token and returns that back to the frontend."

From testing we have noticed that the bot returns a successful scan with a template DEI.md file.

cc: @kaxada

In the response congratulations email:
- The following text MUST be removed as we are not providing this: In the coming 3-4 days, we will share a supplemental report on your project's language inclusivity. This report will provide valuable insights into how inclusive your project's language is to diversw audiences. This report is only a supplement to your DEI Badge and has no impact on current or future badges. The report will only be sent to this email and can be used in any way that you see fit.
- This text MUST be changed to only say CHAOSS DEI Project Bronze Badge: We are thrilled to inform you that your recent review submission of your Open Source Project has been recognized and rewarded an All In CHAOSS DEI Bronze badge.

we are looking to integrate an application into the website. This form is currently a Google form located here.

The goal is to add this information to the existing badged repos database.

skills:
MySQL
Node

Description:

The badging bot messages/responses, for example: Welcome messages, Checklists, etc., are currently generated from the event-diversity-and-inclusion repository. These messages are stored in the .github directory in the form of .md files of the event-diversity-and-inclusion repository and are accessed through the GitHub API.

For proper management, debugging, and contribution follow-up, this issue will move the files to this repo.

Solution:

Migrating the .github folder to the badging bot repository/directory

This issue came up from this slack conversation

Issue #22 created a standard for naming files and folders. The goal of this issue is to update the CONTRIBUTING.md to reflect the standard that is in the description of issue #22

This issue is intended to clean up some aspects of the code. This issue focuses on;

• removing all the redundant code that was commented out

• commenting on the necessary comments

• change the casing to match the following rules:

1. Variables and functions: CamelCase
2. Classes and constructors: PascalCase
3. Filenames, constants, and environment variables: Snake_case
4. HTML attributes and CSS class names: Kebab-case

While you are doing so, Please make sure your code never breaks in any way. Be sure to always be running the dev server

Currently, there are actions and processes we can't track unless we log into the server and look at the logs of the docker containers or nginx servers.

The goal is to create a protected endpoint accessible only with an admin login. it should be a log sheet summarising any process happening in the backend. tracking actions, responses from APIs and the server to the user, who logged in, who got signed up, which badges got issued and when. This should also have time stamps and necessary links to the action (if needed).

The logs will be deleted after a certain period or when they reach a certain level of memory.

Skills:
Docker
Linux
Shell Scripting
Node
Nginx
GitHub API