The CHAOSS badging program is a great way to show the diversity and inclusiveness of your event and it's also a great way to see where your event is. Not all events can get Gold level due to restrictions they need to adhere to but that's ok!
https://chaoss.community/diversity-and-inclusion-badging/
This was discussed during todays DEI meeting
We took a look at this in our DEI meeting today. We think its late to submit this for Nest, but are considering to submit for Fedora Week of Diversity which will be on October 14th & 15th. Here is the checklist upon which they review the event: https://github.com/badging/event-diversity-and-inclusion/blob/master/.github/checklist.md
Metadata Update from @jonatoni: - Issue tagged with: type - events
Metadata Update from @jflory7: - Issue assigned to jflory7 - Issue priority set to: waiting on assignee (was: awaiting triage) - Issue tagged with: new change
Nest and FWD have come and gone, but we have a Fedora Release Party coming up in a couple of weeks. I'm familiar with the CHAOSS Badging process already but this could be a good opportunity for someone else to go through the process and document it for future events.
Metadata Update from @jflory7: - Issue tagged with: help wanted
Metadata Update from @jflory7: - Issue priority set to: next meeting (was: waiting on assignee)
Sounds like s great plan:)
Oof. I did not get a chance to do this in the craziness leading up to the release party. :disappointed_relieved:
From an events timeline, our next events are the F38 release party in April/May 2023, and most likely an in-person Flock event in August/September in 2023. We can target the next Release Party as a runthrough for this process. In addition to going through the review process, we should also engage with Fedora Marketing to have an outreach plan about any recognition we might receive as part of this.
In the meantime, I have opened a new issue at gitlab::fedora/community-architecture#4 to keep tabs of this. I am closing this issue out as stale.
stale
Metadata Update from @jflory7: - Issue close_status updated to: stale - Issue status updated to: Closed (was: Open)
Metadata Update from @jflory7: - Issue untagged with: help wanted - Issue priority set to: waiting on assignee (was: next meeting)
Login to comment on this ticket.