Hey, I am Udoka Ugochukwu, python developer and a data science enthusiast, I am enthusiastic about contributing to this project as a reviewer and with my dedication to duty, team spirit and awesome communication skills I am certain this would be a huge success being on your team

I'm Ruth Ikegah, a beginner in open source and I am currently learning Python programming language. I have read through the reviewer's role and guide and will love to be part of the process. I have good communication skills and team-work spirit and I pledge my dedication to my duties.

Description

The best practices criteria and badge of the Core Infrastructure Initiative (CII) Best Practices Badge Program (CII) are both tagged with a release year and from the information in the docs the CII criteria and badges are phased out in every two years at most.

The CII docs also give notice about continuous updates of the best practices criteria and as well as the badges.
Whereas not much information is available about the D&I badge or metrics in that regard.

How do we solve the problem

My recommendations are that we:

• Determine if the Diversity and Inclusion(D&I) metrics and the badges will be continuously updated.
• If they are updated continuously we then specify the duration of the validity period of both the metrics and badges.
• Tag the D&I Badges and metrics with release year information.

I spoke with @Nebrethar today and we are going to archive this repository. This repo has become the new entry point to the DEI badging initiative and there is a lot of overlap and duplication.

Hi @bistaastha and @Nebrethar

The one link on the page is not working.

Also, could you include a link to the Review Guidelines in the markdown to help people navigate.

About the Project

The CHAOSS Diversity and Inclusion Badging Program began as a way to ensure that D&I metrics can have significant impact in the ways that communities function. The program was created to encourage projects and events towards positive diversity & inclusion practices. The goal of the Diversity & Inclusion Badging Program is to encourage projects and events to obtain D&I badges for reasons of pride, leadership, self-reflection, and self-improvement on issues critical to building the inclusive communities.

The primary goals of the Diversity & Inclusion Badging Program include:

• Establishing an environment where projects and events can engage in the D&I badging program
• Aligning the badging program with best practices, guidelines, and recommendations from Diversity & Inclusion efforts on the CHAOSS project
• Connecting with existing badging standards of IMS Global including building an open peer-review system for the D&I Badging Program.

The aim of this project regards all of these goals, and the work will help the entire Diversity & Inclusion Badging Program. The volunteer for this project will assist in creating a badge submission workflow and peer-review system for the badging process.

• Difficulty: Medium
• Requirements: Extensive experience with GitHub and the GitHub workflow. A willingness to meet new members of the open source community.
• Recommended: Experience in the open source community would be a positive, but it is not required.
• Mentors: Matt Snell, Matt Germonprez, Saleh Abdel Motaal

Microtasks

To become familiar with the CHAOSS D&I Badging Program, Please take a look at the following documentation:

• IMS Standards for Digital Badges (Emphasis on the Background section at the bottom of the page)
• The Journal of Open Source Software Submission Process
• A quick Overview of the CHAOSS Project

Once you are more familiar with the related projects, Please complete these microtasks:

Any line marked with a Q contains a question you must answer.
Any line marked with an A contains an action you must take.

• Microtask 0
  After reviewing the IMS Standards for Digital Badges and the Journal of Open Source Software Documentation, answer the following questions:
  Q 0 How would IMS standards be helpful in creating improving the D&I Badging Project?
  Q 1 What parts of the Journal of Open Source Software Documentation could be helpful in improving the D&I Badging Project? (Hint: There are no wrong answers)

• Microtask 1:
  Navigate to the D&I badging repository and review both the Event and Project folders.
  Q 2 How do these folders differ from each other?
  Q 3 How are they similar?

• Microtask 2:
  Review the issue templates, namely those used for submitting to the project. Clone the repository to your local computer and review the issue templates again.
  Q 4 Are the issue templates any different when you view them in GitHub versus your local machine? If so, how?
  Q 5 Explain why this project may want to use GitHub issue templates as a badging submission method.

Hello, everyone, this is Tharun Ravuri. I saw this project called Build documentation for D&I Badging project. I want to know more about the work and how to write the documentation.
BTW is there any separate channel for the discussion of Badging by CHAOSS.

@SMotaal @thecraftman @Nebrethar

Mentors: Matt S., Aastha Bist

They listed they are the mentors. I even tried searching for them in the google groups but couldn't find the group.

So, that's the reason I opened an issue here. Sorry for this.

Hi, my name is xiaoya, a student from Shanghai, China.
I’ve been hanging around in the CHAOSS community for a while and particularly in the D&I working group. I have scanned through the whole badging project but felt a little bit puzzled since I missed out the early months’ progress.

Here is my understanding of this workflow by now to apply for a badge: take project badge as an example, first I need to append my own project name(maybe a link?) into the entry table and leave the badge column blank; second I finish the questionnaire you provide. After all this, I need to wait for other people to review my PR as well as take an assessment for my badging level, is that correct?

Here I have two questions:

1. After my project/event badging being assessed, I assume the badge will be added into the entry table, and apart from this, will it show in other place, like it will be after my project name like a tail or something?
2. And are the events strictly follow the terms defined by GitHub?
   https://developer.github.com/webhooks/

Anyway, look forward to see how the workflow is going to be detailed and wish I could involve myself more !