If we look at resource pack, I believe it is good to make it generic and not labelled as FWD?
It can be names as "Fedora Event Resource Pack by diversity team" and we can make it available to be used outside this team and FWD as well? Thoughts?

Makes sense to me. I don't think we have to limit this to FWD only. We can continue to publish it along with the FWD docs in our repo.

Thanks @amsharma and @jflory7 .. updated google doc.

There are a couple of infographics already created that could go along with this idea. I saw mostly the purpose of use for this content, but I could help with it if I also get a feedback on what would be needed to spread fedora globaly for each team. (stickers, tshirts, flyers, etc).

I saw mostly the purpose of use for this content, but I could help with it if I also get a feedback on what would be needed to spread fedora globaly for each team. (stickers, tshirts, flyers, etc).

I know @duffy had opinions in the past on environment sustainability and swag. Flyers/brochures are probably something we need as a deliverable, but beyond that, it would be cool to experiment with more environmentally-conscious ideas for takeaways / swag. I'm open to suggestions from others as I haven't spent a lot of time thinking about it, but I know others in our community have.

I added a comment on #138 on suggestions for improving event organizer resource pack based on feedback survey by @nikhilkathole with FWD 2018 organizers. The things missing from them in the current draft are:

• Women in Open Source (with examples of women in FOSS, Fedora & other FOSS initivaties to support women eg. Outreachy)
• Maybe some info on Imposter Syndrome or Unconscious Bias would be good. I think this is especially relevant for FWD organizers based on @orionstar25's feedback about systemic bias
• How to find Newcomer issues/ easy first bugs for the hackathon
• Activity suggestions eg. Fedora Badges quest
• Ideas on finding speakers eg. one idea here could be a list of Fedora community members from underrepresented groups interested in speaking opportunities (so organizers can find speakers for their event more easily)

What does the team think about the suggestions? Based on the feedback, I will add them to the draft.

I also see that a lot of content in the draft is not in the docs page. Is there a particular reason why? or just that someone needs to update it?

@bee2502 wrote…
Women in Open Source (with examples of women in FOSS, Fedora & other FOSS initivaties to support women eg. Outreachy)

Maybe we could re-use some of the How do you Fedora? articles from @cprofitt featuring women of Fedora. I cannot remember if @siddharthvipul1 was going to look at resuming this column, but if he is, we could probably buddy up with Vipul to write more contributor profiles to use in the Resource Pack. :smile:

@bee2502 wrote…
Ideas on finding speakers eg. one idea here could be a list of Fedora community members from underrepresented groups interested in speaking opportunities (so organizers can find speakers for their event more easily)

This is a cool idea. It could be modeled after resources like the Women Techmakers Directory from Google or a collection of queer-friendly Community Centers in the U.S.

We should consider ways to safely share contact info without compromising personal privacy (e.g. approximate location or private contact info like phone number).

@bee2502 wrote…
Women in Open Source (with examples of women in FOSS, Fedora & other FOSS initivaties to support women eg. Outreachy)

Maybe we could re-use some of the How do you Fedora? articles from @cprofitt featuring women of Fedora. I cannot remember if @siddharthvipul1 was going to look at resuming this column, but if he is, we could probably buddy up with Vipul to write more contributor profiles to use in the Resource Pack. 😄

If the column is not being resumed, it could be a newcomer task for our team. For example, new contributors can interview and write a CommBlog post about a female contributor from the community . We can possibly provide them with some template questions too.

Other than that, for this section, I know that @jonatoni and @amsharma have given presentation related to these topics before.. so if they are willing to share the slides or if we can find a video of their talk, we can add it to the resource pack..

@bee2502 wrote…
Ideas on finding speakers eg. one idea here could be a list of Fedora community members from underrepresented groups interested in speaking opportunities (so organizers can find speakers for their event more easily)

This is a cool idea. It could be modeled after resources like the Women Techmakers Directory from Google or a collection of queer-friendly Community Centers in the U.S.
We should consider ways to safely share contact info without compromising personal privacy (e.g. approximate location or private contact info like phone number).

I think we can just share the FAS ID and then their email contact would be FAD-ID@f.p.o. For location, I think we can just share the region i.e. EU/APAC etc or timezone if the contributor is willing -- I think this information is available in FAS anyway so we dont have to worry about the privacy issues. For more discussion on this, pls comment on the ticket specifically for this task: https://pagure.io/fedora-diversity/issue/140

@bee2502 wrote
If the column is not being resumed, it could be a newcomer task for our team. For example, new > contributors can interview and write a CommBlog post about a female contributor from the
community . We can possibly provide them with some template questions too.

+1 it makes a great good first issue for people to get involved within the D&I Team. Having a template would make the process much simpler and easier.

I would link to suggest addition of this doc of previous D&I Flock Session in the Docs as well (compiled by @bee2502 ) As being discussed in this ticket #124 : https://docs.google.com/document/d/1IFsaPC09DZXaKrsWnxfb6im2rANmQGH1Wj0Fpeasym4/edit#heading=h.jg2ev5g9eziq

thanks for the feedback and suggestions @nasirhm @jflory7

To summarize,

Regarding commblog posts as a newcomer issue, you can track the discussion on #128

Regarding previous D&I sessions at FLOCK, I created #142 to have a new page on this in teams docs. We can add a link to this page to event resources doc once its created :)

For ideas on finding speakers, we are planning to create a list of speakers from underrepresented groups, we are tracking it in #140

For activity suggestions, @nasirhm will add info on workshop for newcomers in fedora to the docs and this is being tracked in #129

for women in open source related resources, @amsharma @jonatoni do you have any suggestions or would you like to link from your previous talks?

Ideas which are not yet being worked on:

• Maybe some info on Imposter Syndrome or Unconscious Bias would be good. I think this is especially relevant for FWD organizers based on @orionstar25's feedback about systemic bias

• How to find Newcomer issues/ easy first bugs for the hackathon

For newcomer tasks for the hackathon, I think collecting badges can also be a good idea to get familiar with Fedora contributor ecosystem. Here are some badges newcomers can try to collect during the hackathon: https://networksfordata.wordpress.com/2015/10/19/fedorabadges/
Also, it introduces folks to FedoraTagger, AskFedora etc.
What do you think about adding this in the resource pack?

Also re:newcomer issues, does Join SIG have more info on this? I know for folks interested in translation, we can point them towards zanata but I am not sure about other teams eg. how to become a package maintainer?

@bee2502
For newcomer tasks for the hackathon, I think collecting badges can also be a good idea to get familiar with Fedora contributor ecosystem. Here are some badges newcomers can try to collect during the hackathon: https://networksfordata.wordpress.com/2015/10/19/fedorabadges/
Also, it introduces folks to FedoraTagger, AskFedora etc.
What do you think about adding this in the resource pack?

For badges, CommOps maintains this page: https://docs.fedoraproject.org/en-US/commops/contribute/first-steps/ which introduces newcomers to badges.

We can add a link in the resource pack.

Also re:newcomer issues, does Join SIG have more info on this? I know for folks interested in translation, we can point them towards zanata but I am not sure about other teams eg. how to become a package maintainer?

For newcomers the best thing would be to point them to Fedora Join SIG and create a ticket for them here: https://pagure.io/fedora-join/Welcome-to-Fedora/issues for Join SIG to keep track of newcomers and connect them with their respective interests (packaging, infra, docs, etc).

Ideas which are not yet being worked on:

Maybe some info on Imposter Syndrome or Unconscious Bias would be good. I think this is especially relevant for FWD organizers based on @orionstar25's feedback about systemic bias

This has been added as a stretch goal in Nest session. If time doesn't permit that day, I'll make a separate ticket for this and handle it.

@orionstar25 can you pls update this?

@orionstar25 joined the Docs Mentor Hour and raised a few good questions about the Resource Pack and what kind of content we want to be responsible for maintaining. I added this ticket to next week's meeting agenda.

Discussed in 2020-09-10 meeting.

We determined there is an organization question to this ticket. Since this ticket is old and has many comments (i.e. harder to follow), @orionstar25 will open a new ticket about how to organize our docs to make them more usable for anyone who wants to organize more inclusive events (instead of being specific to FWD organizers only—which was never the intention but might have been the interpretation by some).

Closing this ticket as stale and will drive the conversation forward in @orionstar25's ticket!

Actually looking back, this ticket is technically not stale—there are still things we should address here.

But I think the work in this ticket is blocked on the bigger question of how to organize / structure our event-related docs. There are a few different tickets that are probably connected to the structure ticket.

Reopening this, but marking it as blocked.

I am opening this ticket up as help wanted now that the docs are restructured and better organized.

This is going to be a tricky ticket. I am looking at the Resource Pack page, and it is pretty long. I wonder if there are ways we could better organize the content (e.g. breaking it up across different sub-pages like FWD pages). We might also be able to do xref's out to other teams with their own documentation. When we first wrote the Resource Pack, not many teams had made the jump yet. But I think docs.fp.o is more widely used now and we might be able to link out to more updated/current content.

Sharing some points shared by @lilyx in #174:

@lilyx wrote…
I actually would like to propose to give this page a bit of a revamp in general and would love to undertake that if that would be cool with others. I think that it could be made a bit more helpful for organizers with some layout changes and some changes to content: such as making the section focused on python to be a part of a broader section that provides resources of multiple fedora labs so that organizers could have quick access to a few different workflow topics to present on.

Would it also be useful to include some information about our shift to virtual events with Hopin as well?

@lilyx Think you would want to work on this one?

I'm down to work on this.

Would I be able to get access to the 2019 feedback that's referred to in the background heading of this ticket?

@jflory7,I agree and think more division will help a lot with clarity. A balance of clear division, comfortable scroll length, and minimal amount of clicks necessary to get around will be the goal.
Linking across the docs.fp.o will certainly help in that area.

Discussed in 2022-04-25 team meeting.

Given the DEI Resource page and the docs work in 2020, this work appears to be completed. In the meeting, we discussed that this should go to the Mindshare Committee for iterative development of event guidelines and best practices.