[Virtual Event] DPDK Summit North America

[RachelBraunLF]

Virtual Event Submission

Requirements

• Event Name: DPDK Summit North America
• Link to the Event Website: https://events.linuxfoundation.org/dpdk-summit-north-america/
• Provide verification that you are an event organizer: Event & Meeting Planner at The Linux Foundation - rbraun@linuxfoundation.org

Speaker Demographics

• This event commits to Speaker Diversity and Inclusion.
  • Q Detail the process for measuring Speaker Demographics.
  • A Voluntary speaker demographic information is collected during the CFP process and upon registration. Data collected is used only in aggregate form for reporting attendance totals. Voluntary information requested includes: -Gender identity -Identification with an underrepresented group in technology (race, ethnicity, dis/ability, LGBTQ, etc.) -No all-man programs or panels
  • Q Provide the link for the page related to Speaker Demographics if available.
  • A: https://events.linuxfoundation.org/dpdk-summit-north-america/attend/diversity-inclusion/
  • A We collect feedback and ideas from the community via email, linked on the Diversity & Inclusion webpage, found here: https://events.linuxfoundation.org/dpdk-summit-north-america/attend/diversity-inclusion/ We encourage all participants (attendees or speakers) to email us with ideas on how we can create a more inclusive event. We will also include an open text question on the post-event survey for participants to provide their feedback on how we can improve and/or share any ideas they have with us related to D&I practices.

Attendee Demographics

• This event commits to Attendee Diversity and Inclusion.
  • Q Detail the process for measuring Attendee Demographics.
  • A Voluntary attendee demographic information is collected upon registration. Data collected is used only in aggregate form for reporting attendance totals. Voluntary information requested includes: -Gender identity -Identification with an underrepresented group in technology (race, ethnicity, dis/ability, LGBTQ, etc.)
  • Q Provide the link for the page related to Attendee Demographics if available.
  • A: https://events.linuxfoundation.org/dpdk-summit-north-america/attend/diversity-inclusion/
  • A We collect feedback and ideas from the community via email, linked on the Diversity & Inclusion webpage, found here: https://events.linuxfoundation.org/dpdk-summit-north-america/attend/diversity-inclusion/ We encourage all participants (attendees or speakers) to email us with ideas on how we can create a more inclusive event. We will also include an open text question on the post-event survey for participants to provide their feedback on how we can improve and/or share any ideas they have with us related to D&I practices.

Code of Conduct at Event

• This event commits to the Code of Conduct at Event.
  • Q Is the code of conduct posted?
  • A Yes - the Code of Conduct is posted on the virtual event platform. All registrants are required to agree to follow the Code of Conduct before their registration is processed.
  • Q Provide a link for the Event Code of Conduct.
  • A https://events.linuxfoundation.org/dpdk-summit-north-america/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 NA - DPDK Summit NA is a free event. No barriers to entry.
  • Q What are the criteria for qualifying for a diversity access ticket?
  • A
  • Q Provide a link to the page containing information about Diversity Access Tickets.
  • A

[badging-bot]

Thanks for applying to CHAOSS Badging.

Make sure that you have:

• Read through Event submission requirements and guidelines.
• Understood your role as a CHAOSS Badging applicant.

[RachelBraunLF]

Hello! As an FYI - I just realized that the questions asked on the application here: https://chaoss.community/diversity-and-inclusion-badging/ do not map out correctly to the Markdown text (I think that's what it's called.)
For example - on the application, the question is "Provide an example of the Speaker Feedback page if available, however, it displays as "Provide the link for the page related to Speaker Demographics if available." The same goes for Attendee Demographics.

[germonprez]

Hi @RachelBraunLF. Thanks for catching this. We can get this updated today. Sorry for the mix up :)

I think it should universally say: Provide the link for the page related to Speaker Demographics if available

@bistaastha and @ElizabethN what are your thoughts on this?

[ElizabethN]

@bistaastha @germonprez I think we are trying to ask all three things:

1. Detail the process for measuring Speaker Demographics.
2. Provide the link for the page related to Speaker Demographics if available.
3. Provide an example of the Speaker Feedback page if available.

It looks like on the application we only ask 1 and 3. Should we add that to the Speaker and Attendee demographics sections in the application? I think that's what we are trying to say here.

But I'm confused a little because in the submission the link question shows up, so I'm not sure where that comes from:

[RachelBraunLF]

@ElizabethN - I added the answer to collecting feedback from speakers and attendees since I knew the question was asked on the application but was not included in the text that carries over to GitHub. I had assumed that if I didn't include the information, the reviewers would likely inquire about it, so wanted to be proactive. That's why you don't see the question - I just added the answer, not the question. Sorry if that made this more confusing!

[bistaastha]

@ElizabethN @germonprez I believe we are asking for the information about the Speaker Feedback page, since it is the most recent revision of the form before version 2. It still maps to the older Markdown text from Badging Version 1 which asks for the Speaker Demographics page instead. Hence, the different questions. I'll go update this.

@RachelBraunLF Thanks for bringing this up and sorry for the confusion.

[bistaastha]

I'll go ahead and assign the reviewers for this Event.

[badging-bot]

Checklist for @spotz

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

Make sure you have looked into the following documents:

• Reviewer guide
• Reviewer role
• Submission guidelines(In order to get familiar with applicant actions)

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

---

Event Review Checklist

> 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.

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

> Metric based checks

>> Speaker Demographics and Inclusivity

• Measuring Demographics - The Event has a process for measuring speaker demographics.
• Speaker Inclusivity - The Event requests feedback from speakers regarding Diversity & Inclusion.
  • Ask applicant about the process if information is not openly available.

>> Attendee Demographics and inclusivity

• Measuring Demographics - The Event has a process for measuring Attendee demographics.
• Attendee Inclusivity - The Event requests feedback from attendees regarding Diversity & Inclusion.
  • Ask applicant about the process if information is not openly available.

>> 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.

[badging-bot]

Checklist for @Gemarodri

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

Make sure you have looked into the following documents:

• Reviewer guide
• Reviewer role
• Submission guidelines(In order to get familiar with applicant actions)

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

---

Event Review Checklist

> 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.

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

> Metric based checks

>> Speaker Demographics and Inclusivity

• Measuring Demographics - The Event has a process for measuring speaker demographics.
• Speaker Inclusivity - The Event requests feedback from speakers regarding Diversity & Inclusion.
  • Ask applicant about the process if information is not openly available.

>> Attendee Demographics and inclusivity

• Measuring Demographics - The Event has a process for measuring Attendee demographics.
• Attendee Inclusivity - The Event requests feedback from attendees regarding Diversity & Inclusion.
  • Ask applicant about the process if information is not openly available.

>> 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.

[spotz]

Thanks Rachel this looks good and thanks for reporting the issues you found.

@bistaastha This is good on my end

[Gemarodri]

Thank you @RachelBraunLF for the application, I have done the review and it looks great!