Please review - https://docs.google.com/document/d/1A3Ghe1ZMrhfhftIPqoWTbcNuY-9sPR1BzjvzcyKhilI/edit?usp=sharing

Discussed in 2019-07-01 meeting.

We asked the team to share feedback on the D&I agenda by Monday, 8 July. The feedback this week should focus on what major topics we discuss. This helps us filter down to a smaller list. Later on, we can focus on specific details of each ticket we want to focus on, and build from there.

This ticket is mostly comment-driven, so I removed it from the meeting agenda. @amsharma, please add it back if you want to bring up some points for group discussion in a meeting!

Sure.

Gentle reminder everyone, thanks.

Hey @amsharma, thanks for working on this! The Google Doc does not allow comments, so my feedback is below:

Ticket #89 - Defining Fedora Council Diversity Advisor term

Actions to be covered during the hackfest -

• Work on the call for nominations for next Diversity Advisor position.
• Open the nomination ticket.
• Marketing of the call for nominations.
• Encourage qualified contributors to nominate.
• Plan for opening the elections and co-ordinate with Ben Cotton for the same.

If I understand these actions, this work specifically looks like the following:

1. Write a CommBlog post
2. Open a Pagure ticket for nominations
3. Promote CommBlog post on social media
4. Work with @bcotton on Fedora Elections app

Does it make sense to map these out at the Flock hackfest? I think we can do this asynchronously.

The actions you listed are helpful though! Instead of adding them to the Flock hackfest agenda, I suggest adding your actions to the ticket. After Flock, we can follow-up on your list and split this up. I also believe this work is blocked by #103 since we need to agree on language for the role and its responsibilities first before promoting it. :grinning:

Ticket #103 - Define Fedora D&I team lead role, responsibilities and term

@tatica wrote up a description in #103. The draft is ready for review here.

I suggest we work through the draft and finalize it by the end of July / early August. If we are not finished by Flock, we can do a final review at Flock. However, I prefer to avoid this at Flock since I think it is hard to collaborate on this. For me, I need time to read quietly, think about it, and then come back after a day or two with feedback. Talking about it in real-time for Flock will be hard for me.

What do you think?

Ticket #94 - Fedora Women's Day 2019

I think this is an excellent topic for the hackfest.

By Flock, we have a month until the acceptance deadline. It would be a great opportunity to gather feedback on our FWD resource pack. This is a great opportunity to collect feedback from committed and future local organizers. We might also collect feedback from Fedora leadership on useful topics to include in the resource pack.

One specific idea is we can have a sticky-note brainstorm exercise. We can pass out a few sticky notes and ask attendees different open-ended questions to answer. This would also be a nice way of involving everyone in the room. There's always a few quiet people in the back. :)

Ticket #97 - Translation of the very important announcements/articles

I'm not sure how I feel about this one. I think we need more people in the room outside of the D&I Team for this to be productive.

@bex, @jibecfed, and @rluzynski left thoughtful feedback in the ticket. I'm not sure this is a conversation we can have without i18n/l10n folks in the room. If a translation team member could join for 30 minutes, we could allocate specific begin/end time for this topic in the agenda. This way, i18n folks can come and offer feedback, and move on to another session if they have a tight schedule.

@jibecfed or @rluzynski, do either of you plan to attend Flock? If so, could either of you join us for 30 minutes to brainstorm here? If you are not attending, could you suggest someone who could join?

Ticket #101 - D&I Team Goals - 2019 - 2020

I think this is most important for the hackfest. This is a broad discussion and requires balance between brainstorming and then mapping out the ideas into an actionable plan. I think a face-to-face discussion is useful for this, but we need more structure so we stay on-topic and do not run out of time.

Also, I think this discussion would be greatly helped by Ticket #106. I think we should "front-load" #106 discussion before talking about #101.

Ticket #106 - Planning for D&I coffee among friends session for FLock 2019

In #106, we mentioned reviewing collected feedback and thoughts from 1x1 interviews in our hackfest. This feedback is extremely useful to review and could help brainstorming for #101. We could get new ideas based on what people have to share in the 1x1 interviews.

What do you think?

Thanks @amsharma for planning this. I am +1 to @jflory7 's suggestions as well - especially that #89, #103 can be asynchronous.

Additionally, I would like to request some time for feedback on event guidelines draft. We have been lagging on it and meeting in person with team and community seems the best way to collect feedback for now.

However, there seems to be a lot on plate for our hack session. I would suggest we prioritize to 3 main things. Here are my suggestions

1. Fedora Womens Day resource pack
2. Event Guidelines feedback
3. Analysing feedback from 1x1 coffee interviews
4. Translation #97 - depending on if people join

Let me know what you think!

Doc is open for edits - https://docs.google.com/document/d/1A3Ghe1ZMrhfhftIPqoWTbcNuY-9sPR1BzjvzcyKhilI/edit?usp=sharing

+1 to @jflory7 , Since the doc is open for edits, please feel free to make direct edits. Thanks.

Also, I feel, We need to cut down on topics and list what exactly we want to nail down during flock to make the best use of face to face time. We can move out items which can be done offline and list which will have more value for the in-person discussion.

@bee2502:
Additionally, I would like to request some time for feedback on event guidelines draft. We have been lagging on it and meeting in person with team and community seems the best way to collect feedback for now.

@bee2502 If we could focus on one or two things from the event guidelines ticket, what would those tasks be?

I think coming up with concrete ideas for what we do during the hackfest is helpful. If I understand correctly, the current suggested tasks are to review the NumFOCUS guidelines. We could do this asynchronously. Curious for your ideas on making this more interactive.

Or maybe a more better way of phrasing this, what is the most useful and insightful feedback to collect about the event guidelines? We can design an interactive activity around the feedback we want to solicit.

@jflory7:

[...] @rluzynski, do either of you plan to attend Flock? If so, could either of you join us for 30 minutes to brainstorm here? [...]

Yes and yes.

Analysing feedback from 1x1 coffee interviews

This depends when the 1x1 will be done, and also it needs time to gather all the feedback, read and analyze them -> so I think we will not have enough time to do it at Flock, but afterwards we can open a ticket and discuss online when we have meeting or offline commenting in the ticket itself.

Or maybe a more better way of phrasing this, what is the most useful and insightful feedback to collect about the event guidelines? We can design an interactive activity around the feedback we want to solicit.

+1 with Justin. If we know this response we can add the Event Guidelines in the agenda

Ticket #106 - Planning for D&I coffee among friends session for FLock 2019
I agree with Jona on this, however, I assume that since most of the information gathered might be confidential, it would be a great idea to review the notes and main highlights from the interviews and then continue the discussion online.

For the rest of comments +1 and +1 that the main goal of the hackfest would be planning D&I team goals for 2019-2020.

I would like to suggest reserving some minutes to discuss the Diversity Advisory and D&I Team Lead roles separation.

@amsharma indicated that both roles were separated back at Flock 2018 since it might be too much work for a single person, but I would like to discuss if it's really needed. Any leadership role takes a big amount of time and effort, but we might expand the discussion and figure out if we really need them both.

Would this be possible during the Hackfest?

I would like to suggest reserving some minutes to discuss the Diversity Advisory and D&I Team Lead roles separation.
@amsharma indicated that both roles were separated back at Flock 2018 since it might be too much work for a single person, but I would like to discuss if it's really needed. Any leadership role takes a big amount of time and effort, but we might expand the discussion and figure out if we really need them both.
Would this be possible during the Hackfest?

As it was discussed on IRC and team members are still willing to keep roles separate.
Do we still want to add this in the hackfest agenda?

@bee2502:
Additionally, I would like to request some time for feedback on event guidelines draft. We have been lagging on it and meeting in person with team and community seems the best way to collect feedback for now.

@bee2502 If we could focus on one or two things from the event guidelines ticket, what would those tasks be?

The doc is here: https://docs.google.com/document/d/1JPKSTOHPNIhMPxeKsGwJH7KJbKtIFb-tc4i0ZrqFh_Y/edit?usp=sharing

At FLOCK, the activity can be as following:

I would suggest everyone to first read the following sections to get a basic overview of the proposal:
Introduction
Important note on leaving feedback
Table of contents
How to use this guide
Following this, attendees (individually or in group) can pick one section such that we maximize the number of sections covered, and evaluate the guidelines based on following :

1. Select a section of interest and think about the following for each of the suggested guidelines in that section:
   a. Is this relevant for Fedora community? If no, why not and how can we make it more relevant?
   b. As an event organizer, Is this guideline clearly understandable? If not, what is unclear?
   c. What are the efforts (low, medium, high) and impact (low, medium, high) needed to implement this guideline as an organizer of a local Fedora community event eg. Release Party?
   For example, please identify “low effort- high impact” guidelines as 🍎and “high effort-high impact” guidelines as ✅
   d. Do you need more resources to implement this guideline and/or support from Fedora D&I Team?

2. What do you think of general rule for evaluation mentioned in ‘How to use this guide’ section i.e. “As a general rule, we encourage conference organizers to implement all of the 🍎 measures and at least one of the ✅ suggestions.”
   a. Is this feasible for smaller local community events like Release Parties?
   b. For global community conferences eg. FLOCK, FUDCONs, should this rule be different? If so, what?

In the end, we can ask people to give a short 2 min talk about their findings and results.

I think coming up with concrete ideas for what we do during the hackfest is helpful. If I understand correctly, the current suggested tasks are to review the NumFOCUS guidelines. We could do this asynchronously. Curious for your ideas on making this more interactive.

@bee2502:
Additionally, I would like to request some time for feedback on event guidelines draft. We have been lagging on it and meeting in person with team and community seems the best way to collect feedback for now.
@bee2502 If we could focus on one or two things from the event guidelines ticket, what would those tasks be?

The doc is here: https://docs.google.com/document/d/1JPKSTOHPNIhMPxeKsGwJH7KJbKtIFb-tc4i0ZrqFh_Y/edit?usp=sharing
At FLOCK, the activity can be as following:
I would suggest everyone to first read the following sections to get a basic overview of the proposal:
Introduction
Important note on leaving feedback
Table of contents
How to use this guide
Following this, attendees (individually or in group) can pick one section such that we maximize the number of sections covered, and evaluate the guidelines based on following :

Select a section of interest and think about the following for each of the suggested guidelines in that section:
a. Is this relevant for Fedora community? If no, why not and how can we make it more relevant?
b. As an event organizer, Is this guideline clearly understandable? If not, what is unclear?
c. What are the efforts (low, medium, high) and impact (low, medium, high) needed to implement this guideline as an organizer of a local Fedora community event eg. Release Party?
For example, please identify “low effort- high impact” guidelines as 🍎and “high effort-high impact” guidelines as ✅
d. Do you need more resources to implement this guideline and/or support from Fedora D&I Team?

What do you think of general rule for evaluation mentioned in ‘How to use this guide’ section i.e. “As a general rule, we encourage conference organizers to implement all of the 🍎 measures and at least one of the ✅ suggestions.”
a. Is this feasible for smaller local community events like Release Parties?
b. For global community conferences eg. FLOCK, FUDCONs, should this rule be different? If so, what?

In the end, we can ask people to give a short 2 min talk about their findings and results.
Does this answer your questions? @jflory7 @jonatoni

I think coming up with concrete ideas for what we do during the hackfest is helpful. If I understand correctly, the current suggested tasks are to review the NumFOCUS guidelines. We could do this asynchronously. Curious for your ideas on making this more interactive.

@bee2502:
Additionally, I would like to request some time for feedback on event guidelines draft. We have been lagging on it and meeting in person with team and community seems the best way to collect feedback for now.
@bee2502 If we could focus on one or two things from the event guidelines ticket, what would those tasks be?

The doc is here: https://docs.google.com/document/d/1JPKSTOHPNIhMPxeKsGwJH7KJbKtIFb-tc4i0ZrqFh_Y/edit?usp=sharing

At FLOCK, the activity can be as following:
I would suggest everyone to first read the following sections to get a basic overview of the proposal:
Introduction
Important note on leaving feedback
Table of contents
How to use this guide

Following this, attendees (individually or in group) can pick one section such that we maximize the number of sections covered, and evaluate the guidelines based on following :

1. Select a section of interest and think about the following for each of the suggested guidelines in that section:
   a. Is this relevant for Fedora community? If no, why not and how can we make it more relevant?
   b. As an event organizer, Is this guideline clearly understandable? If not, what is unclear?
   c. What are the efforts (low, medium, high) and impact (low, medium, high) needed to implement this guideline as an organizer of a local Fedora community event eg. Release Party?
   For example, please identify “low effort- high impact” guidelines as 🍎and “high effort-high impact” guidelines as ✅
   d. Do you need more resources to implement this guideline and/or support from Fedora D&I Team?

2. What do you think of general rule for evaluation mentioned in ‘How to use this guide’ section i.e. “As a general rule, we encourage conference organizers to implement all of the 🍎 measures and at least one of the ✅ suggestions.”
   a. Is this feasible for smaller local community events like Release Parties?
   b. For global community conferences eg. FLOCK, FUDCONs, should this rule be different? If so, what?

In the end, we can ask people to give a short 2 min talk about their findings and results.

Does this answer your questions? @jflory7 @jonatoni

I think coming up with concrete ideas for what we do during the hackfest is helpful. If I understand correctly, the current suggested tasks are to review the NumFOCUS guidelines. We could do this asynchronously. Curious for your ideas on making this more interactive.

I would like to suggest reserving some minutes to discuss the Diversity Advisory and D&I Team Lead roles separation.
@amsharma indicated that both roles were separated back at Flock 2018 since it might be too much work for a single person, but I would like to discuss if it's really needed. Any leadership role takes a big amount of time and effort, but we might expand the discussion and figure out if we really need them both.
Would this be possible during the Hackfest?

As it was discussed on IRC and team members are still willing to keep roles separate.
Do we still want to add this in the hackfest agenda?

If we have time left after other activities, we can discuss this. As this decision is based on the team, this can also be discussed before or after hackfest. During the hackfest, I would suggest we concentrate more on things where we want community inputs.

Do we still want to plan one? Should we initiate a discussion on mailing list?

@tatica @jonatoni @jflory7 @bee2502 ?

It's all on you @amsharma - We advanced a lot during Flock, and we have FWD upcoming, so I guess would be good to start planning it once FWD ends.

@amsharma Thank you for organizing this at last year's Flock!

I am closing this ticket as complete since this was carried out at Flock last year.