TBD

This is the place for asking questions about CHAOSS Badging related to the GSoD project idea. The questions about microtasks should go under #25.

For Season of Docs office hours look at #26. The questions here can be about what is outside the scope of the office hour discussion and the microtasks, but are still related to CHAOSS Badging.

/cc @Nebrethar

My project, Crowdsourcing Translation for CHAOSS Diversity & Inclusion Badging.

• README.md for Crowd sourcing Translation for D&I Workflow

For the Translation process,The integration will be done using Crowdin.

Crowdin is completely free of charge for open-source projects but there are some criteria that must be met.

The Criteria list.

• Number 8 from the list, it requires to keep the "News" section of your website up to date.
  Just realized the Chaoss community news is last updated August 15, 2019.

• Number 7 requires to have an active community of collaborators. For My current repo should i include more collaborators or what do you think @SMotaal @Nebrethar

Regards.

Related Issues

Depends on chaoss/website#341

This issue tracks the creation of a Proof of Concept repository.

• Create parent repository — https://github.com/badging/diversity-and-inclusion/
  • Create README.md
  • Add the badging link to README.md
  • Add the template link to README.md

• Create badging repository — https://github.com/badging/project-diversity-and-inclusion/
  • Create README.md
  • Create PULL_REQUEST_TEMPLATE.md
  • Apply master branch protection rule
  • Create a mock-project branch.

• Create separate issue for documentation (#3)

/cc @Nebrethar

In order to discuss GSoD microtasks (#25) and other things related to CHAOSS Badging, we set up an office hour call - link here.

/cc @Nebrethar

This issue documents the creation of the [email protected] as the project coordination inbox for all external correspondence.

The following members have access to the account credentials:

• @SMotaal
• @Nebrethar

TODOs

• Subscribe [email protected]
• Unsubscribe [email protected]
• Retire [email protected]
• Keep the account credentials in the single-source doc shared by @germonprez with project coordinators

This issue tracks the creation of a Proof of Concept repository.

• Create parent repository — https://github.com/badging/diversity-and-inclusion/
  • Create README.md
  • Add the badging link to README.md
  • Add the template link to README.md

• Create badging repository — https://github.com/badging/event-diversity-and-inclusion/
  • Create README.md
  • Create PULL_REQUEST_TEMPLATE.md
  • Apply master branch protection rule
  • Create a mock-event branch.

• Create separate issue for documentation (#3)

/cc @Nebrethar

This issue tracks the process on how we want to transparently syndicate our minutes and agenda.

At the moment we switched over from using the board to a more traditional doc — https://docs.google.com/document/d/1WrY4PjOrC_Fp6aiWFjfRRZuujlolSraUlTAJHPfbw9I/

TODO

• tbd

As a CHAOSS project, these repositories need to be licensed under MIT. (see Project Charter 8.3.2)

This issue is asking to add a LICENSE file in each repo with the MIT license text.

Example: https://github.com/chaoss/wg-evolution/blob/master/LICENSE

Google Season of Docs - Microtasks

Project overview

The CHAOSS Diversity and Inclusion Badging Program began as a way to ensure that D&I metrics can have a significant impact on the ways that communities function. The aim of the CHAOSS D&I Badging program is to bring D&I metrics into use for propelling good D&I practices in different open source systems.

This project will focus on framing documentation for the D&I Badging program and aligning it in such a way that it makes sense after translation. This work would focus on more community-facing docs related to Badging and also on existing Markdown files.

Submitting microtasks

All microtasks must be submitted as a response to this issue.

Once you submit your first microtask, your responses will be recorded in a document on hackmd.io. These documents will be regularly updated, and some formats may be changed to unify the documents. Your submission's hackmd document may be found at the bottom of this post.

After a period of about a week, our project mentors (@Nebrethar @bistaastha) will comment on the document with advice and direction.

Microtask 0:

Q 0 Review JOSS documentation on submission and review and see how it is related to the current workflow.

The Journal of Open Source Software is one of the primary references used for building out the CHAOSS Badging process. The goal is to compare how the current process works in comparison to the review process of JOSS.

Reference:

• Joss Documentation

Q 1 Review the Core Infrastructure Initiative self-report badging system on projects and events and report schematic differences.

Projects and events are very different, but how different are they in our program? List one thing you would change about either, or both.

Reference:

• CII home page
• Sample CII badge and criteria

Microtask 1:

Q 0 Submit a non-existent project to understand the workflow.

Create a draft PR after adding a mock event in either the Project Badging or Event Badging repository. Record your observations as a part of the microtask.

Reference:

• Project Badging
• Event Badging

Q 1 Review a mock event created by someone else.

If available, take the time to review an event that someone else has posted. If no fake events have been posted yet for this session, use one of the mock events from this year's Google Summer of Code application session:

• badging/event-diversity-and-inclusion#1
• badging/diversity-and-inclusion#2

These are great mock events, but we recommend using a fake event submitted for GSoD, if available.

Microtask 2:

Q 0 Provide a brief summary of the submission and review process.

After reviewing the workflow process and all of the moving parts that create it, provide your idea of how this workflow can be best explained. This task is is focused to the submission and review workflow of the Badging Program.

Concise answers are appreciated, but provide as much detail as you want!

Current Submissions

tharun143
JackieBinya
xiaoya-Esther

From @germonprez:

Hi Saleh and Matt,

I wanted to keep in the loop on a few things. I've been working with Steve Winslow at the Linux Foundation regarding the D&I badging program. The Linux Foundation is quite supportive of this work. This is a good thing :)

I was hoping that you both might have just a bit of time for a chat next week. This way, I could walk you through some of the documents (legal) and logos that the LF is preparing to help in the program.

/cc @Nebrethar @germonprez

This issue tracks bi-weekly progress and updates for the CHAOSS Diversity and Inclusion Working Group.

Agenda Feb26 thru Mar10

• Saleh to recap feedback from Feb18 D&I meeting

• Discuss the purpose of Diversity & Inclusion primary repository

• PR Template !== Issue Template

• Pending badge?!

• Decide on PR Process/Responsibilities

• Propose @CHAOSS/Branding in community meeting — @SMotaal

  CHAOSS branding will be in the https://github.com/chaoss/governance/

Related Threads

• chaoss/wg-dei#277

@bistaastha @xiaoya-Esther @thecraftman I'd like to do a cleanup of some of the badging repos and docs, and it seems like this repo was used primarily in setting up the initial iteration of the badging program. Since there's no README and no activity for a few years, would it be ok if I archived this repo? Thanks much!

TBD

Important Note: This issue is being closed for now and will be revisited after closing #29.

This issue tracks the process of moving all non-contributor-facing documentation into https://github.com/badging/documentation.

This issue tracks bi-weekly progress and updates for the CHAOSS Diversity and Inclusion Working Group.

Agenda Mar25 thru Mar29

• Review @bistaastha's Proposal #12

  Due Mar29

• Mention Milestones to our "Soft" launch #13

  MVP applicants walking through process from start to finish

  per Mar25 D&I meet

• Begin articulating Terms and Conditions Requirements #15

  Draft CHAOSS Conformance Requirements section

  per Mar11 LF sync-up

Agenda Mar30 thru Apr05

• Review @thecraftman's Proposal #11

  Due Apr07

• Discuss GitLab parity #14

  • @Nebrethar create file to speculate on changes

  Google Doc

  per Mar25

Related Threads

• Agenda Card — https://github.com/badging/meta/projects/1#card-35152104
• Agenda Card — https://github.com/badging/meta/projects/1#card-35357620

Currently, submission guidelines for Events and Projects are listed at:
https://github.com/Nebrethar/Docs-Diversity-Inclusion-Badging

Those can either be added to the README of this repository or as separate files here. Another approach would be to put these guidelines on respective Event and Project repos.

@badging/maintainers Where would these fit better?

This issue is open on behalf of @thecraftman to track work related to their Outreachy proposal which is due on April 7, 2020.

Links

• Draft
• Notes

Go through the README to determine how to apply for an event badge at https://github.com/badging/diversity-and-inclusion/
​

1. The goal is to open a “draft” Pull Request against master following the outlined process — feel free to creatively mock it like it is for a real event.

2. It helps to keep track of the steps you took in a secret gist, just the over all, nothing to detailed which can be found in the draft PR.

3. Place a link to this secret gist in a comment below. Please feel free to also keep notes on inconsistencies or things you felt could be improved — constructive feedback is a vital component of open collaboration.

4. Once you are done with the PR, place a link to to it in a comment below.
   ​
   Note We will not yet review or merge PRs, we will discuss the task here and close the issue afterwards.

For CHAOSS Badging, it is still left to be considered how reviewers might officially sign up and get involved in the review process.

@SMotaal @Nebrethar

Go through the README to determine how to apply for an event badge at https://github.com/badging/diversity-and-inclusion/
​
The goal is to open a “draft” Pull Request against master following the outlined process — feel free to creatively mock it like it is for a real event.

It helps to keep track of the steps you took in a secret gist, just the over all, nothing to detailed which can be found in the draft PR.

Place a link to this secret gist in a comment below. Please feel free to also keep notes on inconsistencies or things you felt could be improved — constructive feedback is a vital component of open collaboration.

Once you are done with the PR, place a link to to it in a comment below.

Note We will not yet review or merge PRs, we will discuss the task here and close the issue afterwards.

This issue tracks the creation of documentation for the Proof of Concept repositories.

TBD — Please feel free edit or start from scratch!

• Document repository structure
  • Diversity & Inclusion repository — https://github.com/badging/diversity-and-inclusion/
  • Event Diversity & Inclusion — https://github.com/badging/event-diversity-and-inclusion/
  • Project Diversity & Inclusion — https://github.com/badging/project-diversity-and-inclusion/

Relates to #1, #2.

This issue is open on behalf of @bistaastha to track work related to their Google Summer of Code proposal which is due on March 31, 2020.

Links

• Draft
• Notes

The D&I Documentation is scattered across the repository at present, I propose hosting the documentation on Read the docs after some certain enrichment of it.

Read the Docs is:

• free
• easy to get started - full instructions and guidelines
• automating building, versioning, and hosting
• neat and authentic page styles
• qualify the docs with good navigation
• designed for technical documentation, many technical readers are familiar with the page style
• already applied by Augur（from whom we can obtain advices）

I think we can have online collaborations on documentation using hackmd or something like that, and the overall organizing can be updated on Github during the early phases.
Once it is settled, we can host the documentation on Read the Docs and continue updating via Github, since they can synchronize.

This issue tracks bi-weekly progress and updates for the CHAOSS Diversity and Inclusion Working Group.

Agenda Mar11 thru Mar24

• Badge-athons

  chaoss/wg-dei#277

  Issue updated to reflect schedule changes and occurrence rate

• Office Hours

  D&I Badging Mentors (Matt S, Matt G, and Saleh) are to provide times that they are available for questions from applicants

• Discuss bistaastha's doc

  Matt S and Saleh provided feedback for Aastha’s document
  Session at 9AM Central Time tomorrow to review first draft

• Discuss @CHAOSS/Branding

  Required
  Tabled for Wednesday

Related Threads

• Update page in Google Docs

This issue proposes the idea of using slides as a way to drive collaborative efforts in a self documenting fashion.

TODO

• tbd

TBD

Links

• Draft