CFP is closing right now and Patrick is re-opening as we speak as per the plan we'd agreed on.
Given the number of proposals we have, I am not sure we want to do a full 2-week extension. Previous Flock orgs, what do you think about the numbers we have right now? If we decide to keep the extension, I wonder if we close at the 1 week point (22) or the 2 week point (29). Any thoughts? (My cut says close at 22.) Once we know when to close I'll update the website (I have commits ready to push) and do a blog post so people know about the extension.
Registration
==========
Registration remains open.
Registrations: 96
(Should we be concerned about this? This seems low to me?)
Session Proposals
===============
Session proposals: 117 (119 with 2 duplicates)
All numbers below include the 2 duplicates (sorry, too difficult to pull out right now. I'm doing this all manually)
Breakdown of proposal numbers:
--------------------------------------------
Do-Session (3 hrs): 17
Do-Session (2 hrs): 27
Talk (30 min): 50
Talk (60 min): 25
Total proposals: 119
Total minutes: 9300 (155 hours)
Total do minutes: 6300 (105 hours)
Total talk minutes: 3000 (50 hours)
if we accepted all current proposals, it'd require 7 tracks. (note proposals may be redundant and haven't yet been reviewed.)
% of proposals that are do: 37%
% of proposals that are talk: 63%
% of minutes of proposed do: 68%
% of minutes of proposed talk: 32%
Proposal topics:
=============
I did some manual card sorting by hand of all of the proposals and came up with some rough clusters / categories. We don't have to go with these, but they're a way to understand what topics people submitted. Definitions for all topics follow the counts.
Technical Infrastructure and Automation: 26 (could probably be broken up)
What we ship: 19
Disciplines: 18
Community Infrastructure: 14
Modularity: 12
Cloud and Containers: 7
Ecosystem: 2
Technical Infrastructure and Automation (26)
-----------------------------------------------------------
Sessions that involve strategy around the infrastructure that supports and produces Fedora as we move towards CI/CD and automation as well as sessions about specific components and technologies that are part of this infrastructure. There's talks about packaging in here too, not 100% sure they belong.
What we ship (19)
------------------------
Sessions that involve the specific production of the artifacts we ship and the teams/SIGs that produce them, including Fedora Editions (workstation, server, atomic), spins, arches, EPEL.
Disciplines (18)
---------------------
These sessions involve talking about the practice of specific disciplines and the status of specific discipline-centered teams within Fedora that include: design, marketing, legal, globalization / internationalization, websites
Community infrastructure (14)
----------------------------------------
Sessions about community management, outreach, ambassadors, diversity, commops: anything focused on managing community membership at human level in some form.
Modularity (12)
--------------------
Sessions that center on the modularity effort. There are others that mention modularity but these ones focus on it.
Cloud and Containers (7)
---------------------------------
Sessions about working with cloud platforms, building containers, container tech, etc.
Ecosystem (2)
-------------------
Sessions that involve the ecosystem around Fedora. There's only two, one about Fedora being included in the Microsoft / Windows ecosystem and one about a hardware vendor.
Cheers,
~m