From Fedora Project Wiki

No edit summary
 
(14 intermediate revisions by 5 users not shown)
Line 4: Line 4:


'''At a glance''':
'''At a glance''':
* ''Location'': Brno [Tentative],
* ''Location'': TBD. Ideally near a Red Hat office to reduce costs.
Potential cities include:
* Barcelona, Spain
* Brno, Czech Republic
* Berlin, Germany
* Madrid, Spain
* Munich, Germany
* Neuchâtel, Switzerland
* Puteaux, France
* Waterford, Ireland
 
* ''Dates'': May 1,2 and 3 [Tentative]
* ''Dates'': May 1,2 and 3 [Tentative]


Line 11: Line 21:
== Logic Model ==
== Logic Model ==


[[Image:Diversity FAD 2020 Logic Model.png|center|750px]]
 




Line 18: Line 28:
[[Diversity|Fedora Diversity]] is an initiative in the Fedora community. The Fedora Diversity and Inclusion team supports and encourages all kinds of different people to join and contribute in Fedora. We also aim to better understand the diverse community that composes Fedora and the unique needs and wishes of the groups that make up Fedora. Since our team is new, we plan to accomplish primary and secondary goals of the Diversity and Inclusion Team for this year.  
[[Diversity|Fedora Diversity]] is an initiative in the Fedora community. The Fedora Diversity and Inclusion team supports and encourages all kinds of different people to join and contribute in Fedora. We also aim to better understand the diverse community that composes Fedora and the unique needs and wishes of the groups that make up Fedora. Since our team is new, we plan to accomplish primary and secondary goals of the Diversity and Inclusion Team for this year.  


In our very first FAD, we have our major objectives to accomplish: (1) Build the strategy to On-boarding new team members (2) Mini D&I event packages (3) Planning to create outreach Materials (4) Core team members to work on D&I Governance Tickets to complete them. We will achieve these goals with brainstorming, exchanging experience, holding sessions and discussions, presentations, video production, and blog posts.
In our very first FAD, we have our major objectives to accomplish: (0) Refine Team's goals (1) Build the strategy to On-boarding new team members (2) Mini D&I event packages (3) Planning to create outreach Materials (4) Core team members to work on D&I Governance Tickets to complete them. We will achieve these goals with brainstorming, exchanging experience, holding sessions and discussions, presentations, video production, and blog posts.


=== Primary Goals ===
=== Primary Goals ===


''tl;dr'':
* A retrospective of D&I team's work
 
* Defining D&I team's goals
* Defining D&I team's goals
* Define strategies for on-boarding new team members
* Define strategies for on-boarding new team members
Line 29: Line 38:
* Planning to create outreach Materials
* Planning to create outreach Materials
* Core team members to work on D&I Governance Tickets
* Core team members to work on D&I Governance Tickets
* Clean the ticket queue
* Plan a yearly schedule for events and activities based on important dates (FWDs, Fedora Anniversary, IDPwD, etc) that we could easily fix on time/date worldwide and.
* Create, organize and have a ready swag package (either digital/physical or both) ready for this already planned activities.
* Define the D&I Governance Structure. Either we will have an advisory position or we will have a round table.
==== A retrospective of D&I team's work ====
It has been a bunch of years since D&I team formed, it is good time to do a retrospective of the efforts team has put-in so far and how it impacted Fedora community overall. It will be nice to sit together in a room and try to answer these questions as a team : 
* What kind of work D&I team thinks was more effective and important in the space of diversity and inclusion?
* What it was which did not work so well and did not have an impact?
* What were the roadblocks?
* What was helpful?
* What is that we should just stop doing and what is that we should continue to put our efforts in?


==== Defining D&I team's goals ====
==== Defining D&I team's goals ====
''tl;dr'':


* Review exiting team goals
* Review exiting team goals
* Revisit the need of existing goals - which one to keep and which one to leave
* Revisit the need of existing goals - which one to keep and which one to leave
* Adding new goals which team thinks are important
* Adding new goals which team thinks are important
* Create a strategy or plan for all events to follow that help us visualize more how Diverse and Open our Fedora community is


As a team, we all are self motivated to walk on the path of diversity and inclusion and committed to keep Fedora a welcoming community as it is now and even more. But, Defining the goals always help us to be more active and regular and easy to measure the success rate somewhat :)
As a team, we all are self motivated to walk on the path of diversity and inclusion and committed to keep Fedora a welcoming community as it is now and even more. But, Defining the goals always help us to be more active and regular and easy to measure the success rate somewhat :)
Line 48: Line 71:
This is time to revisit these goals and refine them according to need of the hour.
This is time to revisit these goals and refine them according to need of the hour.


==== Code of Conduct (CoC) analysis ====
==== Define strategies for on-boarding new team members ====
 
 
* Encourage participation to other Fedora subprojects
 
For example, they can explore and collect Fedora Badges to get to know different areas in Fedora community. We should also encourage them to get involved and communicate with different teams in Fedora to better aid their D&I oriented efforts.
* Seek help for tasks where we need support from other Fedora subprojects
For example, these contributors can support us with Design, translation, video creation and captioning.
* Facilitate cross-team communication across Fedora
* Leveraging their local network and FOSS involvement for outreach events
* Members who are also involved with other open source projects beyond Fedora can help us learn more about successful D&I practices in other projects.
* Pathways to get more community members involved
* Have one action item for community members during Fedora podcast. Broadly, we can publish a 'call for help' with clear and concise action items at some intervals.
*  This initiative can help - https://fedoraproject.org/wiki/Marketing/Contributor_Recruitment . Currently this initiative is in its planning/development phase.
 
Leveraging their local network and FOSS involvement for outreach events like FWD
 
 
==== Mini D&I event packages ====


''tl;dr'':  
* Packages for meetups, socials, local hackfests, film screenings, skill shares etc.
* This ties into Mindshare $100-150 events.
* This also ties into one of the goals the FPL mentions here for 2020: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ZBU4MYRMMAE2Z7DL4NPPECTMX2FBQAVL/
* Putting together a package might mean different things. But the basis would be: how to request and receive resources (money & swag), marketing materials for before the event, materials for the event. Strategy plan on how to achieve favorable outcomes (new contributors/users & also a general D&I welcome). And also tips and hints on running an event in general.
* This also ties into the resource pack we share with FWD organizers. It's not very detailed but it's the start of what we want to do to help empower local organizers to put together more Fedora events in their own communities. https://docs.google.com/document/d/17_MicCWj4o08VU3HhxcOJ_N7iBGURXgb6o1xaq0y_c0/edit?usp=sharing . This is kind of content with a need for: social media templates for advertisement of the events, posters, ready to go slide deck, suggestions for swag, and also a “how to” to get enabled to do this.
* Create a digital folder with swag available for locations that can receive physical swag (FADs, FWD, D&I Meetups, etc)


* Discuss what areas the current Code of Conduct succeeds and where it falls short
==== D&I Governance Tickets ====
* Analyze how effectively the CoC is communicated and how we can improve on visibility
* Apply CoC to any relevant examples of harassment or bullying and propose changes as necessary


Having a Code of Conduct is essential to any open source project. It creates the playing field for how our community interacts and behaves with one another. Ensuring that it empowers contributors to be excellent to each other and create a welcoming and inclusive space is important. There are countless examples of CoC across the open source world. Some work well and others don't. How does Fedora's stack up against projects that seem to be handling diversification efforts well? For projects that aren't doing as well, are there key points or lessons we can learn to avoid future pitfalls? Critical analysis and collaborative discussion about the current Fedora CoC would be a target item for a Diversity FAD to ensure our project is up to spec with other successful projects in the greater open source community.
* Core team members to work on D&I Governance Tickets
* There are many such tickets pending since long time due to lack of better direction and common consensuses. Like :
* Evaluate Summer Coding internship expectations
* Determine workflow for status updates to Fedora Council
* Define Fedora D&I team lead role, responsibilities and term
* Diversity decision making process
* Defining Fedora Council Diversity Advisor term
Team need a common platform to get together and resolve these long pending important tickets.


=== Secondary Goals ===
=== Secondary Goals ===


In addition, we will attempt to complete the following secondary goals as time allows:
In addition, we will attempt to complete the following secondary goals as time allows:
# '''D&I or women's event for Flock : Planning a D&I or women's event for Flock should also be on the list(women’s lunch). This idea can be broadened. The idea that Fedora promotes D&I for D&I sake. For example, we do a session at a *different* events that are not Fedora specific. Say Devconf, or an open source summit, a D&I social "sponsored by Fedora".'''
# '''Creating Outreach Materials : Another cool agenda item/idea would be to try to focus some outreach. Create some materials (email, blog posts, social media posts) that are strategically sent to groups that would be interested in what we are doing. For example, internal Red Hat Pride group for those of us Red Hatters, local pride and ally groups, diversity in open source groups, diversity in tech groups. Etc'''
# '''Social Hours for Fedora by D&I : Calling for Fedora contributors on remote social hours and sharing thoughts/ideas/chatting etc. To make it more engaging/interesting for people to attend, we had the idea to use boardgamearena.com as an activity to bring people together.'''
# '''Make adjustments to the work-flow of the Diversity and Inclusion  Team to improve productivity and timeliness of future, upcoming tasks'''
# '''Make adjustments to the work-flow of the Diversity and Inclusion  Team to improve productivity and timeliness of future, upcoming tasks'''
# '''Work towards clearing out the Fedora Diversity and Inclusion Team tickets queue''' (see: [https://pagure.io/fedora-diversity/issues tickets])
# '''Work towards clearing out the Fedora Diversity and Inclusion Team tickets queue''' (see: [https://pagure.io/fedora-diversity/issues tickets])
Line 67: Line 122:
=== Q&A ===
=== Q&A ===


# '''Why do we need a diversity survey?'''
# '''Why do we need a D&I FAD?'''
#* Numbers are crucial for the Fedora Project in every aspect. It's one thing to say we are a diverse community, but another to be able to show that. We would better understand how many contributors belong to which minority group and what issues they are facing. With that info, we can begin to improve on ways to make Fedora more accessible and inclusive for them. This is going to be first of its kind in Fedora and will help understand the diverse dimensions of our community at a high level.
#*  
# '''Why should there be a diversity marketing campaign?'''
 
#* Fedora Diversity is an important project for on-boarding new Fedora contributors from diverse areas and backgrounds. Being more inclusive creates a more dynamic environment with new ideas to further and advance the project forward. It is critical for two Fedora objectives: '''building open source diverse communities and developing the science and practice of diverse communities'''. We're looking to engage a pool of diverse people to further the open source movement in and outside our community. By focusing on an underrepresented discipline within FLOSS/Fedora, we are making the investment into diversity that will give us returns in reaching individuals with new and powerful ideas.
# '''Why during DevConf?'''
#* We would like to take help and guidance from the FPL, F-CAKE and other folks who may attend DevConf. It will be easy to reach out to them, and if we align the FAD with DevConf in terms of date and location, it will save on travel expenses for bringing interested people to the FAD.


Add your question here and we're happy to answer! Make sure you let us know in [https://webchat.freenode.net/?channels=fedora-diversity #fedora-diversity] if you have left a question here.
Add your question here and we're happy to answer! Make sure you let us know in [https://webchat.freenode.net/?channels=fedora-diversity #fedora-diversity] if you have left a question here.
Line 81: Line 133:


The completion of these objectives will create the following positive changes within Fedora:
The completion of these objectives will create the following positive changes within Fedora:
 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
* '''Diversity survey'''
** One of the line items for building open source communities is including current and potential contributors to our project community. To effectively create an inclusive environment, an understanding of the community we have is fundamental to creating an inclusive atmosphere. The survey results allow us to understand the composure of the community and how effective of a performance we are at creating an open and friendly environment for contributors across the world.
** In addition to understanding our current contributors, the results allow us to better impact a future generation of contributors. The feedback we would receive from this survey would illuminate key areas of success and areas needing improvement. With that insight, we can have targeted focus towards improving weaker areas to include more underrepresented groups in our project community.
* '''Marketing campaign'''
** Taking the results of the survey, we can create focus groups or targeted strategies to directly improve representation of underrepresented groups in Fedora. The campaign allows us to focus specifically on outreach and exposing the project as an inclusive and friendly environment. The marketing campaign is the extension to the survey and aims to build our community further by inviting new groups of individuals into the project community.
* '''Code of Conduct analysis'''
** In order to promote a global perspective and create a welcoming community, a comprehensive Code of Conduct is important to govern general interactions among contributors. The Code of Conduct drives the belief that we as contributors must always ''be excellent to one another'', and this builds the community as a united global team.


These outcomes connect with the Fedora Community [[Objectives]] by innovating the focus towards diversity-related issues as an open source project and being a leader across the open source world by devoting time and resources to addressing these needs and tasks. By supporting this FAD, Fedora is sending a clear message that it supports building an inclusive, diverse community and supports the team in the above mentioned purpose and goals planned for the FAD. The end result of the FAD is intended to bolster the community's engagement with underrepresented groups and bring more contributors with a variety of ideas and unique perspectives into the project. The long-term vision that would be supported by this FAD is project that is more representative of people from various parts of the world and a range of identities that are committed towards growing and developing Fedora with their time, ideas, and energy.
These outcomes connect with the Fedora Community [[Objectives]] by innovating the focus towards diversity-related issues as an open source project and being a leader across the open source world by devoting time and resources to addressing these needs and tasks. By supporting this FAD, Fedora is sending a clear message that it supports building an inclusive, diverse community and supports the team in the above mentioned purpose and goals planned for the FAD. The end result of the FAD is intended to bolster the community's engagement with underrepresented groups and bring more contributors with a variety of ideas and unique perspectives into the project. The long-term vision that would be supported by this FAD is project that is more representative of people from various parts of the world and a range of identities that are committed towards growing and developing Fedora with their time, ideas, and energy.
Line 101: Line 146:


{|class="wikitable sortable"
{|class="wikitable sortable"
! border="1" | Name        !! Remote? !! Fri !! Sat !! Sun !! Core Tasks
! border="1" | Name        !! Remote? !! Fri !! Sat !! Sun
|-
| [[User:Tatica|Tatica Leandro]] || Yes  ||  X  || X || X || Fedora [[Diversity Adviser]]; direction and team strategy; survey planning, execution, and analysis; marketing focus
|-
| [[User:Jflory7|Justin W. Flory]] || No  ||  X  || X ||  X || Community focus ([[CommOps]]); CoC critical analysis; marketing and outreach strategy for on-boarding new contributors
|-
| [[User:Bee2502|Bee Padalkar]] || No  ||  X  || X || X || Survey planning, execution, and analysis; expertise in analysis and metrics from other examples in Fedora, Community focus ([[CommOps]]) and outreach strategy.
|-
|-
| [[User:Amsharma|Amita Sharma]] || No  || X  || X || X || Survey planning, execution, and analysis; assisting in marketing and outreach, work on COC expansion and marketing, test and spread about private pagure repo for reporting issues
| [[User:Jflory7|Justin W. Flory]] || No  ||   X  || X || X  
|-
|-
| [[User:Jonatoni|Jona Azizaj]] || No || X || X || X || Marketing strategy, [[Ambassadors]] representative, member of [https://openlabs.cc/ Open Labs] / [http://oscal.openlabs.cc/ OSCAL] (>50% female participation)
| [[User:amsharma|Amita Sharma]] || No ||   X || X || X  
|-
|-
| [[User:Marinaz|Marina Zhurakhinskaya]] || Yes || X || X || X || Survey planning, providing feedback; can join in afternoons (EST mornings)
| [[User:tatica|Tatica Leandro]] || Depend on Funding ||   X || X || X  
|-
|-
| [[User:bex|Brian Exelbierd]] || No || X || X || X || FCAIC, assistance
| [[User:riecatnor|Marie Nordin]] || No ||   X || X || X  
|-
|-
| [[User:Rhea|Radka Janeková]] || No  || X  || X || X || Event on-site logistics; Survey planning, execution, and analysis
| [[User:jonatoni|Jona Azizaj]] || No  ||   X  || X || X  
|-
|-
| [[User:alishapapun|Alisha Mohanty]] || Depend on Funding  ||  X  || X ||  X
|}
|}


== Planning Prerequisites ==
== Planning Prerequisites ==
A lot of the ongoing discussion and planning is happening in our [https://pagure.io/fedora-diversity/issue/8 Pagure issue] for the FAD. The below checklist may not actively reflect where we currently are with planning (but we will try keeping it up to date). (for organizers: [[How to organize a FAD]])
* <strike>Create wiki page skeleton, fill out basic information</strike>
* <strike>Expand on the purpose of the FAD and what objectives we aim to accomplish</strike>
* <strike>From purposes, derive perceived impact on Project and how our work aligns with the mission of Fedora, along with how supporting this FAD advances the future and growth of the Fedora Project (see: a completed [https://pagure.io/FedoraLogicModelTemplate Fedora logic model] would be especially helpful!!!)</strike>
* <strike>Discuss current purposes and impacts on the mailing list or in a meeting; come to final agreement</strike>
* <strike>Confirm and finalize ideal dates for as many participants as possible</strike>
* <strike>Choose a venue based on locations, available dates of FAD participants, and '''budget''' (multiple proposals are acceptable)</strike>
* <strike>On mailing list or meeting, vote on proposed locations and agree on a destination to pitch</strike>
* <strike>Research transportation, food options, other smaller parts of FAD for budgeting</strike>
* Plan and arrange small social event for team (e.g. dinner or small trip to local venue or attraction)
* <strike>Create proposal ticket in Fedora Council Trac '''NO LATER THAN OCTOBER 10'''</strike>
* Begin framing scope of survey / marketing campaign
* <strike>Finalize venue reservations</strike>
* <strike>Arrange refreshments</strike>
* <strike>Arrange social event</strike>
== Plan ==
=== Proposal 1: DevConf ===
# '''Location:'''  Brno University of Technology Faculty of Information Technology. - Brno - Czech Republic
# '''Date:''' 25 – 30 January 2017
# '''Schedule'''
#* Participants arrive at Jan 26 (a day before devconf)
#* Participants leave at Jan 30
# Important skills (one or more)
#* Community management
#* Data analysis
#* Diversity and inclusion training
#* Experience from underrepresented group(s)
# Other considerations
#* Transportation from airport / bus station to Red Hat offices will need to be arranged (renting a vehicle or better solution?)
=== Proposal 2: Open Labs Hackerspace, OSCAL ===
# '''Location:'''  Tirana, Albania
# '''Date:''' (tentative) 13 - 14 May 2017
# '''Schedule'''
#* Participants arrive at May 12
#* Participants leave at May 16
# Important skills (one or more)
#* Community management
#* Data analysis
#* Diversity and inclusion training
#* Experience from underrepresented group(s)
# Other considerations
#* Transportation from airport / bus station to Open Labs will need to be arranged (Jona able to help as a local or renting a vehicle?)




== Logistics ==
== Logistics ==


Further details about these logistics are present in the [[FAD_Diversity_2017#Budget|full budget]]. Specific details about stores, restaurants, or menus will be planned closer to the event (within the confines of the allocated funds for the logistics). Non-budgetary specifics will be chosen once a proposal is finalized.
=== Proposal 1: DevConf ===
The first proposal is to organize it after [https://devconf.cz/ DevConf] in Brno, Czech Republic.
* '''Snacks/Beverages''':
** $30 USD
* '''Lunch''':
** $120 USD
*** Appx. $30 USD per person for four people
* '''Dinner''':
** $150 USD
'''''TOTAL''''': $300 USD
=== Proposal 2: Open Labs Hackerspace, OSCAL ===
The second proposal is to organize it after [http://oscal.openlabs.cc OSCAL] in Tirana, Albania.
* '''Snacks/Beverages''':
** $30 USD
* '''Lunch''':
** $120 USD
*** Appx. $30 USD per person for four people
* '''Dinner''':
** $150 USD
'''''TOTAL''''': $300 USD
== Budget ==
=== Proposal 1: DevConf ===
The first proposal is to organize it after [https://devconf.cz/ DevConf] in Brno, Czech Republic.
{|
! # !! Contributor !! Travel Plan !! Estimated Travel Cost !! Accommodation
|-
| 1 || [[User:Amsharma|Amita]] || BOM<=>PRG<=>Brno || $650 + $40 = $690 USD || 65 $/night * 6 = $390 USD
|-
| 2 || [[User:Bee2502|Bee]] || BOM<=>PRG<=>Brno || $650 + $40 = $690 USD || sharing
|-
| 3 || [[User:Jonatoni|Jona]] || TIA=>VIE=>Brno=>VIE=>BRU || $200 + $36 = $236 || 65 $/night * 6 = $390 USD
|-
| 4 || [[User:Jflory7|Justin]] || DBV<=>VIE<=>Brno || $140 + $36 = $176 USD || sharing
|-
|}
# '''Travel:''' $1792 USD for airfare, bus, train, etc. funding needed to get attendees to the FAD
# '''Accommodation:''' $780 USD for hotel, etc. needed to have attendees sleep during the FAD
#* [http://www.vista-hotel.cz/homepage/ Hotel Vista]
# '''Space:''' $0
#* Red Hat Office
# '''Meals:''' $300 USD = $150 for lunch + snacks ($30/meal est. per each of 4 people + $30 of snacks) + $150 for one social dinner
# '''Supplies:''' $0 for anything else you may need
'''Total budget: ~$2872 USD
=== Proposal 2: Open Labs Hackerspace, OSCAL ===
The second proposal is to organize it after [http://oscal.openlabs.cc OSCAL] in Tirana, Albania.
{|
! # !! Contributor !! Travel Plan !! Estimated Travel Cost !! Accommodation
|-
| 1 || [[User:Amsharma|Amita]] || BOM<=>TIA || $900 USD || 28 $/night * 5 = $140
|-
| 2 || [[User:Bee2502|Bee]] || BOM<=>TIA || $900 USD || sharing with Amita
|-
| 3 || [[User:Jonatoni|Jona]] || - || $0 || $0 /hometown/
|-
| 4 || [[User:Jflory7|Justin]] || DBV<=>TIA || $327 USD || 20 $/night * 5 = $100
|-
|}
# '''Travel:'''  $2127 USD for airfare, bus, train, etc. funding needed to get attendees to the FAD
# '''Accommodation:'''  $240 USD for hotel, etc. needed to have attendees sleep during the FAD
#* [http://bit.ly/2dfB199 London Hotel]
# '''Space:''' $300 USD
#* [https://www.openlabs.cc Open Labs Hackerspace]
# '''Meals:''' $300 USD = $150 for lunch + snacks ($30/meal est. per each of 4 people + $30 of snacks) + $150 for one social dinner
# '''Supplies:''' $0 USD
'''Total budget: ~$2967 USD
NOTE - Travel ticket cost is subject to change with the delay in time to book.
--[[User:Bee2502|Bee2502]] ([[User talk:Bee2502|talk]]) 19:56, 19 January 2017 (UTC) FAD proposal for Brno at FIT, VUT during devconf.cz (Jan 27-29, 2017) has been accepted.


== Related Pagure Ticket ==
== Related Pagure Ticket ==


More information about the FAD can be found [https://pagure.io/fedora-diversity/issue/8 here]
More information about the FAD can be found in this ticket - https://pagure.io/fedora-diversity/issue/115


== Schedule ==
== Schedule ==

Latest revision as of 13:55, 1 February 2020

Error creating thumbnail: File missing

This is the main page for the Fedora Diversity FAD, which focuses on reviewing and finishing our current goals, and defining the next plans to improve diversification efforts in our community.

At a glance:

  • Location: TBD. Ideally near a Red Hat office to reduce costs.

Potential cities include:

  • Barcelona, Spain
  • Brno, Czech Republic
  • Berlin, Germany
  • Madrid, Spain
  • Munich, Germany
  • Neuchâtel, Switzerland
  • Puteaux, France
  • Waterford, Ireland
  • Dates: May 1,2 and 3 [Tentative]


Logic Model

Purpose

Fedora Diversity is an initiative in the Fedora community. The Fedora Diversity and Inclusion team supports and encourages all kinds of different people to join and contribute in Fedora. We also aim to better understand the diverse community that composes Fedora and the unique needs and wishes of the groups that make up Fedora. Since our team is new, we plan to accomplish primary and secondary goals of the Diversity and Inclusion Team for this year.

In our very first FAD, we have our major objectives to accomplish: (0) Refine Team's goals (1) Build the strategy to On-boarding new team members (2) Mini D&I event packages (3) Planning to create outreach Materials (4) Core team members to work on D&I Governance Tickets to complete them. We will achieve these goals with brainstorming, exchanging experience, holding sessions and discussions, presentations, video production, and blog posts.

Primary Goals

  • A retrospective of D&I team's work
  • Defining D&I team's goals
  • Define strategies for on-boarding new team members
  • Building mini D&I event packages
  • Planning to create outreach Materials
  • Core team members to work on D&I Governance Tickets
  • Clean the ticket queue
  • Plan a yearly schedule for events and activities based on important dates (FWDs, Fedora Anniversary, IDPwD, etc) that we could easily fix on time/date worldwide and.
  • Create, organize and have a ready swag package (either digital/physical or both) ready for this already planned activities.
  • Define the D&I Governance Structure. Either we will have an advisory position or we will have a round table.


A retrospective of D&I team's work

It has been a bunch of years since D&I team formed, it is good time to do a retrospective of the efforts team has put-in so far and how it impacted Fedora community overall. It will be nice to sit together in a room and try to answer these questions as a team :

  • What kind of work D&I team thinks was more effective and important in the space of diversity and inclusion?
  • What it was which did not work so well and did not have an impact?
  • What were the roadblocks?
  • What was helpful?
  • What is that we should just stop doing and what is that we should continue to put our efforts in?


Defining D&I team's goals

  • Review exiting team goals
  • Revisit the need of existing goals - which one to keep and which one to leave
  • Adding new goals which team thinks are important
  • Create a strategy or plan for all events to follow that help us visualize more how Diverse and Open our Fedora community is

As a team, we all are self motivated to walk on the path of diversity and inclusion and committed to keep Fedora a welcoming community as it is now and even more. But, Defining the goals always help us to be more active and regular and easy to measure the success rate somewhat :) Some of the existing goals we have are : Outreachy Summer 2018 Defining policy for room sharing or single room booking for being more inclusive with the help of council Fedora Women Day Fedora Diversity Team Presence in Flock At least one more new diversity event, which we would like to introduce or Do on bigger scale like FWD

This is time to revisit these goals and refine them according to need of the hour.

Define strategies for on-boarding new team members

  • Encourage participation to other Fedora subprojects

For example, they can explore and collect Fedora Badges to get to know different areas in Fedora community. We should also encourage them to get involved and communicate with different teams in Fedora to better aid their D&I oriented efforts.

  • Seek help for tasks where we need support from other Fedora subprojects

For example, these contributors can support us with Design, translation, video creation and captioning.

  • Facilitate cross-team communication across Fedora
  • Leveraging their local network and FOSS involvement for outreach events
  • Members who are also involved with other open source projects beyond Fedora can help us learn more about successful D&I practices in other projects.
  • Pathways to get more community members involved
  • Have one action item for community members during Fedora podcast. Broadly, we can publish a 'call for help' with clear and concise action items at some intervals.
  • This initiative can help - https://fedoraproject.org/wiki/Marketing/Contributor_Recruitment . Currently this initiative is in its planning/development phase.

Leveraging their local network and FOSS involvement for outreach events like FWD


Mini D&I event packages

  • Packages for meetups, socials, local hackfests, film screenings, skill shares etc.
  • This ties into Mindshare $100-150 events.
  • This also ties into one of the goals the FPL mentions here for 2020: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ZBU4MYRMMAE2Z7DL4NPPECTMX2FBQAVL/
  • Putting together a package might mean different things. But the basis would be: how to request and receive resources (money & swag), marketing materials for before the event, materials for the event. Strategy plan on how to achieve favorable outcomes (new contributors/users & also a general D&I welcome). And also tips and hints on running an event in general.
  • This also ties into the resource pack we share with FWD organizers. It's not very detailed but it's the start of what we want to do to help empower local organizers to put together more Fedora events in their own communities. https://docs.google.com/document/d/17_MicCWj4o08VU3HhxcOJ_N7iBGURXgb6o1xaq0y_c0/edit?usp=sharing . This is kind of content with a need for: social media templates for advertisement of the events, posters, ready to go slide deck, suggestions for swag, and also a “how to” to get enabled to do this.
  • Create a digital folder with swag available for locations that can receive physical swag (FADs, FWD, D&I Meetups, etc)

D&I Governance Tickets

  • Core team members to work on D&I Governance Tickets
  • There are many such tickets pending since long time due to lack of better direction and common consensuses. Like :
  • Evaluate Summer Coding internship expectations
  • Determine workflow for status updates to Fedora Council
  • Define Fedora D&I team lead role, responsibilities and term
  • Diversity decision making process
  • Defining Fedora Council Diversity Advisor term

Team need a common platform to get together and resolve these long pending important tickets.

Secondary Goals

In addition, we will attempt to complete the following secondary goals as time allows:

  1. D&I or women's event for Flock : Planning a D&I or women's event for Flock should also be on the list(women’s lunch). This idea can be broadened. The idea that Fedora promotes D&I for D&I sake. For example, we do a session at a *different* events that are not Fedora specific. Say Devconf, or an open source summit, a D&I social "sponsored by Fedora".
  2. Creating Outreach Materials : Another cool agenda item/idea would be to try to focus some outreach. Create some materials (email, blog posts, social media posts) that are strategically sent to groups that would be interested in what we are doing. For example, internal Red Hat Pride group for those of us Red Hatters, local pride and ally groups, diversity in open source groups, diversity in tech groups. Etc
  3. Social Hours for Fedora by D&I : Calling for Fedora contributors on remote social hours and sharing thoughts/ideas/chatting etc. To make it more engaging/interesting for people to attend, we had the idea to use boardgamearena.com as an activity to bring people together.
  4. Make adjustments to the work-flow of the Diversity and Inclusion Team to improve productivity and timeliness of future, upcoming tasks
  5. Work towards clearing out the Fedora Diversity and Inclusion Team tickets queue (see: tickets)
  6. Collect pictures and video assets from various locations and contributors for later video production

Q&A

  1. Why do we need a D&I FAD?


Add your question here and we're happy to answer! Make sure you let us know in #fedora-diversity if you have left a question here.

Impact

The purpose, goals, and deliverable outlined above help further the project-wide Objectives identified by the Fedora Council. The on-going objective that this FAD focuses on most is building open source software communities.

The completion of these objectives will create the following positive changes within Fedora: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

These outcomes connect with the Fedora Community Objectives by innovating the focus towards diversity-related issues as an open source project and being a leader across the open source world by devoting time and resources to addressing these needs and tasks. By supporting this FAD, Fedora is sending a clear message that it supports building an inclusive, diverse community and supports the team in the above mentioned purpose and goals planned for the FAD. The end result of the FAD is intended to bolster the community's engagement with underrepresented groups and bring more contributors with a variety of ideas and unique perspectives into the project. The long-term vision that would be supported by this FAD is project that is more representative of people from various parts of the world and a range of identities that are committed towards growing and developing Fedora with their time, ideas, and energy.


Detailed Work Items & Final Attendees

Participants

Travel days
Travel days are Thursday and Monday. On-site participants are leaving early on Monday morning.
Name Remote? Fri Sat Sun
Justin W. Flory No X X X
Amita Sharma No X X X
Tatica Leandro Depend on Funding X X X
Marie Nordin No X X X
Jona Azizaj No X X X
Alisha Mohanty Depend on Funding X X X

Planning Prerequisites

Logistics

Related Pagure Ticket

More information about the FAD can be found in this ticket - https://pagure.io/fedora-diversity/issue/115

Schedule

Work in Progress

Retrieved from "https://fedoraproject.org/w/index.php?title=Diversity_Hackfest_2020&oldid=565097"