@bee2502 said…
Imposter Syndrome or Unconscious bias workshop session

I like the idea of an unconscious bias workshop. Google developed a workshop with resources for participants and organizers. This could be a useful base to start with. I would be interested in running something like this, and we can pull from the experiences of the Google team and others who have run the workshop.

@bee2502 said…
Create new community oriented content at FLOCK!

By accident, the candy swap became one of my favorite parts of Flock – partly because candy is yummy, but also because you get to literally see the diversity of the Fedora community in a fun and unusual way: with candies and sweets from nearly every continent. This year, instead of running it on the side, I was hoping to propose this as an actual session. It could be fun for the Diversity Team to champion this too.

Another idea that came up in the channel was running a workshop to build a foundation for inclusive event guidelines for other events in Fedora, like Flock, FADs, and/or release parties. A lot of these ideas are in this Etherpad for now, but it could be a good opportunity to target this new objective to "launch" at Flock.

+1 for unconscious bias workshop. I checked the content of google, that seems more aligned with the closed work space. We can use the basics from it and then develop it according to our community.

We can also conduct some workshop with all the female attendees to discuss the ideas of being more inclusive for female contributors in Fedora and then we can have some pictures too.

+1 for unconscious bias workshop. I checked the content of google, that seems more aligned with the closed work space. We can use the basics from it and then develop it according to our community.

+1

We can also conduct some workshop with all the female attendees to discuss the ideas of being more inclusive for female contributors in Fedora and then we can have some pictures too.

Can you explain this more?

Etherpad for planning: https://etherpad.persephone.cloud/p/FLOCK2018

Because of the looming deadline tomorrow for Flock sessions, I submitted a half-day hackfest proposal for the D&I team in the Flock CFP Pagure (flock#52).

I think this format is more useful for our team and allows us flexibility to address many of the topics listed above. We also have the flexibility to make more decisions about what we want to focus on and include in July based on the information we have available. This measure ensures we will be reviewed during the first selection round for Flock; however, over the next two months, we should establish better scope of what we want to accomplish at Flock.

I hope nobody minds that I went ahead and submitted the proposal, but I thought this type of proposal would give us the most flexibility and leisure to establish our scope and goals, without the possibility of missing the first round of the Flock CFP deadline. We can always add another proposal (e.g. for the unconscious bias workshop) once we have to chance to discuss further.

Thanks a lot @jflory7 for doing it. I have seen the ticket (atleast read it once quickly) and it seems reasonable to me. I also don't want to have too many things (proposals) which we can't handle and I really want that we should focus of what you have proposed in the ticket https://pagure.io/flock/issue/52 ::
1. Best practice event inclusion guidelines for Fedora events (fedora-diversity#54)
2. Fedora Women Day 2018 (fedora-diversity#66)

It is important to give a nice coverage to above two topics specially when we all are together. We have seen in past that it makes it easier to progress when we all are together at same place. Hope to get this proposal selected. Thanks again.

Nice work on the proposal @jflory7 , my only concern is how many people will visit the diversity sprint since it has the format of a team meeting/hacksession for planning. I think our plan was to collect feedback on event inclusion guidelines during flock and I feel like a short talk/workshop would be a better way to reach the audience... Right now it seems more for internal team planning
Not saying that we should not do internal planning but I guess that shouldn't be the main feeling after reading the proposal if we want to collect feedback from a wider audience.

List of Diversity and Inclusion Team sessions proposed :100:

[evening activity] International Candy Swap: https://pagure.io/flock/issue/50
Create new community oriented content at FLOCK!
Take a picture with female attendees in 'Strong women' pose?
Fun video of contributors from around the world?

Imposter Syndrome workshop and Unconscious bias training: https://pagure.io/flock/issue/54

Mini FAD for Fedora Women Day/ Fedora Appreciation Week : https://pagure.io/flock/issue/52
Secondary Goals:
Get involved with diversity team workshop!
Community members can sign up to organize FWD in your community.

Feedback session on inclusive event guidelines

We will also collaborate with RH in organizing and promoting their workshop for first time speakers and session organizers at FLOCK to include wider Fedora community. @jflory7 I cannot find the link to discussion on ML.. can you link it please?

Also, @recursedd will work on commblog post introducing fedora event guidelines draft #54 before FLOCK.
https://meetbot.fedoraproject.org/fedora-diversity/2018-06-15/diversity.2018-06-15-13.02.html

@bee2502 wrote…
[evening activity] International Candy Swap: https://pagure.io/flock/issue/50

I was originally planning to run this on my own, but I'm happy to do it under the D&I Team flag too. :grinning:

@bee2502 wrote…
Not saying that we should not do internal planning but I guess that shouldn't be the main feeling after reading the proposal if we want to collect feedback from a wider audience.

That's fair. I think a mini-FAD is still the best format for us to do this, because my understanding of how this will work at Flock is that teams will be in a large, open space (not individual rooms) to collaborate, so it becomes easier to go from table to table for different teams and groups. Perhaps @bex or @mattdm could clarify if that understanding is correct.

In either case, we can try to do some advance outreach in the week before Flock to make a call for participation in our session to help with event inclusion guidelines. Also, last year, session organizers stood up at the beginning of Flock to give a quick pitch for their session verbally in front of the entire conference – I anticipate this will be done again this year, so we can also make a verbal plug at the very beginning of Flock too.

@bee2502 wrote…
Secondary Goals:
Get involved with diversity team workshop!
Feedback session on inclusive event guidelines

For both of these secondary goals, I think they should fit into the mini-FAD. The best way to get involved with the team is help out with some of the work and activities we're doing. If someone wants to get involved, the best opportunity is during a dedicated session when we plan to work together on our tickets and planning work.

I'm hoping we can attract some interest for the event inclusion guidelines too. For planning purposes, we could try to launch with this first at our session, so people interested in that can come for it, and then once we finish, they can change tables or hang out for some of the other discussion topics.

@bee2502 wrote…
We will also collaborate with RH in organizing and promoting their workshop for first time speakers and session organizers at FLOCK to include wider Fedora community. @jflory7 I cannot find the link to discussion on ML.. can you link it please?

The threads were split into two posts (1, 2). Lenka Bocincova (lbocinco [at] redhat [dot] com) confirmed an interest to run the session again, but I did not volunteer us to help organize these again this year.

From my memory, our plan was to advise / offer suggestions on how to improve visibility for their speaker sessions by using the mailing list and Community Blog as tools for outreach. I don't think our planned collaboration was to go beyond this because of concerns over limited team bandwidth leading up to Flock.

List of Diversity and Inclusion Team sessions proposed 💯
[evening activity] International Candy Swap: https://pagure.io/flock/issue/50
Create new community oriented content at FLOCK!
Take a picture with female attendees in 'Strong women' pose?

If we want to take a photo with all the women that will participate at Flock we should write on the mailing list (flock ML) so they know our plan, and it's not necessary to be during Candy Swap.

Fun video of contributors from around the world?

I like the idea.

I was originally planning to run this on my own, but I'm happy to do it under the D&I Team flag too. 😀

I think is fine to do this on your own, and not under D&I team :) and it makes more sense.

That's fair. I think a mini-FAD is still the best format for us to do this, because my understanding of how this will work at Flock is that teams will be in a large, open space (not individual rooms) to collaborate, so it becomes easier to go from table to table for different teams and groups. Perhaps @bex or @mattdm could clarify if that understanding is correct.
In either case, we can try to do some advance outreach in the week before Flock to make a call for participation in our session to help with event inclusion guidelines. Also, last year, session organizers stood up at the beginning of Flock to give a quick pitch for their session verbally in front of the entire conference – I anticipate this will be done again this year, so we can also make a verbal plug at the very beginning of Flock too.

+1, in this way we can invite people to our session to help us with their feedback.

The threads were split into two posts (1, 2). Lenka Bocincova (lbocinco [at] redhat [dot] com) confirmed an interest to run the session again, but I did not volunteer us to help organize these again this year.
From my memory, our plan was to advise / offer suggestions on how to improve visibility for their speaker sessions by using the mailing list and Community Blog as tools for outreach. I don't think our planned collaboration was to go beyond this because of concerns over limited team bandwidth leading up to Flock.

I agree that we don't have bandwidth to do this now, it's better to focus on the things we have ongoing and prepare for the Flock proposals we have submitted.

Update: our proposals have been accepted. :100:

• https://pagure.io/flock/issue/52
• https://pagure.io/flock/issue/54

@jonatoni said…
+1, in this way we can invite people to our session to help us with their feedback.

In this case, let's make sure to do some outreach in the week or two leading up to Flock to help build awareness that we want outside feedback on the event guidelines. This should encourage some other folks to show up at whatever we're situated if they know we will cover it first when we start.

@jonatoni said…
I agree that we don't have bandwidth to do this now, it's better to focus on the things we have ongoing and prepare for the Flock proposals we have submitted.

+1. For the D&I Team hackfest, I think it is okay if we wait until closer to Flock to set a final agenda for what we will cover (other than the event guidelines, which we know we will). The session should reflect the work we are already doing in Pagure in other places. So I think it will be better to see where we are closer to Flock, and then prioritize key tasks that would help to cover face-to-face.

As for the imposter syndrome workshop, it would help to cover this early – this one will take some planning. Do we want to set a special-topic, one hour meeting for this sometime this month? If so, what day or a time? If we want to get all of us at once, it might need to be on a weekend. Otherwise, it's probably better to plan for a weekday at a CEST- / IST-friendly time.

If we want to take a photo with all the women that will participate at Flock we should write on the mailing list (flock ML) so they know our plan, and it's not necessary to be during Candy Swap.

Yes, sure. However, I would still like to take some fun pictures during candy swap.

I was originally planning to run this on my own, but I'm happy to do it under the D&I Team flag too. 😀

I think is fine to do this on your own, and not under D&I team :) and it makes more sense.

Why?

@jonatoni said…
+1, in this way we can invite people to our session to help us with their feedback.

In this case, let's make sure to do some outreach in the week or two leading up to Flock to help build awareness that we want outside feedback on the event guidelines. This should encourage some other folks to show up at whatever we're situated if they know we will cover it first when we start.

I think @recursedd is working on a CommBlog draft introducing the draft of event guidelines. We can put a small post about our session using those links.

@jonatoni said…
I agree that we don't have bandwidth to do this now, it's better to focus on the things we have ongoing and prepare for the Flock proposals we have submitted.

+1. For the D&I Team hackfest, I think it is okay if we wait until closer to Flock to set a final agenda for what we will cover (other than the event guidelines, which we know we will). The session should reflect the work we are already doing in Pagure in other places. So I think it will be better to see where we are closer to Flock, and then prioritize key tasks that would help to cover face-to-face.

I think the goals are this:
Mini FAD for Fedora Women Day/ Fedora Appreciation Week : https://pagure.io/flock/issue/52
Secondary Goals:
Get involved with diversity team workshop!
Community members can sign up to organize FWD in your community.
Feedback session on inclusive event guidelines

As for the imposter syndrome workshop, it would help to cover this early – this one will take some planning. Do we want to set a special-topic, one hour meeting for this sometime this month? If so, what day or a time? If we want to get all of us at once, it might need to be on a weekend. Otherwise, it's probably better to plan for a weekday at a CEST- / IST-friendly time.

I have exams. We can do it this week or on weekend of 21-22 May.

ACTION ITEMS
Publish post introducing our goals for D and I sprint, blocking on post introducing event guidelines draft and FWD post
Meet and work on Imposter syndrome workshop

@bee2502 said…
I think @recursedd is working on a CommBlog draft introducing the draft of event guidelines. We can put a small post about our session using those links.

Makes sense. It would be good to get this out later in July. I'll follow up in the event guidelines ticket.

@bee2502 said…
I think the goals are this:
Mini FAD for Fedora Women Day/ Fedora Appreciation Week : https://pagure.io/flock/issue/52

+1 for the FWD focus.

For Appreciation Week, we should work closely with the CommOps team since this is a topic already covered in their session.

@bee2502 said…
Secondary Goals:
Get involved with diversity team workshop!
Community members can sign up to organize FWD in your community.
Feedback session on inclusive event guidelines

+1 for event guidelines feedback. I think this is actually a primary goal. [EDIT: It is listed as a top priority item in flock#52]

I think getting community members to propose a FWD session is something best covered outside of our workshop. Since it's Flock, it's likely people will not have much bandwidth to write a proposal. If it were me, I would need to talk with other people in my home region and look at other resources to calculate a budget. We can try to promote FWD and encourage others to submit a session, and point them to the resources in place to organize an event.

One thing I'd like to revisit would be low-hanging fruit type of tasks for our team. I feel like we are at a good point now to think about these kinds of tasks and planning them out for new contributors to get involved. This could also be a way to involve anyone who happens to be in attendance and is also a newcomer.

@bee2502 said…
I have exams. We can do it this week or on weekend of 21-22 May.

I assume you mean July. :smile: In either case, perhaps we can plan an audio/video call later this month for putting the workshop resources together. It helps that we have the Google workshop resources and your personal experiences running these at Mozilla to start with.

Discussed in 2018-07-27 meeting.

We had a brief moment to touch on this in yesterday's meeting.

Prepping event guidelines

We wanted to move forward with migrating the event guidelines to Google Docs. This will help us gather feedback and make it easier to show what we are working on at Flock.

I am actioned to do this over this weekend. I will post to the mailing list when this is done.

Session planning call

We wanted to hold an audio/video call to plan out the sessions we proposed for Flock this year. We will try to coordinate this over the next week, but we are at low bandwidth for team members. @amsharma is traveling, @bee2502 is going through exams, and I am getting ready to move cities in this coming week.

Nonetheless, we will try to hold this in the next week if possible. We will probably coordinate it ad-hoc in IRC / Telegram.

we need to write a report - Diversity team in flock, 2018. Any volunteers ?

Discussed in 2018-09-07 meeting.

We put out a call for writers in the meeting – both @bee2502 and @jonatoni are blocked this month and unable to take this. I can take this, but I am due two articles on the CommBlog, for Appreciation Week and the CommOps Flock session. I could have it done by the end of September.

@amsharma Could you get it done sooner or are you also blocked?

Discussed in 2018-09-07 meeting.

We put out a call for writers in the meeting – both @bee2502 and @jonatoni are blocked this month and unable to take this. I can take this, but I am due two articles on the CommBlog, for Appreciation Week and the CommOps Flock session. I could have it done by the end of September.
@amsharma Could you get it done sooner or are you also blocked?

I have an internal RH event to organize and FWD coming up in September. I will see what I can do before September , but can't promise.

@amsharma said…
I have an internal RH event to organize and FWD coming up in September. I will see what I can do before September , but can't promise.

Okay, no worries. I will take this ticket in the meanwhile.

Flock happened in August and I think an event report is a little late to publish. I am going to close this ticket as complete and we can continue post-Flock goals in other relevant tickets.

Thanks everyone involved for making the Flock session possible this year. :tada: