Logic Model
image/svg+xml
Logic Model
Template by Matthew Miller
CC-BY-SA 3.0 or newer
Inputs
people, time, hardware, money
Activities
the work we do
Outputs
tangible results of that work
Outcomes
measurable changes in Fedora
Impact
the high-level goals
Mission
Vision
Everything in a column to the right should have support from one or more items to the left. Everything in a column to the left should connect to a higher-level concept on the right.
To the left of the double line: things we actually can work on and do. Over here on the right, changes we expect to happen as the result of our effort.
Planning goes from right to leftEffort goes from left to right
Logic Model for
Update pungiUpdate bodhiUpdate mirrormanagerPlan for EPEL / EPICUpdate rel-eng scriptsUpdate fedora-reposAdd defaults to fedora-releaseModular DNF • Initial modularity enablement • Performance enhancementsStream expansion feature workModule repo auto-creationmodule.md auto-generationRemove module review roadblockTag default streams into baseCreate lifecycle tooling • for packagers • for usersWrite SO MANY docsGuidelines updates as neededOngoing MBS workModule-to-FLIBSModule-to-FlatpakFreshmaker for the aboveHackfests and FADs: • At devconf.cz & devconf.us • Stand-alone • at other eventsBlog posts Modularity Objective: The Release
Build a repository for Fedora containing a wide selection of software easily maintained by packagers. Popular versions of software desired by users are available on Fedora and EL bases Packagers spend less time on maintenance while delivering the same or more content. Fedora packages have a packager-defined lifecycle. Modular Repo• Release / Updates• EPEL (EPIC?)• Mirroring• .repo file Packager Tools• module creation• lifecycle management• documentation Build Infrastructure:• stream branching• stream expansion• MBS enhancements• local builds• Koji tagging• more documentation If it should be pretty obvious how these support the mission and vision; if not, time to rethink!
• Fedora users can choose longer-lifecycle or always-latest versions and stick with those across multiple base OS releases• Fedora is more useful, especially in the emerging cloud / containers world, resulting in more Fedora users• Enterprise Linux users get access to a broader array of Fedora software with the same advantages as above — Fedora packager effort has more impact• Developers turn to Fedora applications and stacks as a convenient starting place, no matter their base distro or OS• Packagers can offer more versions of software with less overall work
Fedora packages have a packager-defined lifecycle. Fedora packagers aren't put off by building for EL and EL packagers build for Fedora. Application-Stack Images• Docker / OCI• Flatpak
Training Automated Testing Teams: • Rel-Eng • Factory • Infrastructure • Bodhi • Modularity WG • DNF • fedpkg • Container Images Team • Flatpak developers • Fedora packagers • Docs teamHardware: possible need for new builders and new storage as this takes offTravel: Funding for FADs and other outreach =-5