From Fedora Project Wiki

m (Update category from Category:Diversity to Category:Diversity_and_Inclusion)
 
(40 intermediate revisions by 7 users not shown)
Line 1: Line 1:
[[Image:Lápis-945x400.jpg]]
+
[[Image:Lápis-945x400.jpg|thumb|450px]]
 +
 
 +
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'': FIT, VUT Brno CZ. More information [https://devconf.cz/#venue here],
 +
* ''Dates'': Jan 27-29, 2017
 +
 
 +
 
 +
 
 +
== Logic Model ==
 +
 
 +
[[Image:Diversity FAD 2017 Logic Model.png|center|750px]]
  
This is the main page for the Fedora Diversity Day, which is a [[FAD]] focused on review and finish our current coals and define the next plans to improve the Diversity efforts in our community.
 
  
 
== Purpose ==
 
== Purpose ==
[https://fedoraproject.org/wiki/Diversity Fedora Diversity] is a new initiative in Fedora community. This is to support and encourage all kind of different people to join and contribute in Fedora. Since we are new, we have planned to accomplish some primary goals of the diversity team.
 
In our very first FAD, we have few objectives to accomplish i.e. Diversity Survey, Diversity Marketing Campaign and COC Expansion.
 
  
We would like to achieve our goal of Diversity Survey, Diversity Marketing Campaign And COC Expansion via brainstorming, experience exchange, sessions/discussions, presentations, video making and blog posts.
+
[[Diversity|Fedora Diversity]] is a new 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) Diversity Survey, (2) Diversity Marketing Campaign, and (3) CoC critical analysis. We will achieve these goals with brainstorming, exchanging experience, holding sessions and discussions, presentations, video production, and blog posts. If FAD happen to be around devconf, then we would like to discuss our agenda with FPL and F-CAKE.
  
 
=== Primary Goals ===
 
=== Primary Goals ===
  
# Diversity Survey
+
==== Diversity survey ====
#* Define strategies for the usage of the Survey
+
 
#* Finish the questionnaire
+
''tl;dr'':
#* Select tool
+
 
#* Define timeline
+
* Define strategies for usage of survey
# Diversity Marketing Campaign
+
* Finish the questionnaire for survey
#* Define reach of the campaign
+
* Select tool and create draft
#* Use first survey results to create focus groups
+
* Define time-line
# CoC expansion
+
 
#* Discuss in deep CoC to see if it's wide enough against the current harassment and bullying cases we have
+
The diversity survey is one of the founding goals of the team. Similar to the [https://floss2013.larjona.net/ FLOSS Survey 2013] which received responses from 1,650 members of various open source communities, we want to have the same insight and understanding to our own community within Fedora. It's no surprise that Fedora is a global community spanning all the four corners of Earth. But it's hard to understand the unique needs and wishes of our community if we don't know they are there or what they think we could do better. The survey is the means to this end and best understanding how our community is composed to make Fedora a more welcoming and inviting place for our global community of contributors.
 +
 
 +
At a FAD, we would define the strategies for using the survey and what kind of outcomes we hope to get from creating this survey. What kind of info are we hoping to gain? How will this help us create a more welcoming and friendly environment for contributors? What kind of resources and help will be able to provide, and how can we use responses in this survey to make sure we apply these resources and help the most effective way? Once we have a strategy defined, the final questionnaire can be prepared based on [[Diversity/Survey|earlier drafts of questions]] as well as data from FLOSS Survey 2013. After the questionnaire questions and scope are defined, the best tool to fit our needs for delivering the survey will be selected and an initial draft of the survey will be prepared. The final step to accomplishing this goal is creating a timeline for how and when we want to deploy this survey to the greater Fedora community.
 +
 
 +
==== Diversity marketing campaign ====
 +
 
 +
''tl;dr'':
 +
 
 +
* Define reach of the campaign
 +
* Use first survey results to create focus groups
 +
 
 +
A diversity-specific marketing campaign would be one of the outcomes from the data collected from the survey. While we would not have a data set to work with immediately, we want to create plans for how we can focus on reaching out to underrepresented groups and encourage participation. Ensuring we have the right tooling ahead of time for managing and manipulating the collected data is necessary for successful understanding of the survey results. An additional task for this goal would be to discuss how we could create focus groups for specific groups (ethnic, gender, or other) to encourage participation in Fedora and open source.
 +
 
 +
==== Code of Conduct (CoC) analysis ====
 +
 
 +
''tl;dr'':
 +
 
 +
* Discuss what areas the current Code of Conduct succeeds and where it falls short
 +
* 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.
  
 
=== 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:
# '''Make adjustments to the working process of the Diversity Team, to fulfill in the future all 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 Team tickets queue''', [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])
# '''Collect the pictures from all the locations for video making'''
+
# '''Collect pictures and video assets from various locations and contributors for later video production'''
  
=== Q & A ===
+
=== Q&A ===
  
# '''Why Diversity Survey?'''
+
# '''Why do we need a diversity survey?'''
#* Numbers are important for the Fedora project in every aspect. We would like to drill down how many contributors belong to which minority group and what issues they are facing and how we can help them. This is going to be first of its kind and will help understand the diverse dimensions of the Fedora community at a high level.  
+
#* 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 Diversity Marketing Campaign?'''
+
# '''Why should there be a diversity marketing campaign?'''
#* Fedora Diversity is an important project for onboarding new Fedora Contributors from diverse areas and it is more important to be inclusive. 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 more diverse people pool to further open source, and focusing on an underrepresented discipline within FLOSS/Fedora and making sure the investment we're putting into diversity will give us returns in reaching those folks is a good one.
+
#* 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?'''
+
# '''Why during DevConf?'''
#* We would like to take help and guidance from FPL and few other folks, who may attend devconf and it will easy to reach out to them, if we align the FAD with devconf in terms of date and location.
+
#* 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.
+
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.
  
 
== Impact ==
 
== Impact ==
  
The completion of these goals will create the following positive change within the project:
+
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'''.
* outcome
+
 
* outcome
+
The completion of these objectives will create the following positive changes within Fedora:
* outcome
+
 
 +
* '''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 following Fedora Community [[Objectives]] by ''explain connection here''.
+
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.
  
 
<!-- FAD proposals with connections to the project's current 12-18 month objectives will be given priority. If you feel your FAD connects to something that could or should be such an objective but is not currently, please bring it to the Fedora Council. See http://fedoramagazine.org/lets-talk-about-fedora-project-objectives/ for some background on this planning process and on how outcomes link activity output to impact. -->
 
<!-- FAD proposals with connections to the project's current 12-18 month objectives will be given priority. If you feel your FAD connects to something that could or should be such an objective but is not currently, please bring it to the Fedora Council. See http://fedoramagazine.org/lets-talk-about-fedora-project-objectives/ for some background on this planning process and on how outcomes link activity output to impact. -->
Line 55: Line 94:
 
=== Participants ===
 
=== Participants ===
  
{{admon/note | Travel days | Travel days are Thursday and Sunday.  On-site participants are leaving early and no on-site hacking will take place on Sunday.}}
+
{{admon/note | Travel days | Travel days are Thursday and Monday.  On-site participants are leaving early on Monday morning.}}
  
 
{|class="wikitable sortable"
 
{|class="wikitable sortable"
! border="1" | Name        !! Remote? !! Fri !! Sat !! Sun   !! Core Tasks
+
! border="1" | Name        !! Remote? !! Fri !! Sat !! Sun !! Core Tasks
|-
 
| [[User:tatica|Tatica Leandro]] || Hopefully not  ||  X  ||  X  || X || Fedora Diversity Adviser, Analysis of Survey results, Marketing Strategy 
 
|-
 
| [[User:Jflory7|Justin W. Flory]] || Hopefully not  ||  X  ||  X  || X || COC Expension and Marketing Strategy
 
|-
 
| [[User:Bee2502|Bee]] || Hopefully not  ||  -  ||  X  || X || Survey Details, Analysis of Survey results and session on how to conduct survey
 
 
|-
 
|-
| [[User:amsharma|Amita]] || Hopefully not ||  - || X || X || Analysis of Survey results and help in Marketing
+
| [[User:Tatica|Tatica Leandro]] || Yes ||  X || X || X || Fedora [[Diversity Adviser]]; direction and team strategy; survey planning, execution, and analysis; marketing focus
 
|-
 
|-
| [[User:jonatoni|Jona Azizaj]] || Hopefully not || X || X || X || Marketing Strategy
+
| [[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.
 
 
=== Activities ===
 
 
 
{|class="wikitable sortable"
 
! border="1" | Name        !!
 
 
|-
 
|-
| [[User:tatica|Tatica Leandro]] || TBD
+
| [[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]] || TBD
+
| [[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:Bee2502|Bee]] || TBD
+
| [[User:Marinaz|Marina Zhurakhinskaya]] || Yes || X || X || X || Survey planning, providing feedback; can join in afternoons (EST mornings)
 
|-
 
|-
| [[User:amsharma|Amita]] || TBD
+
| [[User:bex|Brian Exelbierd]] || No || X || X || X || FCAIC, assistance
 
|-
 
|-
| [[User:jonatoni|Jona Azizaj]] || TBD
+
| [[User:Rhea|Radka Janeková]] || No  ||  X  || X || X || Event on-site logistics; Survey planning, execution, and analysis
 
|-
 
|-
 
|}
 
|}
 
* See [[FAD_Fedora_Talk_2009_game_plan]] for an example
 
  
 
== Planning Prerequisites ==
 
== Planning Prerequisites ==
  
See the [[How to organize a FAD]] list; you can keep your to-do list here.
+
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>Completed work item</strike>
+
* <strike>Create wiki page skeleton, fill out basic information</strike>
* Work out budget
+
* <strike>Expand on the purpose of the FAD and what objectives we aim to accomplish</strike>
* Decide on Dates and Location
+
* <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>
* Arrange Facilities
+
* <strike>Discuss current purposes and impacts on the mailing list or in a meeting; come to final agreement</strike>
* List Resources
+
* <strike>Confirm and finalize ideal dates for as many participants as possible</strike>
* Be Somewhat Structured
+
* <strike>Choose a venue based on locations, available dates of FAD participants, and '''budget''' (multiple proposals are acceptable)</strike>
* Arrange Lodging
+
* <strike>On mailing list or meeting, vote on proposed locations and agree on a destination to pitch</strike>
* Arrange Refreshments
+
* <strike>Research transportation, food options, other smaller parts of FAD for budgeting</strike>
* Arrange a Social Event
+
* Plan and arrange small social event for team (e.g. dinner or small trip to local venue or attraction)
* Another action item
+
* <strike>Create proposal ticket in Fedora Council Trac '''NO LATER THAN OCTOBER 10'''</strike>
* Another action item
+
* Begin framing scope of survey / marketing campaign
* Another action item
+
* <strike>Finalize venue reservations</strike>
 +
* <strike>Arrange refreshments</strike>
 +
* <strike>Arrange social event</strike>
  
 
== Plan ==
 
== Plan ==
  
=== Proposal one - At DevConf ===
+
=== Proposal 1: DevConf ===
 
# '''Location:'''  Brno University of Technology Faculty of Information Technology. - Brno - Czech Republic
 
# '''Location:'''  Brno University of Technology Faculty of Information Technology. - Brno - Czech Republic
# '''Date:''' (tentative) 27 29 January 2017
+
# '''Date:''' 25 30 January 2017
 
# '''Schedule'''
 
# '''Schedule'''
#* Participants arrive at Jan 25
+
#* Participants arrive at Jan 26 (a day before devconf)
#* Schedule item
 
#* Schedule item
 
#* Schedule item
 
 
#* Participants leave at Jan 30
 
#* Participants leave at Jan 30
 
# Important skills (one or more)
 
# Important skills (one or more)
#* skill
+
#* Community management
#* skill
+
#* Data analysis
#* skill
+
#* Diversity and inclusion training
# Personnel (people who might fit the bill)
+
#* Experience from underrepresented group(s)
#* Tatica Leandro (Venezuela, Diversity Advisory) '''Confirmed? Y'''
+
# Other considerations
#* Name (location, role) '''Confirmed? (Y/N)'''
+
#* Transportation from airport / bus station to Red Hat offices will need to be arranged (renting a vehicle or better solution?)
#* ''others?''
+
 
 +
=== 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
 
# Other considerations
#* Tatica needs to be online during week days, so she might need to travel only-on-weekends or try to make her trip as short as possible (work)
+
#* 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 ==
'''Snacks/Beverages:''' Details go here.
 
  
'''Lunch:''' Details go here.
+
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
  
'''Dinner:''' Details go here.
+
'''''TOTAL''''': $300 USD
  
 
== Budget ==
 
== Budget ==
  
'''If you want funding from Red Hat, ask the [[OSAS]] team. If you can find other ways to fund your FAD, that's great too!'''
+
=== 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 !! Dept !! Arrv !! Dept !! Arrv !! Cost
+
! # !! 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
 
|-
 
|-
| Tatica Leandro || Cucuta or Caracas, departure || Travel to FAD, arrival || Travel from FAD, departure || Cucuta or Caracas, arrival || Ticket cost (Usually cheaper from Cucuta)
+
| 3 || [[User:Jonatoni|Jona]] || - || $0 || $0 /hometown/
 
|-
 
|-
| Name || Travel to FAD, departure || Travel to FAD, arrival || Travel from FAD, departure || Travel from FAD, arrival || Ticket cost
+
| 4 || [[User:Jflory7|Justin]] || DBV<=>TIA || $327 USD || 20 $/night * 5 = $100
 
|-
 
|-
| Name || Travel to FAD, departure || Travel to FAD, arrival || Travel from FAD, departure || Travel from FAD, arrival || Ticket cost
 
 
|}
 
|}
  
# '''Travel:'''  $A for airfare, bus, train, etc. funding needed to get attendees to the FAD
 
# '''Housing:'''  $B for hotel, etc. needed to have attendees sleep during the FAD
 
#* link to hotel room booking website, if applicable
 
# '''Space:''' $C for renting space to hack in, if applicable
 
#* address and travel details for the space
 
# '''Supplies:''' $D for anything else you may need
 
#* item
 
#* item
 
#* item
 
  
''Total budget:  $A+B+C+D
+
# '''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 ==
 +
 
 +
More information about the FAD can be found [https://pagure.io/fedora-diversity/issue/8 here]
 +
 
 +
== Schedule ==
 +
 
 +
Work in Progress
  
[[Category:Diversity]]
+
----
 +
[[Category:Diversity and Inclusion]]
 
[[Category:FAD]]
 
[[Category:FAD]]

Latest revision as of 20:10, 13 September 2018

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: FIT, VUT Brno CZ. More information here,
  • Dates: Jan 27-29, 2017


Logic Model

Diversity FAD 2017 Logic Model.png


Purpose

Fedora Diversity is a new 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) Diversity Survey, (2) Diversity Marketing Campaign, and (3) CoC critical analysis. We will achieve these goals with brainstorming, exchanging experience, holding sessions and discussions, presentations, video production, and blog posts. If FAD happen to be around devconf, then we would like to discuss our agenda with FPL and F-CAKE.

Primary Goals

Diversity survey

tl;dr:

  • Define strategies for usage of survey
  • Finish the questionnaire for survey
  • Select tool and create draft
  • Define time-line

The diversity survey is one of the founding goals of the team. Similar to the FLOSS Survey 2013 which received responses from 1,650 members of various open source communities, we want to have the same insight and understanding to our own community within Fedora. It's no surprise that Fedora is a global community spanning all the four corners of Earth. But it's hard to understand the unique needs and wishes of our community if we don't know they are there or what they think we could do better. The survey is the means to this end and best understanding how our community is composed to make Fedora a more welcoming and inviting place for our global community of contributors.

At a FAD, we would define the strategies for using the survey and what kind of outcomes we hope to get from creating this survey. What kind of info are we hoping to gain? How will this help us create a more welcoming and friendly environment for contributors? What kind of resources and help will be able to provide, and how can we use responses in this survey to make sure we apply these resources and help the most effective way? Once we have a strategy defined, the final questionnaire can be prepared based on earlier drafts of questions as well as data from FLOSS Survey 2013. After the questionnaire questions and scope are defined, the best tool to fit our needs for delivering the survey will be selected and an initial draft of the survey will be prepared. The final step to accomplishing this goal is creating a timeline for how and when we want to deploy this survey to the greater Fedora community.

Diversity marketing campaign

tl;dr:

  • Define reach of the campaign
  • Use first survey results to create focus groups

A diversity-specific marketing campaign would be one of the outcomes from the data collected from the survey. While we would not have a data set to work with immediately, we want to create plans for how we can focus on reaching out to underrepresented groups and encourage participation. Ensuring we have the right tooling ahead of time for managing and manipulating the collected data is necessary for successful understanding of the survey results. An additional task for this goal would be to discuss how we could create focus groups for specific groups (ethnic, gender, or other) to encourage participation in Fedora and open source.

Code of Conduct (CoC) analysis

tl;dr:

  • Discuss what areas the current Code of Conduct succeeds and where it falls short
  • 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.

Secondary Goals

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

  1. Make adjustments to the work-flow of the Diversity and Inclusion Team to improve productivity and timeliness of future, upcoming tasks
  2. Work towards clearing out the Fedora Diversity and Inclusion Team tickets queue (see: tickets)
  3. Collect pictures and video assets from various locations and contributors for later video production

Q&A

  1. Why do we need a diversity survey?
    • 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.
  2. 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.
  3. 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 #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:

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


Detailed Work Items & Final Attendees

Participants

Note.png
Travel days
Travel days are Thursday and Monday. On-site participants are leaving early on Monday morning.
Name Remote? Fri Sat Sun Core Tasks
Tatica Leandro Yes X X X Fedora Diversity Adviser; direction and team strategy; survey planning, execution, and analysis; marketing focus
Justin W. Flory No X X X Community focus (CommOps); CoC critical analysis; marketing and outreach strategy for on-boarding new contributors
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.
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
Jona Azizaj No X X X Marketing strategy, Ambassadors representative, member of Open Labs / OSCAL (>50% female participation)
Marina Zhurakhinskaya Yes X X X Survey planning, providing feedback; can join in afternoons (EST mornings)
Brian Exelbierd No X X X FCAIC, assistance
Radka Janeková No X X X Event on-site logistics; Survey planning, execution, and analysis

Planning Prerequisites

A lot of the ongoing discussion and planning is happening in our 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)

  • Create wiki page skeleton, fill out basic information
  • Expand on the purpose of the FAD and what objectives we aim to accomplish
  • 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 Fedora logic model would be especially helpful!!!)
  • Discuss current purposes and impacts on the mailing list or in a meeting; come to final agreement
  • Confirm and finalize ideal dates for as many participants as possible
  • Choose a venue based on locations, available dates of FAD participants, and budget (multiple proposals are acceptable)
  • On mailing list or meeting, vote on proposed locations and agree on a destination to pitch
  • Research transportation, food options, other smaller parts of FAD for budgeting
  • Plan and arrange small social event for team (e.g. dinner or small trip to local venue or attraction)
  • Create proposal ticket in Fedora Council Trac NO LATER THAN OCTOBER 10
  • Begin framing scope of survey / marketing campaign
  • Finalize venue reservations
  • Arrange refreshments
  • Arrange social event

Plan

Proposal 1: DevConf

  1. Location: Brno University of Technology Faculty of Information Technology. - Brno - Czech Republic
  2. Date: 25 – 30 January 2017
  3. Schedule
    • Participants arrive at Jan 26 (a day before devconf)
    • Participants leave at Jan 30
  4. Important skills (one or more)
    • Community management
    • Data analysis
    • Diversity and inclusion training
    • Experience from underrepresented group(s)
  5. 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

  1. Location: Tirana, Albania
  2. Date: (tentative) 13 - 14 May 2017
  3. Schedule
    • Participants arrive at May 12
    • Participants leave at May 16
  4. Important skills (one or more)
    • Community management
    • Data analysis
    • Diversity and inclusion training
    • Experience from underrepresented group(s)
  5. 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

Further details about these logistics are present in the 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 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 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 DevConf in Brno, Czech Republic.

# Contributor Travel Plan Estimated Travel Cost Accommodation
1 Amita BOM<=>PRG<=>Brno $650 + $40 = $690 USD 65 $/night * 6 = $390 USD
2 Bee BOM<=>PRG<=>Brno $650 + $40 = $690 USD sharing
3 Jona TIA=>VIE=>Brno=>VIE=>BRU $200 + $36 = $236 65 $/night * 6 = $390 USD
4 Justin DBV<=>VIE<=>Brno $140 + $36 = $176 USD sharing


  1. Travel: $1792 USD for airfare, bus, train, etc. funding needed to get attendees to the FAD
  2. Accommodation: $780 USD for hotel, etc. needed to have attendees sleep during the FAD
  3. Space: $0
    • Red Hat Office
  4. Meals: $300 USD = $150 for lunch + snacks ($30/meal est. per each of 4 people + $30 of snacks) + $150 for one social dinner
  5. 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 OSCAL in Tirana, Albania.

# Contributor Travel Plan Estimated Travel Cost Accommodation
1 Amita BOM<=>TIA $900 USD 28 $/night * 5 = $140
2 Bee BOM<=>TIA $900 USD sharing with Amita
3 Jona - $0 $0 /hometown/
4 Justin DBV<=>TIA $327 USD 20 $/night * 5 = $100


  1. Travel: $2127 USD for airfare, bus, train, etc. funding needed to get attendees to the FAD
  2. Accommodation: $240 USD for hotel, etc. needed to have attendees sleep during the FAD
  3. Space: $300 USD
  4. Meals: $300 USD = $150 for lunch + snacks ($30/meal est. per each of 4 people + $30 of snacks) + $150 for one social dinner
  5. Supplies: $0 USD

Total budget: ~$2967 USD

NOTE - Travel ticket cost is subject to change with the delay in time to book.


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

More information about the FAD can be found here

Schedule

Work in Progress