Changes/Two Week Atomic/RACI

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 17, 2015.

Definitions

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

Responsible

The person responsible for the performance of the task. There should be exactly one person with this assignment for each task.

Assists

Those who assist completion of the task.

Consulted

Those whose opinions are sought; and with whom there is two-way communication.

Informed

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						0%
	script run from cron nightly					?
	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						0%
	listener for successful builds					0%
	automatic test execution					0%
	basic smoketests functional (deeper testing desired, but out of scope here)					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%
Create automatic release system						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					0%
	fallback mechanism for no builds in two weeks					0%
Create new website						0%
	decide on location (stand alone, still part of getfedora.org, or labs.fpo)					0%
	site design					0%
	new copy (introduction, documentation, disclaimers)					0%
	new artwork					0%
	site implementation					0%
	changes to getfedora.org as/if appropriate (crosslinks, etc.)					0%
Trademark approval		mattdm	—	Council	Other change owners	0%
	for use of Fedora Atomic Host	mattdm	—	Council	Other change owners	0%
	possibly for new artwork	mattdm	—	Design, Council	Other change owners, Websites	0%
Overall communication and coordination		mattdm	jzb	Cloud SIG, upstream Project Atomic, Release Engineering, Websites, Design	FESCo	10%

Glossary of Nicknames

• ausil Dennis Gilmore
• jzb Joe Brockmeier
• kushal Kushal Das
• mattdm Matthew Miller
• maxamillion Adam Miller
• walters Colin Walters

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.