From Fedora Project Wiki

Responsibility Matrix for the Two Week Atomic Fedora Change

This is a RACI matrix for tasks required to implement Two Week Atomic. We'll also use it for basic progress tracking, because one wiki table is less evil than two.

Is this current?

It is, as of June 18, 2015.


Here, we're using what Wikipedia calls "RACI (alternative scheme)":

The person responsible for the performance of the task. There should be exactly one person with this assignment for each task.
Those who assist completion of the task.
Those whose opinions are sought; and with whom there is two-way communication.
Those who are kept up-to-date on progress; and with whom there is one-way communication.

Task Table

This an early cut. Please feel free to add new tasks as appropriate — just let one of the coordinators know.
Task Subtask Responsible Assists Consulted Informed Current Status
Update koji for nightly image builds ausil maxamillion mattdm, jkurik 0%
script run from cron nightly mattdm ?
update script for installer iso " 0%
better implementation with pungi4 (non-blocker) " 0%
only build if contents change (non-blocker) " 0%
Create automated test system kushal QA, mattdm, jkurik 0%
listener for successful builds mattdm 0%
automatic test execution " 0%
basic smoketests functional (deeper testing desired, but out of scope here) mattdm, QA 0%
results to fedmsg " 0%
results dashboard " 0%
auto-file ticket or bug if test fails or no image found (update existing ticket if not first failure) " 0%
mechanism to mark a build as bad even if automatic tests pass " 0%
mechanism to mark a build as bad even if automatic tests pass " 0%
migrate to taskotron instead of tunir, when tasktron is ready (non-blocker) " 0%
Create automatic release system maxamillion mattdm, jkurik 0%
every two weeks, scan for images which pass all tests " 0%
integration with fedimg " 0%
upload to alt.fpo (or main mirrors?) " 0%
automatically update website " 0%
email announcement jzb " 0%
fallback mechanism for no builds in two weeks " 0%
Create new website jzb mattdm, jkurik 0%
decide on location (stand alone, still part of, or labs.fpo) jzb 0%
site design jzb 0%
new copy (introduction, documentation, disclaimers) jzb 0%
new artwork jzb 0%
site implementation jzb 0%
changes to as/if appropriate (crosslinks, etc.) jzb 0%
Trademark approval mattdm Council, jzb Other change owners, jkurik 75%
for use of Fedora Atomic Host mattdm Council Other change owners 75%
possibly for new artwork (optional) mattdm Design, Council Other change owners, Websites 0%
Overall communication and coordination mattdm jzb Cloud SIG, upstream Project Atomic, Release Engineering, Websites, Design FESCo, jkurik 10%

Glossary of Nicknames

Various Task Notes

  • If we get to the point of only building images when there are changes to the content set, that process still needs to notify the testing process that no build was generated on purpose rather than due to failure, and that then trickles down to the automatic release process in the (unlikely, but theoretical) possibility that nothing changes in the content set for two whole weeks.