Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[In-Person Event] cdCon + GitOpsCon 2023 #238

Closed
4 of 5 tasks
JessicaRoheLF opened this issue Mar 14, 2023 · 10 comments
Closed
4 of 5 tasks

[In-Person Event] cdCon + GitOpsCon 2023 #238

JessicaRoheLF opened this issue Mar 14, 2023 · 10 comments
Assignees
@LamiWilliams @Anita-ihuman
Labels
review-end

Comments

@JessicaRoheLF
Copy link

In-Person Event Submission

Requirements

Event Demographics

  • This event commits to Event Diversity and Inclusion.
    • Q Detail the process for measuring Event Demographics.
    • A uring the registration process, we ask several questions related to attendee demographics to allow us to better serve our attendees onsite, and ensure our attendees can make the most of the event, as well as be comfortable. Important to note, these questions are not required, and are optional for attendees to complete. Examples of these questions include: Do you have a disability that we should be mindful of as we try to accommodate everyone for this event? Do you identify as a person of color? What gender do you identify with? How old are you?
    • Q Provide an example of an opt-out option on the Event registration page if available.
    • A All demographic-related questions are not required - an attendee may choose to answer, or not. In addition to making these questions not required, we also provide the option for a registrant to select “prefer not to answer”. A selection of Prefer Not to Answer is available for the following questions: Do you identify as a person of color, What gender do you identify with, and How old are you.
    • Q Provide an example of a demographics text input box on the Event registration page if available.
    • A There is not a text input box on the event registration page.

Inclusive Experience at Event

  • This event commits to the Code of Conduct at Event.
    • Q Provide an example of the Event Feedback page if available.
    • A We send out a post-event survey to all attendees where we ask a question similar to the following: “Diversity and Inclusion are vital to the future of the linux ecosystem and it is imperative to us that everyone in the community that wants to participate feels welcome to do so. Please share any feedback or ideas regarding Diversity and Inclusion initiatives to help us improve future events.” Another question we ask in the survey is "Please rate the following statement based on your event experience: I felt included at the event." We also encourage all attendees to share any ideas with us during the event, and have the contact information for the SVP & GM of Events, as well as the specific Event Manager made easily accessible should anyone want to share their feedback prior, during, or after the event.
    • Q Is the event team using feedback from previous event's attendees, speakers, and volunteers to improve DEI at this event?
    • A Yes, after each event, a feedback survey is deployed to speakers, attendees, sponsors, etc. We use the feedback provided in this survey to help plan for future events, including the current year’s event.
    • Q Does the event team plan to use feedback from this event's attendees, speakers, and volunteers to improve DEI at future events?
    • A Any feedback provided in the post-event survey is shared with event stakeholders and planning committees for discussion on implementation.
    • Q How can attendees learn more about accessibility at the event?
    • A We include Resources available to our attendees on the event webpage: https://events.linuxfoundation.org/cdcon-gitopscon/attend/diversity-inclusion/#onsite-resources
    • Q Does the event platform allow attendees to suggest future accomodations for the event?
    • A We encourage all attendees to share any ideas with us during the event, and have the contact information for the SVP & GM of Events, as well as the specific Event Manager made easily accessible should anyone want to share their feedback prior, during, or after the event. Additionally, during the registration process, we ask registrants if they have any accommodations requests we should be aware of.
    • Q Will the event platform be accessible to attendees and speakers after the event?
    • A Keynotes and other event recordings will be made available on the CNCF or LF YouTube Channel shortly after the event concludes.

Code of Conduct at Event

  • This event commits to the Code of Conduct at Event.
    • Q Is the code of conduct posted at Event venue?
    • A Yes, the code of conduct will be printed and available onsite and at all off-site venues. We have the code of conduct linked in all event emails, as well as on the event website for easy reference.
    • Q Provide a link for the Event Code of Conduct.
    • A https://events.linuxfoundation.org/cdcon-gitopscon/attend/code-of-conduct/

Diversity Access Tickets

  • This event commits to the Diversity Access Tickets.
    • Q How many different types of diversity access tickets are available for the event?
    • A We offer 2 types of access tickets for the event; need-based registration scholarships + travel funding. We use a scholarship program to provide diversity access tickets to support individuals who may not otherwise have the opportunity to attend.
    • Q What are the criteria for qualifying for a diversity access ticket?
    • A We place an emphasis on funding applicants who are from historically underrepresented or untapped groups and/or those of lower socioeconomic status. If an individual works for a company that has the ability to fund travel, we ask that they not apply to save scholarship funds for those who need it. We ask applicants to provide a few key pieces of information on their application including their Company or Organization, whether they can receive funds from their organization, a brief description of the ways they are involved in technology and/or open source communities, and why they want to attend the conference. We also ask if they belong to an underrepresented and/or marginalized group. This field is not required and is optional to include.
    • Q Provide a link to the page containing information about Diversity Access Tickets.
    • A https://events.linuxfoundation.org/cdcon-gitopscon/attend/scholarships/

Family Friendliness
@badging-bot
Copy link
Contributor

badging-bot bot commented Mar 14, 2023

Thanks for applying to CHAOSS Badging.

Make sure that you have:

@badging-bot
Copy link
Contributor

badging-bot bot commented Mar 15, 2023 •
edited by LamiWilliams
Loading

Checklist for @LamiWilliams

@LamiWilliams Thank you for becoming a part of this Event Badging review.

Make sure you have looked into the following documents:

In order to avoid receiving excessive notifications from this repository, set your subscription status to Not Watching.

In-Person Event Submission

Requirements

Initial checks

  • Event is about Open Source technologies and systems.
  • Event information is publicly available on a website.
  • The Event Code of Conduct is publicly available.
  • The applicant is the organizer of the event.

💡 Ensure all the initial checks are marked before proceeding with Metric based checks

Event Demographics

This event commits to Event Diversity and Inclusion.

  • Q Detail the process for measuring Event Demographics.
  • A uring the registration process, we ask several questions related to attendee demographics to allow us to better serve our attendees onsite, and ensure our attendees can make the most of the event, as well as be comfortable. Important to note, these questions are not required, and are optional for attendees to complete. Examples of these questions include: Do you have a disability that we should be mindful of as we try to accommodate everyone for this event? Do you identify as a person of color? What gender do you identify with? How old are you?
  • Q Provide an example of an opt-out option on the Event registration page if available.
  • A All demographic-related questions are not required - an attendee may choose to answer, or not. In addition to making these questions not required, we also provide the option for a registrant to select “prefer not to answer”. A selection of Prefer Not to Answer is available for the following questions: Do you identify as a person of color, What gender do you identify with, and How old are you.
  • Q Provide an example of a demographics text input box on the Event registration page if available.
  • A There is not a text input box on the event registration page.

Event Demographics

  • Measuring Demographics - The Event has a process for measuring demographics.
  • Opt-Out - The Event provides an opportunity to opt-out of providing demographic data
  • Text Input - The Event provides a text box to input variable demographics such as Gender, Race, or Ethnicity

Inclusive Experience at Event

This event commits to the Code of Conduct at Event.

  • Q Provide an example of the Event Feedback page if available.
  • A We send out a post-event survey to all attendees where we ask a question similar to the following: “Diversity and Inclusion are vital to the future of the linux ecosystem and it is imperative to us that everyone in the community that wants to participate feels welcome to do so. Please share any feedback or ideas regarding Diversity and Inclusion initiatives to help us improve future events.” Another question we ask in the survey is "Please rate the following statement based on your event experience: I felt included at the event." We also encourage all attendees to share any ideas with us during the event, and have the contact information for the SVP & GM of Events, as well as the specific Event Manager made easily accessible should anyone want to share their feedback prior, during, or after the event.
  • Q Is the event team using feedback from previous event's attendees, speakers, and volunteers to improve DEI at this event?
  • A Yes, after each event, a feedback survey is deployed to speakers, attendees, sponsors, etc. We use the feedback provided in this survey to help plan for future events, including the current year’s event.
  • Q Does the event team plan to use feedback from this event's attendees, speakers, and volunteers to improve DEI at future events?
  • A Any feedback provided in the post-event survey is shared with event stakeholders and planning committees for discussion on implementation.
  • Q How can attendees learn more about accessibility at the event?
  • A We include Resources available to our attendees on the event webpage: https://events.linuxfoundation.org/cdcon-gitopscon/attend/diversity-inclusion/#onsite-resources
  • Q Does the event platform allow attendees to suggest future accomodations for the event?
  • A We encourage all attendees to share any ideas with us during the event, and have the contact information for the SVP & GM of Events, as well as the specific Event Manager made easily accessible should anyone want to share their feedback prior, during, or after the event. Additionally, during the registration process, we ask registrants if they have any accommodations requests we should be aware of.
  • Q Will the event platform be accessible to attendees and speakers after the event?
  • A Keynotes and other event recordings will be made available on the CNCF or LF YouTube Channel shortly after the event concludes.

Inclusive Experience at Event

  • Speaker Inclusivity - The Event requests feedback from speakers regarding Diversity & Inclusion.
  • Attendee Inclusivity - The Event requests feedback from attendees regarding Diversity & Inclusion.
  • Retention - The Event incorporates feedback from past events, or has a strategy to incorporate feedback into future iterations of the event.
  • Accessibility Requests - Attendees are able to inquire if accomodations are available and make suggestions for future accomodations at events.
  • Session Accessibility - Event attendees are able to access the event platform after the event

Code of Conduct at Event

This event commits to the Code of Conduct at Event.

  • Q Is the code of conduct posted at Event venue?
  • A Yes, the code of conduct will be printed and available onsite and at all off-site venues. We have the code of conduct linked in all event emails, as well as on the event website for easy reference.
  • Q Provide a link for the Event Code of Conduct.
  • A https://events.linuxfoundation.org/cdcon-gitopscon/attend/code-of-conduct/

Code of Conduct at Event

  • Findability - It is possible to find the Code of Conduct on the Event website.
  • Clarity - Event Code of Conduct provides a definition of expected behaviour.
  • Reporting venue - The event has a venue for reporting violations of the CoC at the event website.
  • Support at Event - The Event Code of Conduct provided information about possible methods to provide support to victims of inappropriate behavior.
  • Enforcement - The participants in the Event are required to accept the Code of Conduct.

Diversity Access Tickets

This event commits to the Diversity Access Tickets.

  • Q How many different types of diversity access tickets are available for the event?
  • A We offer 2 types of access tickets for the event; need-based registration scholarships + travel funding. We use a scholarship program to provide diversity access tickets to support individuals who may not otherwise have the opportunity to attend.
  • Q What are the criteria for qualifying for a diversity access ticket?
  • A We place an emphasis on funding applicants who are from historically underrepresented or untapped groups and/or those of lower socioeconomic status. If an individual works for a company that has the ability to fund travel, we ask that they not apply to save scholarship funds for those who need it. We ask applicants to provide a few key pieces of information on their application including their Company or Organization, whether they can receive funds from their organization, a brief description of the ways they are involved in technology and/or open source communities, and why they want to attend the conference. We also ask if they belong to an underrepresented and/or marginalized group. This field is not required and is optional to include.
  • Q Provide a link to the page containing information about Diversity Access Tickets.
  • A https://events.linuxfoundation.org/cdcon-gitopscon/attend/scholarships/

Diversity Access tickets

  • Availability - The event provides one or more Diversity Access Tickets.
  • Ticket allocation - The Event has a process for allocating diversity access tickets.
  • Findability - The information about Diversity Access Tickets is public.

Family Friendliness

This event commits to Family Friendliness.

Family Friendliness

  • Availability - The Event provides one or more services/facilities for families.
  • Findability - The information about the family friendly services provided at the Event is easy to find on the website.

@badging-bot
Copy link
Contributor

badging-bot bot commented Mar 15, 2023 •
edited by Anita-ihuman
Loading

Checklist for @Anita-ihuman

@Anita-ihuman Thank you for becoming a part of this Event Badging review.

Make sure you have looked into the following documents:

In order to avoid receiving excessive notifications from this repository, set your subscription status to Not Watching.

In-Person Event Submission

Requirements

Initial checks

  • Event is about Open Source technologies and systems.
  • Event information is publicly available on a website.
  • The Event Code of Conduct is publicly available.
  • The applicant is the organizer of the event.

💡 Ensure all the initial checks are marked before proceeding with Metric based checks

Event Demographics

This event commits to Event Diversity and Inclusion.

  • Q Detail the process for measuring Event Demographics.
  • A uring the registration process, we ask several questions related to attendee demographics to allow us to better serve our attendees onsite, and ensure our attendees can make the most of the event, as well as be comfortable. Important to note, these questions are not required, and are optional for attendees to complete. Examples of these questions include: Do you have a disability that we should be mindful of as we try to accommodate everyone for this event? Do you identify as a person of color? What gender do you identify with? How old are you?
  • Q Provide an example of an opt-out option on the Event registration page if available.
  • A All demographic-related questions are not required - an attendee may choose to answer, or not. In addition to making these questions not required, we also provide the option for a registrant to select “prefer not to answer”. A selection of Prefer Not to Answer is available for the following questions: Do you identify as a person of color, What gender do you identify with, and How old are you.
  • Q Provide an example of a demographics text input box on the Event registration page if available.
  • A There is not a text input box on the event registration page.

Event Demographics

  • Measuring Demographics - The Event has a process for measuring demographics.
  • Opt-Out - The Event provides an opportunity to opt-out of providing demographic data
  • Text Input - The Event provides a text box to input variable demographics such as Gender, Race, or Ethnicity

Inclusive Experience at Event

This event commits to the Code of Conduct at Event.

  • Q Provide an example of the Event Feedback page if available.
  • A We send out a post-event survey to all attendees where we ask a question similar to the following: “Diversity and Inclusion are vital to the future of the linux ecosystem and it is imperative to us that everyone in the community that wants to participate feels welcome to do so. Please share any feedback or ideas regarding Diversity and Inclusion initiatives to help us improve future events.” Another question we ask in the survey is "Please rate the following statement based on your event experience: I felt included at the event." We also encourage all attendees to share any ideas with us during the event, and have the contact information for the SVP & GM of Events, as well as the specific Event Manager made easily accessible should anyone want to share their feedback prior, during, or after the event.
  • Q Is the event team using feedback from previous event's attendees, speakers, and volunteers to improve DEI at this event?
  • A Yes, after each event, a feedback survey is deployed to speakers, attendees, sponsors, etc. We use the feedback provided in this survey to help plan for future events, including the current year’s event.
  • Q Does the event team plan to use feedback from this event's attendees, speakers, and volunteers to improve DEI at future events?
  • A Any feedback provided in the post-event survey is shared with event stakeholders and planning committees for discussion on implementation.
  • Q How can attendees learn more about accessibility at the event?
  • A We include Resources available to our attendees on the event webpage: https://events.linuxfoundation.org/cdcon-gitopscon/attend/diversity-inclusion/#onsite-resources
  • Q Does the event platform allow attendees to suggest future accomodations for the event?
  • A We encourage all attendees to share any ideas with us during the event, and have the contact information for the SVP & GM of Events, as well as the specific Event Manager made easily accessible should anyone want to share their feedback prior, during, or after the event. Additionally, during the registration process, we ask registrants if they have any accommodations requests we should be aware of.
  • Q Will the event platform be accessible to attendees and speakers after the event?
  • A Keynotes and other event recordings will be made available on the CNCF or LF YouTube Channel shortly after the event concludes.

Inclusive Experience at Event

  • Speaker Inclusivity - The Event requests feedback from speakers regarding Diversity & Inclusion.
  • Attendee Inclusivity - The Event requests feedback from attendees regarding Diversity & Inclusion.
  • Retention - The Event incorporates feedback from past events, or has a strategy to incorporate feedback into future iterations of the event.
  • Accessibility Requests - Attendees are able to inquire if accomodations are available and make suggestions for future accomodations at events.
  • Session Accessibility - Event attendees are able to access the event platform after the event

Code of Conduct at Event

This event commits to the Code of Conduct at Event.

  • Q Is the code of conduct posted at Event venue?
  • A Yes, the code of conduct will be printed and available onsite and at all off-site venues. We have the code of conduct linked in all event emails, as well as on the event website for easy reference.
  • Q Provide a link for the Event Code of Conduct.
  • A https://events.linuxfoundation.org/cdcon-gitopscon/attend/code-of-conduct/

Code of Conduct at Event

  • Findability - It is possible to find the Code of Conduct on the Event website.
  • Clarity - Event Code of Conduct provides a definition of expected behaviour.
  • Reporting venue - The event has a venue for reporting violations of the CoC at the event website.
  • Support at Event - The Event Code of Conduct provided information about possible methods to provide support to victims of inappropriate behavior.
  • Enforcement - The participants in the Event are required to accept the Code of Conduct.

Diversity Access Tickets

This event commits to the Diversity Access Tickets.

  • Q How many different types of diversity access tickets are available for the event?
  • A We offer 2 types of access tickets for the event; need-based registration scholarships + travel funding. We use a scholarship program to provide diversity access tickets to support individuals who may not otherwise have the opportunity to attend.
  • Q What are the criteria for qualifying for a diversity access ticket?
  • A We place an emphasis on funding applicants who are from historically underrepresented or untapped groups and/or those of lower socioeconomic status. If an individual works for a company that has the ability to fund travel, we ask that they not apply to save scholarship funds for those who need it. We ask applicants to provide a few key pieces of information on their application including their Company or Organization, whether they can receive funds from their organization, a brief description of the ways they are involved in technology and/or open source communities, and why they want to attend the conference. We also ask if they belong to an underrepresented and/or marginalized group. This field is not required and is optional to include.
  • Q Provide a link to the page containing information about Diversity Access Tickets.
  • A https://events.linuxfoundation.org/cdcon-gitopscon/attend/scholarships/

Diversity Access tickets

  • Availability - The event provides one or more Diversity Access Tickets.
  • Ticket allocation - The Event has a process for allocating diversity access tickets.
  • Findability - The information about Diversity Access Tickets is public.

Family Friendliness

This event commits to Family Friendliness.

Family Friendliness

  • Availability - The Event provides one or more services/facilities for families.
  • Findability - The information about the family friendly services provided at the Event is easy to find on the website.

@LamiWilliams
Copy link

Thanks for applying! @JessicaRoheLF
I am done with my review @Ruth-ikegah

@Anita-ihuman
Copy link
Contributor

@JessicaRoheLF Thank for applying for a DEI badge for your event.
@Ruth-ikegah I am done with my review

@Ruth-ikegah
Copy link

Hi @JessicaRoheLF, apologies for the delay in this review; we are experiencing downtime of the badging bot (that handles automation and results) because the service that delivers webhooks to trigger the bot is down until further notice. (for more info about the issue, read this link).

Our team is currently exploring other ways to receive payload urgently; we will keep you updated.

Thank you for your patience!

@kaxada
Copy link
Collaborator

kaxada commented Mar 24, 2023

/result

@badging-bot
Copy link
Contributor

badging-bot bot commented Mar 24, 2023

Review percentage: 94

Number of reviewers: 2

@kaxada
Copy link
Collaborator

kaxada commented Mar 24, 2023

/end

@badging-bot
Copy link
Contributor

badging-bot bot commented Mar 24, 2023

Assigned badge: Gold
Markdown Badge Link:

![Assigned badge: Gold](https://img.shields.io/badge/D%26I-Gold-yellow?style=flat-square&labelColor=583586&&link=https://github.com/badging/event-diversity-and-inclusion/issues/238/&logo=data:image/svg+xml;base64,PHN2ZyB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgdmlld0JveD0iMCAwIDI1MCAyNTAiPgo8cGF0aCBmaWxsPSIjMUM5QkQ2IiBkPSJNOTcuMSw0OS4zYzE4LTYuNywzNy44LTYuOCw1NS45LTAuMmwxNy41LTMwLjJjLTI5LTEyLjMtNjEuOC0xMi4yLTkwLjgsMC4zTDk3LjEsNDkuM3oiLz4KPHBhdGggZmlsbD0iIzZBQzdCOSIgZD0iTTE5NC42LDMyLjhMMTc3LjIsNjNjMTQuOCwxMi4zLDI0LjcsMjkuNSwyNy45LDQ4LjVoMzQuOUMyMzYuMiw4MC4yLDIxOS45LDUxLjcsMTk0LjYsMzIuOHoiLz4KPHBhdGggZmlsbD0iI0JGOUNDOSIgZD0iTTIwNC45LDEzOS40Yy03LjksNDMuOS00OS45LDczLTkzLjgsNjUuMWMtMTMuOC0yLjUtMjYuOC04LjYtMzcuNS0xNy42bC0yNi44LDIyLjQKCWM0Ni42LDQzLjQsMTE5LjUsNDAuOSwxNjIuOS01LjdjMTYuNS0xNy43LDI3LTQwLjIsMzAuMS02NC4ySDIwNC45eiIvPgo8cGF0aCBmaWxsPSIjRDYxRDVGIiBkPSJNNTUuNiwxNjUuNkMzNS45LDEzMS44LDQzLjMsODguOCw3My4xLDYzLjVMNTUuNywzMy4yQzcuNSw2OS44LTQuMiwxMzcuNCwyOC44LDE4OEw1NS42LDE2NS42eiIvPgo8L3N2Zz4K)

HTML Badge Link:

<img src='https://img.shields.io/badge/D%26I-Gold-yellow?style=flat-square&labelColor=583586&&link=https://github.com/badging/event-diversity-and-inclusion/issues/238/&logo=data:image/svg+xml;base64,PHN2ZyB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgdmlld0JveD0iMCAwIDI1MCAyNTAiPgo8cGF0aCBmaWxsPSIjMUM5QkQ2IiBkPSJNOTcuMSw0OS4zYzE4LTYuNywzNy44LTYuOCw1NS45LTAuMmwxNy41LTMwLjJjLTI5LTEyLjMtNjEuOC0xMi4yLTkwLjgsMC4zTDk3LjEsNDkuM3oiLz4KPHBhdGggZmlsbD0iIzZBQzdCOSIgZD0iTTE5NC42LDMyLjhMMTc3LjIsNjNjMTQuOCwxMi4zLDI0LjcsMjkuNSwyNy45LDQ4LjVoMzQuOUMyMzYuMiw4MC4yLDIxOS45LDUxLjcsMTk0LjYsMzIuOHoiLz4KPHBhdGggZmlsbD0iI0JGOUNDOSIgZD0iTTIwNC45LDEzOS40Yy03LjksNDMuOS00OS45LDczLTkzLjgsNjUuMWMtMTMuOC0yLjUtMjYuOC04LjYtMzcuNS0xNy42bC0yNi44LDIyLjQKCWM0Ni42LDQzLjQsMTE5LjUsNDAuOSwxNjIuOS01LjdjMTYuNS0xNy43LDI3LTQwLjIsMzAuMS02NC4ySDIwNC45eiIvPgo8cGF0aCBmaWxsPSIjRDYxRDVGIiBkPSJNNTUuNiwxNjUuNkMzNS45LDEzMS44LDQzLjMsODguOCw3My4xLDYzLjVMNTUuNywzMy4yQzcuNSw2OS44LTQuMiwxMzcuNCwyOC44LDE4OEw1NS42LDE2NS42eiIvPgo8L3N2Zz4K' alt='D&I Badging badge state: Gold'/>

@badging-bot badging-bot bot closed this as completed Mar 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LamiWilliams LamiWilliams

@Anita-ihuman Anita-ihuman

Labels
review-end
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@kaxada @LamiWilliams @Ruth-ikegah @Anita-ihuman @JessicaRoheLF