From Fedora Project Wiki

(+initial draft)
 
(Drafting – it also happened!)
 
(36 intermediate revisions by 10 users not shown)
Line 1: Line 1:
This is the main page for the Fedora CommOps [[FAD]], which focuses on reviewing and finishing our current goals, and defining the next plans to improve diversification efforts in our community.
+
This is the main page for the Fedora [[CommOps]] [[FAD]]. Our FAD focuses on measuring community health though data, making that data accessible to the wider Fedora community, and boosting community morale.
  
 
'''At a glance''':
 
'''At a glance''':
 
* ''Location'': Red Hat Czech, Purkyňova 111, 621 00 Brno, CZ.
 
* ''Location'': Red Hat Czech, Purkyňova 111, 621 00 Brno, CZ.
* ''Dates'': Jan 29-31, 2018
+
* ''Dates'': January 29-31, 2018
  
  
 +
= Purpose =
  
== Logic Model ==
+
The purpose of the [[CommOps]] FAD is to
  
[[Image:CommOps FAD 2017 Logic Model.png|center|750px]]
+
# Pursue plan of deploying a GrimoireLabs dashboard, visualizing fedmsg data
'''todo'''
+
# Launch Fedora Appreciation Day in 2018
 +
# Analyze Fedora Elections and develop year-long plan to improve community engagement in elections
 +
# Evaluate critical areas of Fedora that fedmsg integration would be helpful; create development plan for them (e.g. Fedora Magazine / Community Blog)
  
== Purpose ==
+
Fedora CommOps aims to improve "heat and light" inside of Fedora. This translates to "contributions and exposure". CommOps does this with technical work (e.g. fedmsg, data studies, etc.) and non-technical work (community engagement, Community Blog, elections, etc.). The tasks above fit into our greater purpose of bringing more exposure to various areas of Fedora and increasing contribution to key areas.
  
'''todo'''
 
  
=== Primary Goals ===
+
== Primary goals ==
  
'''todo'''
+
Primary goals are our most urgent tasks that set the minimum bar for what we want to accomplish.
  
=== Secondary Goals ===
+
=== GrimoireLabs dashboard ===
  
'''todo'''
+
fedmsg is a powerful tool, but its power is available only to those who know how to use it; a GrimoireLabs dashboard enables others to learn valuable insights from the data without writing any code.
  
=== Q&A ===
+
[https://pagure.io/fedora-commops/issue/114 fedora-commops#114] discusses this task. So far, we evaluated a few different solutions before deciding Grimoire as a best-fit for our use case. We understand already that a fedmsg plugin needs to be written. As a Python tool, it also fits in nicely with the "Fedora stack".
  
'''todo'''
+
The following list explains use cases of visualized fedmsg data in a dashboard with charts, graphs, and other visual aids:
  
== Impact ==
+
* Determine what times (days / months) people contribute the most
 +
** Planning internal Fedora team sprints when more people are contributing
 +
* Evaluate event success if new contributors enter the community after an event is completed
 +
* Understand new contributors better and where they snap off (if they do)
 +
** The Epic Journey of the New Fedora Contributor (i.e. using the visualizations to see pathways / successes / failures of new contributors entering the community for the first time)
 +
** Leveraging Fedora Hubs research to build a dashboard like this
  
'''todo'''
+
The FAD allows us the bandwidth to spend time to discover our needs, map out the development plan for the plugin, and design use cases for potential visualizations. Different parts of this task are addressed in parallel instead of in a linear way. While mapping out the technical requirements, we will discuss what visualizations we want to prepare at launch and how to introduce Fedora contributors to this tool with documentation.
  
== Detailed Work Items & Final Attendees ==
+
Our end deliverable is a year-long plan for how to develop, implement, and promote a GrimoireLabs dashboard powered by fedmsg.
  
=== Participants ===
+
=== Fedora Appreciation Week ===
  
{|class="wikitable"
+
We plan to initiate the first-ever Fedora Appreciation Week in 2018, a week where contributors and users are encouraged to say "thank you" to each other for the hard work put into Fedora.
! border="1" | Name       !! Remote? !! Fri !! Sat !! Sun !! Core Tasks
+
 
 +
The Fedora Appreciation Week is discussed in [https://pagure.io/fedora-commops/issue/110 fedora-commops#110], although the idea pre-dates the ticket. Implementing the idea is difficult because the idea is still broad. This presented an obstacle for us to organize this remotely.
 +
 
 +
The FAD enables us to brainstorm a plan to do a soft launch in 2018 and outline long-term goals that were identified by Brian at the Fedora Diversity FAD in the future. We will evaluate our options for any tooling or automation to make this event require less manpower to run (ensuring consistency for running it in the future). After deciding on implementation details, the team will decide on milestones to track progress for launching the event. This helps us establish communication goals for raising awareness of the event and keep our flow as the event comes closer.
 +
 
 +
Our end deliverable is a proposal for Fedora Appreciation Week, with clear guidelines for what the event is, how the community can participate, and how we will raise awareness in 2018 for this event.
 +
 
 +
 
 +
== Secondary goals ==
 +
 
 +
Secondary goals are other important tasks that are valuable to discuss in person, but are not "mission critical" for the success of our FAD. The depth of discussion on secondary goals depends on our progress with primary goals.
 +
 
 +
=== Improving Fedora elections ===
 +
 
 +
Fedora elections are a critical way to engage with the contributor community to shape the direction of the progress; we want to find ways to make elections more interactive and engaging both for candidates and the community.
 +
 
 +
The last election motivated this item to make it on our FAD agenda. Historically, CommOps supports the release manager in launching the elections each cycle, but the relationship was never formalized or documented. In recent releases, core team members were absent and not able to assist the release manager, but the lack of documentation on supporting tasks for the election led to skipped measures.
 +
 
 +
Our FAD provides an opportunity to…
 +
 
 +
# Document and formalize our supporting role with Fedora Elections
 +
# Improve engagement in community elections to increase participation
 +
 
 +
First, we need to document our supporting tasks in organizing Fedora Elections and create a standard operating procedure, so routine tasks aren't missed. This helps both CommOps and the release manager ensure consistency between election cycles. Second, after identifying our supporting tasks, we want to address community engagement. Are questionnaires useful? How can candidates clearly communicate their platform to the community? What does the community want to know from candidates? What would make the elections more interesting? We hope to answer these questions and create new goals for the Fedora 28 elections (and beyond) to improve engagement.
 +
 
 +
Our end deliverables are two new internal pages that document our supporting tasks for the elections and a "checklist" of things to do every election, as well as a proposal for new changes for the Fedora 28 elections in Summer 2018.
 +
 
 +
=== Adding new fedmsg integrations ===
 +
 
 +
fedmsg is found in many Fedora applications, but it's biased towards technical areas of Fedora; our goal is to identify key community-related areas that have a potential pathway for fedmsg integration and determine how to implement support.
 +
 
 +
An example of this goal is in [https://pagure.io/fedora-commops/issue/108 fedora-commops#108], about the Fedora Magazine and Fedora Community Blog. This specific example is a non-technical area of Fedora, but it has a pathway for integrating to fedmsg (via WordPress plugins).
 +
 
 +
We will identify more areas focused on non-technical areas of Fedora and evaluate if a fedmsg integration is possible before our FAD. Our primary targets is WordPress, but we plan to have more identified before the FAD. Our time together in-person will be spent exploring technical details of integrating the platforms and determining the amount of work required. After, we will outline how to implement an integration. This will include identifying subject-area experts who may be willing to assist, as well as coming up with our own development outline and plan.
 +
 
 +
Our end deliverable is a list of areas that could support a fedmsg integration and a plan (undetermined length) of how to implement them.
 +
 
 +
 
 +
== Q&A ==
 +
 
 +
# '''Is this realistic to accomplish?'''
 +
#* We separated our primary goals out from our secondary goals to make a reliable estimate of work we will accomplish in three days. The worst case scenario is that only the primary goals are met and we never cover the secondary goals. The best case scenario is we cover everything and meet all proposed end deliverables.
 +
# '''A lot of this is technical work. Is CommOps the right group to address some of these things?'''
 +
#* Yes. Writing code may be one activity of our FAD, but it is not a primary task. Our discussions focus on the strategic and far-reaching goals and visions for the technical work. We hope to spend time together mapping out a path forward and communicating clearly with other Fedora developers to mutually support our efforts.
 +
# '''Why so soon?'''
 +
#* The dates are soon, but we chose them to maximize the convenience of the DevConf / FOSDEM week. Many Fedora contributors travel to DevConf and/or FOSDEM, and this allows us to gather people who may not easily attend our FAD. Even if costs are more expensive to book now than a month or two ago, we believe the costs are still less for us to organize during this time because of travel costs we don't have to pay.
 +
 
 +
 
 +
= Impact =
 +
 
 +
Each goal explained above has its own unique impact to the Fedora community.
 +
 
 +
# '''GrimoireLabs dashboard'''
 +
#* ''fedmsg for the masses'': Make fedmsg data more accessible to everyone in Fedora, even without programming knowledge
 +
#* ''Avoiding pitfalls'': Fedora community members can use data to measure impact with their own efforts and understand the health of their own project
 +
# '''Fedora Appreciation Week'''
 +
#* ''Good morale all around'': Emphasize '''Friends''' part of Four Foundations and increase positive interactions in community
 +
#* ''Set an example'': Set an example and the tone for how we treat each other in Fedora community, both for our contributors, potential contributors, and members of other open source projects
 +
# '''Improving Fedora elections'''
 +
#* ''Restore confidence'': Instill confidence in community of the election process (in turn, instills confidence in the community leadership bodies)
 +
#* ''Increase engagement'': More candidates participating in elections, better understand of candidate platforms, more voters in elections
 +
# '''Adding new fedmsg integrations'''
 +
#* ''A whole new world'': Potential to understand non-technical areas of the project in a way we have not accurately measured before
 +
 
 +
 
 +
= Participants =
 +
 
 +
{|class="wikitable" border="1"
 +
! Name !! Confirmed? !! Remote? !! Mon !! Tue !! Wed
 +
|-
 +
| [[User:Bee2502|Bee Padalkar]] || {{check}} || || X || X ||
 
|-
 
|-
| [[User:Jflory7|Justin W. Flory]] || No  ||   X || X || X || '''todo'''
+
| [[User:Bex|Brian Exelbierd]] || {{Check}} ||  || X || X || X
 
|-
 
|-
| [[User:Rhea|Radka Janeková]] || No || || X || X || Event on-site logistics
+
| [[User:wesleyotugo|Dennis Otugo]] || {{check}} || {{check}} || X || ||  
 
|-
 
|-
| [[User:bex|Brian Exelbierd]] || No || X || X || X || FCAIC, assistance '''todo'''
+
| [[User:Dhanesh95|Dhanesh Sabane]] || {{check}}  || {{check}} || X || X || X
 +
|-
 +
| [[User:X3mboy|Eduard Lucena]] || {{check}} || {{check}} || X || X || X
 +
|-
 +
| [[User:Jflory7|Justin W. Flory]] || {{check}}  ||  || X || X || X
 +
|-
 +
| [[User:Rhea|Radka Janeková]] || {{check}}  ||  || X || X || X
 +
|-
 +
| [[User:Skamath|Sachin Kamath]] || {{check}}  ||  || X || X || X
 +
|-
 +
| [[User:Jonatoni|Jona Azizaj]] || {{check}} || || X || X || X
 +
|-
 +
| [[User:Rathann|Dominik Mierzejewski]] || {{check}} || {{check}} || X || X || X
 +
|-
 +
| [[User:bt0dotninja|Alberto Rodríguez Sánchez]] || {{check}} || {{check}} || X || X || X
 
|-
 
|-
 
|}
 
|}
  
== Planning Prerequisites ==
+
= Planning prerequisites =
  
'''todo'''
+
* <strike>Review proposal as team at Monday, Dec. 11 meeting</strike>
 +
* <strike>Calculate final budget</strike>
 +
* <strike>Submit proposal to Fedora Council before Wednesday, Dec. 13 meeting</strike>
 +
* <strike>Complete supporting research leading up to FAD</strike>
 +
* <strike>Gather on Jan. 29!</strike>
  
== Plan ==
+
= Logistics =
  
=== Proposal 1: DevConf ===
+
== Proposal: Post-DevConf ==
  
'''todo'''
+
We propose our FAD dates immediately after [https://devconf.cz/ DevConf] in Brno, Czech Republic.
  
# '''Location:'''  Brno University of Technology Faculty of Information Technology. - Brno - Czech Republic
+
# '''Location:'''  Red Hat Czech, Purkyňova 111, 621 00 Brno, Czech Republic (TPB-B Argentum meeting room)
# '''Date:''' 29 – 31 January 2018
+
# '''Date:''' 2018 January 29 – 31
 
# '''Schedule'''
 
# '''Schedule'''
#* Participants arrive at Jan 26 (a day before devconf)
+
#* Participants arrive on Jan. 28 (or Jan. 25 to participate during DevConf as well – accommodation during DevConf not covered)
#* Participants leave at Feb 01
+
#* Participants leave on Feb. 01
# 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?)
 
  
  
 
== Budget ==
 
== Budget ==
  
'''todo'''
+
{|class="wikitable" border="1"
 +
! Contributor !! Travel Plan !! Estimated Travel Cost !! Accommodation
 +
|-
 +
| [[User:Bee2502|Bee Padalkar]] ||MUC <=> VIE <=> BRQ || ~$130 (''air'') + ~$23 (''bus'') = $153.00 || $184
 +
|-
 +
| [[User:Bex|Brian Exelbierd]] || (''local'') || N/A || (''local'')
 +
|-
 +
| [[User:Jflory7|Justin W. Flory]] || ROC => VIE => BRQ : BRU => ROC || ~$405 + ~$23 (''bus'') + ~$450 = $878.00 || $123 ($246 /2 shared room)
 +
|-
 +
| [[User:Rhea|Radka Janeková]] || (''local'') || N/A || (''local'')
 +
|-
 +
| [[User:Skamath|Sachin Kamath]] || COK => VIE => BRQ : BRU => COK || ~$550 + $23 (''bus'') + ~$520  ~= $1100 || $123 ($246 /2 shared room)
 +
|-
 +
|}
  
=== Proposal 1: DevConf ===
 
  
==== Lunch & Dinner  ====
+
# '''Travel:''' $2131.00 USD
 +
# '''Accommodation''': $429 USD (Not the final value - will be less.)
 +
#* [http://www.a-sporthotel.cz/ A Sport Hotel]
 +
# '''Location''': $0
 +
#* Red Hat Office Brno (TPB-B Argentum meeting room)
 +
# '''Meals''': $460 USD = $72 per attendee + $100 for one social dinner (breakdown below)
 +
# '''Supplies''': $0 for anything else you may need
  
'''todo'''
+
'''Total budget: $3020.00 USD
  
The first proposal is to organize it after [https://devconf.cz/ DevConf] in Brno, Czech Republic.
 
  
* '''Snacks/Beverages''':
+
=== Food ===
** $30 USD
+
 
 
* '''Lunch''':
 
* '''Lunch''':
** $120 USD
+
** $9 USD /ea
*** Appx. $30 USD per person for four people
 
 
* '''Dinner''':
 
* '''Dinner''':
** $150 USD
+
** $15 USD /ea
 +
* '''Total per person''':
 +
** $9 + $15 x 3 days = $72 USD
 +
 
 +
'''''Total food cost''''': '''$460 USD'''
 +
 
 +
= Schedule =
 +
 
 +
* All times in local time (CET / UTC+1)
 +
* '''TPB-B''' = TPB-B is the "older" Red Hat Building at the Technolgicky Park tram stop in Brno
 +
 
 +
== Monday, Jan. 29 ==
  
'''''TOTAL''''': $300 USD
+
Arrival day.
  
==== Travel & Accomodation ====
+
* '''09:10''': (''A Sport Hotel'') Departure, 15-20m walk to TPB-B
 +
* '''09:30''': Arrival at TPB-B, Argentum Meeting Room (''need RH badge for entry'')
 +
* '''10:00''': High-level refresh: goals for FAD, schedule
 +
* '''10:10''': Ticket triage; year-long goals for CommOps in 2018
 +
** Take time together to triage tickets; what's still backburner, what can be closed?
 +
* '''12:30''': Lunch
 +
* '''14:00''': [https://pagure.io/fedora-commops/issue/110 fedora-commops#110]: Fedora Appreciation Week
 +
** ''See ticket for details''
 +
** bex joins
 +
* '''17:00''': Quick retrospective, re-confirm next day schedule
 +
* '''17:30''': Depart from TPB-B
  
'''todo'''
+
== Tuesday, Jan. 30 ==
  
The first proposal is to organize it after [https://devconf.cz/ DevConf] in Brno, Czech Republic.
+
* '''09:10''': (''A Sport Hotel'') Departure, 15-20m walk to TPB-B
 +
* '''09:30''': Arrival at TPB-B, Argentum Meeting Room (''need RH badge for entry'')
 +
* '''10:00''': High-level refresh: goals for FAD, schedule
 +
* '''10:10''': GrimoireLabs implementation
 +
* '''12:30''': Lunch
 +
* '''14:00''': GrimoireLabs implementation
 +
* '''17:00''': Quick retrospective, re-confirm next day schedule
 +
* '''17:30''': Depart from TPB-B
  
{|class="wikitable"
+
== Wednesday, Jan. 31 ==
! # !! Contributor !! Travel Plan !! Estimated Travel Cost !! Accommodation
 
|-
 
| 1 || [[User:Jflory7|Justin]] || '''todo''' DBV<=>VIE<=>Brno || '''todo''' USD || sharing
 
|-
 
|}
 
  
 +
* '''09:10''': (''A Sport Hotel'') Departure, 15-20m walk to TPB-B
 +
* '''09:30''': Arrival at TPB-B, Argentum Meeting Room (''need RH badge for entry'')
 +
* '''10:00''': High-level refresh: goals for FAD, schedule
 +
* '''10:10''': Fedora elections discussion
 +
* '''12:30''': Lunch
 +
* '''14:00''': Fedora elections discussion
 +
* '''16:00''': fedmsg plugins
 +
* '''17:00''': FAD retrospective, GrimoireCon plans
 +
* '''18:00''': Depart from TPB-B
  
# '''Travel:''' $1792 USD for airfare, bus, train, etc. funding needed to get attendees to the FAD
+
== Thursday, Feb. 1 ==
# '''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
+
Departure day.
  
NOTE - Travel ticket cost is subject to change with the delay in time to book.
+
* '''12:38''': (''GrimoireCon'') Train to Prague
  
== Related Pagure Ticket ==
+
= Appendix =
  
'''todo'''
+
== Logic model ==
  
More information about the FAD can be found [https://pagure.io/fedora-diversity/issue/8 here]
+
[[Image:CommOps FAD 2018 Logic Model.png|center|750px]]
  
== Schedule ==
+
= External links =
  
'''todo'''
+
* [https://pagure.io/fedora-commops/issue/125 CommOps FAD tracking ticket]
 +
* [https://pagure.io/fedora-commops/issue/108 fedora-commops#108]
 +
* [https://pagure.io/fedora-commops/issue/110 fedora-commops#110]: Fedora Appreciation Week
 +
* [https://pagure.io/fedora-commops/issue/114 fedora-commops#114]
  
 
----
 
----
 
[[Category:CommOps]]
 
[[Category:CommOps]]
 
[[Category:FAD]]
 
[[Category:FAD]]

Latest revision as of 11:39, 28 January 2018

This is the main page for the Fedora CommOps FAD. Our FAD focuses on measuring community health though data, making that data accessible to the wider Fedora community, and boosting community morale.

At a glance:

  • Location: Red Hat Czech, Purkyňova 111, 621 00 Brno, CZ.
  • Dates: January 29-31, 2018


Purpose

The purpose of the CommOps FAD is to

  1. Pursue plan of deploying a GrimoireLabs dashboard, visualizing fedmsg data
  2. Launch Fedora Appreciation Day in 2018
  3. Analyze Fedora Elections and develop year-long plan to improve community engagement in elections
  4. Evaluate critical areas of Fedora that fedmsg integration would be helpful; create development plan for them (e.g. Fedora Magazine / Community Blog)

Fedora CommOps aims to improve "heat and light" inside of Fedora. This translates to "contributions and exposure". CommOps does this with technical work (e.g. fedmsg, data studies, etc.) and non-technical work (community engagement, Community Blog, elections, etc.). The tasks above fit into our greater purpose of bringing more exposure to various areas of Fedora and increasing contribution to key areas.


Primary goals

Primary goals are our most urgent tasks that set the minimum bar for what we want to accomplish.

GrimoireLabs dashboard

fedmsg is a powerful tool, but its power is available only to those who know how to use it; a GrimoireLabs dashboard enables others to learn valuable insights from the data without writing any code.

fedora-commops#114 discusses this task. So far, we evaluated a few different solutions before deciding Grimoire as a best-fit for our use case. We understand already that a fedmsg plugin needs to be written. As a Python tool, it also fits in nicely with the "Fedora stack".

The following list explains use cases of visualized fedmsg data in a dashboard with charts, graphs, and other visual aids:

  • Determine what times (days / months) people contribute the most
    • Planning internal Fedora team sprints when more people are contributing
  • Evaluate event success if new contributors enter the community after an event is completed
  • Understand new contributors better and where they snap off (if they do)
    • The Epic Journey of the New Fedora Contributor (i.e. using the visualizations to see pathways / successes / failures of new contributors entering the community for the first time)
    • Leveraging Fedora Hubs research to build a dashboard like this

The FAD allows us the bandwidth to spend time to discover our needs, map out the development plan for the plugin, and design use cases for potential visualizations. Different parts of this task are addressed in parallel instead of in a linear way. While mapping out the technical requirements, we will discuss what visualizations we want to prepare at launch and how to introduce Fedora contributors to this tool with documentation.

Our end deliverable is a year-long plan for how to develop, implement, and promote a GrimoireLabs dashboard powered by fedmsg.

Fedora Appreciation Week

We plan to initiate the first-ever Fedora Appreciation Week in 2018, a week where contributors and users are encouraged to say "thank you" to each other for the hard work put into Fedora.

The Fedora Appreciation Week is discussed in fedora-commops#110, although the idea pre-dates the ticket. Implementing the idea is difficult because the idea is still broad. This presented an obstacle for us to organize this remotely.

The FAD enables us to brainstorm a plan to do a soft launch in 2018 and outline long-term goals that were identified by Brian at the Fedora Diversity FAD in the future. We will evaluate our options for any tooling or automation to make this event require less manpower to run (ensuring consistency for running it in the future). After deciding on implementation details, the team will decide on milestones to track progress for launching the event. This helps us establish communication goals for raising awareness of the event and keep our flow as the event comes closer.

Our end deliverable is a proposal for Fedora Appreciation Week, with clear guidelines for what the event is, how the community can participate, and how we will raise awareness in 2018 for this event.


Secondary goals

Secondary goals are other important tasks that are valuable to discuss in person, but are not "mission critical" for the success of our FAD. The depth of discussion on secondary goals depends on our progress with primary goals.

Improving Fedora elections

Fedora elections are a critical way to engage with the contributor community to shape the direction of the progress; we want to find ways to make elections more interactive and engaging both for candidates and the community.

The last election motivated this item to make it on our FAD agenda. Historically, CommOps supports the release manager in launching the elections each cycle, but the relationship was never formalized or documented. In recent releases, core team members were absent and not able to assist the release manager, but the lack of documentation on supporting tasks for the election led to skipped measures.

Our FAD provides an opportunity to…

  1. Document and formalize our supporting role with Fedora Elections
  2. Improve engagement in community elections to increase participation

First, we need to document our supporting tasks in organizing Fedora Elections and create a standard operating procedure, so routine tasks aren't missed. This helps both CommOps and the release manager ensure consistency between election cycles. Second, after identifying our supporting tasks, we want to address community engagement. Are questionnaires useful? How can candidates clearly communicate their platform to the community? What does the community want to know from candidates? What would make the elections more interesting? We hope to answer these questions and create new goals for the Fedora 28 elections (and beyond) to improve engagement.

Our end deliverables are two new internal pages that document our supporting tasks for the elections and a "checklist" of things to do every election, as well as a proposal for new changes for the Fedora 28 elections in Summer 2018.

Adding new fedmsg integrations

fedmsg is found in many Fedora applications, but it's biased towards technical areas of Fedora; our goal is to identify key community-related areas that have a potential pathway for fedmsg integration and determine how to implement support.

An example of this goal is in fedora-commops#108, about the Fedora Magazine and Fedora Community Blog. This specific example is a non-technical area of Fedora, but it has a pathway for integrating to fedmsg (via WordPress plugins).

We will identify more areas focused on non-technical areas of Fedora and evaluate if a fedmsg integration is possible before our FAD. Our primary targets is WordPress, but we plan to have more identified before the FAD. Our time together in-person will be spent exploring technical details of integrating the platforms and determining the amount of work required. After, we will outline how to implement an integration. This will include identifying subject-area experts who may be willing to assist, as well as coming up with our own development outline and plan.

Our end deliverable is a list of areas that could support a fedmsg integration and a plan (undetermined length) of how to implement them.


Q&A

  1. Is this realistic to accomplish?
    • We separated our primary goals out from our secondary goals to make a reliable estimate of work we will accomplish in three days. The worst case scenario is that only the primary goals are met and we never cover the secondary goals. The best case scenario is we cover everything and meet all proposed end deliverables.
  2. A lot of this is technical work. Is CommOps the right group to address some of these things?
    • Yes. Writing code may be one activity of our FAD, but it is not a primary task. Our discussions focus on the strategic and far-reaching goals and visions for the technical work. We hope to spend time together mapping out a path forward and communicating clearly with other Fedora developers to mutually support our efforts.
  3. Why so soon?
    • The dates are soon, but we chose them to maximize the convenience of the DevConf / FOSDEM week. Many Fedora contributors travel to DevConf and/or FOSDEM, and this allows us to gather people who may not easily attend our FAD. Even if costs are more expensive to book now than a month or two ago, we believe the costs are still less for us to organize during this time because of travel costs we don't have to pay.


Impact

Each goal explained above has its own unique impact to the Fedora community.

  1. GrimoireLabs dashboard
    • fedmsg for the masses: Make fedmsg data more accessible to everyone in Fedora, even without programming knowledge
    • Avoiding pitfalls: Fedora community members can use data to measure impact with their own efforts and understand the health of their own project
  2. Fedora Appreciation Week
    • Good morale all around: Emphasize Friends part of Four Foundations and increase positive interactions in community
    • Set an example: Set an example and the tone for how we treat each other in Fedora community, both for our contributors, potential contributors, and members of other open source projects
  3. Improving Fedora elections
    • Restore confidence: Instill confidence in community of the election process (in turn, instills confidence in the community leadership bodies)
    • Increase engagement: More candidates participating in elections, better understand of candidate platforms, more voters in elections
  4. Adding new fedmsg integrations
    • A whole new world: Potential to understand non-technical areas of the project in a way we have not accurately measured before


Participants

Name Confirmed? Remote? Mon Tue Wed
Bee Padalkar Checkmark.png X X
Brian Exelbierd Checkmark.png X X X
Dennis Otugo Checkmark.png Checkmark.png X
Dhanesh Sabane Checkmark.png Checkmark.png X X X
Eduard Lucena Checkmark.png Checkmark.png X X X
Justin W. Flory Checkmark.png X X X
Radka Janeková Checkmark.png X X X
Sachin Kamath Checkmark.png X X X
Jona Azizaj Checkmark.png X X X
Dominik Mierzejewski Checkmark.png Checkmark.png X X X
Alberto Rodríguez Sánchez Checkmark.png Checkmark.png X X X

Planning prerequisites

  • Review proposal as team at Monday, Dec. 11 meeting
  • Calculate final budget
  • Submit proposal to Fedora Council before Wednesday, Dec. 13 meeting
  • Complete supporting research leading up to FAD
  • Gather on Jan. 29!

Logistics

Proposal: Post-DevConf

We propose our FAD dates immediately after DevConf in Brno, Czech Republic.

  1. Location: Red Hat Czech, Purkyňova 111, 621 00 Brno, Czech Republic (TPB-B Argentum meeting room)
  2. Date: 2018 January 29 – 31
  3. Schedule
    • Participants arrive on Jan. 28 (or Jan. 25 to participate during DevConf as well – accommodation during DevConf not covered)
    • Participants leave on Feb. 01


Budget

Contributor Travel Plan Estimated Travel Cost Accommodation
Bee Padalkar MUC <=> VIE <=> BRQ ~$130 (air) + ~$23 (bus) = $153.00 $184
Brian Exelbierd (local) N/A (local)
Justin W. Flory ROC => VIE => BRQ : BRU => ROC ~$405 + ~$23 (bus) + ~$450 = $878.00 $123 ($246 /2 shared room)
Radka Janeková (local) N/A (local)
Sachin Kamath COK => VIE => BRQ : BRU => COK ~$550 + $23 (bus) + ~$520 ~= $1100 $123 ($246 /2 shared room)


  1. Travel: $2131.00 USD
  2. Accommodation: $429 USD (Not the final value - will be less.)
  3. Location: $0
    • Red Hat Office Brno (TPB-B Argentum meeting room)
  4. Meals: $460 USD = $72 per attendee + $100 for one social dinner (breakdown below)
  5. Supplies: $0 for anything else you may need

Total budget: $3020.00 USD


Food

  • Lunch:
    • $9 USD /ea
  • Dinner:
    • $15 USD /ea
  • Total per person:
    • $9 + $15 x 3 days = $72 USD

Total food cost: $460 USD

Schedule

  • All times in local time (CET / UTC+1)
  • TPB-B = TPB-B is the "older" Red Hat Building at the Technolgicky Park tram stop in Brno

Monday, Jan. 29

Arrival day.

  • 09:10: (A Sport Hotel) Departure, 15-20m walk to TPB-B
  • 09:30: Arrival at TPB-B, Argentum Meeting Room (need RH badge for entry)
  • 10:00: High-level refresh: goals for FAD, schedule
  • 10:10: Ticket triage; year-long goals for CommOps in 2018
    • Take time together to triage tickets; what's still backburner, what can be closed?
  • 12:30: Lunch
  • 14:00: fedora-commops#110: Fedora Appreciation Week
    • See ticket for details
    • bex joins
  • 17:00: Quick retrospective, re-confirm next day schedule
  • 17:30: Depart from TPB-B

Tuesday, Jan. 30

  • 09:10: (A Sport Hotel) Departure, 15-20m walk to TPB-B
  • 09:30: Arrival at TPB-B, Argentum Meeting Room (need RH badge for entry)
  • 10:00: High-level refresh: goals for FAD, schedule
  • 10:10: GrimoireLabs implementation
  • 12:30: Lunch
  • 14:00: GrimoireLabs implementation
  • 17:00: Quick retrospective, re-confirm next day schedule
  • 17:30: Depart from TPB-B

Wednesday, Jan. 31

  • 09:10: (A Sport Hotel) Departure, 15-20m walk to TPB-B
  • 09:30: Arrival at TPB-B, Argentum Meeting Room (need RH badge for entry)
  • 10:00: High-level refresh: goals for FAD, schedule
  • 10:10: Fedora elections discussion
  • 12:30: Lunch
  • 14:00: Fedora elections discussion
  • 16:00: fedmsg plugins
  • 17:00: FAD retrospective, GrimoireCon plans
  • 18:00: Depart from TPB-B

Thursday, Feb. 1

Departure day.

  • 12:38: (GrimoireCon) Train to Prague

Appendix

Logic model

CommOps FAD 2018 Logic Model.png

External links